FT232RL is a magic film, said the almighty may be a bit exaggerated, but ... In short it is ftdichip this magical company based on similar technology, do a lot of good products, including turning IIC, turn SPI, password dog and so on. It's a very useful tool.
Anyway In a sentence to describe the cause is, the wrong use of d2xx inside the Ft_programex this function, the film inside the firmware various chaos.
1. VID, PID and INF files
First of all, the VID and PID are out of the way, the original driver can not be used. Baidu's, ah ha, found can be modified by the INF file, so that the original driver can support the new VID and PID.
Because my vid and PID have become CCCC, I added it in the Ftdiport.inf file:
%VID_CCCC&PID_CCCC. Devicedesc%=ftdiport.nt,ftdibus\comport&vid_cccc&pid_cccc
Add inside the Ftdibus.inf
%USB\VID_CCCC&PID_CCCC. Devicedesc%=ftdibus.nt,usb\vid_cccc&pid_cccc
OK, re-add the driver to the unrecognized device, and it becomes recognizable again.
The following INF file can be analyzed, and it is clear that the driver supports which VID and PID can be implemented by modifying the INF file. First, the system will read the INF file to see if the driver can support the device just inserted, then the driver will use the VID and PID to identify the period, similar to the Linux write drive when the main device number and sub-device number.
2. Download libftd2xx1.1.12.tar.gz
The amount, although can be recognized, but with Ft_programmex is unable to set the firmware to the correct, operation once, a plug-in device, Windows on the blue screen.
So, change the vid and PID under Linux and try again.
First down the Linux d2xx support package libftd2xx1.1.12.tar.gz come over.
Well, under this bag I smoked at least five cigarettes, although he only 34k size, mainly the server over the connection has been broken ... Start with chrome, break once, manually click Connect once ... After a few repetitions, there is no patience. So, with the wget. Unlimited attempts to download, disconnect 1 seconds after attempting to reconnect.
wget --tries=inf--read-timeout= http://www.ftdichip.com/Drivers/D2XX/Linux/ Libftd2xx1.1.12.tar.gz
The first set is 1s, the results are constantly trying to connect, and then set to 10s, so every 10s try to connect once, the beginning is always fast, oh haha
FT232RL After changing bricks