Report
3 months ago.

It is not possible to use with DISCO_L072CZ_LRWAN1 yet.

Due to the code is not supported in the online compiler, when trying to compile with GCC_ARM mbed-cli the bin file makes the target to get out of memory (even changing the main_stack_size). If I try to use the newlib-nano, it never compiles due to the guides to run without RTOS in [1,2] explain an old .mbedignore config, and the new LoRaWAN 1.1 - mbed-os release has files with dependencies. Please try to fix it to use in DISCO_L072CZ_LRWAN1 again.

If any idea of how to solve the problem, please guide me through.

[1] https://os.mbed.com/blog/entry/Reducing-memory-usage-by-tuning-RTOS-con/ [2] https://os.mbed.com/questions/82060/Does-mbedignore-still-work/

Question relating to:

Comment on this question

2 Answers

2 months, 2 weeks ago.

Dear Santiago Gil,

I have a basic link driver which support the DISCO_L072CZ_LRWAN1 board, this allows initial testing.

https://os.mbed.com/users/Helmut64/code/STM32L0_LoRa/

We got as well a complete peer to peer Lora protocol stack (commercial) with MQTT support, Push LoRa to MQTT notification on mobiles, etc. , see documentation at www.radioshuttle.de

Regards Helmut

2 months, 2 weeks ago.

newlib-nano is not compatible with RTOS as it is not thread-safe. You should be able to drop the RTOS support using the .mbedignore file, I am not sure why you wouldn't be able to do that. Taking LoRaWAN 1.1 in consideration, yes, it increases the RAM and ROM consumption and it may have an impact on the boards like DISCO_L072Z. But I still believe that you should be able to cut down enough to make it fit into the limits prescribed by the target in question using the .mbedignore file.

We will soon start a campaign to cut-down on the RAM/ROM resource utilization after we are done with priority items in our backlog. Please share with us the exact issue you are facing while trying to build with .mbedignore. It would be helpful if you share your .mbedignore file.

I appologize for the delay in response as it was holiday season and we had limited bandwidth.

Regards,

Hasnain


To post an answer, please log in.