[aprssig] ***SPAM*** Re: ***SPAM*** Oh No!! Fake Prolific 2303 USB<-->Serial Chip Fiasco Now Spreading To FTDI

KF4LVZ aprssigZbr6 at acarver.net
Sat Mar 28 00:08:44 EDT 2015

FTDI has already reversed course on the reflashing.  The newest drivers
no longer do that and they have offered software to fix any chips that
were flashed.  It caused much more trouble than simple dongles because
most devices with integrated USB interfaces are actually just these
serial chips (it's much easier for an embedded processor to communicate
via simple serial rather than directly use USB).  So things other than
simple dongles were being bricked including medical instruments,
laboratory equipment, etc.

On 2015-03-27 21:01, Stephen H. Smith wrote:
> For several years, Prolific Technology has been attempting to fight
> Chinese counterfeit copies of their USB<-->serial chip by playing games
> with recent versions of the driver they provide for this device.   The
> current driver somehow determines that a device has a fake 2303 chip and
> refuses to install or run.   This breaks numerous devices (USB-serial
> dongles, USB-interface GPS units, radio programming cables, etc.) that
> contain "fake" chips.
> Windows Update automatically updates  the Prolific driver when it finds
> it present in a Windows installation.  This has the effect of causing
> devices that initially worked with an older version Prolific driver,
> provided with the device, to stop working after Windows Update
> "helpfully" updates to the "DRMed" driver.   More details on the
> Prolific mess here on my website:
> .   <http://wa8lmf.net/ham/USB-Serial-Dongles.htm>
> For the last year or so, the conventional wisdom was that to avoid this
> headache, insist on USB<-->serial dongles based on the FTDI chip
> instead.  Now it appears that Scotland-based FTDI is facing the same
> problems (Chinese fakes) and is taking even more drastic action.  Their
> latest drivers are actually reflashing the internal EEPROM of fake FTDI
> chips to render them nonfunctional even if you reinstall an older
> non-DRM driver.  This has the effect of permanently "bricking" the
> device the chip is embedded in.
> I somehow missed this story on Slashdot.org when it first ran last
> October, but a passing reference and a link to it appeared today (27 Mar
> 15):
> <http://hardware.slashdot.org/story/14/10/22/185244/ftdi-reportedly-bricking-devices-using-competitors-chips?sdsrc=popbyskid>
> "FTDI Reportedly Bricking Devices Using Competitors' Chips.
> It seems that chipmaker FTDI has started an outright war on cloners of
> their popular USB bridge chips. At first the clones stopped working with
> the official drivers, and now they are being intentionally bricked,
> rendering the device useless. The problem? These chips are incredibly
> popular and used in many consumer products. Are you sure yours doesn't
> contain a counterfeit one before you plug it in? Hackaday says, "It’s
> very hard to tell the difference between the real and fake versions by
> looking at the package, but a look at the silicon reveals vast
> differences. The new driver for the FT232 exploits these differences,
> reprogramming it so it won’t work with existing drivers. It’s a bold
> strategy to cut down on silicon counterfeiters on the part of FTDI. A
> reasonable company would go after the manufacturers of fake chips, not
> the consumers who are most likely unaware they have a fake chip."
> In a series of Twitter posts, FTDI has admitted to doing this. "

More information about the aprssig mailing list