Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

Wireless settings storage NVM vs. FDS

Hello!

We are developing with nRF5 SDK 16 on a nRF52840 - is there a certain cause that connection settings for e.g. Gazell is stored in NVM mode? We were concerned about flash wear and rewrote the gazell pairing library to use FDS, also beeing able to CRC the stored info was a consideration. We were wondering what the official stance and recommendation of Nordic concerning this topic is. Also if this is of interest for official use, we are willing to share the code.

Kind regards

  • Hi Bernhard, 
    I don't have a solid answer on why we chose to use NVMC module instead of FDS. But my guess is that we want to make it generic and using NVMC is pretty straight forward on showing how the data is stored. But maybe another explanation is that we have been using NVMC module since earlier SDKs where fds was not at production level. (FDS was only out of experimental since SDK v17.0 )

    It's summer time here in Norway and we have most of our staff away. I will forward your question to our team when they are back to give you a better explanation and on if we plan to switch to fds and get help from your code. 

  • Hi Bernhard, 
    The information I got from the team was that the Gazell pairing was developed before the fds and that's the reason it used NVM module. 
    We currently stopped development on the nRF5 SDK platform so I don't think there is any plan to have new release of the library. 

Related