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?
Make sure you have followed the getting started:
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.
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>)
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.
Did anyone from Nordic review your custom board (schematic and layout)?
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)?
I didnt have to change generic LFCK usage
Thank you very much for the help.