Open donn opened 1 year ago
Info : TAP lx.cpu does not have valid IDCODE (idcode=0x0) Info : TAP auto0.tap does not have valid IDCODE (idcode=0x80000000) Info : TAP auto1.tap does not have valid IDCODE (idcode=0xc0000000) Info : TAP auto2.tap does not have valid IDCODE (idcode=0xe0000000) Info : TAP auto3.tap does not have valid IDCODE (idcode=0xf0000000) Info : TAP auto4.tap does not have valid IDCODE (idcode=0xf8000000) Info : TAP auto5.tap does not have valid IDCODE (idcode=0xfc000000) Info : TAP auto6.tap does not have valid IDCODE (idcode=0xfe000000) Info : TAP auto7.tap does not have valid IDCODE (idcode=0xff000000) Info : TAP auto8.tap does not have valid IDCODE (idcode=0xff800000) Info : TAP auto9.tap does not have valid IDCODE (idcode=0xffc00000) Info : TAP auto10.tap does not have valid IDCODE (idcode=0xffe00000) Info : TAP auto11.tap does not have valid IDCODE (idcode=0xfff00000) Info : TAP auto12.tap does not have valid IDCODE (idcode=0xfff80000) Info : TAP auto13.tap does not have valid IDCODE (idcode=0xfffc0000) Info : TAP auto14.tap does not have valid IDCODE (idcode=0xfffe0000) Info : TAP auto15.tap does not have valid IDCODE (idcode=0xffff0000) Info : TAP auto16.tap does not have valid IDCODE (idcode=0xffff8000) Info : TAP auto17.tap does not have valid IDCODE (idcode=0xffffc000) Info : TAP auto18.tap does not have valid IDCODE (idcode=0xffffe000) Info : TAP auto19.tap does not have valid IDCODE (idcode=0xfffff000) Warn : Unexpected idcode after end of chain: 21 0xfffff800
That seems to indicate that you have an issue at the JTAG level, VexRiscv itself not being involved yet
Can you probe the jtag ?
Will have to borrow a JTAG programmer, but I'll see what I can do.
I should mention though this particular series of messages is also in the guide, so I thought they were "expected."
Colleague just tried with an Arty A7- curiously, when programming with Digilent Adept, OpenOCD connects fine, but if programming with OpenOCD it just hangs.
Ahhh my bad, i were assuming it was using jtag XD Sorry. Don't know so much about it
So the Error: !!! Error: Can't communicate with the CPU Error: !!!
Are some checks which are done when openocd VexRiscv connect to be sure the system is alive.
Hmm not sure how i can help as i don't realy know that flow with the litex_server
I'm following this guide: https://github.com/enjoy-digital/litex/wiki/Use-GDB-with-VexRiscv-CPU
However, after starting litex_server and OpenOCD (
litex_server --uart --uart-port=/dev/ttyACM0 --bind-port=1234
), OpenOCD fails to connect to the CPU. Initially it was just quitting altogether with the same issue as https://github.com/enjoy-digital/litex/issues/1532: I applied the workaround in the issue, but then ran into another issue:Here's how I generate my gateware, for reference: