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
  • What you described may not explain why the bootloader update is not performed. I would suggest to test with a development kit (or your own board) not with the product that you can't flash with the programmer.

    Just to find the root cause.

    So you now have watchdog timer in your application code and you want to keep feeding it when you are in bootloader ? The last solution is to let the watchdog trigger the reset before you switch to bootloader (in stead of branching directly, let the watchdog reset and the bootloader will enter bootloader mode after checking the GPREGRET flag).

Reply
  • What you described may not explain why the bootloader update is not performed. I would suggest to test with a development kit (or your own board) not with the product that you can't flash with the programmer.

    Just to find the root cause.

    So you now have watchdog timer in your application code and you want to keep feeding it when you are in bootloader ? The last solution is to let the watchdog trigger the reset before you switch to bootloader (in stead of branching directly, let the watchdog reset and the bootloader will enter bootloader mode after checking the GPREGRET flag).

Children
No Data
Related