Closed ivankravets closed 5 years ago
I have no idea what was wrong, I'm only tracking both the main repo and the risc-v repo.
I'll try to update, but I'd rather wait for the risc-v fork to be upstreamed, there are too many differences to accommodate.
I tried RISC-V fork. The same problem. What is interesting, it works good on Linux.
I tried RISC-V fork. The same problem.
then open a ticket there.
I just released 0.10.0-8, with the latest commits. There are many cleanups in the RISC-V code.
Could you check if the problem was solved?
Thanks for the update. I've just tested and still can reproduce this issue.
It means the problem is caused by the RISC-V patches.
It'll take some time to clean the RISC-V patches. I suggest you also complain to the RISC-V OpenOCD maintainers.
I suggest you also complain to the RISC-V OpenOCD maintainers. I did https://github.com/riscv/riscv-openocd/issues/234
Meanwhile, we disabled PIPE mode for RISC-V openOCD and use TCP port to communicate with their boards.
could you retry with the latest release (*-10)?
This issue is kills my ability to use Code Confidence plugin.
...on Windows 10 that is with System Workbench and STLink V2.
I suggest you repeat the same test using the Windows binaries packed by Freddy Chopin and let me know the result.
I am aware of some problems introduced by the RISC-V patches in previous releases, but the latest -10
release should be clean, I removed most of the RISC-V patches in the common code.
I just released 0.10.0-12, with the latest upstream master.
Please check if the problem was solved. If not, reopen the ticket.
Thank you. I will test.
We had a similar problem with ARM before which was resolved a few months ago (https://github.com/gnu-mcu-eclipse/openocd/issues/18). The similar issue could be reproduced for RISC-V now:
/cc @palmer-dabbelt