RE: Serial DFU causing nrf_dfu_flash: Flash write failed (0x3)

Galaxy88 — Tue, 28 Jul 2020 16:27:52 GMT

Thank you Turbo J, your answer made me discover that both the source and destination address to nrf_df_flash have to be 4 byte aligned. Works like a charm now.

RE: Serial DFU causing nrf_dfu_flash: Flash write failed (0x3)

Galaxy88 — Mon, 27 Jul 2020 19:19:00 GMT

Thank your response, I have changed the packet size to 130 so I can get a data size of 128 as suggested but I still have the same error as logged below. Am I still missing something?

EDIT: Both the source and destination address to nrf_df_flash have to be 4 byte aligned, problem solved. Removing SLIP has the side effect of misalignment of the source address in RAM caused by the OPCODE

<debug> nrf_dfu_validation: Write address set to 0x00026000
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
<info> nrf_dfu_settings: Backing up settings page to address 0x7E000.
<debug> nrf_dfu_settings: Destination settings are identical to 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]
<info> app:  Transfer completed. Received: 0 bytes
<info> app:  No command received start RX again
<info> app:  Transfer completed. Received: 6 bytes
<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: 0
<debug> nrf_dfu_flash: Flash erase success: addr=0x00026000, pending 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]
<info> app:  Transfer completed. Received: 0 bytes
<info> app:  No command received start RX again
<info> app:  Transfer completed. Received: 129 bytes
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00026000, src=0x20007273, len=128 bytes), queue usage: 1
<debug> nrf_dfu_flash: Flash write failed (0x3): addr=0x00026000, len=0x80 bytes, pending 0
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<info> app:  Transfer completed. Received: 129 bytes
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00026080, src=0x20007273, len=128 bytes), queue usage: 1
<debug> nrf_dfu_flash: Flash write failed (0x3): addr=0x00026080, len=0x80 bytes, pending 0
<debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
<info> app:  Transfer completed. Received: 129 bytes
<debug> nrf_dfu_req_handler: Handle NRF_DFU_OP_OBJECT_WRITE (data)
<debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x00026100, src=0x20007273, len=128 bytes), queue usage: 1
<debug> nrf_dfu_flash: Flash write failed (0x3): addr=0x00026100, len=0x80 bytes, pending 0

RE: Serial DFU causing nrf_dfu_flash: Flash write failed (0x3)

Turbo J — Mon, 27 Jul 2020 17:37:03 GMT

You are trying to write to an odd flash address - this won't work. Flash writes must be 4-byte aligned.

In your case, write 128 bytes per DFU packet and not 127. Any yes, that means your raw packet will be a bit larger than 128 bytes.