[CHERIoT] Revocation bitmap and meta SRAM ctrl point to same address space
Open
@thommythomaso is already working on this.
Since Aug 20, 2026.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
With the current tooling, both the system port to the revocation bitmap as well as the base address of the meta SRAM controller point to the same address space leading to a duplication of the entries in the address map and the linker script.
The meta SRAM is not directly accessible in the address map as it sits behind the CHERIoT subsystem. We need to adapt `topgen` to resolve this duplicated entry.
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.