[rram_ctrl,rma] OTP access after RMA completion
Open
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
The lc_ctrl_fsm tries to do an OTP request to the OTP partition after an RMA operation. This does not work anymore because the OTP is inside the RRAM and the RRAM is disabled after the RMA operation has completed.
The short term fix for now, the disabling of the RRAM after the RMA is disabled. But a proper solution is required.
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 with the lc_ctrl_fsm flow described in the issue and trace its OTP request after RMA completion, then inspect how RRAM is disabled at that point. A complete fix must provide a proper post-RMA OTP access path rather than relying on the short-term RRAM-disabling change; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100