The boards.txt file in the optiboot distribution still has
upload.protocol=stk500 for all or most of the board types. Newer versions of
avrdude may operate incorrectly with this specification, and yield odd
debugging information even under "working" circumstances. For example, the
latest version of avrdude seems to use the "generic SPI" command for reading
the chip signature bytes; this command is not supported by optiboot (it's
ignored and a response is "faked") This will cause avrdude to report an
invalid signature of 000000 even though the bootloader has correct signature
bytes internally.
Original issue reported on code.google.com by wes...@gmail.com on 23 Apr 2013 at 3:44
Original issue reported on code.google.com by
wes...@gmail.com
on 23 Apr 2013 at 3:44