That was unfortunately not the only problem. As I wrote in my last posting, the FTDI-module gets disconnected by the following simple process: avrdude -p m8 -P /dev/ttyUSB0 -c avrftdi (or even by reading out the fuses: avrdude -p m8 -P /dev/ttyUSB1 -c avrftdi -b 19200 -U lfuse:r:-:i -vvv) and I really don't know why?! The disconnect happens between these 2 lines from avrdude: (as far as I was able to observe it by tail -f)
Description : FT2232D based generic programmer avrdude info: Pin is zero val 0! 2011/11/2 Joerg Wunsch <[email protected]>: > As Daniel Schulz wrote: > >> My setup: >> ADBUS0 : SCK >> ADBUS1 : MOSI >> ADBUS2 : MISO >> >> ADBUS4 : RESET >> >> >> Is RESET correct on ADBUS4? > > I already replied that it must go to ADBUS[3], because /RESET is > essentially the chip select signal when performing ISP programming. > > No idea whether this was the only problem or not. > > -- > 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] > https://lists.nongnu.org/mailman/listinfo/avrdude-dev > _______________________________________________ avrdude-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avrdude-dev
