[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-chat] Re: GUI wrapper for avrdude
From: |
Michael Hennebry |
Subject: |
RE: [avr-chat] Re: GUI wrapper for avrdude |
Date: |
Mon, 27 Aug 2007 18:12:30 -0500 (CDT) |
On Mon, 27 Aug 2007, Eric Weddington wrote:
> > -----Original Message-----
> > From: address@hidden
> > [mailto:address@hidden
> > On Behalf Of Joerg Wunsch
> > Sent: Monday, August 27, 2007 2:25 PM
> > To: address@hidden
> > Subject: Re: [avr-chat] Re: GUI wrapper for avrdude
> >
> > Michael Hennebry <address@hidden> wrote:
> >
> > > You can let the tool read or infer the offsets from the elf file.
> > > E.g. any 1 byte section named .hfuse can be infered to carry fuse
> > > data regardless of its offset.
> >
> > What about things like user-defined EEPROM sections? User-defined ROM
> > sections? Oh, there's already a popular one named .bootload.
The default linker script already moves
sections named .eeprom* into .eeprom.
When making the flash hex file,
AVR Studio's make files pass -R .eeprom to
avr-objcopy to remove the .eeprom section.
.bootload would go into the flash hex file.
> > I'm not too fond about the idea of hardcoding section names. This
> > didn't work too well in the past -- look at all the people who try to
> > debug an application consisting of a .text plus a .bootload section in
> > AVR Studio within a single application.
Let there be hardcoded default section names
and parameters like --hfuse-section-name .
> To be fair, there may be a bug in AVR studio where it doesn't load any other
> code section other than .text. That obviously needs to get fixed.
As far as I can tell, AVR Studio used avr-objcopy correctly last year.
Is this a new problem?
> What I would very much like to avoid is having one set of offsets for
> "Xmega", another set of offsets for "Ymega", and a third for "Zmega". If we
> can choose a set of offsets that will *probably* work for all AVR families
> (and ideally for the AVR32 as well, but I'm flexible on this point), then I
> can almost *guarantee* that these offsets will be adopted by AVR Studio
> tools as well. ;-) I'm open to suggestions...
If we teach avrdude about elf files,
is there any great need to use AVR Studio for programming?
--
Mike address@hidden
"Horse guts never lie." -- Cherek Bear-Shoulders
- Re: [avr-chat] Re: GUI wrapper for avrdude, (continued)
- Re: [avr-chat] Re: GUI wrapper for avrdude, David Brown, 2007/08/26
- Re: [avr-chat] Re: GUI wrapper for avrdude, Joerg Wunsch, 2007/08/26
- Re: [avr-chat] Re: GUI wrapper for avrdude, Xiaofan Chen, 2007/08/26
- RE: [avr-chat] Re: GUI wrapper for avrdude, Eric Weddington, 2007/08/27
- Re: [avr-chat] Re: GUI wrapper for avrdude, Bob Paddock, 2007/08/27
- RE: [avr-chat] Re: GUI wrapper for avrdude, Michael Hennebry, 2007/08/27
- RE: [avr-chat] Re: GUI wrapper for avrdude, Eric Weddington, 2007/08/27
- RE: [avr-chat] Re: GUI wrapper for avrdude, Michael Hennebry, 2007/08/27
- Re: [avr-chat] Re: GUI wrapper for avrdude, Joerg Wunsch, 2007/08/27
- RE: [avr-chat] Re: GUI wrapper for avrdude, Eric Weddington, 2007/08/27
- RE: [avr-chat] Re: GUI wrapper for avrdude,
Michael Hennebry <=
- RE: [avr-chat] Re: GUI wrapper for avrdude, Eric Weddington, 2007/08/27
- Re: [avr-chat] Re: GUI wrapper for avrdude, Joerg Wunsch, 2007/08/28
- Re: [avr-chat] Re: GUI wrapper for avrdude, Michael Hennebry, 2007/08/28
- RE: [avr-chat] Re: GUI wrapper for avrdude, Eric Weddington, 2007/08/28
- Re: [avr-chat] Re: GUI wrapper for avrdude, Joerg Wunsch, 2007/08/29
- Unified ELF file [was: RE: [avr-chat] Re: GUI wrapper for avrdude], Eric Weddington, 2007/08/29
- Re: Unified ELF file [was: RE: [avr-chat] Re: GUI wrapper for avrdude], Erik Christiansen, 2007/08/29
- Re: Unified ELF file [was: RE: [avr-chat] Re: GUI wrapper for avrdude], Joerg Wunsch, 2007/08/30
- Re: Unified ELF file [was: RE: [avr-chat] Re: GUI wrapper for avrdude], Erik Christiansen, 2007/08/30
- Re: Unified ELF file [was: RE: [avr-chat] Re: GUI wrapper for avrdude], Erik Christiansen, 2007/08/30