Hello,
I am currently developing a LoRaWAN Class A device using the NUCLEO-WL55JC1 development board and the "LoRaWAN_End_Node_LBM" example from STM32CubeWL (version 1.5.0).
I am facing an issue with context restoration after a reset. I am using the provided StoreContext() and RestoreContext() functions exactly as implemented in the example. However, after each reboot, the device always restarts the join procedure instead of resuming the previous session. As a result, the DevNonce is incremented on every reset.
This behavior is problematic because repeated resets will continuously increment the nonce value. According to the LoRaWAN specification, this value is limited (16-bit), and once the limit is reached, the device will no longer be able to join the network.
My understanding is that, when the context is correctly restored, the device should resume its previous session without triggering a new join procedure.
Could you please clarify:
* What is the correct sequence to restore the LoRaWAN modem context after a reset when using LBM?
* Are there additional steps required before sending uplinks without performing a new join?
* Should the modem automatically resume the previous session when the context is restored, or is an explicit action required to reactivate the restored session?
* Is there any known limitation or condition that forces a rejoin even if the context is restored?
Thank you for your support.
Best regards,
Pierre
