About the S132 SDK 17.0.2 DFU

RE: About the S132 SDK 17.0.2 DFU

Vidar Berg — Tue, 23 Nov 2021 10:58:56 GMT

The received image is apparently failing the hash validation check. Here is the error you getting:

NRF_DFU_EXT_ERROR_VERIFICATION_FAILED

The hash of the received firmware image does not match the hash in the init packet.

Link: nrf_dfu_ext_error_code_t

You can you read out the flash on the device to see how much the uploaded image differs from the correct image?

RE: About the S132 SDK 17.0.2 DFU

Chienheng — Tue, 23 Nov 2021 10:26:33 GMT

Thanks you answer! I changed the code.

Now I can continue the next step.

but when I ran to the last step (cmd: Excute, all the data was sent, offset and crc are correct),

I recieved the 0x60 0x04 0x0b 0x0c, what does it mean?

RE: About the S132 SDK 17.0.2 DFU

Vidar Berg — Tue, 23 Nov 2021 08:47:33 GMT

Hello,

[quote user=""]When I was sent the first block, I recieved the nofity: 0x60 0x03 0x03.[/quote]

The value 0x60 means this notification is a response to a request, where the following byte, 0x3 (NRF_DFU_OP_CRC_GET), is the request was in response to. And the final byte is the is the response code (NRF_DFU_RES_CODE_INVALID_PARAMETER).

But I don't understand why the bootloader would return this error for the CRC request. What happens if you set the packet receipt notification to '0', do you get the same error?

Best regards,

Vidar