FTDI driver kills fake FTDI FT232??

[nitro2k01]

Jamie, what does dmesg output after you plug in the device in Linux?

[toysareforboys]

Jamie, what does dmesg output after you plug in the device in Linux?

[   69.144050] usb 8-1: new full-speed USB device number 2 using uhci_hcd
[   69.268064] usb 8-1: device descriptor read/64, error -71
[   69.492047] usb 8-1: device descriptor read/64, error -71
[   69.708069] usb 8-1: new full-speed USB device number 3 using uhci_hcd
[   70.036064] usb 8-1: device descriptor read/64, error -71
[   70.260069] usb 8-1: device descriptor read/64, error -71
[   70.476060] usb 8-1: new full-speed USB device number 4 using uhci_hcd
[   70.888039] usb 8-1: device not accepting address 4, error -71
[   71.204082] usb 8-1: new full-speed USB device number 5 using uhci_hcd
[   71.616047] usb 8-1: device not accepting address 5, error -71
[   71.616096] usb usb8-port1: unable to enumerate USB device

-Jamie M.

[linux-works]

you should be able to use the ftdi fixer (not by ftdi, but by some linux guys) to set the pid and vid.

the key is to have only one dongle plugged in and refer to it by /dev/ttyUSB0.  it will then set the vid and pid for you if you give it both arguments to the CLI.

[toysareforboys]

you should be able to use the ftdi fixer (not by ftdi, but by some linux guys) to set the pid and vid.

the key is to have only one dongle plugged in and refer to it by /dev/ttyUSB0.  it will then set the vid and pid for you if you give it both arguments to the CLI.

Do you have a link to the software "by some linux guys"? I've been trying to use ft232r_prog version 1.24 by Mark Lord, but I don't see anywhere I can tell it to write to /dev/ttyUSB0



-Jamie M.

[neslekkim]

sudo ./ft232r_prog --old-pid 0x0000 --new-pid 0x6001

[linux-works]

