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

Bootloader update OTA not working (Application OTA is working)

Hello,

I am tring to do a Bootloader update OTA using the bootlader DFU Dual Bank. Application update OTA is working fine while it is not the case for Bootloader update OTA.

For Bootloader update, I have tried with a Zip file and .bin + .dat files on NRFConnect (Android). In both scenarios, I can see that the file was successfully transferred to the nrf52. However the old bootloader does not get replaced with the new one. I have a led on the boards that tells me which bootloader is active. The leds shows the old boatloader running even that the transfer of the files was successful

SDK Version: 11 Chip: NRF52 softdevice: s132 2.0.0 The files were generated with nrfutil.exe

Application OTA is working perfectly. I just need to replace the bootloader OTA to support the Watchdog.

Any idea why the Bootlader update OTA is not working? and why i am not receiving any error message?

Thank you, Karim

Parents
  • I am currently testing on my own board. I do have few products with the modified bootloader that I would like to update, once I have the right bootloader

    1. I have managed to have a bootloader that handle an App with watchdog -> the issue here that I cannot update the bootloader in product currently having previous Bootlodder. Transfer OTA finishes successfully but it seems like the bootloader doesn't get swapped with the new one. I verified this with a led

    2. I tried your last solution in order to allow App update OTA with a bootloder not supporting Watchdog. What I did is before calling bootloader_util_reset() I added an infinite look and wait for the watchdog to fire a reset. in NRFconnect it keep opening the image file but then it restarts

    I think the best thing is to find a way to update directly the bootloader (option 1) in order to have all the products with the same bootloader

Reply
  • I am currently testing on my own board. I do have few products with the modified bootloader that I would like to update, once I have the right bootloader

    1. I have managed to have a bootloader that handle an App with watchdog -> the issue here that I cannot update the bootloader in product currently having previous Bootlodder. Transfer OTA finishes successfully but it seems like the bootloader doesn't get swapped with the new one. I verified this with a led

    2. I tried your last solution in order to allow App update OTA with a bootloder not supporting Watchdog. What I did is before calling bootloader_util_reset() I added an infinite look and wait for the watchdog to fire a reset. in NRFconnect it keep opening the image file but then it restarts

    I think the best thing is to find a way to update directly the bootloader (option 1) in order to have all the products with the same bootloader

Children
No Data
Related