Own driver "Develop" based on FTDI part 2

After we have generated a new hardware last time, which we can no longer use, we will now create a suitable driver.

In the device, we now have our "own" FTDI-Chip as an unknown device:

 

For our blog articles today, we need:

-Our FTDI chip faded yesterday

-Software FT_INF (https://www.ftdichip.com/Support/Utilities.htm#FT_INF)

-FTDI driver (https://www.ftdichip.com/Drivers/D2XX.htm)

In our blog we describe the x64 version for Windows.

 

Now we first start the installed software FT_INF.

Here we have to make a few adjustments:

With Chip Type we don't have to set anything, because we let FT232R selected.

At Vendor ID/Product ID we have to set something:

Device Descripton: Florians USB Device

Port Description: Florians Serial Port

Vendor ID: 1000

Product ID: 5824

Inital Index: 0

Then, we add these hardware settings to the driver by clicking the > > arrows:

For the next step, we need the original FTDI driver. We have already downloaded this from the beginning and now only have to unpack it:

FT_INF requires the files, ftdibus.inf, and ftdiport.inf under "Time Stamp/File Names". These must be loaded in the software FT_INF. To do this, simply click on the folder in the respective line and search the file in the Explorer:

So the window now has to look at you with the loaded files:

As a last setting, we change the company name from the Manufacturer details, possibly you can also customize the output path (to the desktop):

Now we should check all the settings again and adjust everything, we click on "Generate Files". Then 2 new INF files are created:

As a next step, we will replace the newly created INF files in the original driver.

We can now deliver these 5 files and 3 folders with our hardware. Now we've finished creating our driver.

In the next step, we will install this driver on Windows. Since this driver is unsigned, Windows will not easily accept the problem and ask for permission several times. On Windows 10, the Unsigned Driver mode must be activated only with a restart:

Enabling unsigned drivers using the advanced startup settings:
-Shift key (Large letters) hold down and click on Restart
-Problem handling
-Advanced options
-Start settings
-Click to start new
-Use the 7 key to deactivate the force of the driver signature.
-Windows 10 restarts

Now we go back to the device manager and right-click on our still unknown device and choose update drivers:

Then we choose "Search on the computer for driver software." from:

In the next window, we will give you the path to our new driver:

Windows now finds suitable drivers in the folder, but Windows meckert because of unsigned drivers, please select "Install this driver software anyway" here:

The first part of the driver (FTDI-Bus) has been successfully installed:

Now we have to install the driver for the serial port (FTDI-Port). To do this, we repeat the following steps:

Now we have installed our own "Florians Serieller Port":

This is now also shown in the device with Serial Port number:

And also under the USB devices, our device is displayed with the new name:

 

Under the properties of "Florians USB Device" we can now read PID (5824), VID (1000) and serial number (AZ33548379), without which we need an FTDI tool:

It will now only be possible to follow with difficulty, which uses an FTDI adapter and can now display your own names in the device manager:

The serial adapter can now be used as normal again. There is no difference to the "original" FTDI driver.

Now you could change more of the driver and reveal even less information on FTDI. But you can find out for yourself.

We wish you lots of fun and success with further experimentation.

Basics software

Leave a comment

All comments are moderated before being published

Recommended blog posts

  1. Install ESP32 now from the board manager
  2. Lüftersteuerung Raspberry Pi
  3. Arduino IDE - Programmieren für Einsteiger - Teil 1
  4. ESP32 - das Multitalent
  5. OTA - Over the Air - ESP programming via WLAN