• State Verified Answer
  • Replies 1 reply
  • Subscribers 75 subscribers
  • Views 2308 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 221231
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

MBR settings + DFU settings backup

Nopik

Currently in memory map nRF5 SDK 15.2 (which apparently is a base for Thread SDK) says for nrf52840:

Bootloader settings 0x000F F000 - 0x0010 0000 (4 kB)
MBR parameter storage 0x000F E000 - 0x000F F000 (4 kB)

However, the example DFU attached to Thread SDK 2.0 to store backup of bootloader settings at 0xfe000 area. I.e. settings from 0xff000 are duplicated to 0xfe000. Is that OK? What about MBR settings? Should they occupy different area? 

What settings MBR need to store?

Also, is the MBR source code available anywhere?

Parents
  • +1

    Hi,

    The MBR store parameters (progress, source pointer, etc) to the params page during bootloader copying (ie DFU of the bootloader itself) to ensure that the copy routine can withstand any unexpected resets. Since the params page is only used in the final step of a bootloader update it is ok to also use it as a backup page. 

    The source code for the MBR is not available unfortunately.

Reply
  • +1

    Hi,

    The MBR store parameters (progress, source pointer, etc) to the params page during bootloader copying (ie DFU of the bootloader itself) to ensure that the copy routine can withstand any unexpected resets. Since the params page is only used in the final step of a bootloader update it is ok to also use it as a backup page. 

    The source code for the MBR is not available unfortunately.

Children
No Data
Related
Terms of service