-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sample Sketch compare.pinmode() for T_4.x #92
Comments
Yes you are correct and I'll update the "compare" wakeup for the Teensy4, Thanks! |
Glad I saw that in the right context. Someone on the forum having issue with https://forum.pjrc.com/threads/62763-Snooze-Calling-a-function-on-a-pin-interrupt Way out of my experience with snooze - but seemed like a simple question to start. So scanned some code - but there is a lot behind the scenes ... |
It is a lot of code that touches a lot of hardware on the Teensy's so it's been a journey trying to get everything to play nice with each other. The actual code to put a Teensy to sleep is not that bad for the Teensy 3.x not so much for the T4 but it's the wakeup code that gets hairy. |
Saw your post on that thread - all the best on the family health front - your code does a great job encapsulating the transition and hardware with lots of details to handle. Waking and sleeping and and handling transitions across that for tracking interrupts with certain amounts of dead time in the process, and snooze needing to be the master to make it happen usably. |
Glancing through the code to answer forum question in: \libraries\Snooze\examples\sleep\sleep_all_wakeups\sleep_all_wakeups.ino
where pin 11 is not a T_4 compare pin I see coded to pin 11:
` Teensy 4.0
Compare pins: 0, 1, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23
********************************************************/
// trigger at threshold values greater than 1.65v
//(pin, type, threshold(v))
//compare.pinMode(11, HIGH, 1.65);
// trigger at threshold values less than 1.65v
//(pin, type, threshold(v))
compare.pinMode(11, LOW, 1.65);
}`
The text was updated successfully, but these errors were encountered: