Hello,
I am currently working with a custom nRF52832 module for UART communication. The firmware is based on the Nordic SDK’s ble_app_uart example, and the script runs perfectly on the official nRF52832 development board.
However, when I flash the same firmware to my custom nRF52832 module, the BLE functionality works but the app_timer (RTC-based) and uart communication functionality does not work.
After debugging, I noticed that the code gets stuck at a specific point repeatedly during execution, and it seems related to the RTC initialization or operation.
The custom module uses only one external 32 MHz crystal (for BLE), and does not have a 32.768 kHz LF crystal. I suspect the problem is due to the lack of the LF crystal, which is typically used for the RTC andapp_timer.after debugging i get my script everytime get stucked at debug data
<info> app_timer: RTC: initialized.
<info> app: Debug logging for UART over RTT started.
<info> app: Connected <info> app: Data len is set to 0xF4(244)
<info> app: p_evt->type: 2
<info> app: BLE_NUS_EVT_RX_DATA: 0
getting stucked after this and nothing work
Could you please confirm:
-
Is it mandatory to have an external 32.768 kHz crystal for
app_timerto work properly? -
Can I configure the firmware to use the internal RC oscillator (RCOSC) as the LFCLK source instead?
-
Are there any specific SDK configurations or changes I need to make in
sdk_config.hor system initialization to switch to the RC oscillator?Any help or guidance on resolving this issue would be greatly appreciated.
Best regards,
Shambhu Jangid
