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

C3 firmware recovery system (choosing firmware banks) #54

Closed
andrewgreenberg opened this issue Nov 22, 2021 · 1 comment
Closed

C3 firmware recovery system (choosing firmware banks) #54

andrewgreenberg opened this issue Nov 22, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request
Projects

Comments

@andrewgreenberg
Copy link
Member

After discussion today, we decided that we're gong to try to leave Bank 0 the way it is, forever, and leave that as the "Bank of first and last resort". We'll only update Bank 1 with new firmware.

We need code that runs in Bank 1 that chooses to switch back to Bank 0 if:

  • We get too many reboots due to system lockups
  • We lose communication with the ground
  • Other reasons?

This code would switch back to Bank 0 which we know vaguely works and can do communication and firmware updates.

@andrewgreenberg andrewgreenberg added enhancement New feature or request high priority labels Nov 22, 2021
@andrewgreenberg andrewgreenberg added this to the OreSat0 Handoff milestone Nov 22, 2021
@andrewgreenberg andrewgreenberg added this to To do in C3 Firmware via automation Nov 22, 2021
@wrh2 wrh2 added the C3 label Apr 22, 2022
@ryanpdx
Copy link
Member

ryanpdx commented Jun 2, 2024

No longer relevant

@ryanpdx ryanpdx closed this as completed Jun 2, 2024
C3 Firmware automation moved this from To do to Done Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
C3 Firmware
  
Done
Status: Done
Development

No branches or pull requests

4 participants