Unable to advertise over bluetooth using custom board (Taiyo Yuden EYSHCNZWZ, nrf52832)

[mmak]

Hi,

I am currently working on a custom flex board using the Taiyo Yuden EYSHCNZWZ (based on the nrf52832). I am able to program the device with the soft device, bootloader, and application. I know the application I have uploaded is running as the LED I have connected to the module is able to blink using the app timer. 

Note that I am basing off my code using the ble_app_uart example and using the SDK15.0 and soft device v7.0.1.

However, I am unable to find my device over Bluetooth. I'm unsure whether or not it is a hardware or software issue, but I am leading towards software. Currently I have the following softdevice clock configuration set:

#define NRF_SDH_CLOCK_LF_SRC 1

#define NRF_SDH_CLOCK_LF_RC_CTIV 0

#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 0

#define NRF_SDH_CLOCK_LF_ACCURACY 7

I was wondering if I am missing any other configuration settings? Also, below is the block diagram of the taiyo yuden module showing the connected external lf and hf clocks.

[Einar Thorsrud]

Hi,

The LF clock configuration matches a 32.768 clock with 20 ppm accuracy, and that should be fine. Also, for advertising (which is what is relevant for finding the device over Bluetooth), the accuracy does not mean much. And as the LED blinks by the help of the app timer, the LF clock is running. So the issue resides somewhere else.

Did you start advertising in your application? Perhaps you can share your application so that I can have a look?

[mmak]

Hey! I can share my main file to you if it helps. 

 8304.main.zip 

[Einar Thorsrud]

Hi,

It looks like it should be advertising. Do you get any warnings when you build? Or runtime errors? Have you seen anything wile debugging? Also, how have you confirmed that it is not advertising (you cannot find it)?

[mmak]

Using segger studios and didnt see any warnings during building nor runtime errors.

Used my phone to check for nearby devices when the device is powered on and couldn't find it.

Is it possible that the issue can be hardware related then? 

[Einar Thorsrud]

It could be, but it is too early to conclude. Can you test a simple BLE example from the SDK (with minimal configuration changes if needed to run on your HW)? Also note that some OSs will filter out some types of advertisements, so if you have an extra DK or dongle it could be god to test with nRF Connect for Desktop, and see if you see the advertisement packets there.

[mmak]

Hey!

I was able to scan the device using the nrfconnect app instead of trying to find it using the traditional iphone bluetooth pairing menu.

I was able to find the device using an android device as well, although it mentions that I can only pair with the device through the use of an app (not sure why though, but this seems more of a software issue). 

Anywho, thanks for the help with the issue!