Dual Bank DFU with external qspi flash over Thread

RE: Dual Bank DFU with external qspi flash over Thread

AS_Kalpa — Thu, 06 May 2021 17:56:50 GMT

Hi ashish!

I'm facing the same issue, but I can't achieve this:

[quote userid="85239" url="~/f/nordic-q-a/71469/dual-bank-dfu-with-external-qspi-flash-over-thread"]We have successfully directed incoming DFU packets to external QSPI flash by modifying nrf_dfu_flash_erase to qspi_earse in on_data_obj_create_request() and nrf_dfu_flash_store to QSPI store in on_data_obj_write_request().[/quote]

I did the same updates:

in on_data_obj_write_request():

in on_data_obj_create_request():

but I have my code stucked after the first write operation:

Can you give me any tips about your solution?

Thanks,

Alessio

RE: Dual Bank DFU with external qspi flash over Thread

Jørgen Holmefjord — Fri, 12 Feb 2021 13:29:46 GMT

I'm a bit confused by the log. It looks like it is copying the new firmware, is this not the case?

There seems to be some glitching or missing logs around line 41-42, so it is a bit hard to see exactly what happens. Disabling logging in the application should help you get all logs from bootloader. You may also configure the RTT to ble blocking if buffer is full, to make sure you get all logs.

RE: Dual Bank DFU with external qspi flash over Thread

ashish_shukla — Thu, 11 Feb 2021 13:39:18 GMT

Hi,

Thanks for your detailed explanation.

I'm using nRF5 SDK for Thread and Zigbee v4.0.0 which uses SDK 16.0

I doubt that there is something wrong with the way I'm debugging the boot loader.

In a working case - where DFU completes successfully and a new image boots. After successful completion of DFU image transfer, DFU client node is reset. After Node reset - I don't see any boot loader logs. I've to exit from JlinkExe process and reconnect with the device to get logs again. Now if I wait for sufficient amount of time - around 30 seconds, I get logs from new image.

If I don't wait for 30 seconds and immediately exit from JlinkExe process and connect with the device - I get boot loader logs but device firmware is not updated. I'm attaching logs for this case. By looking at logs - can you make sense of what's going wrong ?

devzone.nordicsemi.com/.../6708.logs.txt

Exiting immediately and reconnecting with the device is the only way to get boot loader logs.

RE: Dual Bank DFU with external qspi flash over Thread

Jørgen Holmefjord — Tue, 09 Feb 2021 17:03:51 GMT

Hi,

Which SDK version are you using?

If you are using the latest version, the Thread DFU Client application is not allowed to modify the bank_0 and bank_1 members in nrf_dfu_settings_t. These members will be copied from the Bootloader settings backup page by the following function:

static void settings_forbidden_parts_copy_from_backup(uint8_t * p_dst_addr)
{
#if NRF_DFU_IN_APP || NRF_BL_DFU_ALLOW_UPDATE_FROM_APP
    REGION_COPY_BY_MEMBER(settings_version, bank_current, p_dst_addr);
    REGION_COPY_BY_MEMBER(bank_0, write_offset, p_dst_addr);
    REGION_COPY_BY_MEMBER(sd_size, progress, p_dst_addr);
    REGION_COPY_BY_MEMBER(boot_validation_crc, peer_data, p_dst_addr);
#else
    REGION_COPY_BY_MEMBER(settings_version, enter_buttonless_dfu, p_dst_addr);
    REGION_COPY_BY_MEMBER(init_command, peer_data, p_dst_addr);
#endif
}

In order for the Thread DFU client to notify to the bootloader that there is a new firmware available, it writes the bank_current member (this happens in postvalidate() function in client):

if (!is_trusted)
{
    if (ret_val == NRF_DFU_RES_CODE_SUCCESS)
    {
        s_dfu_settings.bank_current = NRF_DFU_CURRENT_BANK_1;
    }
    else
    {
        nrf_dfu_settings_progress_reset();
    }
}

If the settings page is not valid (invalid CRC), the backup page will be restored. Are you able to debug the bootloader and see where it runs inside nrf_dfu_settings_reinit()?

Best regards,
Jørgen