-
Notifications
You must be signed in to change notification settings - Fork 796
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.
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
[rv_dm,rtl] Fix acknowledgment of reset in dmstatus.allhavereset
/dmstatus.anyhavereset
#15123
Comments
Triaged for |
Depending on how we intend to implement the delayed debug unlock feature, this may be something that we have to fix as well. CC @rswarbrick |
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
This adds tracking logic for NDM reset requests and issues an acknowledgement to the DM_CSRs so that dmstatus.allhavereset / dmstatus.anyhavereset can be asserted at the correct time. Fixes lowRISC#15123 Signed-off-by: Michael Schaffner <msf@opentitan.org>
pulp-platform/riscv-dbg#118:
This is incorrect behavior and should be fixed, but it is currently not urgent for us, because the
rstmgr
resets the system reset domain unconditionally wheneverndmreset_req
is asserted (a few cycles after asserting this signal).The text was updated successfully, but these errors were encountered: