RE: Protecting flash area

Edvin — Mon, 30 Sep 2019 11:28:33 GMT

[quote user="awneil"]But it is erased by a full chip erase?[/quote]

Yes. Definitely. But if it is programmed during production, together with the bootloader, then it will remain for the lifetime. The bootloader will never erase the UICR.

RE: Protecting flash area

awneil — Fri, 27 Sep 2019 15:12:23 GMT

[quote userid="26071" url="~/f/nordic-q-a/52672/protecting-flash-area/212322"]The UICR is never touched by the Bootloader[/quote]

But it is erased by a full chip erase?

RE: Protecting flash area

Edvin — Fri, 27 Sep 2019 14:13:56 GMT

Hello,

There are a few different approaches to this.

You can either store this information using FDS. The bootloader will not (if set up correctly) erase the FDS area during firmware updates.

However, if this is data that is never meant to change or be updated, which it sounds like based on the info you describe:

[quote user=""]store some info about production to flash memory (DeviceID, production date etc)[/quote]

I would recommend to store this information in the UICR. The Customer[N], N=0-31, is a good place to store this information.

The UICR is never touched by the Bootloader.

As mentioned, the DFU will not touch the end of the flash, typically used for FDS. If you search for NRF_DFU_APP_DATA_AREA_SIZE in sdk_config.h in the bootloader project, this is the define that says how many bytes (right below the bootloader in flash) that is reserved. If you use FDS, which typically use 3 FDS pages, this will equal 3 * 4096 bytes = 12288 bytes.

If you want to reserve some extra space, add another page, so you have FDS pages + 1 reserved.

Best regards,

Edvin