-
Notifications
You must be signed in to change notification settings - Fork 34
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
Merge to upstream #8
Comments
Also keeping it aligned with upstream would be beneficial to prevent issues like #6 from happening, which were fixed in upstream already some time ago. |
I personnaly have no interrest in that, but i understand that some people have.
Yes that's one of the issues :/
Yes that's right, already had issues with update of GCC being more picky ^^ So, i'm all for what you propose, the issue is just man power and my personnal willing to do it myself, as i never use it on windows. |
Good to hear that. I'm adding it to my backlog for next week. |
Note that for some time I won't have a Windows machine at hand, so I won't be able to work on #9. |
+1 on this. @MarekPikula Did you ever make progress on this? I'd like to help if I can. |
@MarekPikula @adamfeuer
( Efinix provide the funding :) ) I will have to do some area overhead mesurement to soo how much is lost exactly. |
Amagad, on Artix 7, the whole CPU (in a small config), with the debug infrastructure + jtag tap : So, not a small overhead to get the official style debug :( |
So, i think it would make sense, even if VexRiscv implement the official RISC-V debug spec too, to merge the lightweight VexRiscv non standard debug implemention in upstream openocd. |
@Dolu1990 That's fantastic about getting the standard RISC-V debug spec implemented. Personally that would be the way I would prefer, despite the lots of extra LUTs/FFs. Has this change already been merged to the master/main branch? Re: getting the lightweight JTAG for VexRiscv merged to upstream, does it provide the same functionality? I guess either way I'd be willing to try to get it merged to upstream. I'll look at it today and see if I can update the current code to the current OpenOCD head, I guess that would be the first step. |
Not yet merged, but soon will be merged in dev for sure (~2 weeks).
For regular baremetal stuff, yes, that's mostly the same, but things as debug linux kernel / mmu handeling could be way better with the official RISC-V openocd implementation.
See #24 And as far as i know, that should be all. |
@adamfeuer Hi, unfortunately I didn't have much of a chance to work on it since the 2 years or so. |
Ahh that's two diferent things, i was talking about the official RISC-V debug implemention in VexRiscv to be merge in the VexRiscv dev branch in 2 weeks. The dnltz thing is about update this openocd fork with openocd upstream (VexRiscv style debug support) |
@adamfeuer Note, that this openocd fork also add a jtag driver over TCP, with a very simple protocol : And that's all. Here is a client implementation for SpinalSim : |
Do you consider merging this version upstream so that there is no need for custom build in future?
This would require also making it Windows-compatible (mainly WinSock-compatible for
jtag-tcp
). I'll create separate issue for this though.The text was updated successfully, but these errors were encountered: