FTDI Driver Breaks Hardware Again (eevblog.com)

janoc writes: It seems that the infamous FTDI driver that got famous by intentionally bricking counterfeit chips [NOTE: that driver was later removed] has got a new update that injects garbage data ('NON GENUINE DEVICE FOUND!') into the serial data. This was apparently going on for a while, but only now is the driver being pushed as an automatic update through Windows Update, thus many more people stand to be affected by this.

Let's hope that nobody dies in an industrial accident when a tech connects their cheap USB-to-serial cable to a piece of machinery and the controller misinterprets the garbage data.

Comments

Microsoft's responsibility and WHQL

[Anonymous Coward]

What is Microsoft's responsibility here?

They are pushing out drivers that bricks hardware through their Windows Update service?

How the hell did this pass their WHQL?

Re: Microsoft's responsibility and WHQL

[Anonymous Coward]

Yep, Microsoft should revoke WHQL on future driver versions and refuse to certify FTDI drivers in the future.

This is a blatant violation of trust; end users have no way to know if the FTDI chips in their devices are genuine.

This would be how I'd handle it.
1) After you login you see a message from windows. Automatic update of FTDI serial driver has failed. FTDI serial driver reports non genuine hardware. Warning the use of counterfeit hardware may cause system instability or other undesirable behaviour. Wouuld you like to disable the previous driver, or continue using it and mark it as non upgradeable? A non upgradeable driver may have bugs and other issues that could, in time, expose your system to threats. Long term use is not recommended.

At this point, I think I'd avoid FTDI hardware...

[stazeii]

Son of a.... I spent, literally, 4 hours yesterday trying to troubleshoot a 3d Printer (Tinyboy 3D), with it not working. MProg from FTDI said the chip was fine (right vendor and product ID), but it just wouldn't work. I tried every driver I could find. Finally, I uninstalled the driver, disabled wifi, plugged it in, waited for Windows 7 to install the version it knew (2.4 something), used Mprog 3.5 to reprogram the chip as legit (as per: https://www.youtube.com/watch?...), unplugged, replugged (at which point windows reinstalled it again, with 2.4), and suddenly it started working! I can confirm this "Non Genuine" serial data, since I opened up the Arduino IDE and saw that on the serial console. You know, I sympathize with FTDI. They're having their tech ripped off. But, it's inappropriate to punish end users who don't have any say. Sure, we could not buy stuff that uses counterfeit chips, but many sellers aren't even going to know. FTDI should be pursuing the counterfeiters in China, and using what legal system China has to stop it. Either that, or create a version of the chip that has such a low price point, they put the cloners out of business by providing legit-working-alternatives for a price point. So annoying that I've lost time because FTDI does this crap, and apparently Microsoft is okay with it (I don't see how this should have passed WHQL).

Re:Supply chains

[Anonymous Coward]

But you sure as fuck won't be sure you're getting ACTUAL FTDI components. FTDI WILL NOT GUARANTEE that a chip is real unless it is purchased directly from them. This includes chips purchased THROUGH THEIR DISTRIBUTORS.

They can't police their own fucking distributors, dude. Get a fucking grip.

Re: Keeping me happy for disabling auto-updates

[Anonymous Coward]

Potentially compromised and working or not working.

Damned if you do, damned if you don't.

Re: Supply chains

[guruevi]

The problem I've found with a LOT of USB things even the FTDI ones is that they're only putting out a stepped up 12V or even just 5V while classically the serial port was a bit above 12V.

Although the spec allows for +3V/-3V at the lowest end, most stuff just won't work well. Also the stepped up voltages seem to have a lot of noise and variation, again something the spec allows but "back in the day" few allowed for those.

Also, the USB data bus frequency leaks noise into the serial bus portion, sometimes visibly on a scope or definitely noticeable on a spectrum analyzer. The problem probably being poor design and shielding on modern computers. I've also had some issues with ground loops but that is only in very specific circumstances.

For critical applications, I've found the Ethernet serial servers are more reliable. Even running commands through an Arduino will do better in a pinch. But those cheap USB adapters are good enough for setting up a switch or uploading a firmware when the device is out of order anyway but are not intended to be permanently attached.

CH340 works just FINE!

[MindPrison]

I'm a big consumer of the Arduino clones (and FYI - Arduinos are FREE to clone for everyone, it's a part of the concept).

The chip has now been replaced with the CH340 - which even though it lacks some of the FTDI features, is a bang up chip that gets the job done - even at really high Serial speeds, I've yet to see one of them fail on me (I use Linux, where CH340 runs right out of the box, windows needs a driver).

I've not even heard of the FTDI before all of this came up.