Attachments (0)
Nordic Case Info
  • Case ID: 208139
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

App gets stuck when jumping from bootloader

EarthLord

Greetings,

I'm having the same weird issue as this question, though I don't understand the answer to it https://devzone.nordicsemi.com/f/nordic-q-a/34447/app-gets-stuck-when-booted-from-bootloader-works-fine-without-bootloader---sdk15---0xcafebabe-in-registers

I'm using Eclipse + ARM GCC 6.2.1 , SDK15.0, S112 v6.0.0, NRF52810.

When the application + SD is flashed directly after erasing the flash everything works well.

The issue occurs when

  • When I merge the  App + SD with the bootloader + bootloader settings and then flash the merged hex
  • When a DFU over BLE occurs

The issue is the app is loaded and the initial LED blink and UART output is sent, but then it gets stuck. Note that I'm not using BONDS in the application.

Regards, Prithvi

  • 0

    since you say that

    LED blink and UART output is sent

    I assume you know for sure that the application is actually started. But do you know where it is stuck? could you connect a debugger and check, and maybe add DEBUG to your processor symbols and check if you end up in the app_error_handler?

  • +1 in reply to run_ar

    OK, here's the update. The application is in the DEBUG mode but there aren't any error messages. If I use GDB and at the point where it gets stuck if I `continue` the application runs properly.

    I've went back to the bootloader from here and worked from there and its working properly now. I had made some changes to the lfclk and app timer to make LED blink in the bootloader. I think that was the issue. Thanks for the help!

  • 0 in reply to EarthLord

    Can you share more about what was the problem and how you have solved it?

    Thanks,

    Elkana

  • 0 in reply to Elkana

    As I mentioned earlier, I think fiddling with the LFCLK and app timer might have caused the issue. The DFU project in the link in the earlier message is now working for us.

Terms of service