Timeline for nRF52 non-volatile storage/recall of a variable - is there a simple solution?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 22, 2022 at 6:32 | vote | accept | TommyS | ||
| Apr 27, 2022 at 17:06 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 28, 2021 at 17:05 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 30, 2021 at 16:05 | history | bumped | Community Bot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 31, 2021 at 15:21 | answer | added | Juraj ♦ | timeline score: 2 | |
| Jun 16, 2021 at 2:10 | comment | added | TommyS | One other options is that upon bootup the sketch on my device would read user-selected values on the connected external BLE device app (phone, ectc) and use them as the variables values in the sketch: for example time-delay selection for auto-off. . | |
| Jun 16, 2021 at 2:05 | comment | added | TommyS | Reviewed the options. Just thinking out loud: Adadfuit already has some QSPI libraries and the chip on their boards. But requires 6 wires (normal SPI 4 wires). NVM is a no-external-parts solution, but does interfere with the nRF5's BLE softdevice stack requiring some fancy programming. I am leaning towards EEPROM and FRAM for ease of addressing/programming, but both require some (small) external real estate. However only a 1 or 2 wire I2C interface. | |
| Jun 14, 2021 at 20:04 | comment | added | TommyS | Thank you both. I am digesting the linked information. Will decide and try. So far, I gathered that I need to be careful with not placing any write/erase related functions inside the "loop" as not to "wear out" the memory. | |
| Jun 14, 2021 at 14:26 | comment | added | Juraj♦ | arduino.cc/reference/en/libraries/arduino-nvm | |
| Jun 14, 2021 at 13:09 | comment | added | Dave Newton | Your options are the internal flash or an external EEPROM. If you're dealing with the internal flash then some sort of FS is likely the easiest choice. External EEPROM/FRAM can be as simple as an I2C chip and library. LFS doesn't create a "sort of persistent storage space", it's an FS abstration. There's also things like github.com/d00616/arduino-NVM. | |
| Jun 14, 2021 at 12:09 | history | asked | TommyS | CC BY-SA 4.0 |