i'm using the SysTIck peripheral for short-term delays (<100ms).... as such, the MCU will enter its IDLE mode when awaiting a SysTick interrupt; and all is well here....
pushing the envelope a bit more, i enter STANDBY mode where i'm awaiting a button-press (GPIO interrupt) to awaken the MCU.... once i'm ACTIVE, i can successfully enable SysTick and enter IDLE for a short period of time before awaiting the next button-press....
the problem arises when i use the RTC to wakeup from STANDY after (say) a few seconds.... when i then go to use the SysTick peripheral, i'm finding that **ALL** of my wakeups from IDLE occur after ~150ms -- regardless of what value i've placed in the SysTick->LOAD register!!!!!
note that SysTick works just fine when used **BEFORE** using the RTC to enter STANDBY.... and as i mentioned above, coming out of STANDBY with a GPIO interrupt also works just fine....
something about using the RTC with the 32kHz LFCLK screws up SysTick, which is presumably using the 48MHz processor clock.... it's odd, however, in that i believe the processor clock really is running at 48MHz when coming out of STANDY; busy-wait loops of known duration continue to delay as expected....
given the nature of my tooling environment, it's difficult to create a "standalone program" usable in CCS to reproduce the problem.... in the meantime, i'm more than willing to quickly try any suggestions to ensure SysTick works correctly after awakening from an RTC STANDBY....
