Skip to content
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

Merged
merged 2 commits into from
Mar 15, 2024

Conversation

msfschaffner
Copy link
Contributor

@msfschaffner msfschaffner commented Mar 14, 2024

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

@msfschaffner msfschaffner changed the title Rv dm fixes [rv_dm] WARL behavior and NDM tracking fixes Mar 14, 2024
hw/ip/rv_dm/rtl/rv_dm.sv Outdated Show resolved Hide resolved
@msfschaffner msfschaffner force-pushed the rv-dm-fixes branch 3 times, most recently from 79fe316 to 6da3819 Compare March 15, 2024 00:07
@msfschaffner msfschaffner marked this pull request as ready for review March 15, 2024 00:32
@msfschaffner msfschaffner requested review from a team and vogelpi as code owners March 15, 2024 00:32
@msfschaffner msfschaffner requested a review from a team as a code owner March 15, 2024 06:52
@msfschaffner msfschaffner requested review from HU90m and pamaury and removed request for a team and HU90m March 15, 2024 06:52
@msfschaffner
Copy link
Contributor Author

If anyone with an FPGA setup could help me debug the rv_dm_access_after_wakeup_* SiVal non-ROM_EXT tests that would be appreciated.

@rswarbrick
Copy link
Contributor

@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.

@msfschaffner
Copy link
Contributor Author

@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>
@msfschaffner msfschaffner merged commit b3c7206 into lowRISC:master Mar 15, 2024
32 checks passed
@rswarbrick rswarbrick mentioned this pull request Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[rv_dm,rtl] Potential issue with hartsel WARL behaviour
3 participants