FTDI Chip problems!

Hello everyone!

Recently... i'm suffering with a huge FTDI headache.

For a long time I've been using severam nanos in my projects. But recently... not sure what happening, but everything is wrong!

Don't know the source of the problem. But I believe it could be a mix of 64bit operating system with recente releases of FTDI drivers. I'm telling this, because everything worked in a Win7 32bit stable environment where everything went fine for about 2 years, til.. changing to win8 64bit in a recent pc format.

The fact is that I can't get any of this FTDI based usb-to-serial devices runing on windows. Already tried different drivers and always get the epic "code 43" and "usb not recognized" issue. Already googled a lot, and can't resolve the zero vendor id.

This happens with all devices I have. And those usb-to-serial are brand new.

Using linux i have different results. Well... I can't connect to Arduino Nano.

I get the same result... however, I can connect to the other ones:

Nano is working with a script I made probably one year ago. It has been programmed only one time, as I had other nano for development. (that I lost somewhere in my junkyard-like room. but this one had the same problem also) Program inside uses serial to send data via bluetooth. So, I'm not sure if for some reason this collides...

Also, this nano was powered via usb for some time. Not sure if this ruined the chip.

So... my questions are:

1) Using arduino's serial for output can interfere with pc-to-arduino communication? If yes, is it possible to "reset" atmega in a easy way?

2) Anyone experienced similar problems... killed FTDI chip and.. tried to recover it?

3) Any clever suggestions? :)

Thank you so much!

Is the same as this ? http://forum.arduino.cc/index.php?topic=272355.0

Pullup the Device Manager, open the Ports, right click the FTDI part, Properties, click Details, select Hardware IDs under the upper pulldown. Select the one that ends VID_0403&& PIUD_6001 if you have a choice. If your has 0s, you may have a counterfeit FTDI part.

Driver Rev 2.12.0.0

Peter_n:
Is the same as this ?
http://forum.arduino.cc/index.php?topic=272355.0

It’s a similar problem… posted some hours earlier.
Sorry! :roll_eyes:

CrossRoads:
Select the one that ends VID_0403&& PIUD_6001 if you have a choice.
If your has 0s, you may have a counterfeit FTDI part.

Thank you, CrossRoads!
Even before registering yesterday, your FTDI-driver-related-posts all over this forum were a reference for me!

However, I disagree with the 0’s on VID-PIUD counterfeit argument.
My current defective arduinos already worked before! (in 2012 for exemple)
The one on the picture was programmed only 2-3 times. Lst time about one year ago using win7 32 bit. Now it does not enumerate in any environment.

But for example,
The small FT323R chip is recognized at my work’s pc (win7 32 bit) and at my laptop ubuntu 64bit… but on win 8.1 64bit shows 0’s on VID-PIUD!
The larger only works my laptop ubuntu 64bit.

My conclusions are that VID_0000&&PIUD_0000 is a windows default for a device descriptor Request error.
And this could result from:

→ Defective or damaged FTDI chip
→ Driver

A counterfeit FTDI can be answer… but not if already worked before.

I believe that my Nano’s chip is damaged because lots of times I used the USB to power the device.
The other ones… I’m still trying to get conclusions. But different behaviors in different environments smells like a driver issue.

Now… my big doubt is if possible to reprogram the VID/PID of a supposedly defective chip.

Those counterfeit FTDI chips do work.... a little. In linux you might not have a problem, not with the real ones, not with the counterfeit ones.

In Windows, the FTDI driver was working with both. So the drivers were "updated" by the manufacturer that only the real FTDI was working and the counterfeit ones failed. Perhaps the counterfeit ones are changed meanwhile. I assume Microsoft testes the real FTDI chips, and perhaps the drivers are heating up the counterfeit ones too much.

Did you use Arduino Nano clones ? The cheapest possible ones ? Perhaps they had those counterfeit chips.

Peter_n: In Windows, the FTDI driver was working with both. So the drivers were "updated" by the manufacturer that only the real FTDI was working and the counterfeit ones failed.

If this is true... then using the old drivers should be the answer.

Peter_n: Did you use Arduino Nano clones ? The cheapest possible ones ? Perhaps they had those counterfeit chips.

Yes... but I'm using the same cheap clones since 2012. And always worked with no problems via Arduino IDE or CodeBender.

The supposed counterfeit chips only stopped working a few weeks ago! Coincidentally, after moving to 64bit windows.

The other UART cheap clones from the picture are brand new! Both work ok using linux but are recognized on win 64bit (7/8.1) as USB\VID_0403&PID_0000&REV_0600

(Hope to try a 32bit soon just to ensure..)

I already read this topic a few times, and the answer could fit, but if those nanos never worked at all... But they've been in use for quite long!

