[otp_ctrl/dv] use mem_bkdr_util interface to read check ECC uncorrectable error
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
Current OTP testbench stores expected otp array in otp_ctrl_scoreboard.
When we backdoor write OTP memory to create ECC error, this was not updated on scb.
So the current scb can only predict ECC correctable error.
Proposed solution: Since the mem_bkdr_util is used, we can directly store OTP memory array in mem_bkdr_util and it should update the backdoor injected errors.
V3 or future release: If the read is ECC uncorrectable error, OTP_CTRL will trigger fatal alert and lock the block. So to check the read data from this ECC uncorrectable error is not very important.
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 otp_ctrl_scoreboard expected OTP array and the existing mem_bkdr_util use in the OTP testbench. Confirm how backdoor-injected ECC errors update memory state, then check the uncorrectable-error path and its expected fatal alert and lock behavior. Done means the scoreboard reflects injected memory errors consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100