[AVR targets] Atmel Studio GDB server

[gchapman]

https://www.avrfreaks.net/forum/making-gdb-attach-gdbserver-instead-launching#comment-2420641

… (although atbackend can act as a gdb server if someone wants to use it with a gdb-enabled frontend)

Reason: atbackend.exe as an alternative to AVaRICE.

The next post in that thread shows partial integration via MIEngine.

https://github.com/Microsoft/MIEngine

 

• This topic was modified 7 years, 8 months ago by support. Reason: updated title to mention AVR

[support]

Hi,

Sure, you can configure VisualGDB to use the Atmel gdb server as well (as well as any other IDE with GDB support), although it won’t provide many advanced features included with our OpenOCD fork (e.g. automatically resolving driver issues, profiling, monitoring memory in the background), so we normally advise getting a debug probe supported by OpenOCD and using it instead.

[gchapman]

Thank you for I was not aware of  the OpenOCD advantages.

 

The intention of my post was in the context of AVR and support for recently announced AVR (tinyAVR 1-series, tinyAVR 0-series, megaAVR 0-series)

gnutoolchains.com AVR is from FSF instead of from Microchip.

AVaRICE is FOSS.

My assumption is y’all’s goal is to start with FOSS then extend that if necessary.

Edit:

FSF AVR GCC 8 adds tinyAVR 1-series :

https://gcc.gnu.org/gcc-8/changes.html

ATtiny212, ATtiny214, ATtiny412, ATtiny414, ATtiny416, ATtiny417, ATtiny814, ATtiny816, ATtiny817, ATtiny1614, ATtiny1616, ATtiny1617, ATtiny3214, ATtiny3216, ATtiny3217

• This reply was modified 7 years, 8 months ago by gchapman.

[support]

Hi,

No problem, thanks for sharing this. For AVR devices using the Atmel gdb server could be indeed better than the open source AVaRICE tool.

[gchapman]

Thank you for extending the thread’s title.

 

For VisualGDB, is there a preference for AVaRICE, or, is it any AVR GDB server?

Reason:

Risk reduction for eventual Atmel Studio EOL.

https://www.avrfreaks.net/forum/come-join-us-mplab-now-supports-avrs

 

[support]

Hi,

AVaRICE does a pretty good job for an open-source tool, so we do recommend using it. If the license of the Atmel GDB server allows using it with non-Atmel products like VisualGDB, it could be a good alternative to AVaRICE, however it might be tough troubleshooting it as it’s likely not designed to be used outside Atmel Studio.

[Author]

Posts