FTDI Community

General Category => Discussion - Software => Topic started by: amolina on April 22, 2021, 05:35:32 PM

Title: FT_Prog EEPROM accidentally change Product ID and lost connection (help)
Post by: amolina on April 22, 2021, 05:35:32 PM

Hi.

Accidentally change Product ID from 0x6011 to 0x6012 on EEPROM by FTDI FT Prog on FT4232H and now can't connect again to revert changes.

Option will be disconnect EEPROM or there are other way to do?

Thanks

Title: Re: FT_Prog EEPROM accidentally change Product ID and lost connection (help)
Post by: FTDI Community on April 23, 2021, 04:49:27 PM

Hello,

You need to edit the INF files in the driver install files (2.12.28 (https://www.ftdichip.com/Drivers/CDM/CDM%20v2.12.28%20WHQL%20Certified.zip)) to include your changed PID. See this App Note which should help (Section 4):
AN_107_AdvancedDriverOptions_AN_000073 (https://ftdichip.com/wp-content/uploads/2020/08/AN_107_AdvancedDriverOptions_AN_000073.pdf).

Connect the device and point the driver install to the INF files that you edited in Device Manager. They should install and device should enumerate ok.
Note that editing the driver files breaks any certification and some OS versions (Windows 7 x64 and newer) require drivers to be certified. See TN_129 Driver Release Signing (https://ftdichip.com/wp-content/uploads/2020/08/TN_129_Driver-Release-Signing.pdf) to try and overcome this problem. Disabling the OS certification check is an easy temporary method.

You can now use FT_PROG to change the VID and PID back to their defaults:
https://ftdichip.com/utilities/#ft_prog (https://ftdichip.com/utilities/#ft_prog)

Now the device should enumerate automatically next time it’s connected.

If you have any further problems please contact your local support office:

https://ftdichip.com/technical-support/ (https://ftdichip.com/technical-support/)

Best Regards,
FTDI Community

Title: Re: FT_Prog EEPROM accidentally change Product ID and lost connection (help)
Post by: amolina on April 27, 2021, 09:27:58 AM

Hi.
I can't continue because modified .INF files are not certificated and Windows don't let me install.

May be this files will help but the link is broken: Could you get this?

http://ftdichip.com/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products(FT_000072).pdf
http://ftdichip.com/Documents/AppNotes/AN_WHQL_Certified_Driver_Process_v100(FT_000063).pdf

Thanks