nRF5340 drop connection before going to low power

Hi, 

I´m using a Fanstel BC40M board with a nRF5340 on board as a peripheral device.

Being connected to a central, it triggers some tasks in the peripheral. The peripheral does some task using some peripherals like SPIM, timers, PPI, etc., sends some BLE notifications and then sometimes drops connection before going to low power.

This happens on some devices and not on others (same firmware, same hardware).

The error is: Disconnected from device xx:xx:xx:xx:xx:xx, reason: BLE_HCI_CONNECTION_TIMEOUT

After a while the device reconnects but has the same behaviour.

I'm using Zephyr nRF Connect SDK 2.5.0.

So far, I have tried:

- Increase connection timeout.

- Define different crystal accuracies in prj.conf.

CONFIG_CLOCK_CONTROL_NRF_K32SRC_xxPPM
No success.
any clue?
Thank you!
Parents
  • Update:

    I added in prj.conf:

    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
    CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y
    It uses the internal RC instead of the 32Khz external crystal.
    Now things seem to be working on the board that failed.
    Do you think this is a board specific problem or there is something wrong with the 32Khz crystal configuration?
Reply
  • Update:

    I added in prj.conf:

    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
    CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y
    CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y
    It uses the internal RC instead of the 32Khz external crystal.
    Now things seem to be working on the board that failed.
    Do you think this is a board specific problem or there is something wrong with the 32Khz crystal configuration?
Children
No Data
Related