[reggen] Consider adding an ALERT_TEST_REGWEN register
@thommythomaso is already working on this.
Since Jun 22, 2026.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
@cfrantz pointed out that it would be better to lock down the ALERT_TEST CSR of all HWIP blocks. This CSR can be used for alert testing. Every HWIP has it and it's auto-generated by the regtool and inserted directly after the also auto-generated interrupt registers at the beginning of an IP's address space. This makes it cumbersome to lock access to the ALERT_TEST CSR for production software.
To simplify that, the following ideas came to mind:
1. Add an ALERT_TEST_REGWEN register. This is low effort and complexity but touches every HWIP. Unless the register is added at the end of the address map, a major version increase for every HWIP is triggered.
2. Re-arrange the address map of every HWIP to move the ALERT_TEST register to a a different address in a space which is a power-of-2 segment apart from the beginning of the HWIPs address space. The power-of-2 separation enables efficient locking via ePMP.
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.
Assessment
This issue has not been assessed yet.