DFU - Bootloader fails to complete update with error 'Request to copy BL failed'

RE: DFU - Bootloader fails to complete update with error 'Request to copy BL failed'

Hung Bui — Tue, 11 Jun 2019 08:55:58 GMT

In new softdevice (v6.1.1) we has updated the MBR so it will use the NRF_MBR_PARAMS_PAGE_ADDRESS to store the bootloader location and setting instead of UICR. But it's still backward compatible, it will check the UICR if the MBR param page is empty.

RE: DFU - Bootloader fails to complete update with error 'Request to copy BL failed'

Anne van Rossum — Fri, 07 Jun 2019 14:58:25 GMT

What's the purpose of NRF_MBR_PARAMS_PAGE_ADDRESS if it needs to be set in UICR anyway?

RE: DFU - Bootloader fails to complete update with error 'Request to copy BL failed'

rjdunn — Mon, 03 Dec 2018 16:00:01 GMT

Thanks for your reply!

For the step you are asking about ('Upload the concatenated binary to our custom board's Flash'), I'm using X-Modem to transfer a binary containing INIT_PACKET+BL_IMAGE to the NVM of the custom board. A task running on the host chip of the custom board then starts the DFU process. Next, via SPI, it transfers the Init Packet first, then the BL Image, to the NRF52. For each of these transfers the task runs through the sequence of operations defined here.

The changes made to the secure_serial Bootloader were mostly related to SPI functionality, and removal of serial functionality. Otherwise, they are very similar.

With regard to NRF_UICR_MBR_PARAMS_PAGE_ADDRESS, I see that in the file dfu_settings.c, the variable 'm_uicr_mbr_params_page_address' is set to NRF_MBR_PARAMS_PAGE_ADDRESS which is 0x7E000, Also I've confirmed that this address is still 0x7E000 during runtime, by printing it when the error occurs. Same for the start-address of the bootloader (NRF_UICR_BOOTLOADER_START_ADDRESS).

I may be mistaken but is the linker file responsible for writing the correct values to these addresses? I have attached my linker file here, as perhaps there is an issue with it that I'm not aware of. Again, it is the same file as that used in the secure_serial_dfu example.

Do you know if it is required to build the bootloader settings.hex and concat it with the BL for the DFU of the BL to work? I haven't seen this specified anywhere, but just wondering if this is the missing piece.

Lastly, which file is the code snippet you posted in? I have searched the entire SDK for the vars 'm_check_copy_bl_params', and 'EMPTY_FLASH_BITMAP', and they cannot be found..

Thanks again for your help

devzone.nordicsemi.com/.../secure_5F00_dfu_5F00_serial_5F00_gcc_5F00_nrf52.ld

RE: DFU - Bootloader fails to complete update with error 'Request to copy BL failed'

Hung Bui — Mon, 03 Dec 2018 14:20:14 GMT

Hi,

Could you let me know what exactly you did at this step "- Upload the concatenated binary to our custom board's Flash" ?

So the binary image of the bootloader is not transferred via SPI ?

Do you transfer the init data ?

I assume that you has made quite a significant change in the bootloader ?

We would need to have a look at your code to figure out what could be wrong here.

But have you made sure you written to NRF_UICR_MBR_PARAMS_PAGE_ADDRESS (UICR.NRFFW[1]) the address for MBR parameter ? NRF_MBR_PARAMS_PAGE_ADDRESS by default at 0x7E000. This value need to be written to NRF_UICR_MBR_PARAMS_PAGE_ADDRESS . If you use other address you need to write that into the UICR.

The address of the bootloader need to be written in NRF_UICR_BOOTLOADER_START_ADDRESS as well.

I attached is the snippet of the code in the MBR, most likely it's the NRF_UICR_MBR_PARAMS_PAGE_ADDRESS was not pointing to correct location.

m_check_copy_bl_params wouldn't return NOMEM.