New Firmware Release Candidate v1.20.0

[Xykon]

A new version 1.20.0.rc4 is now available with the following updates:

Co-Authored-By: @iwahdan
mods/modusocket: use getaddrinfo() instead of n_gethostbyname() in mod_usocket_getaddrinfo()
esp32/modusocket:Add mpy API to get/set DNS servers ipv4 addr
mods/machrtc: Add optional parameter backup_server to specify two NTP servers
esp32: Fixes in order to get the LoRaWAN US915 certification passing
esp32/frozen: updated MQTTMsgHandler.py
esp32/pycom_config: fix typos

Co-Authored-By: @robert-hh
help: Simplify and extend help()
mods/machspi.c: Fix the bug in spi.read()
esp32/micropython: correction to keyboard interrupts exposure

Update IDF libraries to pycom-esp-idf/idf_v3.1 ebff2ed
mods/machrtc: Fix rtc.synced()

Fix typo in get_idf_libs.py

Example1: Set primary and secondary (backup) ntp server.

from machine import RTC
rtc = RTC()
rtc.ntp_sync('pool.ntp.org', backup_server='ntp.ubuntu.com')
rtc.synced()

Example2: Check and update name server configuration

import socket
# Check configured name servers
socket.dnsserver()
==> ('8.8.8.8', '8.8.8.8')
# Check primary name server (index: 0)
socket.dnsserver(0)
==>  (0, '8.8.8.8')
# Set primary name server (index: 0)
socket.dnsserver(0, '10.0.0.1')
# Set secondary name server (index: 1)
socket.dnsserver(1, '192.168.1.1')
socket.dnsserver(0)
==>  (0, '10.0.0.1')
socket.dnsserver()
==>  ('10.0.0.1', '192.168.1.1')

[crumble]

Have you changed someting in _thread or i2c as well?

up to ec2 I had huge problems with i2c and a pytrack.
Under rc3 it was more stable when serializing i2c with a lock. But deepsleep failed once without visible i2c exception.

Now it runs for some hours without a problem on a LoPy and WiPi3. I hope you have done a great job. Not that I have a lot of bad luck and and miss allways the issue.;)

[Xykon]

@crumble said in New Firmware Release Candidate v1.20.0.rc0:

Have you changed someting in _thread or i2c as well?

Maybe it's the updated IDF libraries... I haven't changed anything in the source code related to that functionality.

[crumble]

I move back to FAT file system. LittleFS worked fine for some time, but suddenly it was not possible to upload files with the ATOM plugin running Windows 10.

>>>
>>>
Uploading project (main folder)...
Not safe booting, disabled in settings

Reading file status
Failed to read project status, uploading all files
Creating dir lib
[1/5] Writing file lib/dth.mpy (2kb)
[2/5] Writing file lib/pycoproc.mpy (6kb)
Failed to write file, trying again...
Failed to write file, trying again...
timeout
[3/5] Writing file lib/pytrack.mpy (0kb)
Failed to write file, trying again...
Failed to write file, trying again...
timeout
[4/5] Writing file lib/sfGPS.mpy (7kb)
Failed to write file, trying again...
Failed to write file, trying again...
timeout
[5/5] Writing file main.py (4kb)
Failed to write file, trying again...
Failed to write file, trying again...
Upload failed.: timeout Please reboot your device manually.

The failed to write messages do not pop up always after two files. Sometimes after main.py

I flashed the firmware with erasing the file system flag, it failed.
I flashed again with FAT and it worked.
Flashed 3rd time with LittleFS and failed again.

Maybe a timestamp problem? I had no problems during the afternoon. Time zone is Berlin. Problem started around 20:00 local time.

FTP worked well.

[rogerrr]

Hi,

When will be able to use macfilter and/or commissioner in cli function ?
Else, is there a way to secure the mesh networks ?

Thanks

[Paul Thornton]

@rogerrr Hi, whilst I can confirm Macfilter/commissioner is on our roadmap but I dont have a timeframe for delivery at the moment.

re current security methods. All mesh traffic is currently encrypted with a pre shared key that matches across all nodes.

[rogerrr]

@paul-thornton thanks for your answer,
Can i set this value ?

[Paul Thornton]

@rogerrr @Xykon Could you answer this?

[serafimsaudade]

I'm testing this new fw v1.20.0.rc4 release with GPY with lasted NB modem fw.
Resume:
1 - I'm able to connect and send data over NB (Portugal - MEO operator)
2 - rtc.ntp_sync() is working over NB and WIFI
3 - rtc.synced() is working over NB and WIFI
4 - I notice that sometimes the usocket.read() don't timeout, I will continue doing more tests.

keep the good work.

[crumble]

Bad luck today run into the i2c issue on init of pytrack:

  File "main.py", line 62, in <module>
  File "lib\pytrack.py", line 8, in __init__
  File "lib\pycoproc.py", line 102, in __init__
  File "lib\pycoproc.py", line 164, in set_bits_in_memory
  File "lib\pycoproc.py", line 155, in magic_write_read
  File "lib\pycoproc.py", line 117, in _read
OSError: I2C bus error

It will be nice, if this message has more details inside the development firmware. It is the same when reading or writing on the python level. But maybe a "doesn't work on my machine" is helpful, too ;)

[crumble]

@xykon

Update IDF libraries to pycom-esp-idf/idf_v3.1 ebff2ed

I tried to compile debian submodule on win10. But fail with a lot of the idf_v3.1* branches.
It misses include files from the folder mbedtls

mods/modussl.h:19:25: fatal error: mbedtls/net.h: No such file or directory
compilation terminated.
mods/moduhashlib.c:26:26: fatal error: mbedtls/sha1.h: No such file or directory
compilation terminated.
In file included from mods/modussl.c:28:0:
mods/modussl.h:19:25: fatal error: mbedtls/net.h: No such file or directory
compilation terminated.
In file included from mods/lwipsocket.c:31:0:
mods/modussl.h:19:25: fatal error: mbedtls/net.h: No such file or directory
compilation terminated.

origin/master compiles without problems.

Can I give the original idf v3.1.2 a try or do I need your changes?
Hey, there is a change for i2c. I have no clue what this means, but i had to have it. Just too scared to brick the device without your go ;)

[robert-hh]

@crumble Dis you issue in the esp-idf folder the command:

git submodule update --init

[crumble]

@robert-hh
Thanks a lot Robert. I had done this in master branch only or it failed for some reason.

Was not able to link it with idf_v3.1 but idf_v3.1.1 works.

[robert-hh]

@crumble You have to do that after any checkout in the esp-idf repository. So if you change to v3.1, you have to repeat that. And in the Micropython subdirectory you have to rebuild mpy-cross.

[Sympatron]

@iwahdan @Xykon
What happend to the development branch and version 1.19 (which is still in beta)?
Was it abandoned? As far as I can see they both branched from 1.18, but with similar changes, especially regarding the new directory structure.
Is everything that was new/fixed in 1.19 also in 1.20?

[brotherdust]

@iwahdan
May I suggest enabling OrderedDict in collections?

#define MICROPY_PY_COLLECTIONS_ORDEREDDICT (1)

[brotherdust]

This post is deleted!

[brotherdust]

@iwahdan
Getting build errors on release-candidate:HEAD (2/27/19):

LINK build/WIPY/release/application.elf
lib/libbt.a(bt.o):(.literal.btdm_check_and_init_bb+0x4): undefined reference to `btdm_rf_bb_init_phase2'
lib/libbt.a(bt.o): In function `btdm_check_and_init_bb':
/Users/iwahdan/esp/pycom-esp-idf/components/bt/bt.c:1165: undefined reference to `btdm_rf_bb_init_phase2'
collect2: error: ld returned 1 exit status
make: *** [application.mk:632: build/WIPY/release/application.elf] Error 1

Any thoughts here?
Thanks!

[crumble]

@brotherdust

Any thoughts here?

Do you use an old esp-idf branch? The pycom-esp-idf master is an old version used by the stable firmware. If you want to compile 1.20 you have to switch to v3.1.something. I am on the 3.1.1 branch.

[Xykon]

@brotherdust The official IDF version for release-candidate branch is idf_v3.1 (see Jenkinsfile)

Also make sure to update submodules in both the IDF and the firmware repo (see README.md)