As Neil Davey wrote: > Reading | | 0% > 0.00savrdude: > Send: . [1b] . [08] . [00] . [08] . [0e] . [1d] . [04] . [04] . [00] 0 > [30] . [0 > 0] . [00] . [00] 8 [38] > avrdude: Recv: > avrdude: Recv: > avrdude: Recv: > avrdude: Recv: > avrdude: Recv: > avrdude: Recv: > avrdude: Recv: > avrdude: Recv: > avrdude: stk500v2_command(): command failed > avrdude: stk500v2_cmd(): failed to send command
Too bad the Win32 build of avrdude doesn't display the response bytes. However, my guess as that this bootloader simply doesn't implement the CMD_SPI_MULTI command (SPI passthrough). Due to the history of how avrdude's STK500 support has been developed, this command is used quite a lot in avrdude, but probably not at all by Atmel's stk500.exe command. It could/should be possible to convert most if not all of avrdude's stk500v2 protocol handling to native commands instead, but someone has to do it. As an alternative, you might have a look at Matthias Weißer's USBisp device. It also contains a bootloader that talks enough of the STK500 (v1) protocol to bootstrap the device. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ avrdude-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avrdude-dev
