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

[John]

With SDS 6.0.0 shouldn't the application start at 0x14000 rather than 0x16000?

[Hugh]

As John points out, the lower application address is 0x14000; the only other change we made for successful operation was the following (which I think you made):

   // Initialize the SoftDevice handler module.
   #if defined(BOARD_PROTO_1)
      // Note no 32kHz crystal on the Fujitsu module
      SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, false);
   #else
      SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, false);
   #endif

[George]

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.

[John]

You are welcome. Unfortunately I do not have the knowledge to help you with your current hurdle. Hopefully someone answers the other question you opened on the error code