Skip to content

Conversation

@en-sc
Copy link
Contributor

@en-sc en-sc commented Jan 29, 2025

[3.2. Reset Control] allows for a system-wide reset to reset the Debug Module.
Link:

power-up and while {dmcontrol-dmactive} in {dm-dmcontrol} is 0. If there is another mechanism to reset the DM, this mechanism must also reset all the harts accessible to the DM.

However, dmactive field description used to prohibit any other DM reset mechanism.

The commit fixes this inconsistency.

[3.2. Reset Control] allows for a system-wide reset to reset the Debug
Module.
Link: https://github.com/riscv/riscv-debug-spec/blob/a4678108534bef5b4fbf51e92acacd08b28c17af/debug_module.adoc?plain=1#L100

However, `dmactive` field description used to prohibit **any** other DM
reset mechanism.

The commit fixes this inconsistency.
@rtwfroody
Copy link
Collaborator

I don't think this is inconsistent. There should not exist a separate mechanism that resets the DM, but if there is then it must also reset all the harts.

It might be worth mentioning that caveat about resetting all the harts in the dmactive description, but we shouldn't change the language away from "this should not exist."

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.

2 participants