I'm having trouble with OTAA in my area, the JoinAccept message is not received by my SodaqOne. It would be nice to have the option to store the OTAA status in EEPROM and reload it on reboot.
Of course a configuration would be required that toggles this option, so it is still possible to start a fresh session if required.
AFAIK the following parameters must be saved in EEPROM:
AppSKey (save once)
FCntUp (save on every transmitted packet)
FCntDown (save on every received packet)
Note: I do not know how many times the EEPROM can be safely written, since it is emulated EEPROM. Does this mean it is effectively infinite? And does it take a lot (relatively speaking) of power to write to the EEPROM?
Steps needed:
Get AppSKey from LoRa module (how?) after OTAA and store in EEPROM
Track FCntUp (how?) and store in EEPROM after every transmit.
Track FCntDown (how?) and store in EEPROM after every received message.
On boot, restore AppSKey, FCntUp and FCntDown to the LoRa module (how?)
I'm having trouble with OTAA in my area, the JoinAccept message is not received by my SodaqOne. It would be nice to have the option to store the OTAA status in EEPROM and reload it on reboot. Of course a configuration would be required that toggles this option, so it is still possible to start a fresh session if required. AFAIK the following parameters must be saved in EEPROM: AppSKey (save once) FCntUp (save on every transmitted packet) FCntDown (save on every received packet)
Note: I do not know how many times the EEPROM can be safely written, since it is emulated EEPROM. Does this mean it is effectively infinite? And does it take a lot (relatively speaking) of power to write to the EEPROM?
Steps needed:
Anything I missed?