From: Eric W. <ewe...@cs...> - 2005-10-25 14:44:40
|
David Braendler wrote: > Hi, > I've just downloaded the latest and greatest WinAVR 20050214 and AVR > Studio (4.12 Build 452) > > I'm generating a .elf file with and trying to debug this in AVR studio > (using STK500) When I compile with the -gdwarf-2, it does not seem to > generate any debug information. A dwarfdump shows nothing. Compiling > with a -gstabs and the debug information is there (an see it with avr- > objdump) There is an error with the dwarfdump utility: currently it displays nothing, even though AFAIK it built correctly. There is a bug report about dwarfdump on the WinAVR project site. Yes -gdwarf-2 is the correct way to go. > Actually I came to this after trying to use avarice (complained about > innappropriate ioctl ). Hmm. That's odd. You might want to post a bug report on the avarice project site in SourceForge. > Avrdude totally crashes. Looking at both these > things with portmon it appears that a couple of the commands being > issued are not recognised be the STK500 firmware version 4, and version > 2.01. Yeah, I believe that would be correct. That version of avrdude does not know how to talk to version 2 of the stk500 firmware. IIRC, avrdude has been updated recently to take care of this, but I have to put together a new release of WinAVR to include the new version of avrdude. > > I think that generating an elf file with debug information is the > correct way to go from a web search. Am I correct in this assumption?? Yes. Also, you can find a lot of help on the AVR Freaks website: www.avrfreaks.net. There are several incredibly active forums there including a forum for AVR GCC. HTH Eric Weddington |