RES: [En-Nut-Discussion] JTAG problems

[Ronaldo Bianchin]

Donwload the new gcc from the address http://www.atmel.com/dyn/resources/prod_documents/AVRGccTools.zip and use the -gdwarf-2.

I don't know if it's realy necessary, but I made it in the entire ethernut project (make cleanall and make install after the changes).

Ronaldo Bianchin

----- Mensagem original -----
De:		Harald Kipp [SMTP:harald.kipp at egnite.de]
Enviada em:		terca-feira, 27 de julho de 2004 04:35
Para:		Ethernut User Chat (English)
Assunto:		Re: [En-Nut-Discussion] JTAG problems

Jens,

app/Makedefs includes two compile option lines:

CPFLAGS   = $(MCFLAGS) -Os -Wall -Wstrict-prototypes 
-Wa,-ahlms=$(<:.c=.lst) $(DEFS)
#CPFLAGS  = -g $(MCFLAGS) -O0 -Wall -Wstrict-prototypes 
-Wa,-ahlms=$(<:.c=.lst) $(DEFS)

If you uncomment the second one, source level debug
information will be included in the elf file. Running

  make clean
  make your_appname.coff

should create the coff file for AVRStudio.

Btw. anyone tried AVRStudio's new elf support?

Although based on ICCAVR, you may also look at
http://www.ethernut.de/en/iccavr/
for a sample debug session.

Harald

At 09:18 27.07.2004 +0200, you wrote:
>Hello,
>
>We are currently trying to debug an application using the
>AVR JTAG interface. We are able to download the program
>to the ATMega 128 using the interface, so we expect it to
>work correct. It is also possible to debug the application
>at assembler level, but it seems that the AVRStudio isn't
>able to get the informations required for source level
>debugging. Has anyone a small example (source & makefile)
>to make shure that the application is generated with the
>correct compiler / tool settings?
>
>Regards
>
>Jens

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