-
Notifications
You must be signed in to change notification settings - Fork 804
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] WARL behavior and NDM tracking fixes #22038
Conversation
79fe316
to
6da3819
Compare
6da3819
to
bcbbbdb
Compare
bcbbbdb
to
384bc91
Compare
If anyone with an FPGA setup could help me debug the |
@msfschaffner: About the testing side of things: I've filed an issue (#22048) to track the work that needs doing. Assigning it to a PROD milestone is clearly the next job! I assume M4, but will leave that to someone with more knowledge of the roadmap/timescale. |
Thanks! PROD.M4 sounds right! |
Update code from upstream repository https://github.com/pulp- platform/riscv-dbg to revision 358f90110220adf7a083f8b65d157e836d706236 This also connects the nextdm input and ndmreset ack inputs in rv_dm, and ties them off. Implementation of ndmreset ack comes in a subsequent commit. Fixes lowRISC#19750 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 fixes #19750 and #15123.
TODO: we should file issues for BLT/TLT extensions.
@rswarbrick can you take care of the BLT part?
I filed an issue for TLTs here: #22044