you don't refer to it by ttyUSB0 in mark's program (that's the one I was thinking of).

that's why I said, make sure only ONE ftdi dongle is on your system.  his app will find it and set its pid and vid.  that's why you don't give /dev/ttyUSB0 on the command line.  it would have been sensible to do that, but he makes you have only 1 connected and if he finds it, he writes to it.

[toysareforboys]

sudo ./ft232r_prog --old-pid 0x0000 --new-pid 0x6001

Tried that the first time, just said it couldn't find the ftdi chip on usb. I had lots of other USB stuff plugged in at the time though.

you don't refer to it by ttyUSB0 in mark's program (that's the one I was thinking of).

that's why I said, make sure only ONE ftdi dongle is on your system.  his app will find it and set its pid and vid.  that's why you don't give /dev/ttyUSB0 on the command line.  it would have been sensible to do that, but he makes you have only 1 connected and if he finds it, he writes to it.

Sweet, I'll give it a go. Before I was booted off USB plus had a USB mouse. I've now got it burnt to DVD and no other USB devices so we'll see if it works! Thanks!

-Jamie M.

[toysareforboys]

Nope, no go

ubuntu@ubuntu:~/ft232r_prog-1.24$ sudo ./ft232r_prog --old-pid 0x0000 --new-pid 0x6001 --old-vid 0x0000 --new-vid 0x0403

ft232r_prog: version 1.24, by Mark Lord.
ftdi_usb_open() failed for 0000:0000: device not found
ubuntu@ubuntu:~/ft232r_prog-1.24$

I think in the source code it's trying to look at it by vid/pid. I wonder if we can edit the source to make it do a blind write of the vid/pid to /dev/ttyUSB0?

-Jamie M.

[linux-works]

can you omit the 'old' stuff and just feed it the new vid and pid?

maybe even try setting just one at a time?

[toysareforboys]

can you omit the 'old' stuff and just feed it the new vid and pid?

maybe even try setting just one at a time?

Nope, when you omit either the old vid or pid it uses the default vid and pid to try and read it (0403/6001):

ubuntu@ubuntu:~/ft232r_prog-1.24$ sudo ./ft232r_prog --new-pid 0x6001 --new-vid 0x0403

ft232r_prog: version 1.24, by Mark Lord.
ftdi_usb_open() failed for 0403:6001: device not found
ubuntu@ubuntu:~/ft232r_prog-1.24$ sudo ./ft232r_prog --new-pid 0x6001

ft232r_prog: version 1.24, by Mark Lord.
ftdi_usb_open() failed for 0403:6001: device not found
ubuntu@ubuntu:~/ft232r_prog-1.24$ sudo ./ft232r_prog --new-vid 0x0403

ft232r_prog: version 1.24, by Mark Lord.
ftdi_usb_open() failed for 0403:6001: device not found
ubuntu@ubuntu:~/ft232r_prog-1.24$

I found out that Mark Lord lives not far from me, lol! I sent him an e-mail to see if he can help

-Jamie M.
(p.s. here's the relevant source code from Mark's program where it's erroring out on me:

Code: [Select]

ftdi_init(&ftdi);
atexit(&do_deinit);

memset(&ee, 0, sizeof(ee));
ee.old_vid = 0x0403;; /* default; override with --old_vid arg */
ee.old_pid = 0x6001; /* default; override with --old_pid arg */
process_args(argc, argv, &ee); /* handle --help and --old-* args */

if (ftdi_usb_open_desc(&ftdi, ee.old_vid, ee.old_pid, NULL, ee.old_serno)) {
fprintf(stderr, "ftdi_usb_open() failed for %04x:%04x:%s %s\n",
ee.old_vid, ee.old_pid, ee.old_serno ? ee.old_serno : "", ftdi_get_error_string(&ftdi));
exit(ENODEV);
}
atexit(&do_close);

[linux-works]

maybe your device is just plain BAD (?)

[toysareforboys]

maybe your device is just plain BAD (?)

It wasn't bad before the equipment manufacturer bricked it, but they bricked it really good

I think I'll smash open the epoxy fill tonight and see if I can find the FTDI chip. If I can I'll order a new one and swap it out.

-Jamie M.

[toysareforboys]

I heard back from Mark Lord, doesn't sound good

-----Original Message-----
From: Mark Lord
Sent: Thursday, April 23, 2015 6:43 PM
To: Jamie M.
Subject: Re: FTDI chip unbricking, with vid 0000 AND pid 0000 plz help!

The device has to show up in "lsusb" for anything on Linux to work with it.
So, do "lsusb" without it plugged in, then plug it in (wait a few secs)
and do "lsusb" again, and compare.  Anything new show up?

--
Mark Lord
Real-Time Remedies Inc.

On that news I've decided to break it open and see if I can find the FTDI chip to replace it. Yikes.



-Jamie M.

[madworm]

Comment by Nuno Gonçalves: "The driver (2.12) is back on windows update. Clones are getting bricked again."

Any confirmations?

[MadMike]

Comment by Nuno Gonçalves: "The driver (2.12) is back on windows update. Clones are getting bricked again."

Any confirmations?

It's not back. Unless it was only there for a short time and they've pulled it yet again, which seems unlikely.
http://catalog.update.microsoft.com/v7/site/Search.aspx?q=USB%5cVID_0403%26PID_6001 (IE only, thank you Microsoft  ) Latest FTDI driver update was 2014-08-26.

Edit:
Ignore the above. I'm being stupid.
I was just told by a coworker that the date listed is when the driver was made, not when it was published to windows update as I had assumed. A quick look at the version number, which I should have done, confirms that 2.12 is indeed on windows update.

[Macbeth]

NEW LabVIEW Driver for DE-6000 is available for collecting data from the DE-6000. The driver is written in LabVIEW 2013 and requires the optional DE-6000-DTK IR-USB interface adapter.

Everything about the "DE-6000" is dodgy to me. When a seller only lets you know price by "Request a quote" that usually means megabucks and slimy salesmen in the middle. It's just a DE-5000 relabelled and sold for a fortune. No thanks, I got mine from Japan with the tweezers and 4 wire croc clips for $99 delivered.

However, to be fair to IET, the LabVIEW driver is nothing whatsoever to do with the FTDI driver. Think of it more like the front end graphical interface. Does the DE-6000 include this driver, hence the huge markup, or is it another "request a quote" add on?

[rsjsouza]

Everything about the "DE-6000" is dodgy to me.

No kidding! Image from their page:

[AlfBaz]

However, to be fair to IET, the LabVIEW driver is nothing whatsoever to do with the FTDI driver. Think of it more like the front end graphical interface. Does the DE-6000 include this driver, hence the huge markup, or is it another "request a quote" add on?

Thanks to a member here and the group he belongs to I managed to get the protocol details for the DE5000 with the express mission of creating my own de5000 labview drivers. Whenever I get around to finishing it I wonder what would happen if I tired release them into labviews online driver repository

[Macbeth]

However, to be fair to IET, the LabVIEW driver is nothing whatsoever to do with the FTDI driver. Think of it more like the front end graphical interface. Does the DE-6000 include this driver, hence the huge markup, or is it another "request a quote" add on?

Thanks to a member here and the group he belongs to I managed to get the protocol details for the DE5000 with the express mission of creating my own de5000 labview drivers. Whenever I get around to finishing it I wonder what would happen if I tired release them into labviews online driver repository

Don't worry. IET will have put some code in their LabVIEW driver to ensure it only works with their DE6000. I've seen this before with my Siglent SDG1025. This is also sold rebranded as a LeCroy Wavestation and the LeCroy LabVIEW driver does not work with the Siglent (it checks model number using a *IDN? SCPI request. Yeah, piss easy to work around ).

Now I commend you for not wanting to step on IETs toes by ensuring your driver only works with the Japanese DER DE5000. I suggest you collaborate with IETs developers. They are clearly open to this as they must have collaborated with Cyrusteks developers in Taiwan to develop the custom DE6000 firmware, and it is obviously in their interests to let you know how you can perform a check for DE5000 or DE6000 in your LabVIEW driver. I can't see any reason for them to with-hold this information from you  , so pop them an email.

[Mechatrommer]

maybe your device is just plain BAD (?)

or maybe linux is not everything in this world... here windows version...
http://www.reddit.com/r/arduino/comments/2k0i7x/watch_that_windows_update_ftdi_drivers_are/clgviyl
(sorry if its been overridden somewhere i didnt read all 100+ pages...

otoh and here some pointer on spotting real vs fake chip (maybe again i didnt read all 100+ pages)...



the most prominent difference is the detent (whats that called), the fake one got sharp detent... i checked all my china purchase arduino, usb-serial, and chip stocks they are all seem similar to the real chip, smoother detent... no?

[Mechatrommer]

btw i'm on WinXP old driver. so this auto-update-brick crap (which i'm sure can be disabled in ctl panel) is invisible to me hence i'm invinsible, for now. i dont blame ftdi i'll continue to support them, they paid subscription to ftdi-fi, paid real engineers and all. its just their action brick without warning is too noob for a professional person. the engineer responsible for this or the GM who made the decision must be too young to know what life is.

[Liv]

I wrote a utility for Windows to determine and recovery of counterfeit FT232RL chips. Recovery is possible using a modified driver (inf files attached).

[XFDDesign]

Nice! Thank you for that!

[rsjsouza]

That is a very nice utility, Liv! I can attest it reliably detected a Genuine FT232 part from this kit.

[0xdeadbeef]

Note that it gives false positives on "programmed" devices.