Debug GIGA using IDE2 Debugger?

[KurtE]

I noticed that the new board release 4.0.10 now has some stuff in the boards.txt and the like that enables the debug button in the IDE.

Does it work? Any suggestions on which hardware debugger to use? setup?

In my case I have a:

ST-Link V2 with an OliMex 20 to 10 pin converter which I used to use to program a board that Trossen Robotics used to make:

J-Link Mini EDU - Which sometimes connects and could debug using the Seger software.

And one that I believe @ptillisch mentioned for dbugging a different board, from Tindie:
CMSIS-DAP Compliant SWD Debugger from Alex Taradov on Tindie

And the person who sold those also recommened using an RPI Pico...

Suggestions?

[Merlin513]

Hope someone from Arduino Team jumps in here since I have not been able to get the J-link mini edu to work properly as well.

[KurtE]

Found at least a partial solution, which I posted in the thread:

Arduino IDE 2.2.1 debug failure

@wwatson @Merlin513 @ptillisch: Some success I downloaded the latest version of the JLINK software: I created the debug_custom.json file: { "servertype": "jlink", "device": "STM32H747XI_M7", "interface": "SWD", "serverpath": "D:/Program Files/SEGGER/JLink_V794/JLinkGDBServerCL" } Note: Update the above to where you installed the JLINK code. .. [image] Edit: wondering if other debugger modules will work as well, like the STLink/V2 Or the Tinde cmis-dap (likewise Pico)?

As I mentioned in that thread, it would be nice to know if other hardware debuggers can be used and if so what is needed to do so.

[davet322]

nightly build from 12/14 allows debugging arduino giga with stlink

see
arduino ide nightly build 11-30. set up small sketch. Debugger does not start with stlink and arduino giga · Issue #2299 · arduino/arduino-ide (github.com)

[KurtE]

@davet322

nightly build from 12/14 allows debugging arduino giga with stlink

Thanks,

I have a STLink V3 on order should arrive next week. I have been doing it using J-llink mini which works some, but you have to add file to each sketch....

Now to play

[KurtE]

Quick update: I tried with the other debug dongle that @ptillisch mentioned for a different board
CMSIS-DAP Compliant SWD Debugger from Alex Taradov on Tindie
And it appears like it might work

[Merlin513]

I will second that - using the same CMSIS-DAP SWD debugger as you. Do get a bit more info on whats going on with the peripherials but without does not show where any lower than top calls to mbedos.

for instance if I look at the I2C clock issue, Shows me it dies in Wire.cpp - setClock -> wire.cpp( master->frequency(freq) but thats it. So as long as you are using it to debug your sketch you are ok.

[Merlin513]

Had a thought - Maybe Arduino should think about providing a .a file with the debug stuff set up so each users does not try and create their own.

[KurtE]

I agree that it would be nice if they provided some easy mechanism for developers to rebuild and debug the main core code base.

The only other boards I remember doing much with, that their Arduino boards manager code would install the majority of their core with a static library, was some of the Robotis boards, like OpenCM 9.04.

One thing that was nice, though was reasonably easy to setup a developers version, in your /hardware directory where if you use the main (or might have been master) branch it built the same way as their release, but if you changed to the dev branch, it was setup to build all of the code from sources, which was both great for debugging as well as fixing or extending the core base code. When you issued a Pull Request, you would copy the header files to a specific location as well as the generated archive file.

@ptillisch and other Arduino developers... Wonder if something like this is possible here?

[the_marox666]

Hi, I have a Stlink V3. Could be used to debug Arduino Giga? at which CN should be plugged?

[ptillisch]

@KurtE

J-Link Mini EDU - Which sometimes connects and could debug using the Seger software.

I saw you already got it working by installing the proprietary SEGGER software and adjusting the debugger configuration via a debug_custom.json file added to the sketch. In case you find that inconvenient, you might be glad to hear that, since Arduino IDE 2.3.0, it is now possible to use a J-Link debug probe without installing the SEGGER software or adding a debug_custom.json file to the sketch. The platform has been configured to configure the free open source OpenOCD tool that is installed along with the "Arduino Mbed OS Giga Boards" platform appropriately for use with a J-Link debug probe.

1. Select Tools > Programmer > JLink from the Arduino IDE menus.
2. Click the "Start Debugging" button on the Arduino IDE toolbar.

If you are using Windows, the debugger initialization might fail with the following error message shown in the "gdb-server" panel at the bottom of the Arduino IDE window:

Warn : Failed to open device: LIBUSB_ERROR_NOT_SUPPORTED.
Error: No J-Link device found.

The reason is that the drivers provided by SEGGER are incompatible with OpenOCD it is necessary to replace them with the WinUSB drivers.

I'll provide instructions you can follow to install the WinUSB driver:

1. Download the "Zadig" driver installation tool from this website:
   http://zadig.akeo.ie/
   ⓘ Note that the use of Zadig is officially recommended by the OpenOCD developers.
2. Plug your USBasp into your computer.
3. Start "Zadig".
4. From the dropdown menu in the "Zadig" window, select "J-Link".
   If it doesn't show up on the menu, then select Options > List all devices from the Zadig menus and check again.
5. Click the up or down arrows next to the Driver selection box on the right side until you see "WinUSB".
6. Click the "Replace Driver" button.
7. Wait for the driver replacement process to finish.
8. Close the "Zadig" window.

Now click the "Start Debugging" button on the Arduino IDE toolbar again. Hopefully this time it will start up and work as expected.

---

In case you wish to continue using the debug_custom.json approach, you should be aware of this:

Starting 2.3.0 debugger with J-Link fails: "unable to find CMSIS-DAP device"

Hi @HarrySatt. A significant rework of the debugger configuration system was released in Arduino IDE 2.3.0. This was necessary because as more and more Arduino boards platforms started taking advantage of the debugger feature, some advanced requirements emerged that were not properly accommodated by the original the initial experimental system. The new system is more powerful and flexible, so this change will greatly benefit the platform developers and users in the years to come, but unfortunat…

[ptillisch]

@the_marox666

I have a Stlink V3. Could be used to debug Arduino Giga? at which CN should be plugged?

Sure. It is supported starting from Arduino IDE 2.3.0, with the latest version of the "Arduino Mbed OS Giga Boards" platform. I'll provide instructions:

1. Connect the ST-LINK to the GIGA R1 WiFi board.
2. Connect the ST-LINK to your computer with a USB cable.
3. Select Tools > Programmer > STMicroelectronics STLINK from the Arduino IDE menus.
4. Click the "Start Debugging" button on the Arduino IDE toolbar.

@the_marox666

at which CN should be plugged?

Does "CN" mean connector??? If so, then connect it to the header marked "JTAG" on the board's silkscreen.

[ptillisch]

@KurtE

it would be nice to know if other hardware debuggers can be used

I have also verified it is working with a DAPLink-based debug probe (with Tools > Programmer > ARM CMSIS-DAP Compatible selected from the Arduino IDE menus).

I bought a manufactured probe, but in theory it should be possible to make DIY one since the ARM DAPLink firmware is open source:

GitHub - ARMmbed/DAPLink

I gave it a try with a dodgy Chinese "Blue Pill" board I happened to have in my board hoard, but unfortunately never managed to get it working as a debug probe even though I was able to flash the firmware.

[KurtE]

Thanks @ptillisch - I updated the solved marking to one of your new ones here as it gives a lot more information to the users, on how to use several different debugging probes.

Thanks again!

[laramsey]

So with j-link, it seems like there are two ways to go here. One is OpenOCD / Zadig, and the other is Segger. The devil is in the details; I respect the work you guys put into this, and would love to avoid re-inventing any wheels here. Is there any consensus as to which is easier / better to achieve? I just want to get started debugging my giga project that's overdue. (That is, I don't care about Ford vs. Chevy - just want to reach the destination on time.) I hope this is a reasonable question to ask on the forum...

