It is entirely possible that your bricked FTDI device is not an FT232 and has a different PID code, such as 6011, 6014, etc. I have confirmed this specifically for FTDI FT232 devices. In the ftdibus.inf and ftdiport.inf files you opened earlier, replace all instances of 6001 with 0000. If your PID has been set to 0000, then you can continue below. If your device still does not work as expected you likely are experiencing other issues and this guide is not for you. If your PID is set to a value like 6001 or 6010 then it has a valid PID and has not been bricked. Note: If your PID value is not nulled (0000) then your device has not been disabled by the new FTDI drivers. Select Hardware IDs from the details tab and verify that the Product ID has been set to '0000'. Open the properties dialog for the device in question. Open Device Manager by running devmgmt.msc from the start menu search box or run dialog. Once the file is downloaded and decompressed, open ftdibus.inf and ftdiport.inf in your text editor of choice. Should FTDI remove the download above, I have hosted it locally here: This is currently available from the FTDI driver download site here: To get started, download the 2.10.00 version of the Virtual COM Port driver. This guide is provided for educational purposes ONLY. Following this guide could brick your device even worse than it already is.
0 Comments
Leave a Reply. |