oxidecomputer / oxidecomputer/hubris
SP should try to notice that no DRAM is available
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
Recently I was booting a Cosmo and forgot to insert any DRAM. I think there are two things that we should look at here:
- Before we go from A2 to A0, we should see if any DIMMs are present via SPD.
- The SP5 system can come to rest with a final post code of
0xea00e316which indicatesTpAblErrorNoMemoryAvailableInSystem.
I think (1) would be useful and a way to generate an ereport, but (2) is also a secondary way that this can happen, but probably lower in priority. There are a few other general classes of error that can happen on start up that we may want to notice and figure out how to deal with.
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 SP startup path from A2 to A0 and how SPD results are handled. Review the 0xea00e316 post code, TpAblErrorNoMemoryAvailableInSystem, and existing ereport paths. Done means startup with no DIMMs is detected and reported, with the chosen handling covered by tests or another demonstrated check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100