nRF51 OTA DFU not working after successful image verification

RE: nRF51 OTA DFU not working after successful image verification

Hung Bui — Thu, 07 May 2015 12:50:03 GMT

@diode: according to this you should send 0000000000000000a4020000 instead.

RE: nRF51 OTA DFU not working after successful image verification

diode — Wed, 06 May 2015 18:32:34 GMT

It seems the 12-byte file size packet is divided to three parts, the size of softdevice, bootloader and application. Since I was only transferring the application image, I wrote a packet like a40200000000000000000000 where 0x000002a4 is the size of application image. Was the packet format correct? Do I need to also include the size of SoftDevice and bootloader?

RE: nRF51 OTA DFU not working after successful image verification

diode — Wed, 06 May 2015 16:25:25 GMT

@HungBui I have used the command "nrfjprog --readcode filename.hex" to read out the image to hex files. You can find the hex before OTA here and after OTA here. A diff output shows they are not different. However, according to the log, the image verification is successful (returning request op code of 1). Also, I tried intentionally interrupt the OTA DFU in the middle, and read out the hex file after that. The file is also not different from the other two. What could happen in this process?

RE: nRF51 OTA DFU not working after successful image verification

Hung Bui — Wed, 06 May 2015 11:58:39 GMT

Hi Diode,

You can try to read out (using nrfjprog) the chip's binary to see if the image has been updated properly or not. If possible you can upload it (the bootloader hex file, the blinky hex and the readout hex file of your chip after you finish DFU) here so that I can have a look.

You can also debug the bootloader to see why it doesn't jump to your application. You can find information on how to change the bootloader configuration to support debugging here. If it's not easy to debug with Linux and gcc, you can try to sending information via UART for debugging.