[dv/keymgr] a direct sequence to change otp key on the fly
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
From PR: https://github.com/lowRISC/opentitan/pull/17739
We plan to write a direct sequence test to change otp input key on the fly. The expected DUT behavior is to check keymgr won't sample the changed key again after the first sampling.
1). Suggest to write a direct sequence test: because the scb won't predict the exact clock cycle where design sample the otp keys.
2). V3 test: in current chip level design, otp output key to keymgr should not change until the next power cycle.
cc: @fati
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
Read PR 17739 first, then locate the keymgr and OTP verification entry points for direct-sequence and chip-level tests. Add a direct sequence that changes the OTP input key after its first sampling and verifies that keymgr does not sample the changed value again; the V3 case should preserve the key until the next power cycle.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100