On nRF Connect application, my phone can't find my custom board.

Question

Hi, I'm using metamotionR of Mbientlab that have nRF 52832 ( I attached the circuit of metamotionR ) 
 but, I want to develop new firmware on this device. so, I started with secure_bootloader_ble_s132_pca10040, the example of SDK 16. 
 Before the test of my device, I tried my nRF52 DK Board with the example, it worked very well! 
 And then, after changing the board definition along my board, I tested my device. the result is that my device can turn on its LEDs, but On nRF Connect of my two cellphones( iPhoneX and LG Smartphone ), I can't find this device. so, may I ask you somebody what causes this problem ? 
 Please help me...

bjorn-spockeli · Accepted Answer

HI Wongi The SDK examples are configured to use run on the Nordic development kits with an external 32kHz crystal as the Low Frequency clock source- It does not seem that the metamotionR board has an external 32kHz crystal by looking at the block diagram. So it could be that you need to alter the sdk_config.h to the following to use the internal RC oscillator instead of the XTAL. // //========================================================== // Clock - SoftDevice clock configuration //========================================================== // NRF_SDH_CLOCK_LF_SRC - SoftDevice clock source. // <0=> NRF_CLOCK_LF_SRC_RC // <1=> NRF_CLOCK_LF_SRC_XTAL // <2=> NRF_CLOCK_LF_SRC_SYNTH #ifndef NRF_SDH_CLOCK_LF_SRC #define NRF_SDH_CLOCK_LF_SRC 0 #endif // NRF_SDH_CLOCK_LF_RC_CTIV - SoftDevice calibration timer interval. #ifndef NRF_SDH_CLOCK_LF_RC_CTIV #define NRF_SDH_CLOCK_LF_RC_CTIV 16 #endif // NRF_SDH_CLOCK_LF_RC_TEMP_CTIV - SoftDevice calibration timer interval under constant temperature. // How often (in number of calibration intervals) the RC oscillator shall be calibrated // if the temperature has not changed. #ifndef NRF_SDH_CLOCK_LF_RC_TEMP_CTIV #define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2 #endif // NRF_SDH_CLOCK_LF_ACCURACY - External clock accuracy used in the LL to compute timing. // <0=> NRF_CLOCK_LF_ACCURACY_250_PPM // <1=> NRF_CLOCK_LF_ACCURACY_500_PPM // <2=> NRF_CLOCK_LF_ACCURACY_150_PPM // <3=> NRF_CLOCK_LF_ACCURACY_100_PPM // <4=> NRF_CLOCK_LF_ACCURACY_75_PPM // <5=> NRF_CLOCK_LF_ACCURACY_50_PPM // <6=> NRF_CLOCK_LF_ACCURACY_30_PPM // <7=> NRF_CLOCK_LF_ACCURACY_20_PPM // <8=> NRF_CLOCK_LF_ACCURACY_10_PPM // <9=> NRF_CLOCK_LF_ACCURACY_5_PPM // <10=> NRF_CLOCK_LF_ACCURACY_2_PPM // <11=> NRF_CLOCK_LF_ACCURACY_1_PPM #ifndef NRF_SDH_CLOCK_LF_ACCURACY #define NRF_SDH_CLOCK_LF_ACCURACY 1 #endif Best regards Bjørn

On nRF Connect application, my phone can't find my custom board.

Top Replies