Main OpenOCD is quite a long way behind the riscv-openocd fork. Please try that
version, and if the problem exists there, then file a bug on github.
riscv-openocd lives at https://github.com/riscv/riscv-openocd
Tim
---
** [tickets:#276] riscv reg command problem**
**Status:** new
**Milestone
I haven't examined the code in detail, but I'm using this message in
riscv-tests and haven't encountered any problems so far. The real reason I
added the message is to know the port that OpenOCD is actually listening on,
when the caller sets it to 0.
---
** [tickets:#147] How to know when Ope
Related to this, I have this change in https://github.com/riscv/riscv-openocd.
The intent is to allow automated software to know when OpenOCD is ready for gdb
to connect to it:
```
diff --git a/src/server/server.c b/src/server/server.c
index 8009d40..f3ae34e 100644
--- a/src/server/server.c
+++ b
