oxidecomputer / oxidecomputer/quartz
cosmo ignition hotswap recovery doesn't work as designed.
Nobody has claimed this yet.
- Dominant language
- VHDL
- Stars
- 22
- Forks
- 2
- Avg merge
- 9h 38m
- Merged PRs (30d)
- 1
Description
We need to decide what needs to happen here, as ignition doesn't currently toggle the hotswap enable signal. We have evidence to suggest that toggling the hot swap too quickly will immediately fault the hotswap, which would be what we're trying to clear here so we need to figure out what the correct behavior is here or how we'd recover this case in the field.
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.
Research direction
Start by tracing the ignition path and the hotswap enable signal, focusing on how recovery is expected to clear a hotswap fault. Investigate the evidence that toggling too quickly faults the hotswap and determine the correct field-recovery behavior. Done means the expected behavior and recovery sequence are decided and the design can implement them.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100