lowRISC / lowRISC/opentitan

[rom_ext] Boot Services (continued)

Open
#19,594 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Priority:P2 SW:ROM_EXT Type:Task
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

- [ ] Investigate moving boot services requests into flash rather than ret-RAM.
- Consumer team wants to have boot-svc commands survive power interruptions.
- Consumer may want to queue boot-svc commands and wait for customer initiated reboot.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the boot-services request handling and its ret-RAM storage, then clarify the consumer requirements for flash persistence, power interruptions, queued commands, and customer-initiated reboot. Done should include an agreed design and validation for the required reboot and interruption scenarios.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.