Hi @jpthibault,
thanks for the quick response, I appreciate it!
After re-installing the driver I got a little closer to programming the firmware, however I ran afterwards in another error, which is now:
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-03-25-17:32)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
force hard breakpoints
Info : clock speed 2000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: riscv.cpu: IR capture error; saw 0x3f not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Unsupported DTM version: 15
Warn : target riscv.cpu examination failed
Info : starting gdb server for riscv.cpu on 3333
Info : Listening on port 3333 for gdb connections
Error: Target not examined yet
Error: Unsupported DTM version: 15
Searching for this type of error, especially JTAG scan chain interrogation failed: all ones led me to this github issue, which says that there is still some issue with my JTAG connection.
Especially connecting TDO to ground should have given me instead of […] all ones an error […] all zeros, however this is not the case for me.
Again, I played around with the ftdi channel in my .tcl file and changed adapter speed to lower and higher speeds, but always get the same error.
Is this still a driver issue or something I did wrong when connecting the pins from Tigard to the board? Again I tried to followed the steps from here, which says:
[…] you’ll need to program your target firmware separately, using an external JTAG programmer connected to the A35’s FPGA JTAG port, not the soft-core port (e.g. connect your programmer TDI/TDO/TCK/TMS to those header pins on the CW313 board, set DIP switches 5-8 to “on” on the A35 target board, and disconnect any other JTAG programmer from the A35’s “jaytag” header).
So I connected these header pins to the CW313 board, have set the DIP switches 5-8 to “on” on the A35 and had no JTAG progammer on the A35 “jaytag” header
I saw that there are three other questions ([1], [2], [3]), however [2] refers to debugging, which is not what I wanted to do and also does not use the CW313 board. [3] uses the CW308 UFO and in [1] a CW305 board was used, and it was said that
“FPGA JTAG” header (lower left corner of the CW305)
on the CW305 should be used.
Trying to apply this to the CW312T-A35 target seems to suggest to connect the programmer pins to the “FPGA Jaytag”, but if I understand it correctly this is not the way it is described here.
I feel like I made some stupid mistake when connecting the Tigard pins to the CW313 board, but as all error messages that I get from openocd are the same for what I tried so far, I am pretty stuck at this point.
Is there any suggestion or explanation that I can find to solve this issue? 