Interfacing with avr-gdb

[epasveer]

Interfacing with avr-gdb

[epasveer]

Hi Bernhard,

Thanks for try it out! And, of course, thanks for your very detailed descriptions. To be honest, I've never used gdbserver before. I knew I would have to revisit it eventually.

I'll get to your points hopefully soon.

Thanks again!

[epasveer]

Hi Bernhard,

For the "alternate gdb executable" bug, I've fixed that in version 1.0.6.

I will be working on the other problems you mention.

[felias-fogg]

Cool, will try it out! My "hardware debugger" for classic AVR ATtinys is meanwhile in state so that people can use it: https://github.com/felias-fogg/dw-link

[epasveer]

Wow, almost a year to the day. I'm getting back to this task.

Over the past year, I've learned a lot about 'gdbserver' and some more about embedded development/debugging. I hope to use this time now to resolve this ticket.

If you want to debug things having to do with avr-gdb, I recommend to download the packages gdb-avr (the avr debugger), simavr (an AVR simulator), and, of course, the avr toolchain gcc-avr.

Fantastic advice. I also found this tidbit that should help me.

https://blog.oddbit.com/post/2019-01-22-debugging-attiny-code-pt-1/

So, I issued the file and the load command:

The 'file' command is already there. It's loading the executable and symbol table from the file. Seer does this and has a optional way to load the symbols from a separate file.

The 'load' command is new to me. It appears to download the executable to the remote end. I'll look to implement this as part of the 'connect' mode in Seer.

The debugger does not show any file under the list of source or library files. I could manually select the source file, though.

I'll debug this with the simavr setup.

I could not set a breakpoint (probably something caused by the two control characters in front of the file name):

Those control characters are actually UTF-8 characters. The first one is a visual tab '>>' character. I wonder how your got the filename? Cut-n-Paste? Or was the filename returned by something? I can filter them out. I just need to know where they are coming from.

[epasveer]

I got Seer working with simavr and avr-gdb. avr-gdb seems to have an older version of the MI interpreter (the api for frontends to interface with gdb). I'll see if I can work around this. Also, I have to manually enter the 'file' and 'load' commands, too. I'll work on this.

Anyway, a pic.

$ simavr -m attiny85 -f 1000000 pipower.elf  -g
Loaded 2498 bytes at 0
Loaded 6 bytes at 800060
avr_gdb_init listening on port 1234

$ seergdb --gdb-program /usr/bin/avr-gdb --connect :1234

[epasveer]

Specifying the program name as the symbol file works for seer.

$ seergdb --gdb-program /usr/bin/avr-gdb --connect :1234 --sym pipower.elf

This has the same effect as using the 'file' command.

[epasveer]

After playing around for a bit, I discovered the "avr" package that OpenSuse provides is extremely out of date. Especially for the version of gdb that is provided. Many of the "mi" api calls that Seer depends on just don't exist or work.

I posted a question on r/embedded and someone responded with a website that does standalone builds of the "avr" toolchain.

https://www.reddit.com/r/embedded/comments/18uockj/latest_avr_linux_toolchain/
https://blog.zakkemble.net/avr-gcc-builds/

Installing this on my machine works perfectly. Here's a screenshot.

[epasveer]

It seems "FLAGS" is not available on avr chips. I'll make this optional in the "assembly view".

[epasveer]

So the summary is to use an avr toolchain that is recent. Like gcc/gdb version 12 or newer.

https://blog.zakkemble.net/avr-gcc-builds/

[epasveer]

Closing this task. The mainline has been updated.