DFU

[Mikael]

Hi,

I use a custom board, softdevice and boot loader.

I use DFU to update a slave chip firmware. Everything goes right until we invalidate and write flash :   

        // Invalidate bank, marking completion.
        nrf_dfu_bank_invalidate(&s_dfu_settings.bank_1);

        uint32_t ret_val = nrf_dfu_settings_write_and_backup(NULL);

the nrf_dfu_settings_write_and_backup lead to a HARDFAULT handler because of accessing flash :

[Mikael]

static inline void wait_for_flash_ready(void)
{
    while (NRF_NVMC->READY == NVMC_READY_READY_Busy) {;}
}

[Vidar Berg]

Hello,

Looks like you are handling DFU in the application code? In that case, you may find this post relevant: https://devzone.nordicsemi.com/f/nordic-q-a/69006/custom-dfu-process. Our bootloader enables write protection on the MBR param page at 0x7E000 by defaullt ( With BPROT if 52832 is used), which could explain the hardfault.

[Vidar Berg]

Is it your main application that calls nrf_dfu_settings_write_and_backup(), and not the bootloader? In that case, make sure the app is compiled with the NRF_DFU_IN_APP flag enabled.  This will prevent the nrf_dfu_settings module from attempting to erase the flash page protected by the BPROT — Block protection peripheral. And note that BPROT protection is automatically disabled in debug interface mode.

[Mikael]

sorry but I don't understand,

we use nordic bootloader for DFU.

then in our app we check if a new binary exist for our slave chip.

we load it in our chip and it is OK

then we always have hardfault handler on nrf_dfu_settings_write_and_backup()

even with NRF_BL_DFU_ALLOW_UPDATE_FROM_APP set to 1

please elaborate

Thanks

[Mikael]

I will try this

NRF_BL_DFU_ALLOW_UPDATE_FROM_APP set to 1 in bootloader

and

NRF_DFU_IN_APP set to 1 in our app.

Is that correct?