This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Dependency of Bootloader on NRF_UICR->CUSTOMER registers

Hi All,

from below post, I found that in SDK11, bootloader code uses NRF_UICR->CUSTOMER[0] register for device type and revision verification so application should not use it for any purpose. 

https://devzone.nordicsemi.com/f/nordic-q-a/32356/dfu-was-getting-failed-after-updating-uicr-register-with-model-no/125129#125129

I just want to know that are bootloader of SDK15.3, 16 and 17 have any such dependency on NRF_UICR->CUSTOMER registers as I am using NRF_UICR->CUSTOMER[0] register in my application to save some important data.

Regards,

Bipin Patel

  • Hi,

    After SDK 11, the bootloader was changed into what is known as the "secure DFU bootloader", and the bootloader from SDK 11 is now referred to as "legacy DFU bootloader".

    With the new bootloader, from SDK 12 onwards, the CUSTOMER fields of UICR are no longer used for bootloader purposes. NRFFW fields of UICR are used, however, as those are reserved for Nordic firmware design. There is also use of the bootloader settings page, which is a flash page dedicated for data storage by the bootloader, and the MBR params page is used for backup of the bootloader settings page starting from SDK 15.3.

    Please also note that in the legacy DFU bootloader, UICR_CUSTOMER_DEVICE_INFO_OFFSET could be used to change the location in UICR used by the bootloader, as mentioned in the thread you referred to in your opening post.

    Regards,
    Terje

  • Thanks a lot Terge for clarification.. Slight smile

    Regards,

    Bipin Patel

Related