RE: [avrdude-dev] [task #5093] Add support for reading ELF files.

[Eric Weddington]

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> rg] On Behalf Of Joerg Wunsch
> Sent: Tuesday, May 08, 2007 2:09 PM
> To: address@hidden
> Subject: Re: [avrdude-dev] [task #5093] Add support for 
> reading ELF files.
> 
> As Eric Weddington wrote:
> 
> Alas, each AVR might have a different default fuse, so we cannot
> simply use 0xff as the default value.

Sure.

> > > > The "universal hex file" is the resulting ELF file from the
> > > > toolchain.
> 
> > > I've heard voices here that not everybody would be happy 
> about this.
> 
> > I don't think it's so much fat and bloated as it's a binary format
> 
> Still, it carries a lot of baggage along with it:
> 
> % ls -l foo.elf *hex
> -rwxr-xr-x  1 j  staff  5115 May  8 21:49 foo.elf*
> -rw-r--r--  1 j  staff  4297 May  8 21:48 largedemo.hex
> -rw-r--r--  1 j  staff    30 May  8 21:48 largedemo_eeprom.hex
> 
> The .elf file on top has *only* the `alloc' sections in it.

Really? The debug info has been stripped from it too?
 
> Sure, it's not *that* fat.  But users have their habits, and often
> have been using load files like intel hex for years.

Well, yeah, but that doesn't mean we need to keep doing it that way,
especially if we can offer a compelling alternative.
 
Eric