Unable to get FT232R drivers loaded under Windows 7 64bit

Same problem here. :disappointed_relieved:

I got a new Nano module. Connected it, the driver auto-installed fine, uploaded the code, everything is OK.

One hour later I replug the board to USB and it is no longer recognized by Win7 64bit - no driver! I manually installed the driver, but it still doesn't work.

This Nano is a clone, it has "www.funduino.com" and "LISA 2011" written on the PCB.

I have found this so far... flip the board over.. near the usb connector there is a FTDI chip read the second line.. You will need a magnifying glass to read it. If it say 1408 It is same chip as mine that I am having trouble with as of Oct 1st. 2014 if it say 1436 It is the same chip as mine that still works, (I have 3 of these)

This info does not help fix the problem but maybe we can narrow it down to a set of H/W Then I am hopeful that some really smart person can fix up a driver.

My chip has a 1402 code.

Can you guys look at the USB device ID and tell me what it is? (right click on the device, Properties, Details, Hardware ID from the drop down list).

Mine is USB\VID_0403&PID_0000&REV_0600 and this PID is the source of the problem: the drivers only recognize PIDs 60xx, not 0000 !!

working one is FTDIBUS\COMPORT&VID_0403&PID_6001

failing one is (it has 2 lines) USB\VID_0403&PID_0000&REV_0600 USB\VID_0403&PID_0000


I confirm the same problem with FTDI 232RL since 1 October....I have problem with 90% ebay purchased FT232. I also have original Digikey chips that working perfect now. Seems like there was some global update from FTDI or Windows to block fakes....

Yep, should be PID_6001...

I have contacted FDTI support for this problem, I am waiting for their reply.

There was a recent FTDI windows driver update, although I can't see anything that might cause devices to stop working.

FTDI - Other hardware - USB Serial Converter

Download size: 825 KB

You may need to restart your computer for this update to take effect.

Update type: Optional

FTDI Other hardware software update released in August, 2014

I believe this is FTDI version 2.12.00, release note here http://www.ftdichip.com/Drivers/CDM/CDM%202%2012%2000%20Release%20Info.rtf I guess if there was a change to nobble fakes they might not publish that info.

That update is pending in my Windows update...

Possibly due to recent news about USB hacking vulnerability they have been tightening up on USB drivers, or someone just goofed an update.

FDTI have a tool to edit the data in their devices called FT_PROG, it might be a way to recover faulty devices. It's also a way to mess it up completely, but if it doesn't work anyway maybe no loss. http://www.ftdichip.com/Support/Utilities.htm

Later edit:

As it turns out the problem is caused by counterfeit chips, I must delete the workaround procedure I have found, because altering device drivers is contrary to the FTDI license agreement.

If you have such a fake chip, please contact the seller for reimbursement.

Unfortunately FT_PROG cannot be used because the program does not see the problematic chip.

Just to be clear, the workaround I described above is to make the driver work with the defective chips, not only FT_PROG!

Vincent77 thank you very much! :) The workaround worked for me, I get my board operating again.

another question, do I need to modify all 60XX positions?

Thank you, not it clear.

Vincent get's the glory. Thanks for finding the solution. I saw that the PID in the .inf file didn't match that shown using USBView but I hadn't gotten around to trying it. The remaining question in my mind is how did the PID get set to 0000. I looked at the .inf file in the Arduino-1.05r2 download that I originally used and which worked and the PID there is 6001, so at some point the PID in my Arduino Nano must have matched one of the 6000 series PIDS. Go figure.

Thanks Vincent. Your solution works great.

Mine has FTDIBUS\COMPORT&VID_0403&PID_6001

Is that programmable? I see a whole bunch of application notes http://www.ftdichip.com/Support/Documents/AppNotes.htm

And the FT_PROG Utility http://www.ftdichip.com/Support/Utilities.htm#FT_Prog

Oops - didn't see the 2nd page of comments before I posted.

I have received the following response from FTDI:

