-
Notifications
You must be signed in to change notification settings - Fork 14
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
Cold Boot Proof of Concept #58
Conversation
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.
coldBoot PoC
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.
Looks good. Left comments.
//you don't need to change any settings below this line (but you can if you know what you're doing): | ||
//__________________________________________________________________________________________________ |
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.
Will the VOLTAGE_SPOOFING_
config be unnecessary moving forward?
@@ -99,3 +103,28 @@ uint8_t key_getSampledState(void) | |||
} | |||
|
|||
///////////////////////////////////////////////////////////////////////////////////////// | |||
|
|||
void keyOn_coldBootTasks(void) |
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.
Suggestion:
This sequence might be better placed in firmwareLiBCM.ino
itself--similar to how setup()
and loop()
define their respective sequences.
From an "object" perspective, a key
says whether it's on
, off
, and if it has changed; but it shouldn't perform the system consequences of those states.
This also applies to key_handleKeyEvent_off()
, key_handleKeyEvent_on()
, and void key_stateChangeHandler()
.
No description provided.