BLE max delays and LP_CLK_RCX

Hi,

We're designing a system that consists of a DA1468x and a few sensors. We're very space constrained, so we've created our PCB without an external 32 KHz crystal, and are instead configuring the low power clock as LP_CLK_RCX. We need to wake the DA1468x every 40 ms to service our sensors. When we run on a DA14681 Pro development kit and utilize its 32 KHz crystal (LP_CLK_32768), everything works great. If, however, we switch to LP_CLK_RCX (still on the pro dev kit), we hit the BLE_MAX_DELAYS_ALLOWED assert in rwble.c.

Here are some steps to reproduce the problem using Dialog's pxp_reporter sample project and a DA14681 pro development kit:

1. Create a new project by cloning the pxp_reporter sample project.
2. In pxp_reporter_task.c, create a new timer to fire every 40 milliseconds and start it. Create an empty handler to be called when the timer expires.
3. Modify custom_config_qspi.h to use the RCX for the low power clock:
#define dg_configUSE_LP_CLK LP_CLK_RCX
4. Build the DA14681-01-Release_QSPI target.
5. Run the program on a DA14681 pro development kit.

The program will trigger the BLE_MAX_DELAYS_ALLOWED assert in rwble.c within 10 to 20 seconds.

What can we do to both wake the system every 40 milliseconds and utilize the LP_CLK_RCX setting? Would you recommend we increase the number of allowed BLE delays, perhaps setting BLE_MAX_DELAYS_ALLOWED to 10 or more?

Thanks!
David