Hi Dialog,
Could you give an explanation, why we sometimes hit the ASSERT_WARNING(0) below, and what we should do to avoid this?
Info: we do not have a XTAL32 (32kHz crystal), but are using the internal RCX oscillator
in rwble.c line 233 ->
if ((DEVELOPMENT_DEBUG) && (USE_POWER_OPTIMIZATIONS))
{
slp_period_retained = slp_period;
/ /如果这个断言击中LP ISRlasts longer than the time
// that has been reserved via LP_ISR_TIME_XTAL32_CYCLES and LP_ISR_TIME_USEC.
if (sleep_lp_cycles && (sleep_lp_cycles < slp_period))
ASSERT_WARNING(0);
}
Best Regards,
Ciano Frost
Keywords:
Device:
Hi ciano,
This assertion probably means that the LP_Hanlder takes too much time to execute and the warning that you get means that it took more time for the BLE core to wake up that the calculated value. Please check a previous thread:
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/some-porblem-sleep-mode
Thanks, PM_Dialog