New Stable Firmware Release v1.18.2
-
Hello everyone,
New Stable release v1.18.2 is released today, changes include:
Improvments
- Updates to MQTT lib.
- Added API to Get/set DNS servers.
- Updated Sequans FW upgrade scripts
- Enabled LCP Echo interval in IDF
- Improved PPP session suspend/resume
- Wifi AP mode on boot now is using only Default AP and SSID -> Initially the onboot wifi mode was using the ssid/pwd configured in pycom-config saved in flash which caused inconvenience for some users when switching between Pybytes FW and other Base FWs since the AP would be brought up with same ssid/pwd. This is now removed and in next releases wifi config saved in flash will be improved for more efficiency and relaiability.
- Added factory modem reset option , method to check UE coverage and Bug fixes
Bug Fixes
- Fixed socket.connect Crash problem when LoRa/Sifgfox initialized before Wifi/LTE
- Updates and bug fixes for LTE module
- Fixed bug in spi.read()..The parameter write=.. in spi.read() was ignored. Instead always 0x55 was sent. (author @robert-hh )
- MQTTlib: Gracefully handle EAGAIN return of Socket.write
- fix an issue in cleaning up user threads during of soft-reset
- Fix issue causing Device crash when safe booting (CTRL-F) while BLE/Wlan enabled
- Fix makefile bug excluding SIPY FIPY LOPY4 from secure Boot process
you can download the sources from here
or you can flash the firmware directly via Firmware Updater tool with latest stable firmware
-
@paul-thornton
Sorry Paul, I never saw your reply until today. Unfortunately our load is pretty complicated; we have one thread for each I2C bus we configure (1 or 2 depending on the system) and two threads doing socket communication (one for outgoing and one watching for incoming). We're keeping track of resets and will monitor the systems. If it doesn't improve with later firmware releases then I'll have to look at debugging the crash. Do you have instructions on how to go about that?-- Mike
-
@mfallavol said in New Stable Firmware Release v1.18.2:
I'm getting somewhat regular crashes with this firmware. The crash begins with:
assertion "netconn_alloc: undefined netconn_type" failed: file "/Users/iwahdan/e
sp/pycom-esp-idf/components/lwip/api/api_msg.c", line 696, function: netconn_alloc
abort() was called at PC 0x401450b7 on core 1I've seen it a few times already today.
Hello @mfallavol, Thanks for the report. Any idea what the board happened to be doing at the time?
-
I'm getting somewhat regular crashes with this firmware. The crash begins with:
assertion "netconn_alloc: undefined netconn_type" failed: file "/Users/iwahdan/e
sp/pycom-esp-idf/components/lwip/api/api_msg.c", line 696, function: netconn_alloc
abort() was called at PC 0x401450b7 on core 1I've seen it a few times already today.
-
@martinnn said in New Stable Firmware Release v1.18.2:
@paul-thornton I saw that the wifi RSSI readout (I am interested in) works on rc 1.20 only, not 1.18. Any comments on when to use rc 1.12 vs. stable 1.18? If you need the new features, try rc, else stick with stable? Although few changes seem to affect the wipy.
You have the correct idea. If you absolutely need features only available in the RC builds then feel free to give them ago. We still offer as much support as we can but there may be bugs/crashes.
If you dont. Stick to the stable builds. they should have most of the bugs ironed out.
-
@paul-thornton I saw that the wifi RSSI readout (I am interested in) works on rc 1.20 only, not 1.18. Any comments on when to use rc 1.12 vs. stable 1.18? If you need the new features, try rc, else stick with stable? Although few changes seem to affect the wipy.
-
@martinnn No not yet. MQTT docs likely wont see much change. changes are bugfix not a change to functionality as far as I am aware. Will confirm re Wifi.
-
Is the documentation already updated? I'm interested in MQTT and Wifi particularly.
-
And yes! ... one now hasz DNSz'y via LTE-NB1 (NB-IOT) 👍🏻
-
@johanbrichau said in New Stable Firmware Release v1.18.2:
This is especially useful on NB-IoT networks as it seems the DNS server config is not given by the mobile network.
Yes! it is! 😇
And Yeah, The Teleoperators didn't design it with DNS-support in mind .... put they left it "Open" ... and put all of the task on the platform supplier ... to implement a function like this ... to define our own DNS-server.
I will test it out on our Operators network, see if we finally can resolve domain names 🙃
-
@combaindeft I had the same question... so I dug up the code changes and figured it out:
usocket.dnsserver(0,'8.8.8.8') usocket.dnsserver(1,'4.4.4.4') usocket.dnsserver() ('8.8.8.8', '4.4.4.4')This is especially useful on NB-IoT networks as it seems the DNS server config is not given by the mobile network. This is really cool. I can remove the hacks to deal with DNS querying in my code.
-
@combaindeft Thanks.. not always easy for a newbie to find all the info.. :-)
-
@iwahdan said in New Stable Firmware Release v1.18.2:
Added API to Get/set DNS servers.
How do you do this?
-
@steve-williams said in New Stable Firmware Release v1.18.2:
@rcolistete I'll give this a go, but where can I get a copy of 1.18.1.r7 from just in case my projects' code doesn't want to play with the new version? Just naturally cautious.. :-) Are all the changes documented?
-
@rcolistete I'll give this a go, but where can I get a copy of 1.18.1.r7 from just in case my projects' code doesn't want to play with the new version? Just naturally cautious.. :-) Are all the changes documented?
-
Useful info, the firmware v1.18.2 is available for manual download :
https://github.com/pycom/pycom-micropython-sigfox/releases
