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

Custom Bootloader

Hi all,

I'm trying to write a custom bootloader that must works in this way:

  1. The new image to flash is received by a uBlox GPRS modem that communicates with the nRF52832 using the SPI;
  2. Through SPI, I'm able to read the new binary file, validate him, and after, write the flash starting @ 0x0001F000 (I'm using S132 V3.0);
  3. I update the Bootloader Settings;
  4. After, when I call the nrf_bootloader_app_start(MAIN_APPLICATION_START_ADDR), that arrives until the last subfunction (nrf_bootloader_app_start_impl), the process remains locked and the new app don't starts;

The nRF52 is mounted in a custom board.

Any idea because this occurs?

Thank you!

Parents
  • Hi Roger,

    Yes, all the steps I've described are done in the Bootloader. My starting point has been the secure DFU bootloader, I've "cut" all the unnecessary code, keeping, obviusly modified, the enter check.

    Yes, the main app receives a notification by the modem when there's a new application and then perform a system reset. Of course, this check is done also every time the circuit is powered.

Reply
  • Hi Roger,

    Yes, all the steps I've described are done in the Bootloader. My starting point has been the secure DFU bootloader, I've "cut" all the unnecessary code, keeping, obviusly modified, the enter check.

    Yes, the main app receives a notification by the modem when there's a new application and then perform a system reset. Of course, this check is done also every time the circuit is powered.

Children
No Data
Related