USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Amanda Hsieh — Tue, 15 Apr 2025 15:57:46 GMT

This case was created three years ago. Please create a new support case for your issue.

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

sniper15 — Tue, 15 Apr 2025 08:38:45 GMT

how do you resolve that,i have a same problem

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Karlo — Fri, 10 Dec 2021 12:27:51 GMT

Ok, no prob.

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Amanda Hsieh — Fri, 10 Dec 2021 11:57:35 GMT

Hi,

Are you working on the same case? If not, please create a new support case for your own. I will start vacation next week and wouldn't reply to this case.

-Amanda

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Karlo — Fri, 10 Dec 2021 07:42:46 GMT

As I said before, the issue is the same. I just provided you a log to help you debug it...

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Amanda Hsieh — Fri, 10 Dec 2021 07:29:48 GMT

Hi,

Please create a new support case for your own issue. Thanks.

-Amanda

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Karlo — Wed, 08 Dec 2021 14:49:38 GMT

Hi, i have same issue, when DFU process was interrupted DFU gets stuck and cant resume with update. It only happens when updating via USB (nrfutil).
Here is log

<warning> nrf_dfu_serial_usb: Could not read from CDC. Error: 0x92.
<debug> nrf_dfu_serial: Set receipt notif target: 0
<debug> nrf_dfu_serial_usb: Allocated buffer 20009D10
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_RECEIPT_NOTIF_SET
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x2, 0x1]
<debug> nrf_dfu_serial: Received serial mtu
<debug> nrf_dfu_serial_usb: Allocated buffer 20009D10
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_MTU_GET
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x7, 0x1]
<debug> nrf_dfu_serial_usb: Allocated buffer 20009D10
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_SELECT (command)
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x6, 0x1]
<debug> nrf_dfu_serial_usb: Allocated buffer 20009D10
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_EXECUTE (command)
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
<info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
source, write not needed. Skipping.
<debug> nrf_dfu_req_handler: Writing valid init command to flash.
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x4, 0x1]
<debug> nrf_dfu_serial_usb: Allocated buffer 20009D10
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_SELECT (data)
<debug> nrf_dfu_req_handler: crc = 0x0, offset = 0x0, max_size = 0x1000
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x6, 0x1]
<debug> nrf_dfu_serial_usb: Allocated buffer 20009D10
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_CREATE (data)
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x00027000, len=1 pages), queue usage: 0
<debug> nrf_dfu_req_handler: Creating object with size: 4096. Offset: 0x00000000, CRC: 0x00000000
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x1, 0x1]
<debug> nrf_dfu_serial_usb: Allocated buffer 2000A514
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00027000, src=0x20009D14, len=1024 bytes), queue usage: 1
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial_usb: Allocated buffer 2000AD18
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00027400, src=0x2000A518, len=1024 bytes), queue usage: 2
0x1
<error> nrf_dfu_serial_usb: Failed to allocate buffer!
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00027800, src=0x2000AD1C, len=1024 bytes), queue usage: 3
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<error> nrf_dfu_serial_usb: Failed to allocate buffer!
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
<error> nrf_dfu_req_handler: Write request too long
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x3
<warning> nrf_dfu_serial: DFU request completed with result: 0x3
<debug> nrf_dfu_flash: Flash erase success: addr=0x00027000, pending 3
<debug> nrf_dfu_flash: Flash write success: addr=0x00027000, pending 2
<debug> nrf_dfu_flash: Flash write success: addr=0x00027400, pending 1
<debug> nrf_dfu_flash: Flash write success: addr=0x00027800, pending 0

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Amanda Hsieh — Tue, 28 Sep 2021 07:39:31 GMT

Hi,

Does the issue also happen to the unmodified SDK 15.2 bootloader?

[quote user="m.li"]Yes, the device is able to be DFU successfully when nrfutil is not interrupted.[/quote]

Can the application run successfully after DFU updating?

[quote user="m.li"]We did not log yet as it is a bit difficult to get debug messages set up with the bootloader. Will update with the log when it is available.[/quote]

It's good to have log to know what happen on the device.

[quote user="m.li"]We are only updating the Application.[/quote]

What is the application? Does it require SD s140_nrf52_7.2.0 to run? Does the board already contain SD s140_nrf52_7.2.0 before DFU updating?

It seems you are running usb-bootloader based on SDK15.2 to update the application running with s140_nrf52_7.2.0. Is that right?

-Amanda

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

m.li — Mon, 27 Sep 2021 14:06:20 GMT

> Have you tried to disable the MSD class as the warning suggested (Disabling MSD - remember power-cycle at the end)?

We have tried to disable MSD on the J-Link but it did not make a difference. We are also not using the Development Kit.

> Are you able to update successfully without the keyboard interrupt?

Yes, the device is able to be DFU successfully when nrfutil is not interrupted.

> Can you provide the debug log while the error happened?

We did not log yet as it is a bit difficult to get debug messages set up with the bootloader. Will update with the log when it is available.

> What do you update? SD+BL or SD+BL+APP?

We are only updating the Application.

> Please post the command you are using to generate the package.

We use this command to generate the DFU package:

nrfutil pkg generate --hw-version 52 --application-version 0 --application app.hex --sd-req 0x00 --sd-id 0x0100 --key-file ../NordicSDK/keys/private.key app_dfu_package.zip

Thanks for your reply.

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

Amanda Hsieh — Fri, 24 Sep 2021 12:50:32 GMT

Hi,

Sorry for the delay.

Have you tried to disable the MSD class as the warning suggested (Disabling MSD - remember power-cycle at the end)?

Are you able to update successfully without the keyboard interrupt?

Can you provide the debug log while the error happened?

What do you update? SD+BL or SD+BL+APP?

Please post the command you are using to generate the package.

See my explanation in this post.

-Amanda

RE: USB-BLE Bootloader stuck unable to DFU after DFU process was interrupted

m.li — Tue, 21 Sep 2021 19:52:30 GMT

Additional question: Is there a way to force the bootloader to restart the DFU from the start (i.e. no resuming) if it is interrupted during the DFU process?

Edit: I've found a workaround by changing nrf_bootloader_fw_activate() in nrf_bootloader_fw_activation.c:

    switch (p_bank->bank_code)
    {
...
        case NRF_DFU_BANK_INVALID:
        default:
            nrf_dfu_settings_progress_reset(); // Added to force a DFU progress reset if the DFU was interrupted
            NRF_LOG_INFO("No firmware to activate.");
            return ACTIVATION_NONE;
    }

Will this have unintended effects on the rest of the bootloader operations?