Re: [avr-gcc-list] New Issues: AVRStudio and debugging with .COF Files

[Joerg Wunsch]

Bryan Jarmain <address@hidden> wrote:

> 1) When loading the COFF file into Studio, the debugging doesn't
> start at main. I need to step through until I get past the init
> functions. This is a relatively minor issue, but a bit annoying.

This is the reply i've once got from Svenn-Ivar Svendson of Atmel:

``This is a general message. The jtag ice module in studio tries to
locate the function that is specified in the 'jtag ice options' on the
debug menu of avr studio. By default it is 'main'.
 
If there is a function called 'main' in the program, Studio should be
able to look it up if the COFF file is according to spec (or what is
becomming the corrected spec). Generally, the customer should have
problems with watching variables as well if this message appears.''

(The latter would explain your issue #3.)

So please make sure your options are set up correctly.  Have a look at
the output of avr-objdump -g, it should properly display a main()
function.

> 2) After loading the COFF file, the contents of all constant arrays
> disappear. If I load the HEX file they reappear. If I then reload
> the COFF file, they remain until I reload the COFF, at which point I
> need to repeat the process.

That sounds like the known issue with AVR Studio's COFF parser when
processing avr-gcc files, listed almost at the end of the Beta README
file.


If you're proud enough to call a JTAG ICE your own, my general advise
is to drop that silly COFF stuff, and use avr-gdb directly on the ELF
file (perhaps with a frontend of your choice if you dislike GDB's user
interface).  This gives you access to the full debugging information
of the ELF file, as well as a powerful debugger. ;-)
-- 
J"org Wunsch                                           Unix support engineer
address@hidden        http://www.interface-systems.de/~j/