Skip to content
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

Move EDU program status history to FRAM #204

Closed
Tracked by #201
PatrickKa opened this issue Dec 18, 2023 · 4 comments · Fixed by #328
Closed
Tracked by #201

Move EDU program status history to FRAM #204

PatrickKa opened this issue Dec 18, 2023 · 4 comments · Fixed by #328

Comments

@PatrickKa
Copy link
Contributor

PatrickKa commented Dec 18, 2023

Description

The EDU program status history is a ring buffer just like the telemetry memory, which is also on the FRAM. Therefore, we should implement a general ring buffer abstraction on the FRAM that can be used for both (see #179).

Edit: Implementing this general FRAM ring array is now tracked separately in #323.

@PatrickKa
Copy link
Contributor Author

Blocked by #185 and #192

@PatrickKa
Copy link
Contributor Author

Also blocked by #207 because we need tests.

@jeromehue jeromehue self-assigned this May 9, 2024
@PatrickKa
Copy link
Contributor Author

As explained in #294, we need a fallback mechanism in case the FRAM does not work. This means that the status history needs to be cached in RAM (maybe with a smaller size, though). If the FRAM works, entries are read from and written to it. Entries are also always written to the cache, but only when the FRAM doesn't work are they also read from the cache.

@PatrickKa
Copy link
Contributor Author

Blocked by #323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants