[marcusob]

Thanks for the quick reply ! I did what you suggested, and it certainly looks healthier, I can test the connection with the Test Button in the new project wizard when I select k210, and OpenOCD not the Jlink software and it works. But I still can’t debug, I get this message

I can see the Jlink under Universal Serial Bus (and I applied the WinUSB like VisualGDB asked me to), and under Ports (COKM ^ LPT) I can see USB-SERIAL CH340 (COM9)

“JTAG scan chain interrogation failed : al zeroes

This error typically indicates JTAG/SWD wiring problems

Please double check”

This is the GDB log

 

C:\Users\marcu\AppData\Local\VisualGDB\EmbeddedDebugPackages\com.sysprogs.riscv.openocd-kendryte\bin\openocd.exe -c “gdb_port 62446” -c “telnet_port 62447” -f interface/jlink.cfg -c “adapter_khz 3000” -f target/kendryte.cfg -c “echo VisualGDB_OpenOCD_Ready”
_ __ _ _
| |/ /___ _ __ __| |_ __ _ _| |_ ___
| ‘ // _ \ ‘_ \ / _` | ‘__| | | | __/ _ \
| . \ __/ | | | (_| | | | |_| | || __/
|_|\_\___|_| |_|\__,_|_| \__, |\__\___|
|___/
Kendryte Open On-Chip Debugger For RISC-V v0.2.3 (2019-02-21)
Licensed under GNU GPL v2
adapter speed: 3000 kHz
Info : auto-selecting first available session transport “jtag”. To override use ‘transport select <transport>’.
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
VisualGDB_OpenOCD_Ready
Info : Listening on port 6666 for tcl connections
Info : Listening on port 62447 for telnet connections
Info : J-Link ARM V8 compiled May 27 2009 17:31:22
Info : Hardware version: 8.00
Info : VTarget = 3.332 V
Info : clock speed 3000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway…
Error: riscv.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: dtmcontrol is 0. Check JTAG connectivity/board power.
Info : Listening on port 62446 for gdb connections
Info : accepting ‘gdb’ connection on tcp/62446
Error: slot_offset called with xlen=-1, slot=0
Info : Got data from 0x0 but expected it from 0x4
Error: slot_offset called with xlen=-1, slot=0
Error: Unexpected HART read back from DMCONTROL: 0 instead of 0

Error: slot_offset called with xlen=-1, slot=0
Info : Got data from 0x0 but expected it from 0x4
Error: slot_offset called with xlen=-1, slot=0
Error: Target not initialized. Return ERROR_FAIL.
Error: get register list failed
Info : Failed detecting Target Description Support, disabling
undefined debug reason 7 – target needs reset
Error: slot_offset called with xlen=-1, slot=0
Info : Got data from 0x0 but expected it from 0x4
Error: slot_offset called with xlen=-1, slot=0
Error: Unexpected HART read back from DMCONTROL: 0 instead of 0

Error: slot_offset called with xlen=-1, slot=0
Info : Got data from 0x0 but expected it from 0x4
Error: slot_offset called with xlen=-1, slot=0
Error: Target not initialized. Return ERROR_FAIL.
Info : dropped ‘gdb’ connection

 

[marcusob]

When I select USB as a debug device I can see the fly swatter, I wander can those settings be used for the Sipeed USB RV debug probe ?

Attachments:

You must be logged in to view attached files.

[Author]

Posts