AW: [En-Nut-Discussion] debugging ethernut apps

[Ernst Stippl]

Hi Henrik!

Thanks for your answere (It's funny to write an email in Austria close to
midnight and get an answere from Australia nearly instantly ...)

You wrote:
Then I also compiled my apps using the same flags into an .elf file. 

Thats where I need the help. which of the makexxxx  file (in which dir) did
you modify i.e. add the "-g3 -gdwart-2" to?

Thanks again!

ernst

-----Ursprüngliche Nachricht-----
Von: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] Im Auftrag von Henrik Maier
Gesendet: Mittwoch, 23. Februar 2005 23:17
An: Ethernut User Chat (English)
Betreff: Re: [En-Nut-Discussion] debugging ethernut apps

Hello Ernst,

I stopped "coffing" and since the advent of AVR studio 4.11, the
ELF/dwarf-2 format seems to work reasonably well. The intermediate step to
create a coff file is not needed any more.

I compiled the Nut/OS libs using the following flag for compiler and linker:

   -g3 -gdwarf-2

It put these flags into UserConf.mk.

Then I also compiled my apps using the same flags into an .elf file. 
Load this .elf file into AVRStudio and you can start source level debugging
incl. Nut/Os routines.

The only draw back is that AVRStudio can't find main() by itself because
Nut/OS overrides main.

Use the project wizard to load the elf file and to select the programmer.


Cheers

Henrik


FOCUS Software Engineering Pty Ltd
Brisbane, Australia - Web: www.focus-sw.com
Phone: +61-402 970 933 - Fax: +61-7-3009 0399


_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion