Andelf

Does this happen every time? I observed random fail on V203 too. I'm trying to resolve this.

Implemented in 090e25cbd396dcba4429a94387844b401614bcc6, needs verification.

I haven't dug into the gdb debugging protocol yet. I prefer to leave it to openocd. Or pyocd.

Oops, it seems Github has changed its macos-latest runner to arm64. 🤣 Thanks for the report.

I came up with an idea to access the Windows driver. The underlying driver interface is ~~open-source~~published: https://github.com/openwch/usb-jtag-spi/blob/9c925295ed755563bd91c59f7da0b6c5e4e0b1ab/src/WIN%20APP/External/CH375DLL.H

Fixed by f7a42dd12a50ed818a7e068bb9677acc8926003f

It's already displayed in basic logging: > 16:26:11 [INFO] Connected to WCH-Link **v2.11(v31)** (WCH-LinkE-CH32V305) v31 is used by official tools. v2.11 is the original version. => `0x020a`

A new "list" subcommand is added recently.

There's something wrong with the usb communication under Linux. I'll check this.

I've seen this error while developing the feature. If data0 is not configured properly, the UART link will print(It's almost always corrupted text): > Please check the SDl, and Enable...