[rtl,escalation] Fix rst_ni connection of pwrmgr's receiver
@nsw-lowrisc is already working on this.
Since Aug 31, 2026.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
The alert_handler's escalation sender rst_ni is connected to rstmgr_aon_resets.rst_lc_io_div4_n[rstmgr_pkg::Domain0Sel] in top_earlgrey, but the pwrmgr's escalation_receiver is connected to rstmgr_aon_resets.rst_lc_io_div4_n[rstmgr_pkg::DomainAonSel]. Notice they are indexed by a different domain, so they are different nets.
It so happens that the behavior of the two resets (differing in the index) is almost the same, since the reset requests from pwrmgr always drives the same value for both domains. There may be minor cycle differences, but we don't expect this to cause reset divergences that can cause incorrect behavior.
Nevertheless, topearlgrey should be fixed to connect pwrmgr's rst_esc_ni to rstmgr_aon_resets.rst_lc_io_div4_n[rstmgr_pkg::Domain0Sel]. This needs to be done via the hjson files for the top.
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.