Re: [avr-gcc-list] Unable to debug code relocated with "-Ttext=" (e.g. bootloader)

[Simon Han]

On Mar 30, 2005, at 6:29 AM, E. Weddington wrote:

> Pieter Conradie wrote:
>
> > AVR Studio and GDB/Insight is unable to debug code when it is 
> > relocated with
> > the linker option "-Ttext=0x1E000" for an ATmega128, e.g. when 
> > creating a
> > bootloader application.
> >
> > This was experienced with WinAVR-20050214 and AVR Studio 4.11, by 
> > loading
> > dwarf-2 and stabs debug format (ELF and COFF).
> >
> > I can verify that the code is correctly generated by inspecting the
> > dissassembly, but the C debugging info is mangled, e.g. the "main" 
> > starting
> > point is incorrectly displayed as "address@hidden: main", in stead of 
> > the
> > proper location of "0000F0B9".
> >
> > Any workaround or linker switch that I should be aware of?
> AFAIK, this is a known issue with AVR Studio: it can't debug 
> bootloaders. Best to ask Atmel directly to see if they have a fix for 
> this yet.

Is there any tool for debugging bootloader code?

Thank you for any pointer,
Simon


> _______________________________________________
> AVR-GCC-list mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-gcc-list