Architecture tracking issue

[duncanrhamill]

Tracking issue for architecture rework

This is the main tracking issue for the rework of the OBC software architecture.

Design

• [ ] Debug system
• [ ] FDIR #34
• [ ] Task system #35
• [ ] "Classical" OBSW vs "Embedded" OBSW

[duncanrhamill]

"Classical" vs "Embedded" OBSW

A kind of major decision is whether or not we go for a classical OBSW design (see "Onboard Computers, Onboard Software and Satellite Operations", Jens Eickhoff), or the current embedded design. Pros/cons of each:

Classical

Pros

• Well understood and documented design practice
• Flexibility in TM design
• FDIR built in

Cons

• Complex design
• Depends(?) on RTOS
• Affects on power consumption?

Embeded

Pros

• Existing codebase could be reused
• May have lower power consumption due to interrupt-driven nature

Cons

• Must be redesigned to accomodate FDIR
• TM/TC routing design incomplete

[duncanrhamill]

Initial design for a classical OBSW architecture have been done, on the SharePoint under Software. For now we are proceeding with the classical system.