where to save NON-volatile device parameters?

[StefXinet]

Dear Nordic,

we need to save few bites (product serial number, few settings). we use BLE with bonding on a FreeRTOS based FW. PM is already using FDS, at it is not clear how to use the FDS without conflict while BLE is running.

What is the best method to store these data?

Thanks!

[Marjeris Romero]

Hi,

For only a few bites you can write directly to the UICR of the chip.

Best regards,

Marjeris

[StefXinet]

Thanks,

I supposed to do something like that. Is it possible to read and write UICR while the SD is running?

I can't find the SD API to read and write the CUSTOMER[x] UICR.

Thanks.

[Marjeris Romero]

Hi again,

Usually you will write data that will not need to be updated in runtime e.g. product serial number just needs to be written once.

[StefXinet]

This is clear, but what if I need to write something on CUSTOMER[x] UICR at runtime?

If it is not suggested to use FDS while BLE is running, and UICR at runtime, where should I save my few data?

[mrono]

StefXinet said:

If it is not suggested to use FDS while BLE is running, and UICR at runtime, where should I save my few data?

You can use FDS while BLE is on, that is not a problem. The BLE peer manager uses FDS to save some data, but you can also use the same FDS to save your data. The FDS library handles that easily.

So for things that are written during production and never change, use UICR. For anything else nonvolatile, use FDS.