Custom Board vs DK and SD110 vs SD130

RE: Custom Board vs DK and SD110 vs SD130

bjorn-spockeli — Tue, 25 Jul 2017 15:09:23 GMT

No problem at all. Happy to hear that you found the cause of the issue :)

RE: Custom Board vs DK and SD110 vs SD130

Benjamin Schlegel — Tue, 25 Jul 2017 13:22:46 GMT

So okay I forgot that I have the 16kb RAM Version on my custom board. I adjusted my RAM to 16kB and now its all good. Sorry for the trouble :)

RE: Custom Board vs DK and SD110 vs SD130

Benjamin Schlegel — Tue, 25 Jul 2017 12:05:00 GMT

Im using Keil. Core Register R15 PC is 0xFFFFFFFE

RE: Custom Board vs DK and SD110 vs SD130

bjorn-spockeli — Tue, 25 Jul 2017 11:58:44 GMT

Which environment are you using? Keil, GCC or Segger Embedded Studio? Do you get any disassembly information, e.g. Program counter(PC) when you're debugging?

RE: Custom Board vs DK and SD110 vs SD130

Benjamin Schlegel — Tue, 25 Jul 2017 11:31:05 GMT

Yes i dont enter applications main() when debugging on custom hardware. I use exactly the same clock source you posted. Like stated in my last comment with experimental_ble_app_blinky I cant atleast debug my main

RE: Custom Board vs DK and SD110 vs SD130

Benjamin Schlegel — Tue, 25 Jul 2017 11:28:59 GMT

I tried experimental_ble_app_blinky from SDK12.3.0 with SD130V2 and this example I can debug. But in this example I run into error at line 456 which is SOFTDEVICE_HANDLER_INIT() with error code 7. I use here again NRF_CLOCK_LF_SRC_RC as clock source. Error Code is invalid param which again I dont understand

RE: Custom Board vs DK and SD110 vs SD130

bjorn-spockeli — Tue, 25 Jul 2017 11:27:13 GMT

So you do not enter application's main() at all when you're debugging on the custom hardware? You have defined NRF_CLOCK_LFCLKSRC as shown below in pca10028.h (or custom_board.h if you've created your own board file)?

#define NRF_CLOCK_LFCLKSRC      {.source        = NRF_CLOCK_LF_SRC_RC,            \
                                 .rc_ctiv       = 16,                                \
                                 .rc_temp_ctiv  = 2,                                \
                                 .xtal_accuracy = NRF_CLOCK_LF_XTAL_ACCURACY_250_PPM}

RE: Custom Board vs DK and SD110 vs SD130

Benjamin Schlegel — Tue, 25 Jul 2017 09:38:05 GMT

And I tested SDK V10 example with S130v1.0.0 and this also works on my custom hardware.

RE: Custom Board vs DK and SD110 vs SD130

Benjamin Schlegel — Tue, 25 Jul 2017 09:25:46 GMT

Flashed App with SDK v12.3.0 and S130v2.0.1 on the custom hardware cannot be debugged. In Debug mode program isnt running.

RE: Custom Board vs DK and SD110 vs SD130

bjorn-spockeli — Tue, 25 Jul 2017 09:21:57 GMT

An application built with SDK v10.0.0 against the S110 v8.0.0 or the S130 v1.0.0 header files will not run if you flash it to a nRF51822 together with the S130 v2.0.1 from SDK v12.3.0. You must ensure that the SoftDevice on the nRF51822 is compatible with the SoftDevice header files used in the application. Are you able to debug your application built with SDK v12.3.0 if you flash it to the nRF51822 along with the S130 v2.0.1?