Hi!
I'm try to use a Atmel ICE connect to AVR emulator port but there is a problem when I try to start with debugger, VM, send this error

F5: Do not start,(no action!)

if I try with
debug/attach process -> unable to start...string is null or empty

The upload with HW ICE Atmel work fine without problem.

in attach the output log file.

Can you help me?
regards

Hi,
I'm sorry but is not clear about two options A/B. Exactly what is to use GDB on the live process on chip?

My purpose is use the VM debugger via ICE emulator, I suppose this is AVR GDB simulator?

your note: for this reason will be never possible to use the ice atmel debugger?

I have lunch the debug via menu/attach/process but there is not any output, VM show immediately a window with the following error message:  Unable to start debug.... this string is null or empty without make any log file output.

in attach the log file with uploder verbose option on during the upload phase that work fine without erros.

for last. Sorry But where Can i find the board.txt and launch.json files? 

regards

I mean that you want to Debug your code actually running on the Uno Board itself, not in some emulated environment on your PC.

It is my confusion over the word emulator, apologies I didn't recognise it as also meaning debugger/programmer.

It *is* possible to setup GDB for the Uno, BUT it will involve:
1) Adding a Local Board.txt and launch.json is done from vMicro > Add Code > Add Custom GDB Debugger (Advanced).
2) Changing the fuse bits on the board and in any relevant platform.txt patterns, which can be overridden in the local board.txt as well.
!Be careful changing fuse bits as you can kill the board!
3) Configuring the launch JSON file to have the correct patterns to launch GDB and OpenOCD for the Atmel ICE and this chip. More detail on the below page:
https://www.visualmicro.com/page/Debugging-Using-Custom-Hardware.aspx

Just to confirm, are you using Microchip/Atmel Studio, or Visual Studio?

My complete setting is:
- VM
- MS visual Studio
- ATMEL ICE hardware
- Arduino UNO or Arduino nano custom board
- Win10 64bit

For this specific older Atmel Hardware, along with changing the fuse bits on the board and using the Debugging capabilities, the safest choice is to use Atmel Studio with the Visual Micro Extension.

This gives a UI for changing the fuse bits, and still has full integration with the Visual Micro toolset, alongside the Atmel specific capabilities of Atmel Studio.

We haven't implemented this within Visual Studio at present due to the risks of changing fuse bits via boards.txt being prone to error, potentially leading to an un-flash able chip.

Your license will work in both Visual Studio and Atmel Studio on the same machine, simply install the Visual Micro Extension in Atmel Studio.

If you have any issues activating it there let us know via email, with your key, and we will ensure it activates as expected.

The Serial Debugger was developed to avoid such intricacies and risks, and is a good alternative for the majority of users.

Just to confirm:
Have you set the Debugging options so it uses the Atmel Studio Debugging?
(Shown in Debug Tab, Using a Hardware Debugger on this page: https://www.visualmicro.com/page/Arduino-for-Atmel-Studio-7.aspx)

Have you selected the DebugWire Interface in the AS Debugging settings?

It should show a specific prompt if the incorrect fuse settings are found on board, to allow the DWEN fuse bit to be set HIGH if it is not already, note the bricking fuse bits on this page if you do change any others:
https://microchipdeveloper.com/8avr:avrfuses

On the Uno you also need to modify the hardware as well, so as you can see coupled with the fuse changes, there is some risk involved here.

Please attach the full message shown in the IDE.

Please also confirm you have modified the board to allow the connection marked ResetEN is broken (on an original Arduino Uno).
(NOTE - Add a jumper here if you want to be able to use the serial programming again in the future, but leave the jumper removed in this debugging scenario)

Please set the vMicro > Debugger > Debug: Off
Also ensure the vMicro > Debugger > Atmel Studio Debugger is Enabled

Then click Debug > Start Debugging and Break (which will reprogram the board and attempt to start debugging).

If the DWEN fuse is not set correctly, it will now offer to do this for you as shown below, and you need to fully cycle the power when prompted on the target board.