Attachments (0)
Nordic Case Info
  • Case ID: 224420
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Changed MBR parameter handling in SDK15.3.0

Adrian Eggenberger

Hi

I was playing around with the new SDK 15.3.0 and most things worked as expected. One thing that causes some trouble is the changed MBR parameter page handling. It seems that new the MBR parameter page is given by the value at address 0xFFE (last word in MBR code???). Can you give an update on this change in MBR parameter page? What is the correct migration path if we wan't to update to the new SDK?

Regards Adrian

Parents
  • 0

    Hi,

    This is specified in the Softdevice specification here.

    Best regards

    Jared 

  • 0 in reply to Jared

    Hi

    Thanks for the link to the definition how the MBR handles the parameter page.

    I guess what confuses me is the following line in the SDK 15.3:

    #define NRF_UICR_BOOTLOADER_START_ADDRESS       (MBR_BOOTLOADER_ADDR)

    With this define the UICR address is on address 0xFFC in the MBR? In the last SDK version this was an address in the UICR.

    Regards Adrian

Reply
  • 0 in reply to Jared

    Hi

    Thanks for the link to the definition how the MBR handles the parameter page.

    I guess what confuses me is the following line in the SDK 15.3:

    #define NRF_UICR_BOOTLOADER_START_ADDRESS       (MBR_BOOTLOADER_ADDR)

    With this define the UICR address is on address 0xFFC in the MBR? In the last SDK version this was an address in the UICR.

    Regards Adrian

Children
  • 0 in reply to Adrian Eggenberger

    Hi,

    Yes, that is correct, it's now in the MBR. It was done because the UICR can't be protected from write. It should be backwards compatible as long as the value on adress 0xFFC is 0xFFFFFFFF.

    Best regards

    Jared

Terms of service