OpenDevicePartnership / OpenDevicePartnership/odp-platform-common
Support Crash Dump Bootflow
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 5
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 9
Description
UEFI played a large role in capturing data on a crash dump. Since the security processor should know when we are performing a crash reboot, it might make sense to move all logistics into a totally separate UEFI image that performs the single task of collecting the data, writing to NVME, and rebooting.
This task is to work with the team that is implementing the crash dump and determine what is necessary for all parts of the boot (UEFI, EC, TZ, etc.) to perform and write whatever is needed in a Rust module.
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
Begin by working with the crash-dump team to map the required responsibilities across UEFI, EC, and TZ during a crash reboot. Define what the separate UEFI image and Rust module must collect, how it writes data to NVMe, and how it reboots; the work is done when all boot components can perform the agreed crash-dump flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100