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

Bootloader does not start application

Hello,

I am trying to get my device (nrf52832) to do DFU OTA, and to do so I am programming the bootloader before programming the s132 softdevice and the application. However, the device seems to stay stuck in bootloader mode without ever starting the application. I am able to perform a DFU using a test application, so the bootloader is indeed functionnal. I have tried merging the bootloader settings file at this location : here. If I only program the softdevice and the application, everything works well (except dfu).

This does not fix my problem. Do my settings have to be different than the ones found in this file? I have already looked through a dozen posts on this site and have yet to find a solution that works. I am using SDK 9.2 and Eclipse gcc. Any help would be greatly appreciated!

Thanks!

Parents
  • I think the meged hex settings are different than the board that you are using. Any how in order to jump from bootloader mode to application the controller first checks weather there is valid flag set or not in the location BOOTLOADER_SETTINGS. So once try to write the value 0x01 using jprog That may resolve the issue

  • If you are uploading an application via dfu service and through the bootloader, then you are most certainly not flashing the application + softdevice + bootlaoder via the Jlink programmer. The memory region 0x7f000 will be written to by the bootloader, to indicate that the application is valid or not after the CRC, which explains why it is not erased. The above command is only for the first time you flash the chip via Jlink programmer, not for after a dfu via bootloader.

Reply
  • If you are uploading an application via dfu service and through the bootloader, then you are most certainly not flashing the application + softdevice + bootlaoder via the Jlink programmer. The memory region 0x7f000 will be written to by the bootloader, to indicate that the application is valid or not after the CRC, which explains why it is not erased. The above command is only for the first time you flash the chip via Jlink programmer, not for after a dfu via bootloader.

Children
No Data
Related