You can follow my Video-Tutorial from the link you posted (https://www.youtube.com/watch?v=SPdSKT6KdF8). It helped a lot of people with the exact same problem.

Indy

The counterfeits worked, and it is hard to tell which is real and which is fake. So don't tell me they worked, because they did work. But recently the Windows driver changed.

It is generally not a good idea to permit Windoze to "update" drivers when it offers to do so, for hardware that is working perfectly. :D

This frequently causes failure of all sorts of things. :astonished:

Paul__B: It is generally not a good idea to permit Windoze to "update" drivers when it offers to do so, for hardware that is working perfectly. :D

This frequently causes failure of all sorts of things. :astonished:

I don't know why people is moving to Win 8, so many troubles..

Hard to avoid with new computers - option to downgrade to Win7 going away. Win10 already being tried out as well.

Indyaner: You can follow my Video-Tutorial from the link you posted (https://www.youtube.com/watch?v=SPdSKT6KdF8). It helped a lot of people with the exact same problem.

Your video is excellent! It deserves being posted on a sticky topic. (Alongside with a FTDI FAQ.) ;)

However, in specific environments its not enought.

mart256: I don't know why people is moving to Win 8, so many troubles..

I moved because a client ordered me a Win8 App... and development environment uses OS resources for testing and debugging. After that, I opted to keep Win8, as it felt better performance besides being a '08 machine. This FTDI issue I also have on Win7 64bit. So, I can't say that is Win8 fault.

I think the problem is in the driver itself. The fact of recent and/or updated Windows releases require certified drivers is not exactly a problem. In theory, should avoid these situations.

mart256: I don't know why people is moving to Win 8, so many troubles.

My sentiments entirely. The only reason I ever use Windoze is to support the program which runs my practice which is written by a team who are not really that sharp and use WIndoze toolkits and MSSQL - which is a horror! Unless you are forced in that manner, it makes vastly more sense to use Linux, generally Linux Mint.

Except Linux does not come preinstalled on many off the shelf computers at stores like Best Buy - you get Windows. And rolling back to Win7 seems to be less and less an option. Even Win7 when it does autoupdates changes the driver - my Win7Pro had older FTDI drivers, updated itself to 2.12.0.0, the wife's 8.1 did the same. Not a problem for real FTDI chips. Corporate world uses mainly Windows also. It's big, it's not going away.

Well I was reluctant to have to go with Win 8.1 when I bought a new laptop last April, mostly because of all the negativity around 8.1, but it was all that Best Buy had in stock at the time. After a few days most my fears had gone away. It's very possible to completely ignore the Metro UI and just use the older desktop UI.

It's been a very stable platform so far will no major complaints on my part. I was able to install older drivers and/or locate updated drivers will little effort. Heck the machine already had a FTDI driver installed for some reason so didn't even have to deal with that. Updated 8.1 CP2102 driver was found on the chip manufacture's web site.

Well I was reluctant to have to go with Win 8.1 when I bought a new laptop last April, mostly because of all the negativity around 8.1, but it was all that Best Buy had in stock at the time. After a few days most my fears had gone away. It’s very possible to completely ignore the Metro UI and just use the older desktop UI.

It’s been a very stable platform so far will no major complaints on my part. I was able to install older drivers and/or locate updated drivers will little effort. Heck the machine already had a FTDI driver installed for some reason so didn’t even have to deal with that. Updated 8.1 CP2102 driver was found on the chip manufacture’s web site. Anyway I’m glad I upgraded as the laptop’s Intel I7 and larger ram runs circles around my older win XP desktop.

CrossRoads: Except Linux does not come preinstalled on many off the shelf computers at stores like Best Buy - you get Windows.

So?

Pardon me - I am or thought I was speaking with engineers(/ teachers/ scientists etc.) in mind.

CrossRoads: Even Win7 when it does autoupdates changes the driver - my Win7Pro had older FTDI drivers, updated itself to 2.12.0.0, the wife's 8.1 did the same.

Well, if you enable "automatic" updating as a "convenience" ... You end up with Silverlight installed.

CrossRoads: Corporate world uses mainly Windows also. It's big, it's not going away.

I'm sure it isn't. But the corporate world leeches on the rest of society - or you don't believe that?

They can afford inefficiency, they have money to burn - our money that we give them because there is no alternative - or you don't believe that?

(Am I sounding like some sort of socialist? I just think I am a pragmatist.)

I guess I am going more for realistic. Auto updates with windows & Norton seem to do a decent job of keeping our home computers virus/worm/trojan horse/whatever free. IT crew at work does the same, with nightly pushes & selected website blocking.

When I was a young engineer and had time time to fool around doing all the computer stuff manually and building machines from parts and fooling with operating systems, it was fun. Now I just want the tools to work and not have to spend my time fighting with what has become a commodity. So it's all perspective.

Well folks, here’s the skinny on the FTDI driver problems. It seems that some Chinese company was making counterfeit FTR232R chips and selling them to several Arduino manufacturers. Gravitech Labs apparently being one. Well FTDI Chip took issue with this. They were also able to detect the counterfeit chips. Sooooo they issued a driver update. You may have noticed that when you uploaded the latest driver that you had to accept a licensing agreement. If you read the agreement you will see all kinds of disclaimers by FTDI Chips .
6.1 To the maximum extent permitted by applicable law, in no event shall the Licensor be liable
; for any:
;
; 6.1.1 special loss or damage;
;
; 6.1.2 incidental loss or damage;
;
; 6.1.3 indirect or consequential loss or damage:
;
; 6.1.4 loss of income;
;
; 6.1.5 loss of business;
;
; 6.1.6 loss of profits;
;
; 6.1.7 loss of revenue;
;
; 6.1.8 loss of contracts;
;
; 6.1.9 business interruption;
;
; 6.1.10 loss of the use of money or anticipated savings;
;
; 6.1.11 loss of information;
;
; 6.1.12 loss of opportunity;
;
; 6.1.13 loss of goodwill or reputation; and/or
;
; 6.1.14 loss of, damage to or corruption of data;

Then when you install the drivers and use them they check to see if your FTR232R chip is counterfeit or not. If it is, they then proceed to change the product ID on the chip to 0000 instead of 6001 or other 6000 series ID number. Then when you try to communicate with your Arduino and the software goes out to install the driver it gives you various error messages because the product ID on the chip is no longer found in the ftdibus.inf file. Kind of rotten on FTDI Chips part. Anyway you can modify the ftdibus.inf file to allow your device to be recognized. I’ve attached instructions.

FTDI Driver Fix.txt (1.59 KB)

Kind of rotten on FTDI Chips part.

Hardly. Just a manufacturer trying to protect their intellectual property.
Think Arduino doesn’t go after counterfeiters as well?