lowRISC / lowRISC/opentitan

[ast / otp] Consider tying specific read / write lock to dev mode

Open
#10,587 1 comment 0 reactions 2 assignees Assigned to @msfschaffner View on GitHub
Component:RTL Earlgrey-PROD Triaged IP:ast IP:otp_ctrl Priority:P3 Type:FutureRelease
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

To prevent specific proprietary pieces from being explored in DEV mode (thus preventing wider distribution of DEV mode parts at the moment), we should enhance `ast` and `otp` to lock out specific pieces even during DEV mode.

This would include ast register read / write lock and also a specific software partition inside otp.

These would be fairly big changes on `otp` right now, so we might not be able to entertain this for the upcoming milestones.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.