From 6c800cde5805ebcc484ed17adfb9098b07c2801b Mon Sep 17 00:00:00 2001 From: Tim Newsome Date: Fri, 23 Feb 2024 08:41:55 -0800 Subject: [PATCH] Fix `hartset` -> {hartsel} Fixes #972 --- debug_module.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debug_module.adoc b/debug_module.adoc index eaf876ce..e5558a8d 100644 --- a/debug_module.adoc +++ b/debug_module.adoc @@ -365,7 +365,7 @@ of {dm-data0}) or hart (e.g. contents of a register modified by a Program Buffe Before starting an abstract command, a debugger must ensure that {dmcontrol-haltreq}, {dmcontrol-resumereq}, and {dmcontrol-ackhavereset} are all 0. -While an abstract command is executing ({abstractcs-busy} in {dm-abstractcs} is high), a debugger must not change `hartset`, and must not write 1 to {dmcontrol-haltreq}, {dmcontrol-resumereq}, {dmcontrol-ackhavereset}, {dmcontrol-setresethaltreq}, or {dmcontrol-clrresethaltreq}. +While an abstract command is executing ({abstractcs-busy} in {dm-abstractcs} is high), a debugger must not change {hartsel}, and must not write 1 to {dmcontrol-haltreq}, {dmcontrol-resumereq}, {dmcontrol-ackhavereset}, {dmcontrol-setresethaltreq}, or {dmcontrol-clrresethaltreq}. If an abstract command does not complete in the expected time and appears to be hung, the debugger can try to reset the hart (using {dmcontrol-hartreset} or {dmcontrol-ndmreset}).