If I remember well, when I used Atmel Studio, during the upload with Atmel-ICE some led on the box flash.

Now nothing flash on the box.

I think the Atmel-ICE is enabled, see attached image.

Hi
I have some problems with the page: https://www.visualmicro.com/page/SAMD-Debugging.aspx the picture are different from my screen, probably a different version of software.

I have the Atmel-ICE connected from the SAM Port to the board MKRWiFi1010.

In VS I have two options: "Atmel-ICE" and "Atmel ICE over OpenOCD(vMicro)" I try both and nothing change.

Here you can find a screenshot to check if you see something wrong.

Thank you
Livio

I have disinstalled Visual Studio and start again from the beginning.

During all the following operations Atmel-ICE is connected via USB to the PC and via JTAG to the board MKRWiFi1010 which is connected to the same PC to another usb port, so is powered on.

Arduino IDE is already installed, version 1.8.13 (the last)

I downloaded again Visual Studio and install with workloads checked only "Sviluppo di applicazioni desktop con C++" (is in italian, I can't dowload it in english, but I add the english pack).

I put the sketch, EthernetHTTPS.ino in a folder and compile with Arduino IDE without errors.

Open Visual Studio -  Extensions – Manage Extensions – Arduino IDE for Visual Studio (Visual Micro) Trial – Download

When I close Visual Studio, Visual Micro is installed.

I open again Visual Studio Without code - Extensions – vMicro – Open Existing Arduino Project – I select the file EthernetHTTPSfile .ino, is loaded without problems.

Now I have to do some selection on Visual Studio, I'm not sure if they are all the necessary ones:
- I select Atmel-ICE as debugger on the left.
- vMicro - Uploader - Hardware Programmer: Atmel-ICE
- vMicro - Debugger (see screenshot1)

VMicro - Build 

The program is compiled without errors, no more strange errors like the first post.
I set a breakpoint at line 55 clicking on the left, a red dot is displayed.
vMicro - Build & Upload
The program is uploaded and stop at breakpoint at line 55.

Now I close this post here, untill here all is ok, the problems are about debugging, next post.

The missing attachment from the previous post.

Good to hear you sorted that. Moved your next questions to a new thread so that we can classify and read posts more easily.

Off-Topic replies have been moved to this Topic.

btw: When you are debugging the underlying core you might find some code comes from .a libraries and therefore there is no source code available for the debugger. Debugging you own code and most libraries should always work. Optimization can be an issue for gdb and some underlying library and core codes are not designed to run without optimization.

I suggest you test the debugger on known code to start with and then delve deeper. The Microsoft GDB system gets it right most of the time. If you have a problem then creating a new forum thread for each seperate issue will help us be more accurate with our answers.