Am 15.01.2014 um 10:52 schrieb Jonathan Schneider <[email protected]>: > > But I am absolutely baffled as to what port to specify. The FT2232D should work out of the box, if you didn’t change the VID/PID. > > If I put usb:999 or even complete garbage after the -P I don’t get any kind > of meaningful error but does seem to know whether I have the FT2232D plugged > in regardless of -P. It looks as if port selection is somehow completely > automatic and -P is ignored. What if I have more than one FT2232D ? You need to put the USB VID/PID of your FTDI in hex after -P like so: '-P 0403:6010‘. Why did you feel the need to put '-P usb:n‘ in the avrdude command line? > > I cannot find clear documentation on how to specify the port for accessing > this kind of device beyond a mention of usb:N which doesn’t seem to do > anything. Maybe I have failed to find the right documentation. I don’t think it’s documented. I didn’t find it either ;) > > There is a reasonable chance the hardware has a silly mistake as last night > was a late one but I would like to know I’ve got the software end right as > well so would appreciate some input (and improved documentation for the next > person). If it doesn’t work, please provide the *full* avrdude command line, with all avrdude output, possibly using -vvvv or -vvvvv.
Best regards, Hannes _______________________________________________ avrdude-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avrdude-dev
