[stm32l476] pyb.stop() mode question on side effects
Posted: Mon Aug 06, 2018 7:38 pm
Dear all,
Before diving into a night of debugging with the STM32L476RG port:
Are there instances that need to be reinitialised after the system is woken up from a pyb.stop()?
Same measurement code:
- using a loop that fires a measurement using pyb.ADC() every 2 seconds --> works
- using rtc.wakeup(2000)/pyb.stop()/rtc.wakeup(None) to optimise power use, it wakes every 2 seconds as expected, but measurements results are all zero.
R
Before diving into a night of debugging with the STM32L476RG port:
Are there instances that need to be reinitialised after the system is woken up from a pyb.stop()?
Same measurement code:
- using a loop that fires a measurement using pyb.ADC() every 2 seconds --> works
- using rtc.wakeup(2000)/pyb.stop()/rtc.wakeup(None) to optimise power use, it wakes every 2 seconds as expected, but measurements results are all zero.
R