System Analysis: S/S Bug-Squashing Firmware Reprogram

[chgio]

Existing diagrams to extend:

• [ ] [MCB] System Capabilities:
  • [ ] add FDIR capability
  • [ ] add Firmware Reprogramming child
• [ ] [SFBD] Root System Function Breakdown
• [ ] [SAB] System Architecture

New diagrams to create:

• [ ] [ES] Firmware Reprogram Scenario:
  • some system bug state (use either failure state or note)
  • placeholder for bug identification through telemetry data
  • bugged subsystem firmware update over serial bus

Next steps: when closing this issue, make a new issue out of the checkbox below:

• [ ] #52

[chgio]

this kind of fix doesn't really sit on the same ladder as #1, #2, #37, so let's still model the failure and its identification. I'm thinking they would be something more "deep-down", that can't just get fixed with a reboot of any kind but needs a change of firmware instead.

[Hello-1122]

no problem

---

From: Giorgio Ciacchella @.> Sent: 03 February 2023 17:20 To: guorbit/obc-model @.> Cc: Anthony Rainey (student) @.>; Assign @.> Subject: Re: [guorbit/obc-model] System Analysis: S/S Bug-Squashing Firmware Reprogram (Issue #3)

this kind of fix doesn't really sit on the same ladder as #1https://github.com/guorbit/obc-model/issues/1, #2https://github.com/guorbit/obc-model/issues/2, #37https://github.com/guorbit/obc-model/issues/37, so let's still model the failure and its identification. I'm thinking they would be something more "deep-down", that can't just get fixed with a reboot of any kind but needs a change of firmware instead.

— Reply to this email directly, view it on GitHubhttps://github.com/guorbit/obc-model/issues/3#issuecomment-1416171621, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXJVFYPBTDWUIZD32LLLPF3WVU465ANCNFSM6AAAAAARJUOBTQ. You are receiving this because you were assigned.Message ID: @.***>

[chgio]

at the System Analysis level, let's actually have a path to represent the telecommand/execution/report pattern, leading to "system does X" not unlike the fault identification placeholder:

• operator issues X t/c
  • g/s sends X t/c
  • system receives X t/c
  • (switch to a Downlink mode: through change mode, collect telemetry -- thanks @muhamedshaheenar for pointing this out!)
  • system does X
  • system sends X report
  • g/s receives X report
• operator interprets X report

at the other end of "system does X", a link to telemetry generation should also be made for when this function is triggered automatically and there is no option to immediately downlink the report.