avrdude-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-gcc-list] Re: [avrdude-dev] [RFC] avrdude FeatureRequestandCall


From: Eric Weddington
Subject: RE: [avr-gcc-list] Re: [avrdude-dev] [RFC] avrdude FeatureRequestandCall for Volunteers
Date: Sat, 10 Mar 2007 13:56:01 -0700

> > Hi Galen, Scott,
> > 
> > Thanks for the feedback. Would an algorithm such as this be 
> acceptable?:
> > 
> > 1. If -U switches exist on command line, then follow those 
> sequences exactly
> > 2. else (no -U switches exist on command line) follow 
> automatic sequence:
> >     2.1. Fuses (verify, if different: write and verify)
> >     2.2. Flash (erase, write, verify)
> >     2.3. EEPROM (verify, if different: erase, write, and verify)
> > 
> > Eric
> 
> Will multiple -U options be honored?

That was the intent, yes. I sort of implied it by saying "-U switches"
(plural) above. But to be explicit, yes, multiple -U options would be
honored just as they are now, no change in that functionality.
 
> So could I tell it to write the flash and fuses, but not the EEPROM?

Yes. The main point was that if *no* -U options were on the command line AND
an ELF file is used as the input file, then it would default to the
"automatic sequence" described above.

> If so then it will work for what I need.
> 
> Thanks!
> 
Great! :-)

Eric





reply via email to

[Prev in Thread] Current Thread [Next in Thread]