-
Notifications
You must be signed in to change notification settings - Fork 307
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
Track and clarify differences with upstream OpenOCD #979
Comments
Regarding
|
The change to |
There is a significant difference in |
The ftdi changes let a user debug a target using cJTAG OSCAN1 protocol. It was added in #320. I'm not sure if it's ever seen significant use. There are significant FreeRTOS changes as well. They support 64-bit targets, and also reorganize a bunch of code so it was easier to support RISC-V with 2 different call stack conventions. This is the one that seems the hardest to upstream since you probably need to check that it still works on some non-RISC-V target before sending it upstream. I don't remember any users ever asking about RISC-V FreeRTOS so probably it's not used much. The breakpoints changes are recent, and are causing quite a few conflicts when merging changes down. I'd prioritize upstreaming these just to reduce the work required in resolving these conflicts. The rtos changes primarily let gdb correctly access registers from individual threads that are not the current one. This is probably important in conjunction with hwthread and multiple harts. |
After the most recent merge #976 the difference with upstream version used looks like so (some differences are omitted):
Some of these files seem suspicious, namely:
The text was updated successfully, but these errors were encountered: