Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Hardware debug on Arduino Giga R1 (Read 179 times)
Jose Martinez
Newbies
*
Offline


Posts: 2
Location: Bergondo
Joined: Apr 10th, 2025
Hardware debug on Arduino Giga R1
Apr 10th, 2025 at 9:27am
Print Post  
Hi,

I'm new to the forum, although I've been a Visual Micro user for over 5 years, which I use as a development tool in my work.

Currently, we have a new project in hand, in which we have decided to upgrade our old Mega2560, which we have pushed to its limits, to the recent Giga R1 with all the advantages it brings.

For this reason, we have acquired a J-Link Ultra+ to be able to debug the two cores of the processor efficiently and comfortably.

However, we have encountered the problem that when trying to configure it, after following all the steps in the installation guide, including driver replacement, with the Arduino Giga R1 board selected, when configuring the debug as Hardware, the only option that appears in the Hardware Debugger section is "Manual/Custom" and the J-Link does not appear as such as indicated in the Visual Micro installation guide.

We have verified that the J-Link works by performing a debug test through its Ozone platform and everything seems to work correctly.

We have tested changing the board to the Portenta H7 (they use the same chip) and in this case, the J-Link does appear as a Hardware Debugger option.

In our understanding, it seems that the MBED_Giga platform is not yet supported by Visual Micro for debugging as the MBED_Portenta platform is.

Is there any solution to support the MBED_Giga platform, such as importing and copying the settings from the MBED_Portenta platform to support this board and be able to use the debug?

Thanks in advance.
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2697
Joined: Feb 13th, 2019
Re: Hardware debug on Arduino Giga R1
Reply #1 - Apr 10th, 2025 at 1:32pm
Print Post  
Thanks for the detail, and we will look at adding this configuration into the pre-configured Debugger listings.

This can be configured today manually, which ensures we get the preconfigured selection correct, as well as get you debugging right now:

1) Download the OpenOCD version from the below URL:
https://www.visualmicro.com/downloads/tools/openocd-0.10.0.20200213/openocd-0.10...

2) Unzip to C:\ProgramData\vmicro\tools, so you have the below folder structure:
C:\ProgramData\vmicro\tools\openocd-0.10.0.20200213\
C:\ProgramData\vmicro\tools\openocd-0.10.0.20200213\bin
C:\ProgramData\vmicro\tools\openocd-0.10.0.20200213\bin-x64
etc...

3) In your Project with the Arduino Giga R1 Board selected, targeting the Main Core, set the below options:
  • vMicro > Debugger > Debug: Hardware
  • vMicro > Debugger > Hardware Debugger: Manual/Custom


4) Click vMicro > Add Code > Add Custom GDB Debugger

5) Open the "GIGA.Release.debugger_launch.json" file from Solution Explorer, and replace its' contents with the attached files contents.

6) Click Debug > Attach to Process or Debug > Start to begin debugging on the Main (M7) core.


Let us know if you have any issues configuring this or problems running the debugging session.
« Last Edit: Apr 10th, 2025 at 1:34pm by Simon@Visual Micro »  

Please Register or Login to the Forum to see File Attachments
Back to top
IP Logged
 
Jose Martinez
Newbies
*
Offline


Posts: 2
Location: Bergondo
Joined: Apr 10th, 2025
Re: Hardware debug on Arduino Giga R1
Reply #2 - Apr 11th, 2025 at 12:46pm
Print Post  
Hi,

First of all, thank you for your help, but I have found that it did not work correctly.

I followed all the steps: downloaded OpenOCD from the link, unzipped it in the indicated path, enabled hardware debugging in the project, added the JSON with the attached configuration; but when I get to the step Debug > Attach to Process, an error appears saying "Unable to start debugging. Invalid characters in the path."

In the output section at the bottom, the following message appears:
1>------ Operación Implementar omitida: Proyecto: MK4xPilot_M7, configuración: Release ARM ------
1>Proyecto no seleccionado para compilarse para esta configuración de solución 
========== Implementación: 0 correcta, 0 con errores, 1 omitido ===========
========== Implementar completado a las 14:26 y tardó 00,062 segundos ==========

I have a second computer at home with another Visual Micro license and I tried to make it work on this one (changing the paths) and I couldn't get it to work. I tried modifying some of the addresses but I don't know what they are associated with, so I couldn't get it to work.

Can you help me understand why this error occurs and how to fix it? Maybe a guideline on which paths or configurations should be implemented in the JSON configuration and where to get them would be enough to avoid unnecessary hassle.

I'm trying to attach the output files for each PC and the JSON files, but I can't find a way to do it in this response, so I'm leaving a link attached with these files. The error is the same on both PCs.

https://texascontrol-my.sharepoint.com/:u:/g/personal/jose_martinez_texascontrol...

Thanks!
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2697
Joined: Feb 13th, 2019
Re: Hardware debug on Arduino Giga R1
Reply #3 - Apr 14th, 2025 at 9:26am
Print Post  
Apologies, I hadn't fully corrected the path for "program", please try the contents of the attached file.  The field should point to the projects' bin file which is in the build folder and named projectname.ino.bin.

We will review the below documentation and add in how to obtain the paths required for the custom JSON approach:
https://www.visualmicro.com/page/Debugging-Using-Custom-Hardware.aspx
  

Please Register or Login to the Forum to see File Attachments
Back to top
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint