Arduino Stack Exchange is a question and answer site for developers of open-source hardware and software that is compatible with Arduino. It only takes a minute to sign up.
Sign up to join this community
I have changed PID and VID of my FTDI board for arduino program because i wanted to rename the com port name. The ic is FT232R a USB to serial UART interface IC. I have store new vid and pid to EEPROM. Now It is showing in unknown devices. I am not able to update driver of it. I have followed this article http://forum.arduino.cc/index.php?topic=6929.0.
Can anyone tell how to make cutmoize driver for it. Any suggestions will be very helpful.
On Windows
You can refer to FTDI's documentation here for details on how to create your own custom device driver. The FTDI website has a lot of resources for this, however they seem to be a little outdated. Microsoft details how drivers work in it's Hardware Dev Center.
On Linux
On Linux it may be as easy as registering the device with modprobe. For example, for a device with a VID of 0102 and a PID of 1234, execute the following from the shell:
modprobe ftdi_sio
echo "0102 1234" | sudo tee /sys/module/ftdi_sio/drivers/usb-serial\:ftdi_sio/new_id > /dev/null
You can do it, but you cannot change the PID and VID without a new certificate.
Did you changed the name with the FT-Prog Tool (MProg is outdated)? You can download the last version from here: https://www.ftdichip.com/Support/Utilities.htm#FT_PROG
You can set everything on your FTDI chip, even change the PID and VID. But at this point, you will not be able to use the standard FTDI driver anymore as you need to sign it with a new certificate (it is about 400$/year).
What you can do is leave the PID and VID and just give another name. So you will be able to use the default driver and you will see your custom name in the device manager.
Of course, in the list you just see "USB Serial Port (COM X)". But in the description of the device (Serial port), you will find this string:
FTDIBUS\VID_0403+PID_6011+YOURCUSTOMNAME&1\0000
If you create an application, you can just check for this, to see if it is your module. If you want more, you have to develop and release your own driver. But you can't do it anymore without a certificate, or without start Windows in unprotected mode.
