-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add JTAG support to the core #4
Conversation
ad7b969
to
bfd8c1a
Compare
3cb69b4
to
23a74cf
Compare
5d8743c
to
942dc04
Compare
156dc1a
to
d4ded17
Compare
Co-Authored-By: Martijn Bastiaan <[email protected]>
Co-authored-by: Martijn Bastiaan <[email protected]>
273246d
to
ecf0858
Compare
89d551d
to
58568da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've:
- Fixed the space leak in the new dual port memory
- Added a JTAG test to CI. It tests breakpoints, register listing, and program loading.
- Added a HDL generation test to CI
- Fixed a CI issue where it couldn't find caches (because newer Cabals follow XDG)
- Looped back the JTAG reset in
cpu
(but notvexRiscv
) - Made sure black boxes / top entities are properly annotated for newer GHCs
The JTAG test is currently disabled, due to OpenOCD and GDB missing in the CI environment. I propose just using Nix shell.
So LGTM, but I also added a whole bunch to this PR so... :-).
Tests the bare minimum: whether HDL can be generated using Clash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments, some just to keep track of "dead code" so we don't forget :)
@cuddlefishie What do you think, is this mergeable? |
Yes, I think this should be good to go now :) |
This is the first step to allow debugging the core with tools like GDB by using
OpenOCD
.TODO: