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,dv] Use the "right enable" in *_jtag_dmi_debug_disabled_vseq #23981

Merged

Conversation

rswarbrick
Copy link
Contributor

This PR looks reasonably large because it depends on #23799. Once that has been merged, there are two remaining commits:

  • [rv_dm,dv] Make DMI bringup in base vseq depend on pinmux connection
  • [rv_dm,dv] Use the "right enable" in *_jtag_dmi_debug_disabled_vseq

The first commit is a tidyup in the base vseq (which I noticed when trying to fix the vseq for the second commit). The second commit is the main point of this PR. Its commit message is as follows:

[rv_dm,dv] Use the "right enable" in *_jtag_dmi_debug_disabled_vseq

The code here was a bit broken and I clearly hadn't previously
understood the difference between "pinmux enabled" and "debug
enabled".

The whole point of this test is supposed to be that DMI transactions
get blocked when pinmux is not enabled. After the changes here, we
actually test that property!

@rswarbrick rswarbrick added Component:DV DV issue: testbench, test case, etc. IP:rv_dm labels Jul 10, 2024
@rswarbrick rswarbrick requested a review from a team as a code owner July 10, 2024 11:50
@rswarbrick rswarbrick requested review from matutem and removed request for a team July 10, 2024 11:50
@rswarbrick rswarbrick force-pushed the rv-dm-jtag-dmi-disabled-with-pinmux branch from 7180d03 to 2988669 Compare July 11, 2024 16:45
Copy link
Contributor

@vogelpi vogelpi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good as well, thanks @rswarbrick .

@rswarbrick
Copy link
Contributor Author

rswarbrick commented Jul 12, 2024

Thanks. I'm going to force-push after rebasing because a bunch of CI(private) tests failed last time for unrelated IT issues. Assuming things look reasonable, I intend to merge this when they finish. (But it's an evening with children! If someone else gets here first, please feel free to hit the merge button! :-D)

The existing logic wasn't quite correct: it only tried to start
DMI (which uses pinmux) if debug was enabled. But we can sensibly talk
to the debug module over DMI even when debug isn't enabled.

Signed-off-by: Rupert Swarbrick <[email protected]>
The code here was a bit broken and I clearly hadn't previously
understood the difference between "pinmux enabled" and "debug
enabled".

The *whole point* of this test is supposed to be that DMI transactions
get blocked when pinmux is not enabled. After the changes here, we
actually test that property!

Signed-off-by: Rupert Swarbrick <[email protected]>
@rswarbrick rswarbrick force-pushed the rv-dm-jtag-dmi-disabled-with-pinmux branch from 2988669 to 1745c4c Compare July 12, 2024 16:16
@rswarbrick rswarbrick merged commit c0f9219 into lowRISC:master Jul 12, 2024
32 checks passed
@rswarbrick rswarbrick deleted the rv-dm-jtag-dmi-disabled-with-pinmux branch July 12, 2024 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:DV DV issue: testbench, test case, etc. IP:rv_dm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants