I have a development board and load the client central BLE blinky to it, then the peripheral BLE blinky to my custom board and power up and the central development board stays LED 1 on and never switches to LED 2.

[americanhoney]

I have a development board and load the client central BLE blinky to it, then the peripheral BLE blinky to my custom board and power up and the central development board stays LED 1 on and never switches to LED 2.  Any suggestions?

[Kenneth]

Hi,

Make sure you have followed the getting started:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/nrf51_getting_started.html?cp=5_1_1

Depending on the example you are using, the LED1 and LED2 may have different meaning. Please refer to the central and peripheral example you are using on what they mean.

Kenneth

[americanhoney]

I see absolutely nothing there that addresses or can help with this situation so the RTFM reply doesnt help. additionally there only 1 single central BLE example in nRF5_SDK_15.3.0_59ac345 so the comment 'depending on the example you are using' is also not helpful.  lastly LED1 means not partnered, LED 2 means partnered (as explained by Nordic <aka you>)

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.3.0%2Findex.html

[Kenneth]

So I assume that if you were using 2pcs of nRF52-DK then the examples (blinky or otherwise) works as intended. I would not say that is clear from your description.

If you have found that the problem is in specific related to your own hardware, then ideally the next step I suggest is:

1. Check if you hardware have placed an external 32kHz crystal, if not, you will need to change the LFCLK source to RC (internal) instead of XTAL (external) when init the softdevice.

2. Once that is in place, check if the custom hardware is visible as a BLE beacon:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/ble_sdk_app_beacon.html 

[Kenneth]

I added some additional comments to previous replies, please have in mind that based on your case description the problem may be anything, and until you have a setup that you do know works (e.g. 2pcs of nRF52-DK) it is difficult to narrow down to what the problem may be.

[americanhoney]

i have a 32G Hz external clock. i will try changing it to internal.

and I do have a setup that works with 2 DK boards.  READ THE COMMENTS!!

[Kenneth]

I suggest to run DTM to test/verify your hardware, e.g.:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/ble_sdk_app_dtm_serial.html?cp=5_1_4_5 

This application note may be useful on how to setup DTM:
https://infocenter.nordicsemi.com/topic/struct_appnotes/struct/appnotes_nan34.html?cp=11_3 

A side question: The examples may be logging over UART, so make sure for instance that RXD pin is pulled high. Otherwise I think most of the pins are simple button/led for the blinky example at least.

[Kenneth]

Did anyone from Nordic review your custom board (schematic and layout)?

[Kenneth]

Any update on the issue?

Best regards,

Kenneth

[americanhoney]

No

[americanhoney]

I put 

NRF_CLOCK->LFCLKSRC=0;

as the first line in the main program.  didnt fix the problem though

[americanhoney]

even added:

NRF_CLOCK->TASKS_LFCLKSTART=0;
NRF_CLOCK->TASKS_LFCLKSTOP=1;
NRF_CLOCK->LFCLKSRC=0;
NRF_CLOCK->TASKS_LFCLKSTOP=0;
NRF_CLOCK->TASKS_LFCLKSTART=1;
while(!NRF_CLOCK->EVENTS_LFCLKSTARTED);

didnt work either

[Kenneth]

To change BLE clock source you should edit sdk_config.h, for instance

#define NRF_SDH_CLOCK_LF_SRC 0
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#define NRF_SDH_CLOCK_LF_ACCURACY 1

You may also need to edit generic LFCK usage:

#define NRFX_CLOCK_CONFIG_LF_SRC 0
#define CLOCK_CONFIG_LF_SRC 0

Please also comment on my other questions/comments:

- Results of DTM tests.

- Pulled up UART RXD line with external pull-up.

- Did anyone from Nordic review your custom board (schematic and layout)?