ADCS MCU - OS non-volatile storage design translation of OBC V1 design

[Aidan-Sheedy]

Motivation/Description ⛰️

The MCU needs a way of storing, updating, and running the ADCS OS. As the STM32 chip itself has no storage to do so, This has been designed for OBC V1, and may be able to be adapted to the ADCS MCU.

Next Steps 🚶

• [x] Review OS storage on OBC V1. It may be called the MRAM section of the design. Key features to look at are:
  • Methods of flashing the OS
  • Size of storage available
  • Complexity of design
  • Storage medium used
  • Availability and cost of components
• [x] Document what parts of the OBC V1 design are transferable to the ADCS MCU and what parts need redesigning. This should be done in the ADCS MCU documentation.
  • [ ] All transferable design features should be documented as the current implementation in the documentation
  • [ ] All non-transferable features or changes required should, along with being documented, have a ticket craeted to address the shortcomings.
• [ ] Create a circuit diagram for the OS Storage. This should be stored in the ADCS Teams and the ADCS GitHub.

Supporting Material and Resources 📖

• OBC V1 Documentation
• OBC STM32 PCB Design
• ADCS MCU Documentation

Definition of Done 💯

This task is done when:

• The OBC V1 OS storage design has been transferred to the ADCS MCU
  • All transferable design features have documented
  • Missing/non-transferable features have a new ticket
• A circuit diagram of the OS storage has been created in the GitHub and the ADCS Teams channel. This is a working document, and is not expected to be complete.

Tags

tag people that should know about this issue

cc: @SeanTedesco @emmapaczkowski @Aidan-Sheedy @jillianmalherbe

[HarrisonMKG]

I am pretty sure that the stm32 itself is able to store the OS without external memory. I think each chip comes with embedded flash memory which is where the code you write to program the board is uploaded and stored.

[dylan-burke]

@Aidan-Sheedy can you make the circuit diagram?