nRFtoolbox Firmware update says "DFU Upload complete" but has failed

[dgerman]

IOS, nRF Toolbox 4.4.4, DFU Library version 4.1.1 

Attempting to flash to ruuvi with nRF52832 reports 

:INFO:Hash failure and

:INFO:Return false in CRC 

to J-Link RTT but gives no indication of failure to iPhone.

It must report error to iPhone.

:INFO:Storing 256 B at: 0x00037f00
:INFO:Before OP crc
:INFO:Received execute object
:INFO:Before OP execute
:INFO:Received create object
:INFO:Before OP create
:INFO:Storing 256 B at: 0x00038000
:INFO:Storing 256 B at: 0x00038100
:INFO:Storing 88 B at: 0x00038200
:INFO:Before OP crc
:INFO:Received execute object
:INFO:Before OP execute
:INFO:Hash failure
:INFO:Current bank is bank 1
:INFO:Waiting for other flash operation to finish.
:INFO:Erasing: 0x0007f000, num: 1
:INFO:Writing settings...
:INFO:Resetting device. 
:INFO:In nrf_dfu_transports_close
:INFO:Inside main
:INFO:In nrf_bootloader_init
:INFO:Return false in CRC
:INFO:In nrf_dfu_transports_init
SDH:WARNING:RAM size should be adjusted to 0xd868 

[Hung Bui]

Hi Dennis, 

Could you let me know a little bit more on how you did the DFU ? How did you generate the DFU .zip file ? Which file did you use ?

Did you flash the bootloader on the ruuvi ? Or it's the default bootloader provided by Ruuvi  ? 

Maybe it's useful to follow this guide. 

[dgerman]

I have not made any changes in bootloader.

I created the ZIP package with

nrfutil pkg generate --hw-version 52  --sd-req 0x91  --debug-mode    \

 --key-file ../../keys/ruuvi_open_private.pem     \

--application ruuvitag_b/s132/armgcc/_build/ruuvi_firmware.hex  dfu.zip

Then transferred it to my iPhone via email. Then used nRFtoolbox to try to flash it.

This procedure is usually successful.

+++++

I am not referring to the fact that there is a CRC error (although I do not know why),

I am only referring to the fact that nRFtoolbox says complete when it should say failed.

Isn't this in the nRFtoolbox app code?

[Hung Bui]

Hi Dennis, I have tried the DFU on Toolbox here and find the similar behavior. It seems that the app didn't check for the last response from the bootloader after the Execute function. We will check with the app team to fix the issue.