• State Verified Answer
  • Replies 14 replies
  • Subscribers 72 subscribers
  • Views 4672 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 115514
Options
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

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.

  • 0 in reply to Hung Bui

    Update: When I include the Hexfile in the bootloader column of the OTA Updater , the DFU works. But , this works only when I include hexfiles which already has the bootloader compiled with it. The Application bar of the OTA Updater does'nt seem to help in updating the firmware on the Board.

  • 0 in reply to Hung Bui

    @Roshan: It's a little bit strange. You sure you haven't modified the bootloader ? And you are using the latest OTA Updater, which is version 1.4 ?

    You can update the hex file in your question, please click edit and add the file. I would suggest to get a hex file before you do DFU (when you only have softdevice and bootloader) and then after you do DFU. Also maybe send me a hex file after you do DFU with the setting that work for you (using the bootloader textbox)

  • 0 in reply to Hung Bui

    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).

  • 0 in reply to Hung Bui

    Hi Hung, I have updated the File_after_BootloaderOTA.hex. I have a program running on a customised board. My goal was to include a OTA feature over ANT to it. I included the files which were used in the dfu_experimental_dualbank s210 to my program. Thus, the bootloader was included. But the application does not run. Also, I tried to update only the application ota_tester to the board. It does not update, even though 'Image is activated, do not power down device' is shown. Final goal: To be able to get my application to go bootloader mode,using a payload from ANTWAREII and updating OTA via ANT, and then to restart the application.

    Thank You.

Related
Terms of service