Flash Eeprom on USB\VID_0000&PID_0000 ?

**jaxone** · 17th February, 2013, 02:53 AM

Somehow I have erased the eeprom on the Galletto 2.
Now windows will detect it but only as : USB Fgtech Driver on USB\VID_0000&PID_0000

Is there ANY way to force a PID / VID change or flash the eeprom WITHOUT desoldering the FTDI chip ?

Windows / Linux does not matter.

Thank you in advance.

**bobolin4o** · 17th February, 2013, 07:47 AM

Look in folder:FG Tech, fgtech_new_driver, fgtibus.inf. Make backup of .inf file!
Open this .inf with notepad, and edit vid, pid to zeros - there is 3 places with vid & pid!. Save. Connect Galletto interface and choose the driver from that folder. Then fix the dump with FG fix tool, i recommend "usb fix2". Remove the edited .inf from folder and copy back tne original .inf. Re-connect the interface and choose the driver again from that folder. That's all.
Regards!

**Maxomat** · 17th February, 2013, 09:22 AM

you can reprogram the eeprom of ftdi devices using ftprog or Mprog:

FTDI Utilities

**jaxone** · 17th February, 2013, 11:11 AM

None of the solutions works as long as the VID and PID are 0000
Also if I change the infor in the .inf file the windows will say the hash of the file is altered and would not install the driver. (I tried that before posting)

**bobolin4o** · 17th February, 2013, 11:26 AM

Try with this!
It create usable Driver for your damaged FT...

"FT_INF has been updated to be compatible with the latest certified version of FTDI's Windows driver, 2.08.24.

FT_INF is a free application allowing users to create custom inf files that can be used in conjunction with FTDI's proprietary drivers. Altering inf files gives users the flexibility to install FTDI devices that do not use FTDI's default Vendor ID / Product ID as well as fine tune some of the more advanced driver settings.

FT_INF is available for download as a zip file by clicking here. The full FT_INF User Guide is available after installation.
Please Note: FT_INF requires the Microsoft .NET Framework 2.0 installed on your system to run the application. This can be obtained from the Microsoft Website (http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en), if your system does not have .NET 2.0 installed please download the file from the above link. To install, double click on the dotnetfx.exe and follow the instructions in the wizard."
Regards!

**Maxomat** · 17th February, 2013, 11:38 AM

Mprog works very well!

Connect Interface to Computer. Open Mprog.

Device -> Scan
Tools -> Read/Parse

Save dump and make a screenshot of everything!

Now VID and PID: Change from ftdi Defaults to "own vid & pid"

insert vid pid, saave template with new Name. Now you can write it back.

**bobolin4o** · 17th February, 2013, 11:43 AM

Originally Posted by Maxomat

Mprog works very well!

Connect Interface to Computer. Open Mprog.

Device -> Scan
Tools -> Read/Parse

Save dump and make a screenshot of everything!

Now VID and PID: Change from ftdi Defaults to "own vid & pid"

insert vid pid, saave template with new Name. Now you can write it back.

Yes, work... but if the windows not recognise the USB device - no drivers??? I think that this is situation here.
In this case i think "FT_INF" is the solution to make windows to recognise the zeros vid & pid... and then will be possible to correct them...

**jaxone** · 17th February, 2013, 05:08 PM

Mprog problem :
---------------------------
Information
---------------------------
All zeros is an invalid VID
---------------------------
OK
---------------------------

So I can not connect to a device that has 0000 as VID.

Problem with FTDI Inf.
I tried that before.
As long as stupid windows can not start the device (Windows will see the device with VID / PID 0000) I can not connect to it.
USB Enumerator must start the device in order to have access to it.

When I generate the inf with FTSI inf the windows keeps telling me :
The System can not find the file specified.

This are the files I generated.

**bobolin4o** · 18th February, 2013, 07:55 AM

So, i see too, thath the windows is stupid (actualy is not...), i kill one USB convertor with zero vid & pid and name "FGTech", and with mod driver no luck for now...

Edit: Successfully repaired! Just browse for compatible driver manually ( in my case it is another USB convertor, installed in Windows) and install it "anyway"... Then you be able to reprogram with "Mprog"

**jaxone** · 18th February, 2013, 01:31 PM

Originally Posted by bobolin4o

So, i see too, thath the windows is stupid (actualy is not...), i kill one USB convertor with zero vid & pid and name "FGTech", and with mod driver no luck for now...

Edit: Successfully repaired! Just browse for compatible driver manually ( in my case it is another USB convertor, installed in Windows) and install it "anyway"... Then you be able to reprogram with "Mprog"

Do you have the drivers for this Fobos ?

i don't see them in my list.

**bobolin4o** · 18th February, 2013, 02:17 PM

Have you installed "TeamViewer"?

**jaxone** · 18th February, 2013, 03:08 PM

Thanks for the offer.
I have sent it back to China today

I got an offer from UPS to send it for free back so I sent it.

Will let you know when the "new" one comes.

Thanks everyone for the help.

**nvh007vn** · 25th June, 2016, 04:08 AM

Originally Posted by bobolin4o

So, i see too, thath the windows is stupid (actualy is not...), i kill one USB convertor with zero vid & pid and name "FGTech", and with mod driver no luck for now...

Edit: Successfully repaired! Just browse for compatible driver manually ( in my case it is another USB convertor, installed in Windows) and install it "anyway"... Then you be able to reprogram with "Mprog"

Hi all brothers,

I got the same problem with my USB-RS232 cable used for Pluto PLC. This cable using FTDI chip.

The vid_0000&pid_0000 appear when I did update driver for USB serial converter from Device Manager and error message as in picture:

https://drive.google.com/folderview?...VE&usp=sharing

I will try to fix as your way and inform you later on.

Thankswith best regards

**morgano** · 25th June, 2016, 08:22 PM

Too much updated ftdi drivers kill counterfeit ft232 devices, so better stay with the driver supplied by vendor of your cable.

**imcumen** · 26th June, 2016, 02:10 AM

found on another forum
Try this:

1) Run the fix it from “Hardware devices not detected or not working”
http://support.microsoft.com/gp/hardware_device_problem...

2) Then refresh the USB Stack
a. Click start-Control Panel - Device Manager –

b. Expand USB Serial Controllers - RIGHT CLICK on EVERYTHING and UNINSTALL all except the category itself.

c. REBOOT the computer. This refreshes the drive and the USB stack

PS:you must disable the updates online drivers in windows 7 or another OS if not deactivated the ftdi died