As Henrik Brix Andersen wrote: > avrdude: serial_recv(): programmer is not responding > avrdude: stk500_recv(): programmer is not responding
Running it with -vvvv gives details about the communication. My guess is that your PL2303 occasionally drops a character. Unfortunately, the current STK500 code (both v1 and v2) doesn't recover from that situation at all, i.e. it makes no retries. It shouldn't be to hard to add retries though. In the jtag2 code (which has partially been cloned from the stk500v2 code, as both low-level protocols are similar to some degree), I had to add retries as some of my tests have been run on a lossy PCI multiport card where my FreeBSD driver randomly catches a `silo overflow' which means that some character gets lost. > It is connected to the host PC through a PL-2303 USB-to-RS232 > converter. I just tried my STK500 behind a PL2303 adapter on FreeBSD (firmware version 2, avrdude straight from CVS), and could not see any problems. The data rate is not exciting though, but that could easily be a latency problem with the uplcom driver here. -- 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
