New Beta Release v1.20.3.b3

[DualMatic]

@robert-hh you must generate an SSH key in your machine:
Generating SSH key

Add the key to your SSH Agent
Add to SSH Agent

Once generated copy and paste it on your github settings:
Add SSH key to Github Account

Clone again the repository with --recursive option

Best regards, hope this is useful to you!

[robert-hh]

@DualMatic No Sir. No joy. The SSH key was installed. Would you mind to compare the list of submodule versions to your's?

[DualMatic]

@robert-hh said in New Beta Release v1.20.3.b3:

P.S.: I had quite a few build systems creations in the past

Yeah I know ;) (I'm novice user RG build enviroments) just I wanted to help you a little bit and return your past support my old username

@robert-hh said in New Beta Release v1.20.3.b3:

@DualMatic No Sir. No joy. The SSH key was installed. Would you mind to compare the list of submodule versions to your's?

/esp/pycom-micropython-sigfox# git submodule status
 d270f79aa16dd8fd4ae3b6c14544283dcb992e9c lib/asf4 (heads/master)
 43a6e6bd3bbc03dc501e16b89fba0ef042ed3ea0 lib/axtls (heads/master-38-g43a6e6b)
 35aaec4418ad78628a3b935885dd189d41ce779b lib/berkeley-db-1.xx (heads/master-7-g35aaec4)
 c8b9823f68c6af0fa52e2c4e009aba4dbf257232 lib/btstack (v1.2~13^2~33)
 e9de7e35f2339598b16cbb375f9992643ed81209 lib/libffi (v3.2.1-146-ge9de7e3)
 159e31b689577dbf69cf0683bbaffbd71fa5ee10 lib/lwip (STABLE-2_1_2_RELEASE)
 3f8d78411a26e833db18d9fbde0e2f0baeda87f0 lib/mbedtls (mbedtls-2.17.0)
 97ce3eacaaa79e8ed6cf71717149ced4f5328ee7 lib/mynewt-nimble (nimble_1_3_0_tag)
 7a4c9d946cf1801771fc180acdbf7b878f270093 lib/nrfx (v2.0.0)
 b618cb1d521cc9e133bdcd0fca154dee2d925dfe lib/nxp_driver (b618cb1)
 58fee7c92bd576814d3f2afd92fbc62990270ecc lib/stm32lib (F0-1.9.0+F4-1.16.0+F7-1.7.0+H7-1.6.0+L0-1.11.2+L4-1.8.1+WB-1.6.0-19-g58fee7c)
 a6b916ba85bef6aad50f1652532b02984dfe2484 lib/tinyusb (0.5.0-680-ga6b916ba)

/esp/pycom-esp-idf# git submodule status
 3b66e5b051381fb70de9c2791df70a06181c64e3 components/asio/asio (asio-1-12-0-200-g3b66e5b0)
 d037ec89546fad14b5c4d5456c2e23a71e554966 components/bootloader/subproject/components/micro-ecc/micro-ecc (v1.0)
 238fc047f2f63d99482aa51996f14ca134096310 components/bt/controller/lib (238fc04)
 fead24e5d5c0f4bd9b8c3d71cf72a87d75631399 components/bt/host/nimble/nimble (remotes/origin/master-254-gfead24e5)
 d2dd95cb8841d88d5a801e3ef9c328fd6200e7bd components/cbor/tinycbor (v0.5.2-17-gd2dd95c)
 98954eb30a2e728e172a6cd29430ae5bc999b585 components/coap/libcoap (v4.2.0-rc4-114-g98954eb)
 a17182e903a9e161a98930648eb6ff78019708ab components/esp_wifi/lib (a17182e)
 a66ee2da5ad059bb4d90e8a7317f907add1d8419 components/esptool_py/esptool (v2.8-23-ga66ee2d)
 968b8cc46dbee47b83318d5f31a8e7907199614b components/expat/expat (R_2_2_5)
 3c8935676a97c7c97bf006db8312875b4f292f6c components/json/cJSON (v1.7.12)
 70170c28c844a4786e75efc626e1aeebc93caebc components/libsodium/libsodium (1.0.12)
 50e4e0d1821a6e5deab0ead9f35ffb4e60625ea6 components/lwip/lwip (remotes/origin/master-194-g50e4e0d1)
 9ef92c551eb8d92677034c3ec8078a8076febf41 components/mbedtls/mbedtls (mbedtls-2.13.1-1358-g9ef92c551)
 6bc94add892437d0fd50f26bfabe78c646648c13 components/mqtt/esp-mqtt (ESP-MQTT_FOR_IDF_3.1-170-g6bc94ad)
 3bcc416e13cc790e2fb45fcfe9111d38609c5032 components/nghttp/nghttp2 (v1.24.0)
 dac1a65feac4ad72f612aab99f487056fbcf5c1a components/protobuf-c/protobuf-c (v1.3.0)
 f5e26c4e933189593a71c6b82cda381a7b21e41c components/spiffs/spiffs (0.2-221-gf5e26c4)
 7d2bf62b7e6afaf38153041a9d53c21aeeca9a25 components/unity/unity (v2.4.3-51-g7d2bf62)
 7e8e249990ec491ec15990cf95b6d871a66cf64a examples/build_system/cmake/import_lib/main/lib/tinyxml2 (2.0.2-659-g7e8e249)

PS. cannot reply on time because not sufficient reputation

[robert-hh]

@DualMatic said in New Beta Release v1.20.3.b3:

PS. cannot reply on time because not sufficient reputation

I added a few.

[robert-hh]

@peterp Building in a up-to-now rarely used mint linux virtual machine worked. So if have to tell now what is interfering with the other build process.
Edit: copying back the pycom-esp-idf directory from the virtual machine to my primary machine worked too. So: Why did the esp-idf not install properly?
Edit2: Found the culprit: two additional lib directories in components/bt and components/esp32. But HOW did they get into the fresh cloned esp-idf? They are in the linker search directories, hmmm.

[robert-hh]

@peterp said in New Beta Release v1.20.3.b3:

Soft reset (Ctrl-D) causes core dumps

Commenting out 'uart_deinit_all();' on line 381 in mptask.c lets the code survive soft reset.
So maybe the delay is to short for the 'MPY:soft reboot' message to get sent.
Yup: Increasing the delay at line 379 to 50000 does the trick.

[peterp]

@robert-hh said in New Beta Release v1.20.3.b3:

two additional lib directories in components/bt and components/esp32. But HOW did they get into the fresh cloned esp-idf? They are in the linker search directories, hmmm.

Maybe some git submodule stuff? I recall some trouble when doing a git checkout that is "too far". E.g., git clone idf3.3.1 and then git checkout idf4.1 would lead to some messed up git submodules and it was just easier to make a fresh git clone from a branch that is just a few commits away from the IDF_HASH without any major changes to submodules and then you can git checkout IDF_HASH and have all the submodules correct.

Did those two directories not show up with git status? I'm sure there is a " correct " way with git to do this checkout in any existing clone, but I couldn't figure it out and just settled on a new clone from a "close" branch as shown above.

[peterp]

@robert-hh said in New Beta Release v1.20.3.b3:

@peterp said in New Beta Release v1.20.3.b3:

Soft reset (Ctrl-D) causes core dumps

Commenting out 'uart_deinit_all();' on line 381 in mptask.c lets the code survive soft reset.
So maybe the delay is to short for the 'MPY:soft reboot' message to get sent.
Yup: Increasing the delay at line 379 to 50000 does the trick.

Awesome @robert-hh I'll check that today!

[robert-hh]

@peterp said in New Beta Release v1.20.3.b3:

Maybe some git submodule stuff?

There are sometimes warnings when changing the branch, that directories cannot be removed because they are empty. In combination with the unneeded lib includes for -L$(ESP_IDF_COMP_PATH)/esp32/lib and -L$(ESP_IDF_COMP_PATH)/bt/libin Makefile line 182ff that could have cause the trouble for my old repository. But I do not understand why that happened too with the new cloned versions of esp-idf. Maybe some caching of paths.

[DualMatic]

I've tested new Beta Release (again thanks for the update)

Regarding ULP question, sadly is not included here but check out my post ULP Testing (pycom firmware with ULP support) as I've managed to "copy" micropython ULP part and integrated more or less on pycom firmware.

Regarding LoRa DeviceTimeReq, DeviceTimeAns not tested, but checking the code I think is not supported yet.

Side note, the Beta release requires to flash entire memory: differential update doesn't work and it complains with wrong size.

Regards

[jand]

@peterp
You now implemented LoRaWAN 1.0.3 (Class A& C). Does that mean that the MAC command “DeviceTimeRequest” can now be used to synchronize the real time clock of an end device? (see https://lora-alliance.org/resource_hub/lorawan-specification-v1-0-3/) If yes, how? Or where can I find that information?

[Sjur Wroldsen]

Hi @peterp,
Any updates on this release?
I see that there hasn't been that much activity lately, and I am eager to include uasyncio in my project : )

[Jean Ferreira]

@peterp can you please provide an update on this? I need updated IDF and MP to stay with this hardware platform but feedback and progress has been slim on the ground the last few months.

There have been no release candidates or beta improvements.

[peterp]

@Jean-Ferreira All I can tell you is that new MP and IDF versions are being worked on, but I can't give you an ETA

[Jean Ferreira]

@peterp is this beta worth testing or has the code base moved on too far? I need to integrate Ulab but the available 1.20.2 with ulab has LTE issues

[peterp]

@Jean-Ferreira said in New Beta Release v1.20.3.b3:

@peterp is this beta worth testing or has the code base moved on too far?

Yes. At this moment, you might test three different options. It could be that either one has their own pros/cons:

• stable FW based in IDF 3.3.1 - 1.20.2.rX for the latest X (right now 1.20.2.r4)
• beta FW based on IDF 4.1 - 1.20.3.b3
• alpha FW based on IDF 4.2.1 - 1.20.3.b4

I need to integrate Ulab but the available 1.20.2 with ulab has LTE issues

I haven't looked into this at all, but I find it surprising that there is a relation between ulab and lte.

[goldfishalpha]

Hello all!

This release doesn't appear to be changing the LoRaWAN mac version to 1.0.3, on a LoPy4. Update performed with Pycom firmware updater tool (not self built).

>>> import os
>>> os.uname()
(sysname='LoPy4', nodename='LoPy4', release='1.20.3.b3', version='v1.11-92f2b22e on 2021-04-19', machine='LoPy4 with ESP32', lorawan='1.0.2', sigfox='1.0.1', pybytes='1.6.1', pygate='1.0.1')
>>>

Could it be that the name was not updated, though the firmware still tries to support 1.0.3?

If this feature requires me building a more recent beta version, would consider it. Could really do with this for testing.

Thanks for any pointers.