This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ANT DFU-OTA Update Fail

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.

Parents
  • 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

  • Hi Roshan,

    From the hex file you sent me seems that the File_after_OTA.hex got something written to the application area (0xD000). I can't tell if it's the correct image or not. But it doesn't look the same as the application flashed on the File_after_BootloaderOTA.hex.

    Could you please also update the hex files of the application firmware you used to update and the bootloader you used ? So that I can test here.

    Please test with unmerged application (not combine with bootloader).

Reply
  • Hi Roshan,

    From the hex file you sent me seems that the File_after_OTA.hex got something written to the application area (0xD000). I can't tell if it's the correct image or not. But it doesn't look the same as the application flashed on the File_after_BootloaderOTA.hex.

    Could you please also update the hex files of the application firmware you used to update and the bootloader you used ? So that I can test here.

    Please test with unmerged application (not combine with bootloader).

Children
No Data
Related