>>>>> "Sébastien" == Sébastien Bourdeauducq
>>>>> <[email protected]> writes:
Sébastien> Hi, thanks for getting the cable working with UrJTAG :)
Sébastien> Le Sat, 23 Oct 2010 18:26:10 +0200, Michael Walle
Sébastien> <[email protected]> a écrit :
>> I've forgot to mention that you have to set the right PID and VID
>> (20b7:0713) in the EEPROM.
Sébastien> Have you been able to use ftdi_eeprom?
Sébastien> As often, we have a lot of luck (hahaha) and it seems the
Sébastien> ftdi_eeprom tool [1] only supports the FT232BM and FT245BM
Sébastien> chips. And it has no option for configuring the other serial
Sébastien> channel as JTAG.
>> If you do so, the kernel won't recognize the serial port anymore
>> (until we submit a patch for the linux kernel)
On the libftdi-1.0 eeprom-new branch I added a lot of effort to get more
EEPROM coverage. I have no 4432 device, so 4432 is not really tested, but
most things should work. I will try to fix things, if I get feedback on
things not working.
Tomas Jarosch is working on adding the extended eeprom feature to
ftdi_eeprom, but essentially it boils down to
(open the ftdi device)
ftdi_eeprom_initdefaults(ftdi, "IKDA", "LLBBC_INTERFACE0",
serial_string);
ftdi_set_eeprom_value(ftdi,"SELF_POWERED", 1),
ftdi_set_eeprom_value(ftdi,"CHANNEL_A_TYPE", CHANNEL_IS_245);
ftdi_set_eeprom_value(ftdi,"CHANNEL_A_DRIVER", DRIVER_VCP);
ftdi_set_eeprom_value(ftdi,"CHANNEL_B_TYPE", CHANNEL_IS_245);
ftdi_set_eeprom_value(ftdi,"CHANNEL_B_DRIVER", DRIVER_VCP);
ftdi_set_eeprom_value(ftdi,"GROUP1_DRIVE", DRIVE_16MA;
ftdi_set_eeprom_value(ftdi,"SUSPEND_PULL_DOWNS", 1);
ftdi_eeprom_build(ftdi); /* Needed to determine EEPROM size*/
ftdi_write_eeprom(ftdi);
(close the device)
Bye
--
Uwe Bonnes [email protected]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkym...@freenode
Twitter: www.twitter.com/milkymistvj
