> -----Original Message----- > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > rg] On Behalf Of Ville Voipio > Sent: Tuesday, March 18, 2008 11:42 PM > To: [email protected] > Subject: Re: [avrdude-dev] Avrdude Gui problem > > > What we have right now is three files xxx.rom, xxx.eep and xxx.fuses, > where the last one is a script to be executed in batch mode. Then we > also have a shell script to patch the serial number into the > .eep file. > > It would be nice, if the factory-floor program could use a > .zip with all > the files (binaries, fuse settings, instruction files) so > that sending a > single file to the subcontractor would suffice.
We already have that now: the ELF file. You can now declare fuse and lockbit settings in your application (via avr-libc API), which gets stored in special sections in the ELF file. Then, programming tools can read the ELF file (which now contains data for flash, eeprom, fuse, lockbits) and program everything. *The AVR Studio programming tools now already do this.* AVRDUDE still needs the capability to read ELF files in order to add this feature. > Oh, and if someone is really going to make such a tool, please try to > keep it open for extensions (not toot tightly bound to > avrdude API). I'd > love the AVR programming tool but kill for such a tool if it > could also > program ARMs and CPLDs through the JTAG connection. I may not be the > only one... > We *are* talking about a GUI for avrdude that is integrated into the avrdude application. This is an *AVR* programmer not a universal programmer. _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
