Re: [avr-libc-dev] Unified ELF file [was: RE: [avr-chat] Re: GUI wrapper for avrdude]

[Rick Altherr]

On Aug 29, 2007, at 1:58 PM, Eric Weddington wrote:

> > -----Original Message-----
> > From: address@hidden
> > [mailto:address@hidden
> >  On Behalf Of Joerg Wunsch
> > Sent: Tuesday, August 28, 2007 11:19 PM
> > To: address@hidden
> > Subject: Re: [avr-chat] Re: GUI wrapper for avrdude
> >
> > As Eric Weddington wrote:
> >
> > > Patches to avrdude are welcome to read an ELF file, and to program
> > > flash, eeprom, and fuses from a single ELF file.
> >
> > Btw., AVaRICE has been working like that for years (using the ELF
> > file, and derive the memory region type based on the offsets).  It
> > only takes care of flash ROM and EEPROM images as loadable images,  
> > but
> > also does already have offsets for fuse (0x820000), lock (0x830000),
> > and signature (0x840000) address spaces.  It eventually reads all
> > possible sections of a particular memory type into an internal image,
> > and then uses it to program the respective memory areas from that.
>
> [CCing avr-libc-dev. Apologies for duplicates. We should probably move
> conversation there.]
>
> One issue that probably should be addressed:
>
> How does a GNU assembler-only project specify fuse settings, lock bit
> settings, etc., in this potential scheme?
>
> Eric Weddington
>
>
>
>
> _______________________________________________
> AVR-libc-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-libc-dev

Well, using the header files I sent out a few days ago, the resulting  
GNU as file (avr-gcc -S) has something like this:

.global lfuse
        .section        .lfuse,"a",@progbits
        .type   lfuse, @object
        .size   lfuse,1
lfuse:
        .byte   -29

--
Rick Altherr
address@hidden

"He said he hadn't had a byte in three days. I had a short, so I  
split it with him."
 -- Slashdot signature

smime.p7s
Description: S/MIME cryptographic signature