I don’t know whether it’s correct that both channels (I’ve never seen one J-Link with 2 channels?!
The board definition says that jlink is the default upload method
},
"frameworks": [
"freedom-e-sdk",
"freertos",
"zephyr"
],
"name": "SparkFun RED-V Thing Plus",
"upload": {
"maximum_ram_size": 16384,
"maximum_size": 16777216,
"protocols": [
"jlink"
],
"protocol": "jlink"
},
"url": "https://www.sparkfun.com/products/15799",
"vendor": "SparkFun"
}
And yeah definitely JLink CLI is invoked here
if tool == "jlink":
assert debug.get("jlink_device"), (
"Missed J-Link Device ID for %s" % board.id)
debug['tools'][tool] = {
"server": {
"package": "tool-jlink",
"arguments": [
"-singlerun",
"-if", "JTAG",
"-select", "USB",
"-speed", "1000",
"-jtagconf", "-1,-1",
"-device", debug.get("jlink_device"),
"-port", "2331"
],
"executable": ("JLinkGDBServerCL.exe"
if system() == "Windows" else
"JLinkGDBServer")
},
"onboard": tool in debug.get("onboard_tools", [])
show original
So first please make sure you have the drivers installed per J-LINK — PlatformIO latest documentation .
You can also try to use https://zadig.akeo.ie/ and load libWin32Usb or libUSB drivers onto the JLink and see if that changes anything in the upload? (Required for ESP32, see ESP32 + J-link debugger does not start - #27 by manuelbl )
) are in CDC / USB-UART adapter mode. Normally they are loaded with libUSB drivers via Zadig and are interacted with via openocd or JLink.exe.