oxidecomputer / oxidecomputer/quartz
Ignition: Consider not doing a MAPO based on A2 PG signal autonomously inside of Ignition Target
@arjenroodselaar is already working on this.
Since Nov 18, 2022.
- Dominant language
- VHDL
- Stars
- 22
- Forks
- 2
- Avg merge
- 9h 38m
- Merged PRs (30d)
- 1
Description
Currently, Ignition is designed to MAPO immediately based on a PG signal going away once 25ms has elapsed after the IBC is enabled.
This function might be better handled by the higher-level software on Sidecar/Scrimlet to determine what to do in case of a fault and it seems like it is safer if Ignition on each board only reports the faults up to software instead of taking autonomous action. If we get the autonomous action in Ignition wrong, it's a field service call to reprogram or replace hardware. If the action is controlled by a higher level software function, that behavior can be changed with a software update.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.