riscv-debug-spec
riscv-debug-spec copied to clipboard
Improve description of cmderr "busy"
-
Improve the wording of what happens if another abstract command is started while the previous one still executes. Make the order of events very clear.
-
Unify the wording of cmderr "busy" requirement for all concerned DM registers. Make it clearer to the reader that the prescribed behavior is the same in all the cases.
See https://github.com/riscv/riscv-debug-spec/issues/1072 for the related discussion.
These clarifications are very helpful - what's the status on getting these integrated?