ble_app_uart example not working nRF52833 and S140

RE: ble_app_uart example not working nRF52833 and S140

trashman — Tue, 30 Mar 2021 13:17:46 GMT

Yeah, but there is an answer for that. I used my own modified beacon example. I've just checked sdk_configs in both places. The one which worked (beacon) had NRF_SDH_CLOCK_LF_SRC set to NRF_CLOCK_LF_SRC_RC, while the other had NRF_CLOCK_LF_SRC_XTAL. The XTAL version worked with my previous ebyte, but it seems it does not work with the new one (other model). 🙂

RE: ble_app_uart example not working nRF52833 and S140

Vidar Berg — Tue, 30 Mar 2021 13:08:04 GMT

Hello,

No problem, thanks for the update. It's only a bit suprising that the ble_app_beacon example worked then, it selects the external 32 KHz crystal by default as ble_app_uart.

RE: ble_app_uart example not working nRF52833 and S140

trashman — Tue, 30 Mar 2021 12:44:36 GMT

Hello, thank you for your reply. Yes, I used pca10100 configuration, I tried both provided hex file and compiled by myself. It seems you were right about clock source. After this little change I can now see Nordic_UART device in nRF Connect app. Thanks a lot!

RE: ble_app_uart example not working nRF52833 and S140

Vidar Berg — Tue, 30 Mar 2021 11:40:04 GMT

Hello,

Did you select the pca10100 configuration (board name for nRF52833 DK) when you built the ble_app_uart project for your module?

[quote user=""]I tried debugging with GDB, it seems that the problem is encountered when `sd_softdevice_enable` is called. [/quote]

It's almost always a problem with the low frequency clock source if the program hangs inside sd_softdevice_enable() call. Not sure if that is the case here, but as a test, please try to change to the 'SYNTH' clock source in sdk_configh (NRF_SDH_CLOCK_LF_SRC==NRF_CLOCK_LF_SRC_SYNTH) to see if you get the same result.

Can you post the CPU registers you see in GDB when the code hangs?