• State Verified Answer
  • Replies 4 replies
  • Subscribers 67 subscribers
  • Views 2740 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 103093
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

firmware hangs in softdevice

George

Hi,

I am using softdevice 6.0.0 and ble_app_hrs example in keil on a custom nRF51822 board. Compilation goes fine but when I try to debug I notice that the firmware seems to be hanging in the softdevice (WFE instruction) and execution never reaches the Application firmware at 0x16000.

I have flashed the softdevice using nRFgo Studio before programming with Keil but the firmware just hangs in the softdevice code (or so it seems).

I am trying to use the internal LF RC oscillator and have changed the application frimware accordingly. Could this be the reason for the softdevice locking up ?

Any ideas?

Thanks, George

Parents
  • 0

    Thanks John ..yes changing the start address to 0x14000 solves the issue.

    As you say clearly the start address needs to be 0x14000 so I'm not understanding why the Keil examples provided with the SDK are set to compile with start address 0x16000 (?)

    Thanks Hugh ..yes that is the only change I did as well.

    Now the firmware is jumping properly into the application section but still I have a problem. The ble_app_hrs example is failing when sd_ble_enable(&ble_enable_params) is called. This function is returning error code 5 ..(NRF_ERROR_NOT_FOUND right?).

    Commenting the following APP_ERROR_CHECK line allows the program to proceed through the rest of the firmware without any other error but of course nothing works.

Reply
  • 0

    Thanks John ..yes changing the start address to 0x14000 solves the issue.

    As you say clearly the start address needs to be 0x14000 so I'm not understanding why the Keil examples provided with the SDK are set to compile with start address 0x16000 (?)

    Thanks Hugh ..yes that is the only change I did as well.

    Now the firmware is jumping properly into the application section but still I have a problem. The ble_app_hrs example is failing when sd_ble_enable(&ble_enable_params) is called. This function is returning error code 5 ..(NRF_ERROR_NOT_FOUND right?).

    Commenting the following APP_ERROR_CHECK line allows the program to proceed through the rest of the firmware without any other error but of course nothing works.

Children
Related