-
Notifications
You must be signed in to change notification settings - Fork 1
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
Use FRAM to store time counters, eliminate RTC backup. #29
Comments
We can always just sub this for the CAP at 1/2 a cent... |
Ok, Microsemi says "You can not leave a CMOS input floating." But I am sceptical. According to the docs, while this is an input in the sense that a current is flowing into a transistor, this is not a gate input. But at least for now, we will put the resistor in since it is low risk. We can always omit it later. |
Still need to update firmware to continuously track elapsed time as per #29.
… rather than RTC backup Closes #29 , #30 , & #35. Overall current draw is still less than 2uA. Currently we unlock/lock the info FRAM where we keep the counters each time we update them, which is once per minute. This uses slightly more power than just leaving them unlocked, unknow if there is any safety benefit. Lightly tested and seems to work, but big changes so needs way more testing.
Closed with 0329562 |
New persistent storage of time since launch count pauses when batteries are out, then resumes when back in. Omits RTC backup capacitor.
So much simpler code. Gets rid of those problematic and expensive backup caps.
Only user impact is that time pauses when there is no battery power, which seems correct.
The text was updated successfully, but these errors were encountered: