Firmware Release v1.20.1

[serafimsaudade]

Hi again,
I'm trying to connect gpy to wireless, but when I do wlan.scan() get this error:

wlan = WLAN(mode=WLAN.STA_AP,ssid="teste", auth=(WLAN.WPA2, 'pass'))
nets = wlan.scan()
OSError: Scan operation Failed!

This work on others fw version.

[robert-hh]

@serafimsaudade The following sequence works for me:

from network import WLAN
wlan = WLAN(WLAN.STA_AP)
wlan.scan()

[serafimsaudade]

@robert-hh but I need to set a custom ssid and password.

[robert-hh]

@robert-hh This sequence works too, after setting the password to a length of 8 min.:

from network import WLAN
wlan=WLAN(mode=WLAN.STA_AP, ssid="teste", auth=(WLAN.WPA2, 'passpass'))
wlan.scan()

Pycom MicroPython 1.20.1.r1 [d4b4717] on 2019-10-09; LoPy4 with ESP32
Type "help()" for more information.

I do not expect that the GPY is different with respect to WiFi.

[serafimsaudade]

@robert-hh

from network import WLAN
import time
wlan=WLAN(mode=WLAN.STA_AP, ssid="teste", auth=(WLAN.WPA2, 'passpass'))
time.sleep(3)
wlan.scan()

If I put a delay >= 3 seconds, works as espected, strange.

[crumble]

Running 1.20.1r1 I am impressed of the boot performance.

But in combination with a pytrack there are a lot of i2c errors. I am not amused to figure out new timings which may result in less errors, but will never remove them all.

Additionally I run now into i2c that can only be resolved by cutting the power suply. Would be great, if the PIC has a watchpig function. So I can track down with less efford, if this is caused by the LoPy or the Pytrack.

[andreas]

Hi there,

@berni said in Firmware Release v1.20.1:

I have disabled the pybytes in the pybytes_config.json file by adding {"pybytes_autostart": false} and that fixed the issue.

We are able to confirm the new firmware obtained from [0] and bundled and flashed to a FiPy device through the process outlined on [1] works flawlessly. Before adding the pybytes_config.json file, we also experienced Guru Meditation errors like outlined above (bad00bad bad00bad bad00bad). We didn't even use LoRa, just WiFi.

@crumble said in Firmware Release v1.20.1:

Running 1.20.1r1 I am impressed of the boot performance.

We are running the Terkin Datalogger [2] and are also very happy about the performance improvements through the efficiency gains of the new mpy file format shipped with MicroPython 1.11 [3] when loading the py/mpy files into memory. On MicroPython 1.9.4, this took about 30(!) seconds and now we are down to 5 seconds [4].

Thanks to all people involved in this release, turtles all the way down to the MicroPython core maintainers - you know who you are!

With kind regards,
Andreas.

[0] https://github.com/pycom/pycom-micropython-sigfox/releases/tag/v1.20.1.r1
[1] https://forum.pycom.io/topic/4518/firmware-update-elf-vs-tar/13
[2] https://github.com/hiveeyes/hiveeyes-micropython-firmware
[3] https://github.com/micropython/micropython/releases/tag/v1.11
[4] https://community.hiveeyes.org/t/micropython-module-freezing/2445/10

[t0000899]

Wlan connection has turned to really unreliable in 1.20 version. In 1.18 connection was instant and never disconnected but in the 1.20 version wlan.connect(...) timeout most of the time and if connection is made it disconnects randomly.
If connection get broken wlan.ifconfig() show (0.0.0.0,0.0.0.0,0.0.0.0,0.0.0.0).

Pycom MicroPython 1.20.1.r1 [v1.11-3138a13] on 2019-10-08; LoPy4 with ESP32
Pybytes Version: 1.1.3
Smart config auto-start is disabled.

Sometimes during FTP transfer there is an unhandled exception and flash memory is formatted:

Memory dump at 0x4020234c: bad00bad bad00bad bad00bad
Guru Meditation Error: Core  0 panic'ed (IllegalInstruction). Exception was unhandled.

From my boot.py file:

if useWlan == True:
	print('Configure WLAN')
	
	from network import WLAN
	wlan = WLAN(mode=WLAN.STA, power_save=True)
	wlan.ifconfig(config='dhcp')
	wlan.connect(AP_name, auth=(WLAN.WPA2, AP_password), timeout=30000)

	del AP_name
	del AP_password

[rcolistete]

@rcolistete said in Firmware Release v1.20.1:

Please update the links for all Pycom devices in :
https://docs.pycom.io/advance/downgrade/
to include the version 1.20.1 for manual firmware download.

Repeating my request.

[benc]

Hi, the release notes mention that uasyncio is included in this release, but I can't find it when I run help('modules').
Any tips of how to import it?
Thanks

