Sending Response: [0x4, 0xB] in serial DFU ?

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Wed, 05 Aug 2020 05:51:18 GMT

it s working now.

the problem is application watch dog timer.now i increased watchdog greater than bootloader tinne inactivity. the reset wont happen it again.

Thanks for your support

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Thu, 30 Jul 2020 07:50:20 GMT

i m sending only command to enter booloader (second time).

1) when i connect rtt viewer , it hold on (ie bootloader mode.)

At the time i m sending dfu transfer, i not getting even ping response.

2) when i remove rtt viewer,it is entering into bootloader and then resetting back to previous application mode.

I m not including BL setting in Step 1.

it may cause any error

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Vidar Berg — Thu, 30 Jul 2020 07:42:00 GMT

Point 1-4 is clear, but I'm wondering if you are attempting to start the DFU transfer in step 5 or if you are only sending that one command to enter bootloader mode.

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Thu, 30 Jul 2020 06:40:04 GMT

1) First, i m programming merged (sd+ booloader hex) in the NRF through jlink.

2) Then i m sending appilaction bin to NRF through uart from MASTER controller.

3) It s updating the firmware and entering into application mode.

4) Above scenario is working fine.

5) Second attempt.i send a command to running application.Its entering into bootloader for few seconds.

And then back to application mode.

Kindly guide me

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Vidar Berg — Thu, 30 Jul 2020 06:15:36 GMT

In this test, are you starting the DFU transfer right after you have entered DFU mode, or do you only send the one command to jump from the app to the bootloader? The bootloader should stay in DFU mode for 2 minutes if you just enter DFU mode and do nothing.

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Wed, 29 Jul 2020 15:49:41 GMT

It entered boatloader after few seconds it back to application code.

But i set NRF_BL_DFU_INACTIVITY_TIMEOUT_MS 120000.

i dont know what do to next?

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Vidar Berg — Wed, 29 Jul 2020 09:25:57 GMT

[quote user="Mayuri"]how do i check whether its enter into bootloader or not?[/quote]

If you have LED(s) on your board you can use those to indicate when you are in DFU mode.

[quote user="Mayuri"]i put some log on bootloader code. But that also not printed in the second time while giving command .[/quote]

This is a known limitation with RTT logging in our examples (it does not work when transitioning from main app to bootloader and vice versa). You may try to disable logging in the app (temporarily) to see if that helps get you the log messages from the bootloader.

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Tue, 28 Jul 2020 13:46:53 GMT

yes, first time it entered into bootloader.

how do i check whether its enter into bootloader or not?

i put some log on bootloader code. But that also not printed in the second time while giving command .

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Vidar Berg — Tue, 28 Jul 2020 13:38:58 GMT

Does the bootloader start out in DFU mode the first time you program it with the Jlink? It sounds like maybe the buttonless mechanism is not working as intended. I.e., not putting the device into Bootloader DFU mode.

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Tue, 28 Jul 2020 12:44:15 GMT

Very first time i flashed secure uart dfu through jlink.

D:\NRF_SDk_latest\nRF5_SDK_15.2\nRF5_SDK_15.2\examples\dfu\secure_bootloader\pca10056_uart_debug\ses

In loader i changed to ../../../../../components/softdevice/s140/hex/s140_nrf52_6.1.0_softdevice.hex

After i send only application file from my master to NRF. It worked.

what did i wrong in that sending application file?

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Vidar Berg — Tue, 28 Jul 2020 11:14:20 GMT

Looks like you are using the same code as here: https://devzone.nordicsemi.com/f/nordic-q-a/64170/ota-over-serial-merging-with-application. Is the Softdevice enabled when you call boot_mode() in your app?

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Tue, 28 Jul 2020 11:06:27 GMT

I m using buttonless over UART.

still i m not enter into boot mode after giving below command.

#define BOOTLOADER_DFU_START 0xB1

void boot_mode()
{
 nrf_delay_ms(100);
               NRF_POWER->GPREGRET = BOOTLOADER_DFU_START;

              nrf_delay_ms(100);

              NVIC_SystemReset(); 
			  
			  }

what i did before merging part

1) bootloader hex + Bl settings merged output1.hex.

nrfutil settings generate --family NRF52840 --application ble_app_rscs_c_pca10056_s140.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 --key-file private.key bl_settings.hex

2) application hex + softdevice hex merged output2.hex

3. output1.hex and output2.hex merged together with final output file

mergehex --merge output1.hex output2.hex --output final_out.hex

after flashing the final out hex to my board running in application at first then

when changing to bootloader using buttonlesss with above inserted code .its entering but not properly timeout and also when sending a new firmware through serial not updating with the new firmware.

application memory

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0x26000

FLASH_SIZE=0xda000

RAM_START=0x20001cd0

RAM_SIZE=0x3e330

uart bootloader memory

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0xe4000

FLASH_SIZE=0x1a000

RAM_START=0x20000008

RAM_SIZE=0x3fff8

here is my memory location

kindly help me out. i have been hold on here for past 3 days.

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Vidar Berg — Tue, 28 Jul 2020 10:38:22 GMT

Good to hear that you were able to fix the upload issue by adding some delays. Regarding the "buttonless" mechanism, is the command to enter DFU mode sent over BLE or UART? The SDK does not provide any example for buttonless entry with UART, but it is pretty easy to implement. Just add a call nrf_pwr_mgmt_shutdown(NRF_PWR_MGMT_SHUTDOWN_GOTO_DFU); when you receive the command to enter DFU.

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Sat, 25 Jul 2020 14:43:03 GMT

It works fine without changing address.

Just increasing delay between create and command. I can able to download a bin file.

After i merged secure UART bootloader + Application file with buttonless.

Its not switching to bootloader mode whiile giving command.

here is my bootloader linker address

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0xe4000

FLASH_SIZE=0x1a000

RAM_START=0x20000008

RAM_SIZE=0x3fff8

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Turbo J — Sat, 25 Jul 2020 09:16:24 GMT

Application flash for S140 7.0.1 starts at 0x27000 and not at 0x26000.

Sounds like your app hex (or linker script) was written for an older softdevice.

RE: Sending Response: [0x4, 0xB] in serial DFU ?

mayuri — Sat, 25 Jul 2020 05:44:19 GMT

Now i get 01 response from nrf.As i follow this link.

After i started to sending image file from master mcu.

i m getting an error from NRF

nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x00026000, len=1 pages), queue usage: 1

<error> app: Received an error: 0x00000001!

Here is my NRF log

<info> app: Inside main
<debug> app: In nrf_bootloader_init
<debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> nrf_dfu_settings: Settings OK
<debug> app: Enter nrf_bootloader_fw_activate
<info> app: No firmware to activate.
<debug> app: Enter nrf_dfu_app_is_valid
<debug> app: No valid app to boot.
<debug> app: DFU mode because app is not valid.
<info> nrf_bootloader_wdt: WDT is not enabled
<debug> app: in weak nrf_dfu_init_user
<debug> app: timer_stop (0x20000024)
<debug> app: timer_activate (0x20000024)
<info> app: Entering DFU mode.
<debug> app: Initializing transports (found: 1)
<debug> nrf_dfu_serial_uart: serial_dfu_transport_init()
<debug> nrf_dfu_serial_uart: serial_dfu_transport_init() completed
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> app: Enter main loop
<debug> app: Shutting down transports (found: 1)
<debug> nrf_dfu_serial: Received ping 1
<info> nrf_dfu_serial_uart: Allocated buffer 2000378C
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_PING
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x9, 0x1]
<debug> app: Shutting down transports (found: 1)
<debug> nrf_dfu_serial: Set receipt notif target: 0
<info> nrf_dfu_serial_uart: Allocated buffer 2000378C
<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> app: Shutting down transports (found: 1)
<debug> nrf_dfu_serial: Received serial mtu
<info> nrf_dfu_serial_uart: Allocated buffer 2000378C
<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> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 2000378C
<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> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 2000378C
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_CREATE (command)
<debug> app: timer_stop (0x20000024)
<debug> app: timer_activate (0x20000024)
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x1, 0x1]
<debug> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 20003810
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (command)
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x3, 0x1]
<debug> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 2000378C
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (command)
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x3, 0x1]
<debug> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 20003810
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (command)
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x3, 0x1]
<debug> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 20003810
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_CRC_GET (command)
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<debug> nrf_dfu_serial: Sending Response: [0x3, 0x1]
<debug> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 20003810
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_EXECUTE (command)
<debug> nrf_dfu_validation: PB: Init packet data len: 64
<info> nrf_dfu_validation: Signature required. Checking signature.
<info> nrf_dfu_validation: Calculating init packet hash (init packet len: 64)
<info> nrf_dfu_validation: Verify signature
<info> nrf_dfu_validation: Image verified
<debug> app: Enter nrf_dfu_cache_prepare()
<debug> app: required_size: 0xACF4.
<debug> app: single_bank: false.
<debug> app: keep_app: false.
<debug> app: keep_softdevice: true.
<debug> app: SD_PRESENT: true.
<debug> app: Bank contents:
<debug> app: Bank 0 code: 0x00: Size: 0x0
<debug> app: Bank 1 code: 0x00: Size: 0x0
<debug> app: pass: 0.
<debug> app: cache_address: 0x26000.
<debug> app: cache_too_small: false.
<debug> app: keep_firmware: false.
<debug> app: delete_more: false.
<debug> nrf_dfu_validation: Write address set to 0x00026000
<debug> nrf_dfu_settings: Writing settings...
<debug> nrf_dfu_settings: Erasing old settings at: 0x000FF000
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x000FF000, len=1 pages), queue usage: 0
<debug> nrf_dfu_flash: Flash erase success: addr=0x000FF000, pending 0
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x000FF000, src=0x20003D14, len=348 bytes), queue usage: 1
<debug> nrf_dfu_flash: Flash write success: addr=0x000FF000, pending 0
<info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
<debug> nrf_dfu_settings: Writing settings...
<debug> nrf_dfu_settings: Erasing old settings at: 0x000FE000
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x000FE000, len=1 pages), queue usage: 1
<debug> nrf_dfu_flash: Flash erase success: addr=0x000FE000, pending 0
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x000FE000, src=0x20003E70, len=348 bytes), queue usage: 1
<debug> nrf_dfu_flash: Flash write success: addr=0x000FE000, pending 0
<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> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 20003810
<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> app: Shutting down transports (found: 1)
<info> nrf_dfu_serial_uart: Allocated buffer 20003810
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_CREATE (data)
<debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x00026000, len=1 pages), queue usage: 1
<error> app: Received an error: 0x00000001!

RE: Sending Response: [0x4, 0xB] in serial DFU ?

Turbo J — Fri, 24 Jul 2020 20:25:25 GMT

[quote userid="75183" url="~/f/nordic-q-a/64139/sending-response-0x4-0xb-in-serial-dfu"]warning> nrf_dfu_ver_validation: SD req not met.[/quote]

The softdevice in the chip is different from the softdevice required in the init packet.

You probably need to update the softdevice before you can DFU the new application.