ANT DFU-OTA Update Fail

[Roshan007007]

Hello,

I am trying the ANT-OTA DFU Update using an ANT Stick and the nr51422 pca 10028 board. The ANT Updater shows that the Image Upload is completed. I am uploading the s210 OTA Tester Application. But the application is not being loaded because the ANTWare II isn't detecting the ANT broadcast from the board. Also, the size of the application, when seen from the nrfgo Studio stays the same. I'm using the SDK 10 version.

File_before_OTA.hex : This is the Hex when the experimental_ant_bootloader is loaded on the board.

File_after_OTA.hex :This is the Hex after the ota_tester is loaded on the board via OTA Updater 1.4 (via application bar) .

File_after_BootloaderOTA.hex :This is the Hex after a custom file with boootloader is loaded on the board via OTA Updater 1.4 (via bootloader bar) .

nrf51422_xxac.hex: Application to be uploaded via OTA Updater.

Thank You.

[Hung Bui]

Hi Roshan,

I want the hex file you used to include into the application text box. The application hex file that you got after you compiled it with Keil/gcc. Not the one you got by dump out the flash by nrfjprog --readcode. I want to compare the hex you used with what updated in the flash.

I would strongly suggest you to test first with simple example from the SDK first before you test with your application. Please test with the ant_broadcast tx example.

[Roshan007007]

Hello Hung,

I have updated the application that I used to update with the OTA Updater. Yes, I have tested the SDK with the application using s310( not s210). This case works perfectly. With my customised application and board, it displays the information in the OTA Updater, but when the application is updated, the application does not start. So , the only thing it comes down to is, how is the application that I have attached differs from the application (Ota Tester). What would be the case when the sample bootloader doesn't work and I would need to write a new bootloader code?

[Hung Bui]

Hi Roshan,

If I could have had the information that example in the SDK can be updated successfully it would be much easier for me.

I checked your hex file you sent and the hex files you provided earlier (File_after_OTA.hex and File_after_BootloaderOTA.hex) the image quite doesn't match. Are you sure the hex are not modified you didn't recompile it with modification in the source code ?

I also try to do a OTA with the hex file you provided, I see no problem with it. The hex updated correctly in the correct location and seem to start as I can see LED 3 and LED 4 lit up.

I attached the hex file after OTA in my answer above for your reference. You can use any compare tool (such as Notepad ++ with Compare plugin) to compare the hex with your provided hex file and can see how the image is updated correctly. I also attached the hex file of the bootloader , that you can use to test. (SDK v10, S210 v5)

If the SDK example application image can be updated, there should be no reason your application shouldn't be updated. You can test by comment out anything in the main loop, and maybe do only a LED blinking in your application, just to test if the image is updated properly and started properly.

[Roshan007007]

Hi Hung, Thank you for your response. I will try it out with the s210. For some reason , the s310 Bootloader works. For now, I will consider this as the answer and the topic closed. Thank you.