sleep_lp_cycles < slp_period

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
ciano
Offline
Last seen:2 days 11 hours ago
加入:2014-10-03 08:13
sleep_lp_cycles < slp_period

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:
PM_Dialog
Offline
Last seen:10 hours 23 min ago
Staff
加入:2018-02-08 11:03
Hi ciano,

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