Replies: 1 comment 1 reply
-
We will start to work on the debugging tools for ROHD. We are going to start small by having a |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been thinking about ways to make interactive debug with a ROHD design easier. With SystemVerilog designs, interactive debug can be pretty painful, but there are (proprietary) tools available that allow tracing of signals through original source code and relation to waveforms.
With ROHD, we already have a really great interactive debug ability through the Dart debugger and its attachment to IDEs like vscode. However, the debugger has a couple limitations that are a little annoying:
I think it would be really cool to build a tool that connects to the Dart debugger and cherry-picks hardware-debug-related information. Waveform history per-signal could be stored in debug-visible variables rather than VCD, which would mean we could attach a live waveform view to that same debug process.
These links seem potentially relevant/interesting:
https://code.visualstudio.com/api/extension-guides/debugger-extension
https://microsoft.github.io/debug-adapter-protocol/
This is probably not a small project to take on, but could really elevate the debuggability of ROHD.
Beta Was this translation helpful? Give feedback.
All reactions