Prolific: Difference between revisions
Created page with "The Prolific 2303 is a USB to serial controller. Cloned versions of the controller was commonly found in serial adapters from Ebay/China until around 2014 when Prolific began..." |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
The Prolific 2303 is a USB to serial controller. Cloned versions of the controller was commonly found in serial adapters from Ebay/China until around 2014 when Prolific began [https://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/msg535270/#msg535270 bricking cloned devices | The Prolific 2303 is a USB to serial controller. Cloned versions of the controller was commonly found in serial adapters from Ebay/China until around 2014 when Prolific began [https://www.eevblog.com/forum/reviews/ftdi-driver-kills-fake-ftdi-ft232/msg535270/#msg535270 bricking cloned devices by overwriting the firmware via the drivers]. Since then, most cheap serial adapters on Ebay use the CH340 or CP2102 controllers instead. | ||
== Troubleshooting == | The driver detects a counterfeit device is by exploiting the behavior of a real chip where write requests to an even address are deferred until it receives the next subsequent request at the odd address. If this address is not subsequent to the even address, the write is request is ignored. Clone chips perform each write immediately which allows Prolific's driver to overwrite the firmware. | ||
=== THIS IS NOT PROLIFIC PL2303 PLEASE CONTACT YOUR SUPPLIER === | |||
==Troubleshooting== | |||
===THIS IS NOT PROLIFIC PL2303 PLEASE CONTACT YOUR SUPPLIER=== | |||
Prolific's newer drivers will check whether the Prolific chip is authentic and if a clone is detected, the driver will refuse to function. Windows will automatically download the latest driver which comes with this 'feature'. Fortunately, their drivers no longer brick the counterfeit device. Short of buying another serial device, the only way to get around it is to use an older version of the driver. | Prolific's newer drivers will check whether the Prolific chip is authentic and if a clone is detected, the driver will refuse to function. Windows will automatically download the latest driver which comes with this 'feature'. Fortunately, their drivers no longer brick the counterfeit device. Short of buying another serial device, the only way to get around it is to use an older version of the driver. | ||
| Line 9: | Line 11: | ||
Alternatively, download the .exe installer and run it inside a VM and then navigate to AppData/temp and retrieve the .inf and .sys drivers from there. | Alternatively, download the .exe installer and run it inside a VM and then navigate to AppData/temp and retrieve the .inf and .sys drivers from there. | ||
== See Also == | ==See Also== | ||
* https://hardware.slashdot.org/story/14/10/24/1330252/ftdi-removes-driver-from-windows-update-that-bricked-cloned-chips | |||
*https://hardware.slashdot.org/story/14/10/24/1330252/ftdi-removes-driver-from-windows-update-that-bricked-cloned-chips | |||
{{Navbox Tinkering}} | |||
[[Category:Tinkering]] | |||
Latest revision as of 18:10, 15 July 2020
The Prolific 2303 is a USB to serial controller. Cloned versions of the controller was commonly found in serial adapters from Ebay/China until around 2014 when Prolific began bricking cloned devices by overwriting the firmware via the drivers. Since then, most cheap serial adapters on Ebay use the CH340 or CP2102 controllers instead.
The driver detects a counterfeit device is by exploiting the behavior of a real chip where write requests to an even address are deferred until it receives the next subsequent request at the odd address. If this address is not subsequent to the even address, the write is request is ignored. Clone chips perform each write immediately which allows Prolific's driver to overwrite the firmware.
Troubleshooting
THIS IS NOT PROLIFIC PL2303 PLEASE CONTACT YOUR SUPPLIER
Prolific's newer drivers will check whether the Prolific chip is authentic and if a clone is detected, the driver will refuse to function. Windows will automatically download the latest driver which comes with this 'feature'. Fortunately, their drivers no longer brick the counterfeit device. Short of buying another serial device, the only way to get around it is to use an older version of the driver.
There is a copy of version 3.3.2.105 of the drivers compatible with Vista in the Cloud/programs/drivers directory. This driver appears to work with Windows 10, though a BSOD can be triggered if you attempt to share/unshare the device with VMware.
Alternatively, download the .exe installer and run it inside a VM and then navigate to AppData/temp and retrieve the .inf and .sys drivers from there.