Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SECURESEED writes that lead to lockup without dummies/hints being enabled are not detected #394

Closed
Silabs-ArjanB opened this issue Jan 23, 2023 · 0 comments
Closed

SECURESEED writes that lead to lockup without dummies/hints being enabled are not detected #394

Silabs-ArjanB opened this issue Jan 23, 2023 · 0 comments

Comments

@Silabs-ArjanB
Copy link
Contributor

image

The enable_i used in lockup_wr shouldn't be there; the other enable_i usage is likely redundant (and if so should be removed)
silabs-oysteink added a commit to silabs-oysteink/cv32e40s that referenced this issue Feb 2, 2023
@silabs-oysteink
Fix for issue openhwgroup#394.
082a5f6 
- Removed 'enable_i' from LFSR modules.
- It is no longer possible to write a locked up value to the LFSR, detection is now independent of the enabling of dummies of hints replacements.

Not SEC clean:
- Alert minor caused by writing a locked up value when dummies/hint replacements are disabled.
- Previously, a locked up value could be stored in the LFSR, resulting in a difference in which dummy or hint was generated on the first instruction after anbling.

Signed-off-by: Oystein Knauserud <Oystein.Knauserud@silabs.com>
Silabs-ArjanB added a commit that referenced this issue Feb 2, 2023
@Silabs-ArjanB
Merge pull request #402 from silabs-oysteink/silabs-oystein_issue-394
df6c2cd 
Fix for issue #394.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Silabs-ArjanB