Giga R1 WiFi Debugging with ST Link V3

Hello,

I am struggling to debug my code using ST Link V3 on Giga R1 WiFi board.
I installed the WinUSB drivers and I still get one or other errors. It has been days now without any progress on this board.

Right now my setup is, Connected USB-C cable to wall outlet (Mobile charger). ST LInkV3 is connected to JTAG port on he board. Seelected 'STMicro ST LINK' as programmer in IDE Tools navigation.

Board is previously programmed with USB-C from IDE. (Can we program this board with STLINK V3 debugger, I couldn't do it)

When I click 'Start Debugging' I get,

CDRTOSConfigure
hla_swd
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : Listening on port 50008 for tcl connections
Info : Listening on port 50009 for telnet connections
Info : clock speed 1800 kHz
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: open failed

[2024-08-20T15:09:07.648Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed
GDB server session ended. This terminal will be reused, waiting for next session to start...

has anyone been successfully debugging their code on Giga R1 board? I am willing to switch to a different debugger type if it works without any issue. Please help.

Hi. The readme for the arduino core for mbed GitHub - arduino/ArduinoCore-mbed says a recomp of the mbed-os lib is required. It also has links for info on debugging. Not done this myself

@ptillisch
I am now using JLink and after installing Zadig and WinUSB drivers you suggested, I now get the follwoing

CDRTOSConfigure
swd
Info : Listening on port 50001 for tcl connections
Info : Listening on port 50002 for telnet connections
Info : J-Link ARM V8 compiled Nov 28 2014 13:44:46
Info : Hardware version: 8.00
Info : VTarget = 2.387 V
Info : clock speed 1800 kHz
Error: Error connecting DP: cannot read IDR

Currently my setup looks like, The Jlink USB and the USB-C cable both go to a USB hub and the hub is connected to my laptop.

Hi @shivamadishetty.

I found another report of someone encountering this error. They found it was caused by a problem in the connections between the debug probe and the target board:

So carefully double check the connections between the ST/LINK probe and the GIGA R1 WiFi board. If you are using a ribbon cable, make sure it is in the right orientation (as opposed to rotated 180 degrees) on the header on the GIGA R1 WiFi board, and also that all ten pins of the header are inserted into the connector (as opposed to the connector being shifted off by one row of pins on the header, resulting in only five pins being inserted).