-
Notifications
You must be signed in to change notification settings - Fork 56
Minor changes #67
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
Minor changes #67
Conversation
Signed-off-by: George Popa <[email protected]> Co-authored-by: Frederic Pillon <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Properly format comment to be inline with Arduino formatting.
Co-authored-by: Frederic Pillon <[email protected]> Signed-off-by: Alex <[email protected]>
Co-authored-by: Frederic Pillon <[email protected]> Signed-off-by: Alex <[email protected]>
Co-authored-by: Frederic Pillon <[email protected]> Signed-off-by: Alex <[email protected]>
Co-authored-by: Frederic Pillon <[email protected]> Signed-off-by: Alex <[email protected]>
Co-authored-by: Frederic Pillon <[email protected]> Signed-off-by: Alex <[email protected]>
Co-authored-by: Frederic Pillon <[email protected]> Signed-off-by: Alex <[email protected]>
From my tests, Lowpower.shutdown(1000); does not trigger a wakeup or standby flag as it should but instead a Brown-out Reset flag. Not sure if that was intended or is a misimplementation of LowPower library. |
Got this with a Nucleo F103RE |
On my F401RE:
On my U385RG-Q:
Something is not consistent here or is by design? |
Ok, i found the problem. U3 series use independent wakeup flags so a change is needed to accomodate the new architecture as such: change this:
to this:
and this:
to this:
But funnily enough, this still doesn't trigger the WAKEUP flag. |
This is what I said here: #66 (comment) |
No description provided.