I can't really confirm if these are the only things that need fixing. I only
have a certain number of cases I can check. (I didn't even know there was a
second instance of "jtag configure.")
So far that one command was the only one that went wrong for me. The failures I
ran into were:
1) A Xil
If I did not made mistakes, here is the list of commands that are impacted by
commit 877cec20dca6.
Now we need to check if any of them has wrong "mode".
Please cross check with me
Commands with mode = COMMAND_CONFIG
src/jtag/hla/hla_transport.c: "hla newdap"
src/jtag/tcl.c: "jtag newtap"
src/ta
> On 6 Feb 2019, at 23:11, Tim Newsome wrote:
>
> ... then https://github.com/riscv/riscv-openocd is the place you want.
just please be aware that this fork may not run properly for other targets.
I tried to merge it into GNU MCU Eclipse OpenOCD, but it affected ARM targets,
so I had to re
The code you're looking for is riscv_get_gdb_reg_list() in
src/target/riscv.c. If you are thinking of making RISC-V-specific changes,
then https://github.com/riscv/riscv-openocd is the place you want. It has
many changes that haven't made it to the OpenOCD mainline yet.
Tim
On Wed, Feb 6, 2019 at
Actually the error is in src/jtag/tcl.c
The right value for the command "jtag configure" should be COMMAND_ANY.
Before commit 877cec20dca6 there were no check on the value, so the wrong value
passed unnoticed.
Our mistake, we merge the commit too quicly, without a complete audit of the
commands t
On Mittwoch, 6. Februar 2019 15:06:33 CET Xen Mann wrote:
> We have figured out, that target_type->get_gdb_reg_list() is mandatory for
> supporting the gdb connection, see proof (if I'm not wrong) in the end of
> the mail. Because my core is a riscV (zeroRiscy) I had a look at the
> target/riscv/ri
On Mittwoch, 30. Januar 2019 11:27:41 CET Xen Mann wrote:
> Hey there again!
> adding this new interface I wonder, how actually does openOCD retrieve the
> information where the program counter(pc) is on the target. At least the
> connected client which is stepping through the lines of source code
---
** [tickets:#225] Error: The 'jtag configure' command must be used after
'init'.**
**Status:** new
**Milestone:** 0.9.0
**Created:** Wed Feb 06, 2019 08:19 PM UTC by Bill Paul
**Last Updated:** Wed Feb 06, 2019 08:19 PM UTC
**Owner:** nobody
Checking out the most recent sources from git
> Does riscV support a GDB-connction. If yes, how?
Yes it does. Why don't you look at the SiFive RISC-V fork of OpenOCD? Otherwise
you might be reinventing a wheel that already exists...
https://github.com/riscv/riscv-openocd
___
OpenOCD-devel mailin
We have figured out, that target_type->get_gdb_reg_list() is mandatory for
supporting the gdb connection, see proof (if I'm not wrong) in the end of the
mail.
Because my core is a riscV (zeroRiscy) I had a look at the
target/riscv/riscv-01x.c. There is no such function pointer in their structure
This is an automated email from Gerrit.
Marc Schink (openocd-...@marcschink.de) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/4885
-- gerrit
commit 378032469b6e4caf4e2c4a05605cbb3a99bde2ee
Author: Marc Schink
Date: Wed Feb 6 13:43:16 2019 +0100
This is an automated email from Gerrit.
Marc Schink (openocd-...@marcschink.de) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/4884
-- gerrit
commit 9398fadb075937f4dcc0bb271e5a5d0e362b7997
Author: Marc Schink
Date: Wed Feb 6 12:07:10 2019 +0100
12 matches
Mail list logo
