Re: [avr-gcc-list] UISP vs AVRDUDE

[E. Weddington]

Keith Gudger wrote:

> I would like to create support under GNU/Linux for the AT43USB355 and
> AT43USB325 development kits.  These boards have a serial EEPROM on board
> to contain the programming code, which is downloaded into the chip's
> program memory at boot-up.
>
> The serial EEPROM can be controlled from a header that interfaces to a
> printer / parallel port.
>
> It would appear that UISP is the better choice to start with, as it
> (probably) contains everything needed to read hex files and write them
> over the parallel port.  Am I correct, or would AVRDUDE be better?  Any
> suggestions are appreciated.  Thank you.
>
>  
Hi Keith!

Perhaps I'm a little biased, but I would think that avrdude is a little 
bit better. There are some advantages to avrdude:
- avrdude can be easily extended (add devices / cables) through a 
text-based configuration file. No compiling is necessary when adding a 
device or cable.
- avrdude is known to run on Linux, FreeBSD, Windows, and Mac OS X. The 
original author of avrdude, Brian Dean, is currently using it on a Mac.
- avrdude has a *native* Win32 version. uisp does not; it has to be 
built and linked to the Cygwin DLL.

avrdude does have the ability to read/write Intel Hex and Motorola 
S-Records.

Also note that uisp was being mostly maintained by Ted Roth, who is no 
longer working on any AVR projects. There is a new maintainer for uisp, 
Margarita Manterola. But I would think that avrdude is probably the more 
active of the two projects.

Sounds like an interesting project....

HTH
Eric