RE: Bootloader DFU Register and Flash Changes

Kyle Krueger — Sun, 30 Oct 2016 14:57:07 GMT

I am having a similar issue. The app will not launch, and the device reboots into DFU_TARG mode again after the DFU service reports a success.

However, with the pca10040 DK the same Bootloader, Softdevice, and App work with no problems.

I have already adjusted the clock speed for ble_init to work for both platforms, and am stumped by this issue.

So it seems like BANK_VALID_APP is not being written to as it should by the DFU service on completion.

I am not in the office right now, but can provide more information on Monday or Tuesday.

RE: Bootloader DFU Register and Flash Changes

Milton — Tue, 25 Oct 2016 13:57:40 GMT

Hi Bjørn,

Thank you for the detailed explanation. It definitely helps to clarify things and to have all the information in one place.

Regards,

Milton

RE: Bootloader DFU Register and Flash Changes

bjorn-spockeli — Tue, 25 Oct 2016 06:44:10 GMT

Hi Milton,

The UICR register at 0x10001014 holds the bootloader start address and is only written to when the bootloader is flashed to the nRF5x device. The bootloader start address will not be altered after this initial write.

The UICR register at 0x10001000 holds the start address of the application vector table which is also the end of the Softdevice region. Only written to when the SoftDevice is initially flashed to the nRF5x device.

The MBR params page at 0x7E000 is used by the Master Boot Record(MBR) to store state information and will be altered when the bootloader issues commands to the MBR.

The bootloader settings page at 0x7F000 and will change during the DFU update to contain data about the received firmware image and the status of the firmware banks. The data isstored in the bootloader_settings_t struct

typedef enum
{
    BANK_VALID_APP   = 0x01,
    BANK_VALID_SD    = 0xA5,
    BANK_VALID_BOOT  = 0xAA,
    BANK_ERASED      = 0xFE,
    BANK_INVALID_APP = 0xFF,
} bootloader_bank_code_t;

typedef struct
{
    bootloader_bank_code_t bank_0;          /**< Variable to store if bank 0 contains a valid application. */
    uint16_t               bank_0_crc;      /**< If bank is valid, this field will contain a valid CRC of the total image. */
    bootloader_bank_code_t bank_1;          /**< Variable to store if bank 1 has been erased/prepared for new image. Bank 1 is only used in Banked Update scenario. */
    uint32_t               bank_0_size;     /**< Size of active image in bank0 if present, otherwise 0. */
    uint32_t               sd_image_size;   /**< Size of SoftDevice image in bank0 if bank_0 code is BANK_VALID_SD. */
    uint32_t               bl_image_size;   /**< Size of Bootloader image in bank0 if bank_0 code is BANK_VALID_SD. */
    uint32_t               app_image_size;  /**< Size of Application image in bank0 if bank_0 code is BANK_VALID_SD. */
    uint32_t               sd_image_start;  /**< Location in flash where SoftDevice image is stored for SoftDevice update. */
} bootloader_settings_t;

A successful DFU of the application will result in the bank_0 field of the bootloader_settings_t struct being set to BANK_VALID_APP = 0x01 and the bank_0_size field is set to the size of the application.

Best regards Bjørn