Follow-up Comment #8, bug #22699 (project avrdude):
Reply to comment #7:
> Changing the devicecode scheme to an Signature based decision
> within the avr910 Firmware is also a mess. To be backward
> compatible (with AVRprog and others) at least the "official"
> Devicecodes have to be there.
Well, they'd only need to be there in order to "offer" them
to avrprog.exe. Upon receiving a selection, just don't care
what it was (unless it's a 0x13, indicating an AT90S1200),
go ahead initializing ISP, and then query the signature.
I just added the extended parameter -x devcode=VALUE to the
avr910 implementation. It allows the user to override the
device code that is sent to the programmer. That might
hopefully serve as a stop-gap measure so at least no separate
avrdude.conf is required.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?22699>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
avrdude-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