[robert-hh]

@benc You have to go to this lib https://github.com/micropython/micropython-lib and get: uasyncio/uasyncio/init.py and uasyncio.core/uasyncio/core.py. Copy it to the board, best under lib/uasyncio. Then you should have the files:

lib/uasyncio/init.py
lib/uasyncio/core.py

You may also copy the files upip.py and upip_utarfile.py from https://github.com/micropython/micropython/tree/master/tools. If you install these on your board (e.g. to lib), you can use that via REPL to install modules from https://micropython.org/pi or https://pypi.org/pypi with the commands:

import upip
upip.install("micropython-uasyncio", "lib")

The status of micropython-lib is somewhat unclear. Not all modules from that lib work with any micropython board. But it is always a good source of inspiration.

[crumble]

I found a workaround for my actual I2C problem.

When I2C Error on init the GPS pop up, this status will stay even on reboot. So intentioned machine.reset(), uploading new python scripts and the watchdog is no solution. So the machine gets into an endless reboot loop until the power supply is cut.

The solution is to catch the I2C error and send the pytrack to deepsleep with gps=True. This resets the GPS, so that the ESP can talk again to it.

try:
  self.i2c.writeto(GPS_I2CADDR, self._mtkSentence)
  utime.sleep_ms(wait_ms)
except Exception as e:
  sys.print_exception(e)
  print("cut off GPS")
  utime.sleep_ms(2000)
  pytrack.setup_sleep(1)
  pytrack.go_to_sleep(True)

So 1.20.1.r1 seems to fix my problems at the moment. Would be nice, if this damn GPS will will be able again to find sattelites and print is able to flush.

[andreas]

@t0000899 said in Firmware Release v1.20.1:

Wlan connection has turned to really unreliable in 1.20 version.

We can confirm this after upgrading to 1.20.1 on FiPy and LoPy4 devices, with or without VARIANT=PYBYTES. We are also spuriously getting these core panics, see also https://community.hiveeyes.org/search?q=bad00bad bad00bad bad00bad.

Guru Meditation Error: Core  1 panic'ed (Cache disabled but cached memory region accessed)
Guru Meditation Error: Core  1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x4020f958: bad00bad bad00bad bad00bad

Guru Meditation Error: Core  1 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x40200754: bad00bad bad00bad bad00bad

[dabal221]

@serafimsaudade How do you solve this "OSError: Scan operation Failed!"?

[serafimsaudade]

@dabal221
I put a time.sleep of 3sec before wlan.scan(). And the error don't happen.

# Change the mode to both AP and station so we can connect to the network
self.wlan.init(mode=WLAN.STA_AP, ssid=system.uniqueGwId, auth=(WLAN.WPA2, self.system.apKey))
# Use internal antena
#self.wlan.antenna(WLAN.INT_ANT)
# Use External antena
self.wlan.antenna(WLAN.EXT_ANT)
try:
    time.sleep(3)
    self.nets = self.wlan.scan()
except Exception as exception:
    print("error", 'startWLAN scan: {0}'.format(exception))

[dabal221]

@serafimsaudade Unfortunately, it does not change anything. :(

[andreas]

@serafimsaudade said in Firmware Release v1.20.1:

I'm trying to connect gpy to wireless, but when I do wlan.scan() get this error:
wlan = WLAN(mode=WLAN.STA_AP,ssid="teste", auth=(WLAN.WPA2, 'pass'))
nets = wlan.scan()
OSError: Scan operation Failed!

This work on others fw version.

@dabal221 said in Firmware Release v1.20.1:

@serafimsaudade How do you solve this "OSError: Scan operation Failed!"?

For us, this flow works

import network

station = network.WLAN()
station.antenna(network.WLAN.EXT_ANT)
station.mode(network.WLAN.STA)
station.init()

then, later, either

station.scan()

or

station.connect(ssid, (auth_mode, password), timeout=int(timeout * 1000))

[dabal221]

@andreas Where can I find Firmware Release v1.20.1? Because when I update Firmware using Pycom Firmware Update I have got 1.20.0.rc13 not 1.20.1

[andreas]

@dabal221 said in Firmware Release v1.20.1:

Because when I update Firmware using Pycom Firmware Update I have got 1.20.0.rc13 not 1.20.1

Maybe the program will offer the newer releases after upgrading the Pycom Firmware Updater itself.

[dabal221]

@andreas said in Firmware Release v1.20.1:

@dabal221 said in Firmware Release v1.20.1:

Because when I update Firmware using Pycom Firmware Update I have got 1.20.0.rc13 not 1.20.1

Maybe the program will offer the newer releases after upgrading the Pycom Firmware Updater itself.

@andreas I have got 1.16.1, it is said that it is the latest stable version.