Production use of NVRAM / EEPROM? [xDot]

[Brad S]

I’m looking at making improved use on NVRAM for our xDots. What I’d like to do, is a one command step at flash time that writes to NVRAM without that data being stored in the main program. This is raising a heap of questions as to options and best practices on these device.

1a) Can an external utility write to the EEPROM to be retrieved by the primary xDot program via (say) nvmRead?
1b) Can a cli utility flash one build that calls nvmWrite(), let it execute and then flash the primary program that calls nvmRead() – with the MTMDK / other Hw (ST-LINK, Segger…)

2)
mdot.h provides nvmRead and nvmWrite, mbed_os provides xdot_eeprom file functions. Are there any cons to using one or the other?

thanks

[Jason Reiss]

Could you use the default firmware AT commands?

[Mikael Grah]

I’m actually looking for a solution to the same question – we’d like to use our own software for the xDot and some configuration needs to be stored i NVRAM. Is there a way to flash NVRAM using a regular .bin copy via the xDot-DK?

[Author]

Posts