ANT DFU-OTA Update Fail

RE: ANT DFU-OTA Update Fail

Roshan007007 — Fri, 12 Aug 2016 14:46:34 GMT

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.

RE: ANT DFU-OTA Update Fail

Hung Bui — Fri, 12 Aug 2016 09:06:07 GMT

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.

RE: ANT DFU-OTA Update Fail

Roshan007007 — Thu, 11 Aug 2016 14:21:54 GMT

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?

RE: ANT DFU-OTA Update Fail

Hung Bui — Thu, 11 Aug 2016 07:53:58 GMT

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.

RE: ANT DFU-OTA Update Fail

Roshan007007 — Wed, 10 Aug 2016 15:03:24 GMT

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.

RE: ANT DFU-OTA Update Fail

Hung Bui — Wed, 10 Aug 2016 09:18:34 GMT

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

RE: ANT DFU-OTA Update Fail

Roshan007007 — Tue, 09 Aug 2016 14:15:45 GMT

The files are attached to the question.

RE: ANT DFU-OTA Update Fail

Hung Bui — Tue, 09 Aug 2016 09:07:30 GMT

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

RE: ANT DFU-OTA Update Fail

Roshan007007 — Mon, 08 Aug 2016 19:57:27 GMT

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.

RE: ANT DFU-OTA Update Fail

Roshan007007 — Mon, 08 Aug 2016 15:03:45 GMT

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 '?

RE: ANT DFU-OTA Update Fail

Hung Bui — Mon, 08 Aug 2016 14:35:08 GMT

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% ?

RE: ANT DFU-OTA Update Fail

Roshan007007 — Mon, 08 Aug 2016 14:22:26 GMT

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.

RE: ANT DFU-OTA Update Fail

Roshan007007 — Mon, 08 Aug 2016 14:13:51 GMT

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.

RE: ANT DFU-OTA Update Fail

Hung Bui — Mon, 08 Aug 2016 13:30:08 GMT

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