[ptillisch]

Hi @laramsey. In my opinion, the OpenOCD approach I described is easier.

However, if you are also using the proprietary tools provided by Segger for applications other than debugging the GIGA R1 WiFi board via Arduino IDE, then the debug_custom.json approach described by @KurtE here (with this modification applied) will be best since it might be that the Segger tools won't work with the WinUSB driver that is used with the OpenOCD approach.

[laramsey]

Hi ptillisch,
Thanks so much for jumping in here. I did go down the Segger software path. It's not my preference, but I hesitate to de-install it since it's all I have working at the moment. So if the debug_custom.json can work, I'd like to use it. I never found the file "JLinkGDBServerCL.*, but I did find the path below. Just a few dll's in there. Anyway, here is my debug_custom.json:

[
  {
    "configId": "arduino:mbed_giga:giga:programmer=jlink",
    "server": "jlink",
    "servertype": "jlink",
    "device": "STM32H747XIH6",
    "interface": "swd",
    "serverPath": "C:/Program Files/SEGGER/JLink_V796g/GDBServer",
    "serverpath": "C:/Program Files/SEGGER/JLink_V796g/GDBServer"
  }
]

and here is the GDBserver output:

Blockquote
[2024-05-14T21:43:19.898Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to "DEBUG CONSOLE" to see GDB interactions.
"C:/Program Files/SEGGER/JLink_V796g/GDBServer" -singlerun -nogui -if swd -port 50000 -swoport 50001 -telnetport 50002 -device STM32H747XIH6
[2024-05-14T21:43:22.437Z] SERVER CONSOLE DEBUG: GDBServerConsole: onBackendConnect: gdb-server program client error Error: read ECONNRESET
[2024-05-14T21:43:22.439Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed
GDB server session ended. This terminal will be reused, waiting for next session to start...
Failed to launch undefined GDB Server: Error: spawn C:/Program Files/SEGGER/JLink_V796g/GDBServer ENOENT

[ptillisch]

You can see why I say the OpenOCD approach is more simple

@laramsey

I never found the file "JLinkGDBServerCL.*, but I did find the path below.

Are you certain the file C:/Program Files/SEGGER/JLink_V796g/JLinkGDBServerCL.exe doesn't exist? If so, there is something wrong with your installation of the "J-Link Software and Documentation Pack". I just installed version 7.96 on my Windows machine and that file is present in my installation.

Likewise, there is no GDBServer executable in the installation. There is a folder of that name. This field of the debug_custom.json is the path of the J-Link GDB Server executable file.

[laramsey]

Yes, I had the path screwed up. Thanks for keeping me straight on that. Guess I was doing that too late at night. Anyway, fixed that (and verified the file is there), but still don't have blast off:

Blockquote
Failed to launch undefined GDB Server: Timeout.
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: STM32H747XIH6
Target device parameters: none
Target interface: SWD
Target interface speed: 4000kHz
Target endian: little

At least I can say the probe itself is good, because it works with Ozone.

[laramsey]

Trying the exact same thing, now getting:

Blockquote
Open On-Chip Debugger 0.11.0+dev-gab95bac57-dirty (2021-05-11-10:45)
Licensed under GNU GPL v2
For bug reports, read
OpenOCD: Bug Reporting
CDRTOSConfigure
embedded:startup.tcl:26: Error: Can't find interface/{programmer.protocol}.cfg
in procedure 'script'
at file "embedded:startup.tcl", line 26
[2024-05-19T02:07:11.898Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed
GDB server session ended. This terminal will be reused, waiting for next session to start...