JTAG configuration

[francislaus]

The JTAG config seems to be broken. See here:

[  157.458035] runme.sh[1181]: Info : TAP riscv.cpu does not have valid IDCODE (idcode=0xfffffffc)
[  157.464833] runme.sh[1181]: Info : TAP auto0.tap does not have valid IDCODE (idcode=0xfffffffe)
[  157.469883] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 34 0x00000000
[  157.474993] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 66 0x00000000
[  157.480373] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 98 0x00000000
[  157.485360] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 130 0x00000000
[  157.490773] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 162 0x00000000
[  157.496120] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 194 0x00000000
[  157.501599] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 226 0x00000000
[  157.506683] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 258 0x00000000
[  157.511991] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 290 0x00000000
[  157.517316] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 322 0x00000000
[  157.522584] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 354 0x00000000
[  157.527596] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 386 0x00000000
[  157.532944] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 418 0x00000000
[  157.538353] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 450 0x00000000
[  157.542453] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 482 0x00000000
[  157.547706] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 514 0x00000000
[  157.552896] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 546 0x00000000
[  157.558174] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 578 0x00000000
[  157.563532] runme.sh[1181]: Warn : Unexpected idcode after end of chain: 610 0x00000000
[  157.568825] runme.sh[1181]: Error: double-check your JTAG setup (interface, speed, ...)
[  157.573762] runme.sh[1181]: Error: Trying to use configured scan chain anyway...
[  157.578365] runme.sh[1181]: Error: riscv.cpu: IR capture error; saw 0x00 not 0x01
[  157.582829] runme.sh[1181]: Warn : Bypassing JTAG setup events due to errors

It seems to run ok in most cases, but might contribute to some problems.

[gameboo]

All I can think of on where this one could be coming from at the moment is possibly from there: https://github.com/CTSRD-CHERI/jtagvpi_to_fmemdmi
We have been aware of these messages, but besides reporting jtag configuration complaints, the tools proceed without issue.