BriComp
Well-known member
Snooze Wake-up Recovery Times - Edited Added Teensy4 Sleep Data
I have been looking at the time it takes for Snooze to wake-up on various Teensy. (What's the plural of Teensy?).
All this started when I found that I could NOT use a Teensy4 in a project because of the very long time (all relative ~4-7ms ) it took to wake-up from a snooze.
I was using a Radio UART device which wakes up from sleep when receiving a Radio Message, signals that event by sending a PIN LOW and 5ms later starts sending out to the Teensy (or whatever MCU) the Serial Data.
Unfortunately with Teensy4 the data will have gone by the time it has woken up.
My interest is in wake-up after a time period (1min) and upon a pin going low. I have set up a test bench with a Teensy feeding the Teensy under test with a LOW going (WAKEUP) wake up signal.
When the Teensy under test wakes up it Sets pin 13 HIGH followed immediately by setting pin 14 HIGH.
Using a cheapo Logic Analyser I have been looking at the time between the WAKEUP signal and pin 13 going HIGH. Also because there is frequent mention of the time that it takes between setting one pin, then another I have also noted the time difference for theses two events.
Because Compile Frequency Setting and Target Compile Speed etc may have an effect I have carried out the tests with these as variables.
I have found that Compiling for Different Speeds i.e. Fastest, Faster, Fast etc., there is very little effect upon the wake up time. However Compile Speed Setting (MHz) does have an effect upon the Wake-up time.
Below is a graph for all three Snooze settings (Sleep, DeepSleep and Hibernate) for the Teensys that I have so far tested. LC at Hibernate and DeepSleep return virtually the same timings.
If I add Teensy4 to the results we have the following graph. All the plots in the bottom left hand corner are for the other Teensys (LC,3.1 and 3.5).
Just carried out a Sleep test on Teensy4. Results with others below. Peculiar looking graph. Can't help but think there might be a problem!
If you are interested in the Numeric results or the graphed data for the individual Teensys then just ask.
If the graphs are too small just click on them to enlarge.
I have been looking at the time it takes for Snooze to wake-up on various Teensy. (What's the plural of Teensy?).
All this started when I found that I could NOT use a Teensy4 in a project because of the very long time (all relative ~4-7ms ) it took to wake-up from a snooze.
I was using a Radio UART device which wakes up from sleep when receiving a Radio Message, signals that event by sending a PIN LOW and 5ms later starts sending out to the Teensy (or whatever MCU) the Serial Data.
Unfortunately with Teensy4 the data will have gone by the time it has woken up.
My interest is in wake-up after a time period (1min) and upon a pin going low. I have set up a test bench with a Teensy feeding the Teensy under test with a LOW going (WAKEUP) wake up signal.
When the Teensy under test wakes up it Sets pin 13 HIGH followed immediately by setting pin 14 HIGH.
Using a cheapo Logic Analyser I have been looking at the time between the WAKEUP signal and pin 13 going HIGH. Also because there is frequent mention of the time that it takes between setting one pin, then another I have also noted the time difference for theses two events.
Because Compile Frequency Setting and Target Compile Speed etc may have an effect I have carried out the tests with these as variables.
I have found that Compiling for Different Speeds i.e. Fastest, Faster, Fast etc., there is very little effect upon the wake up time. However Compile Speed Setting (MHz) does have an effect upon the Wake-up time.
Below is a graph for all three Snooze settings (Sleep, DeepSleep and Hibernate) for the Teensys that I have so far tested. LC at Hibernate and DeepSleep return virtually the same timings.
If I add Teensy4 to the results we have the following graph. All the plots in the bottom left hand corner are for the other Teensys (LC,3.1 and 3.5).
Just carried out a Sleep test on Teensy4. Results with others below. Peculiar looking graph. Can't help but think there might be a problem!
If you are interested in the Numeric results or the graphed data for the individual Teensys then just ask.
If the graphs are too small just click on them to enlarge.
Last edited: