[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avrdude-dev] avrrftdi driver port selection
From: |
Jonathan Schneider |
Subject: |
Re: [avrdude-dev] avrrftdi driver port selection |
Date: |
Wed, 15 Jan 2014 15:55:45 +0000 |
On 15 Jan 2014, at 13:29, Hannes Weisbach <address@hidden> wrote:
> Am 15.01.2014 um 10:52 schrieb Jonathan Schneider <address@hidden>:
>>
>> 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?
Thank you Hannes. May I suggest the manual be updated ?
Useful to know since my FT2232D board has an EEPROM that is nominally setup
like the JTAG section of a Marvell Sheevaplug with different IDs (if it has
been programmed properly which it might not have been).
I tried usb:N because the manual page does mention that syntax.
There is still the question of how do deal with having more than one FT2232D
present. It’s not a problem for me right now but could be and should be catered
for.
Thanks,
Jon