• State Verified Answer
  • Locked Locked
  • Replies 13 replies
  • Subscribers 62 subscribers
  • Views 10110 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 114359
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ble_app_template always end at SVC_Handler

Arthur

Hi !

I'm using an nRF52 on PCA10040 board and nRF5_SDK_11.0.0_89a8197. I want to run the peripheral ble_app_template with SEGGER Embedded Studio v2.20. I correctly set the FLASH (0x1c000) and RAM (0x20002080) START address in the linker options. J-Link correctly downloads both SoftDevice and application (checked with nRFgo Studio).

After it reaches ble_stack_init() the program hangs in SVC_Handler.

I tried both s132_nrf52_2.0.0_softdevice.hex and s132_nrf52_2.0.1_softdevice.hex with the same results.

Parents
  • 0

    Based on your call stack my guess is that something is wrong with your 32 kHz clock configuration. sd_softdevice_enable() takes a parameter that needs to be populated with information about your clock. Are you using a devkit? If you are working on a custom board do you have an external crystal? There are lots of cases here on devzone regarding code hanging in sd_softdevice_enable(). Most often the issue is wrong clock configuration.

    Regarding the RAM requirement; it is a little tricky, but the SDK has implemented a debug feature using either SEGGER RTT or UART. If you use this feature the RAM settings will be printed out to your terminal.

Reply
  • 0

    Based on your call stack my guess is that something is wrong with your 32 kHz clock configuration. sd_softdevice_enable() takes a parameter that needs to be populated with information about your clock. Are you using a devkit? If you are working on a custom board do you have an external crystal? There are lots of cases here on devzone regarding code hanging in sd_softdevice_enable(). Most often the issue is wrong clock configuration.

    Regarding the RAM requirement; it is a little tricky, but the SDK has implemented a debug feature using either SEGGER RTT or UART. If you use this feature the RAM settings will be printed out to your terminal.

Children
No Data
Related