You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems only boards based on the SAMD MCU and featuring a debugger are supported. I tested debugging successfully against the Arduino Zero —see arduino/arduino-pro-ide#216.
You need a debugger. Only the Arduino Zero board includes a debugger for the moment. The Arduino Nano 33 provisions pads for a SWD connection to an external debugger.
@Matszwe02
debugging 8bit AVR involves using a protocol called DebugWire.
Right now we support SAMD chips, and since DebugWire is a complex thing to work with, I can't see it being supported.
You also need either an Atmel ICE, STK500 or Dragon
Even with the atmel ICE the message remains: Error during Debug: Cannot get command line for tool: cannot get programmer tool: undefined 'debug.tool' property
could you please provide a link to the product?
of course if you have SWD pins exposed you can debug, but need the board in question to have the extra config settings defined within boards.txt of its core
Hi @ubidefeo Yes, just as @rei-vilo has said. I used an Arduino M0, this is the same as the Arduino zero but without the edgb. So I plug in my atmel ICE into the SWD connector but am presented with the message mentioned above.
Its as if the PRO IDE doesn't see the Atmal ICE? However, what extra parameters should be set in the boards.txt?
What boards and external debuggers are currently supported and is there a configuration guide available? I've tried an Adafruit M0 Express via JLINK and get the error "https://adafruit.github.io/arduino-board-index/package_adafruit_index.json" and when I try a MKR1000 via JLINK I get the error "Error: unable to find CMSIS-DAP device".
You need a debugger. Only the Arduino Zero board includes a debugger for the moment. The Arduino Nano 33 provisions pads for a SWD connection to an external debugger.
Could other boards (Arduino Uno for example) be supported in the future or is it technically not possible because of this lack of built-in debugger ?
@tomsihap
the ATMega328 (on the Arduino UNO) only supports debugging via WireDebug interface, which needs to be enabled at low level using fuses and is only supported by a bunch of programmers and has never really been successful.
We will support interfaces based on GDB and OpenOCD for our own boards, as well as hybrid debugging over USB like we're experimenting with the Portenta H7.
Debugging on each platform requires implementation by the platform supplier, with a series of debug scripts that launch the required tools, which also have to be installed based on platform specification.
You can read about DebugWire here http://www.ruemohr.org/docs/debugwire.html out of curiosity, but I doubt anyone will ever put effort into implementing tooling for that
Activity
rei-vilo commentedon Feb 28, 2020
It seems only boards based on the SAMD MCU and featuring a debugger are supported. I tested debugging successfully against the Arduino Zero —see arduino/arduino-pro-ide#216.
kampfk3ks commentedon Feb 29, 2020
is there a list of supported Boards? I tried with Uno, nano and Mega and nothing worked so far.
rei-vilo commentedon Feb 29, 2020
Changelog:
Matszwe02 commentedon Feb 29, 2020
Will it support 8 bit Atmega boards?
rei-vilo commentedon Feb 29, 2020
You need a debugger. Only the Arduino Zero board includes a debugger for the moment. The Arduino Nano 33 provisions pads for a SWD connection to an external debugger.
ubidefeo commentedon Feb 29, 2020
@Matszwe02
debugging 8bit AVR involves using a protocol called DebugWire.
Right now we support SAMD chips, and since DebugWire is a complex thing to work with, I can't see it being supported.
You also need either an Atmel ICE, STK500 or Dragon
el-samiyel commentedon Mar 15, 2020
Even with the atmel ICE the message remains: Error during Debug: Cannot get command line for tool: cannot get programmer tool: undefined 'debug.tool' property
Does anything need to be done in a config?
ubidefeo commentedon Mar 15, 2020
@el-samiyel which board are you testing this with?
el-samiyel commentedon Mar 15, 2020
I am using the M0. Considering it doesn't have a edbg can't the atmel ice via swd be used in its place? Thanks
ubidefeo commentedon Mar 15, 2020
could you please provide a link to the product?
of course if you have SWD pins exposed you can debug, but need the board in question to have the extra config settings defined within boards.txt of its core
rei-vilo commentedon Mar 15, 2020
I tried first with the Arduino M0 Pro from Arduino.org and it didn’t work.
Then, with the Arduino Zero from Arduino.cc / Genuino, debugging worked fine.
el-samiyel commentedon Mar 15, 2020
Hi @ubidefeo Yes, just as @rei-vilo has said. I used an Arduino M0, this is the same as the Arduino zero but without the edgb. So I plug in my atmel ICE into the SWD connector but am presented with the message mentioned above.
Its as if the PRO IDE doesn't see the Atmal ICE? However, what extra parameters should be set in the boards.txt?
Board: https://store.arduino.cc/arduino-m0
Thanks
ericklein commentedon May 31, 2020
What boards and external debuggers are currently supported and is there a configuration guide available? I've tried an Adafruit M0 Express via JLINK and get the error "https://adafruit.github.io/arduino-board-index/package_adafruit_index.json" and when I try a MKR1000 via JLINK I get the error "Error: unable to find CMSIS-DAP device".
tomsihap commentedon Sep 4, 2020
Could other boards (Arduino Uno for example) be supported in the future or is it technically not possible because of this lack of built-in debugger ?
ubidefeo commentedon Sep 4, 2020
@tomsihap
the ATMega328 (on the Arduino UNO) only supports debugging via WireDebug interface, which needs to be enabled at low level using fuses and is only supported by a bunch of programmers and has never really been successful.
We will support interfaces based on GDB and OpenOCD for our own boards, as well as hybrid debugging over USB like we're experimenting with the Portenta H7.
Debugging on each platform requires implementation by the platform supplier, with a series of debug scripts that launch the required tools, which also have to be installed based on platform specification.
You can read about DebugWire here http://www.ruemohr.org/docs/debugwire.html out of curiosity, but I doubt anyone will ever put effort into implementing tooling for that
19 remaining items