Pages: [1] 2
Author Topic: New windows drivers killing fake FTDI FT232 chips?  (Read 15614 times)
fn42
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 2


« on: October 22, 2014, 11:26:54 AM »

hey so I haven't seen this myself but apparently the newest FT232 windows drivers reset the PID of the controller to '0' rendering it basically unusable

http://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/

figured I would post this here, I know a lot of people buy the knock-off ebay cables which are probably affected
Logged
nyet
Administrator
Hero Member
*****

Karma: +411/-47
Offline Offline

Posts: 9170


WWW
« Reply #1 on: October 22, 2014, 11:37:01 AM »

Thanks for the heads up. Stickied.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
fn42
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 2


« Reply #2 on: October 22, 2014, 12:33:59 PM »

hackaday article: http://hackaday.com/2014/10/22/watch-that-windows-update-ftdi-drivers-are-killing-fake-chips/

apparently you can re-set the PID with their utility on winxp/linux: http://www.ftdichip.com/Support/Utilities.htm
Logged
nyet
Administrator
Hero Member
*****

Karma: +411/-47
Offline Offline

Posts: 9170


WWW
« Reply #3 on: October 22, 2014, 12:44:23 PM »

A comparison of the die

http://zeptobars.ru/en/read/FTDI-FT232RL-real-vs-fake-supereal
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
turboat
Hero Member
*****

Karma: +42/-2
Offline Offline

Posts: 615


« Reply #4 on: October 23, 2014, 04:04:49 AM »

Anyone found a programatic way of identifying fake FTDI chips? I've emailed FTDI asking how I tell if my chip is real or fake Smiley I suggest everyone else does the same.
Logged
nyet
Administrator
Hero Member
*****

Karma: +411/-47
Offline Offline

Posts: 9170


WWW
« Reply #5 on: October 23, 2014, 09:04:19 AM »

Anyone found a programatic way of identifying fake FTDI chips? I've emailed FTDI asking how I tell if my chip is real or fake Smiley I suggest everyone else does the same.

Newer drivers (just before the bricking ones) apparently don't work with the clones... I wish I knew the version numbers.. maybe somebody can do a bit of research.

Clone owners HAD to use old drivers ...
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
turboat
Hero Member
*****

Karma: +42/-2
Offline Offline

Posts: 615


« Reply #6 on: October 24, 2014, 04:52:57 AM »

Update from FTDI following coverage on zdnet, reddit, el reg, etc:

http://www.ftdichipblog.com/?p=1053

Theyre pulling the destructive driver and will push something out next week, but this sets a very awkward precedent.
Logged
MadCow
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 106


« Reply #7 on: October 26, 2014, 09:12:02 AM »

So could this be why some generic KKL cables don't work at all out of the box while seemingly identical other ones work just fine? I'm glad they pulled the bricking driver though, that was not a well-thought out move. They could've easily just given the end user a warning but they decided on the scorched earth approach.
Logged
edgy
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 66


« Reply #8 on: November 08, 2014, 09:05:46 AM »

A few weeks old, but still important information:

http://hackaday.com/2014/10/22/watch-that-windows-update-ftdi-drivers-are-killing-fake-chips/

http://m.slashdot.org/story/208837
Logged

2002 S4 full stg 3
2001 S4 stg 2
2001 TT 225 stg 2
1988 80q 4.2
2005 A4 (the wife's)
nyet
Administrator
Hero Member
*****

Karma: +411/-47
Offline Offline

Posts: 9170


WWW
« Reply #9 on: November 08, 2014, 10:37:02 AM »


Update from FTDI following coverage on zdnet, reddit, el reg, etc:

http://www.ftdichipblog.com/?p=1053

Theyre pulling the destructive driver and will push something out next week, but this sets a very awkward precedent.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
turboat
Hero Member
*****

Karma: +42/-2
Offline Offline

Posts: 615


« Reply #10 on: November 24, 2014, 02:14:43 PM »

So it may just be coincidence, but my laptop just did a windows update, rebooted and now the FTDI cable doesnt work. Anyone else having issues?

EDIT: So I decided to do some debugging...

The bad FTDI drivers set fake(?) chips to a VID:0403, PID:0000, when the chip should report 4003:6001.

I configured windows to never download drivers from windows update, then I set the PID back to 6001, plugged it in and let windows detect it with the bad (2.12.00 drivers), then hit 'uninstall driver, and delete driver', which causes the driver to be deleted from the 'Driver Store' - the internal database windows uses to locate drivers.

Unsurprisingly, the bad drivers had set my PID to 0x0000 again, so I reset that, plugged it back in and windows loaded up the drivers from January 2014, iirc the 2.10.00 set. Everything was looking peachy, so I fired up NEF and could talk to a spare me7.5 ecu. So I unplugged it again, plugged it back in, and surprisingly it wouldnt work again - because my PID had been set to 0000 again.

So I tested this a few times, set the PID to 6001, plugged it into windows, unplugged it and then checked the pid, everytime the windows laptop would reset the PID to 0000. So I went through and uninstalled all the FTDI drivers from the windows store, even with no drivers installed at all (not even the 2006 ones that ship with windows), when the port would appear as a 'USB Serial port, manufacturer: unknown, device type: other devices' and not work, it would reset the PID when I plug the cable in - so what the heck have FTDI left on my system?

I did a search on system32 and system32/drivers and it turned out quite a lot, so I first tried deleting all the files installed by the 2.12 driver pack - but that didnt work, so I used "pnputil.exe -f -d oem<xy>.inf" to delete the inf for my FTDI drivers. Along the way, I told windows to delete the old ftdi drivers too, given the wierd behaviour I've been seeing.

At this point, I can plug and unplug my FTDI lead without it zeroing the PID. I reinstalled the 2.10 drivers and I can still plug and replug it. Read a eeprom using argdubs tool, and flash file with nef and it all seems to be happy. Of course, it might break tomorrow!
« Last Edit: November 24, 2014, 05:22:07 PM by turboat » Logged
terminator
Sr. Member
****

Karma: +7/-1
Offline Offline

Posts: 288


« Reply #11 on: December 01, 2014, 04:18:31 AM »

My cable died after Windows update  Wink All blue cables use fake FTDI chip.
Logged
turboat
Hero Member
*****

Karma: +42/-2
Offline Offline

Posts: 615


« Reply #12 on: December 01, 2014, 04:41:58 AM »

Set the PID back to 6001 using linux, disable windows update for drivers, delete the bad ftdi drivers using pnputil, install the good ftdi drivers, your lead will work again Smiley

really, do ALL blue leads have fake chips? Shame, I like my blue lead!
Logged
redtop
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 44


« Reply #13 on: December 01, 2014, 06:01:04 AM »

Is there any way to identify a fake chip without plugging it into a computer with "destructive" drivers?
I normally use an XP-machine so I'm safe, but it would be good to know if the adapters I have has real or fake FTDI chips so I know if I can use them in other computers or not.
Logged
turboat
Hero Member
*****

Karma: +42/-2
Offline Offline

Posts: 615


« Reply #14 on: December 01, 2014, 07:08:08 AM »

I haven't yet found one, I emailed FTDI about this months ago, but never got a response. Maybe it's time to reach out again...
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.025 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)