We have investigated the device information that you submitted. This information indicates that the FT232R device is not a Genuine FTDI product. As this device is not genuine it will not operate with FTDI`s certified drivers.

We recommend to all our customers to guarantee genuine FTDI products please purchase either from FTDI directly or from one of our authorised distributors. Please follow this link to locate your local distributor: FTDI Sales Network

For more information please refer to FTDI`s counterfeit statement and driver license agreement.

I think this is also a problem in macs. Does anyone has a solution for Mac? (I tried peering into the FTDI dmg file, but it is binary, so I don't think you can change text like the inf file in windows).

This is interesting , in the INF file for the latest FTDI driver 2.12.00 this text has appeared

; Copyright © 2000-2014 Future Technology Devices International Limited ; ; USB serial port driver installation file for Windows 2000, XP, Server 2003, Vista, Server 2008, ; Windows 7, Server 2008 R2, Windows 8, Windows 8.1 and Server 2012 R2. ; ; ; IMPORTANT NOTICE: PLEASE READ CAREFULLY BEFORE INSTALLING THE RELEVANT ; SOFTWARE: This licence agreement (Licence) is a legal agreement between you (Licensee or ; you) and Future Technology Devices International Limited of 2 Seaward Place, Centurion Business ; Park, Glasgow G41 1HH, Scotland (UK Company Number SC136640) (Licensor or we) for use of ; driver software provided by the Licensor(Software). ; ; BY INSTALLING OR USING THIS SOFTWARE YOU AGREE TO THE TERMS OF THIS LICENCE ; WHICH WILL BIND YOU. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENCE, WE ARE ; UNWILLING TO LICENSE THE SOFTWARE TO YOU AND YOU MUST DISCONTINUE ; INSTALLATION OF THE SOFTWARE NOW. ; ; 1. GRANT AND SCOPE OF LICENCE ; ; 1.1 In consideration of you agreeing to abide by the terms of this Licence, the Licensor hereby ; grants to you a non-exclusive, non-transferable, royalty free licence to use the Software on ; the terms of this Licence. ; ; 1.2 In this Licence a "Genuine FTDI Component" means an item of hardware that was ; manufactured for, and sold by, the Licensor or a member of the Licensor's group of ; companies. It does not include any counterfeit or fake products. ; ; 1.3 If you are a manufacturer of a device that includes a Genuine FTDI Component (each a ; "Device") then you may install the Software onto that device. If you are a seller or distributor ; of a Device then you may distribute the Software with the Device. If you are a user of a ; Device then you may install the Software on the Device, or onto a computer system in order ; to use the Device. ; ; 1.4 In each of those cases you may: ; ; 1.4.1 install and use the Software for your purposes only; and ; ; 1.4.2 only use the Software in conjunction with products based on and/or incorporating a ; Genuine FTDI Component. ; ; 1.5 The Software will not function properly on or with a component that is not a Genuine FTDI ; Component. Use of the Software as a driver for, or installation of the Software onto, a ; component that is not a Genuine FTDI Component, including without limitation counterfeit ; components, MAY IRRETRIEVABLY DAMAGE THAT COMPONENT. It is the Licensee's ; responsibility to make sure that all chips it installs the Software on, or uses the Software as a ; driver for, are Genuine FTDI Components. If in doubt then contact the Licensor.

.. continues....

(my highlights)

You have all read and agreed to that haven't you? :)

So it seems that FTDI are now deliberately disabling counterfeit devices.

The license stated in the INF file is not legally binding, since the driver is installed automatically without the user seeing and given the opportunity to decline the agreement [IANAL]. Disabling user's property is probably illegal, but I doubt you'd win any suit in court.

FTDI are perfectly within their rights to only support genuine products, but I am not sure disabling clones is a sensible tactic, particularly when there is a trivially easy way to circumvent it. They are probably looking forward to the day when only Microsoft approved drivers can be installed on Windows, and it is a crime to tamper with your Windows installation!

I didn't see anything in the INF file that disables counterfeits, so either the change happened in an earlier release or more likely the code is in the binary drivers.

The advice to "only buy from FTDI authorised sellers" may as well be "don't buy FTDI", since not even big suppliers like RS and Farnell are authorised sellers. You'll be ok with Mouser and Digikey though :)