Maix Bit with Sipeed USB-JTAG/TTL RISC-V Debugger about platform-kendryte210

[robertlipe]

I found this while looking for another bug report. I have no actual superpowers for your problem here. (sorry.) After over a year, I'm sure that's frustrating.

I think the meat of this report is:
jtag_examine_chain_end(): Unexpected idcode after end of chain: 581 0xab9b2b91 Warn : 169 268
core.c:1058 jtag_examine_chain_end(): Unexpected idcode after end of chain: 613 0x506ba363 Error: 170 268
core.c:1197 jtag_examine_chain(): double-check your JTAG setup (interface, speed, ...) Error: 171 268
core.c:1506 jtag_init_inner(): Trying to use configured scan chain anyway... Debug: 172 268

I've not had great luck with the Sipeed Debuggers (I'm dumpster diving in search results for a reason) but it looks like the JTAG communication is bad. I'd double check the colored wires between the K210 and the SiPeed/FTDI board. Also check that any devices on the K210 aren't electrically interfering with the signals and that you don't have too much voltage sag. I'd start double checking the colored ones, then K210 attachment, then the USB cables.

After getting frustrating with this last year, I went to Team Segger and considered it money VERY well spent. Now I'm back, punishing myself with this debugger (on a different board, though K210 was my original pairing) and wondering why I do it.

Good luck. I know there's no really tangible help, but you have a shoulder to cry on. :-)