MBR Parameters and Bootloader Settings

RE: MBR Parameters and Bootloader Settings

Sigurd — Wed, 24 Apr 2019 14:47:46 GMT

Hi Gautham T,

Thank you for reporting that. The links should now work.

RE: MBR Parameters and Bootloader Settings

GT — Wed, 24 Apr 2019 14:37:05 GMT

The links to documents are not working. Can you please repost the same?

RE: MBR Parameters and Bootloader Settings

Sigurd — Tue, 12 Sep 2017 18:32:24 GMT

Bootloader Settings: A bootloader settings page contains information about the current DFU process. In addition, it can contain information about the installed application and the firmware version. See this link for more information.

MBR Storage Parameters: This used to store the SD_MBR_COMMAND_COPY_BL or the SD_MBR_COMMAND_VECTOR_TABLE_BASE_SET command when resetting the IC. E.g. under a bootloader update. Also if reset or power is lost, the MBR will read the stored commands and continue the update process. Upon reset the MBR read the stored commands, which will not be erased before the update is finished. Seeing that there is a “copy bootloader” command, the MBR will check if the bootloader was successfully copied, if not, it will re-write the bootloader to the bootloader section.

RE: MBR Parameters and Bootloader Settings

superpak — Tue, 12 Sep 2017 16:35:13 GMT

@sigurdon, Thanks, but I have read that chapter. I was specifically looking for what is contained in the "MBR Storage Parameters" and "Bootloader Settings" in the figure at the end of this page: infocenter.nordicsemi.com/index.jsp

RE: MBR Parameters and Bootloader Settings

Sigurd — Tue, 12 Sep 2017 15:15:24 GMT

Hi,

You can find more information about the MBR(Master Boot Record) and bootloader in the Master Boot Record and bootloader chapter in the SoftDevice Specification.

Some quotes:

The main functionality of the MBR is to provide an interface to allow in-system updates of the SoftDevice and bootloader firmware.

The Master Boot Record (MBR) module occupies a defined region in the SoC program memory where the System Vector table resides.

A bootloader may be used to handle in-system update procedures.

The bootloader has full access to the SoftDevice API and can be implemented like any application that uses the SoftDevice. In particular, the bootloader can make use of the SoftDevice API for Bluetooth® low energy communication.

The bootloader is also responsible for keeping track of and verifying the integrity of the SoftDevice. If an unexpected reset occurs during an update of the SoftDevice, it is the responsibility of the bootloader to detect this and resume the update procedure.