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

Firmware Crash on ble_stack_init()

The firmware crashes when passing the ble_stack_init() when the firmware is download but in debug mode it works fine. The screen shots below shows this event.

We are using S132 and nRF5_SDK_17.0.2_d674dde

Code Snippet

On this scope shots we can see that on debug mode the test point would go low after around 2 seconds but on downloaded it didn't go low even after 3 seconds and more.

Debug Mode

Downloaded

Any thoughts on what is causing this issue?

Parents
  • Hi there

    First off, there shouldn't be any HW restrictions as long as you have followed our reference circuitry. We could do a HW review for you if you have the gerber files and schematics available. But I would suggest creating a private case for that.

    I'm afraid I got no specific things to check out based on your main file (which looks okay), but I have a few suggestions based on similar issues in the past.

    • What kind of debugger are you using? A DK or a J-Link device from SEGGER?
    • What backend are you using for logging if you're using logging at all? You can try disabling that altogether by setting NRF_LOG_ENABLED to 0 in your sdk_config.h file, and you can try inverting the NRF_LOG_BACKEND_RTT_ENABLED and NRF_LOG_BACKEND_UART_ENABLED defines (one of them is usually set to 0 while the other is 1).
    • It's also possible that your board is latched into SWD/debug mode when you power it up. If so, you might need a pulldown on the SWCLK pin, or try to power cycle the board entirely after flashing your application onto it.

    Best regards,

    Simon

Reply
  • Hi there

    First off, there shouldn't be any HW restrictions as long as you have followed our reference circuitry. We could do a HW review for you if you have the gerber files and schematics available. But I would suggest creating a private case for that.

    I'm afraid I got no specific things to check out based on your main file (which looks okay), but I have a few suggestions based on similar issues in the past.

    • What kind of debugger are you using? A DK or a J-Link device from SEGGER?
    • What backend are you using for logging if you're using logging at all? You can try disabling that altogether by setting NRF_LOG_ENABLED to 0 in your sdk_config.h file, and you can try inverting the NRF_LOG_BACKEND_RTT_ENABLED and NRF_LOG_BACKEND_UART_ENABLED defines (one of them is usually set to 0 while the other is 1).
    • It's also possible that your board is latched into SWD/debug mode when you power it up. If so, you might need a pulldown on the SWCLK pin, or try to power cycle the board entirely after flashing your application onto it.

    Best regards,

    Simon

Children
No Data
Related