SoftDevice s110 and SDK v6.1

RE: SoftDevice s110 and SDK v6.1

OlegT — Tue, 18 Oct 2016 07:18:04 GMT

Yeah, You are right here. I haven't. Now I chose NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION and this stage is done. Device connected. Thank You.

RE: SoftDevice s110 and SDK v6.1

Sigurd — Mon, 17 Oct 2016 15:20:24 GMT

Do you have an external crystal on the custom board ? What CLOCK_SOURCE do you use when calling SOFTDEVICE_HANDLER_INIT(CLOCK_SOURCE ,USE_SCHEDULER) ? Try to call SOFTDEVICE_HANDLER_INIT() with the interal crystal CLOCK_LFCLKSRC_SRC_RC

RE: SoftDevice s110 and SDK v6.1

OlegT — Mon, 17 Oct 2016 14:34:57 GMT

No, I don't hit. I go to SOFTDEVICE_HANDLER_INIT() and that's all, I never hit to next line. In uint32_t softdevice_handler_init() I go to line 231 and that's all, I can't hit to 232 line breakpoint. And if I stop program when I'm in softdevice_handler_init() in call stack I don't see nothing, only main() function; IROM1 0x16000 start, size 0x9000; IRAM1 0x20002000 start, size 0x2000;

RE: SoftDevice s110 and SDK v6.1

Sigurd — Mon, 17 Oct 2016 14:05:36 GMT

How do you know that the code is stopping at SOFTDEVICE_HANDLER_INIT? If you add a breakpoint in line 508 in main.c ble_enable_params_t ble_enable_params;, do you hit that breakpoint?

Also, what IROM/IRAM settings are you using?

RE: SoftDevice s110 and SDK v6.1

OlegT — Mon, 17 Oct 2016 13:56:42 GMT

Done. I don't get to this function and to this line too.

RE: SoftDevice s110 and SDK v6.1

Sigurd — Mon, 17 Oct 2016 13:49:57 GMT

Uncomment line 123 in main.c: ble_debug_assert_handler(error_code, line_num, p_file_name); And add a breakpoint in ble_debug_assert_handler line 52.

RE: SoftDevice s110 and SDK v6.1

OlegT — Mon, 17 Oct 2016 13:39:27 GMT

I had level 0 optimization. We can't do break point in " .h". I place break point in app_error_handler() in main.c (it called from APP_ERROR_HANDLER (it called from APP_ERROR_CHECK)) and it didn't get to this break point.

RE: SoftDevice s110 and SDK v6.1

Sigurd — Mon, 17 Oct 2016 13:13:15 GMT

Set optimization level 0 in target options -> C/C++ and define DEBUG in the preprocessor symbols.
Place a break point next to while(loop)(line 59) and line 57, in app_error.h
What for the error to happen, and read the value.

RE: SoftDevice s110 and SDK v6.1

OlegT — Mon, 17 Oct 2016 12:57:08 GMT

I sayd it. 231: err_code = 0; 234: err_code - don't know because it can't perform sd_softdevice_enable() function and then when I press Stop I see only "main" in call stack. Board is custom, but in SDK I try template from nrf6310. There is disassembly, last command that mcu do - 0x00018CF6 DF10 SVC 0x10 after it - nothing.

  231:     err_code = sd_softdevice_enable(clock_source, softdevice_assertion_handler); 
0x00018CF2 4937      LDR      r1,[pc,#220]  ; @0x00018DD0
0x00018CF4 9801      LDR      r0,[sp,#0x04]
0x00018CF6 DF10      SVC      0x10
0x00018CF8 4605      MOV      r5,r0
   232:     if (err_code != NRF_SUCCESS)

RE: SoftDevice s110 and SDK v6.1

Sigurd — Mon, 17 Oct 2016 10:55:18 GMT

What board are you using? The board code starts with PCA + number.

Could you insert a breakpoint in softdevice_handler.c, line 231 and 234, and see what the return code is when debugging?

RE: SoftDevice s110 and SDK v6.1

OlegT — Mon, 17 Oct 2016 10:01:42 GMT

No error returning. It go softdevice_handler_init() -> then calling function sd_softdevice_enable(clock_source, softdevice_assertion_handler); clock_source = 0x00000008; softdevice_assertion_handler = 0x00018c00; and this function didn't return any error code.

RE: SoftDevice s110 and SDK v6.1

Sigurd — Mon, 17 Oct 2016 09:14:07 GMT

According to the compatibility matrix, you are using the correct SoftDevice version (7.3.0). This SoftDevice version uses 88 kB.

In SDK v6.1 the example called ble_app_template is setup to be used with the nRFgo Motherboard (nRF6310), is this the board you are using? Is the softdevice_handler_init(..) function returning any error codes?