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,

Sorry for the late response.

We found that it was a bug that if you enable "Enable softdevice protection" when flashing the softdevice in nRFgo Studio , then the DFU bootloader won't be able to start the application.

So could you please test flashing the softdevice with the option "Enable softdevice protection" unchecked and let me know the result ?

afterOTA.hex

Bootloader: bootloader.hex

[Roshan007007]

No, it still does not get updated, even though it shows that the image has been updated , (don not power down device). No transmission of data, and the size of the application remains the same in nrfgo Studio.

[Roshan007007]

Also, after the image updated , when I click connect to device on the OTA Updater GUI, it connects displaying the "ANT OTA Updater", indicating that the new OTA Tester application hasn't been updated on the board.

[Hung Bui]

It worked fine for me. You mentioned that the "the size of the application remains the same in nrfgo Studio" , it shouldn't change because you can't see the actual size of the application. nRFGo Studio only shows you the size of bootloader and the start address of the bootloader.

Could you try to call nrfjprog --readcode filename.hex after you update and send me the hex file ?

Have you tried to uppload the hex file compiled for the broadcast_tx example ? After you uploaded correctly, LED2 should be blinking.

Do you see the percentage appear on the app increase from 0 to something and then to 100% ?

[Roshan007007]

It didn't work with the broadcast_tx_example. The LED2 doesn't blink. Im uploading using the Application bar on the OTA Updater using the hex files in the _build folder. Where do I send you the hex file generated by ' nrfjprog --readcode filename.hex '?