Using the FT245 Driver under Windows

Installation

In order to operate the sensor terminal board or STK541 under windows, the virtual COM port driver (VCP) from http://www.ftdichip.com/Drivers/VCP.htm has to be used. With the following steps the driver gets installed:

1. Download the driver package "CDM 2.04.06 WHQL Certified.zip"
2. Unpack it in a temp directory.
3. Apply the patch ftdi_cdm_2.04.06.patch manually or with the patch command (e.g., if mingw or cygwin is installed).
4. Connect the USB board to the PC and guide the hardware assistent to the patched directory and complete the installation. Since the WHQL certification breaks with the patch, you have explicitely to confirm, that you want to install that driver.
5. Now you should find the assigned COM port in the device manager.

Patch for ftdibus.inf and ftdiport.inf

diff -ur CDM 2.04.06 WHQL Certified/ftdibus.inf CDM 2.04.06-work/ftdibus.inf
--- CDM 2.04.06 WHQL Certified/ftdibus.inf  Fri Jan 30 15:48:18 2009
+++ CDM 2.04.06-work/ftdibus.inf    Fri Jan 30 16:10:33 2009
@@ -45,11 +45,15 @@
 %USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6001
 %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_00
 %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6010&MI_01
+%USB\VID_1CF1&PID_0001.DeviceDesc%=FtdiBus.NT,USB\VID_1CF1&PID_0001
+%USB\VID_03EB&PID_2109.DeviceDesc%=FtdiBus.NT,USB\VID_03EB&PID_2109

 [FtdiHw.NTamd64]
-%USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6001
+%USB\VID_0403&PID_6001.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_6001
 %USB\VID_0403&PID_6010&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_00
 %USB\VID_0403&PID_6010&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_6010&MI_01
+%USB\VID_1CF1&PID_0001.DeviceDesc%=FtdiBus.NTamd64,USB\VID_1CF1&PID_0001
+%USB\VID_03EB&PID_2109.DeviceDesc%=FtdiBus.NT,USB\VID_03EB&PID_2109

 [ControlFlags]
 ExcludeFromSelect=*
@@ -113,5 +117,8 @@
 USB\VID_0403&PID_6001.DeviceDesc="USB Serial Converter"
 USB\VID_0403&PID_6010&MI_00.DeviceDesc="USB Serial Converter A"
 USB\VID_0403&PID_6010&MI_01.DeviceDesc="USB Serial Converter B"
+USB\VID_1CF1&PID_0001.DeviceDesc="Dresden Elektronik SensTermBoard"
+USB\VID_03EB&PID_2109.DeviceDesc="Atmel STK541"
+
 SvcDesc="USB Serial Converter Driver"
 ClassName="USB"
diff -ur CDM 2.04.06 WHQL Certified/ftdiport.inf CDM 2.04.06-work/ftdiport.inf
--- CDM 2.04.06 WHQL Certified/ftdiport.inf Fri Jan 30 15:48:18 2009
+++ CDM 2.04.06-work/ftdiport.inf   Fri Jan 30 16:02:34 2009
@@ -41,10 +41,15 @@
 [FtdiHw]
 %VID_0403&PID_6001.DeviceDesc%=FtdiPort232.NT,FTDIBUS\COMPORT&VID_0403&PID_6001
 %VID_0403&PID_6010.DeviceDesc%=FtdiPort2232.NT,FTDIBUS\COMPORT&VID_0403&PID_6010
+%VID_1CF1&PID_0001.DeviceDesc%=FtdiPort232.NT,FTDIBUS\COMPORT&VID_1CF1&PID_0001
+%VID_03EB&PID_2109.DeviceDesc%=FtdiPort232.NT,FTDIBUS\COMPORT&VID_03EB&PID_2109
+

 [FtdiHw.NTamd64]
 %VID_0403&PID_6001.DeviceDesc%=FtdiPort232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6001
 %VID_0403&PID_6010.DeviceDesc%=FtdiPort2232.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6010
+%VID_1CF1&PID_0001.DeviceDesc%=FtdiPort232.NTamd64,FTDIBUS\COMPORT&VID_1CF1&PID_0001
+%VID_03EB&PID_2109.DeviceDesc%=FtdiPort232.NTamd64,FTDIBUS\COMPORT&VID_03EB&PID_2109

 [FtdiPort.NT.AddService]
 DisplayName    = %SvcDesc%
@@ -150,11 +155,14 @@
 

 [Strings]
 FTDI="FTDI"
-DESC="CDM Driver Package"
-DriversDisk="FTDI USB Drivers Disk"
+DESC="CDM Driver Package - uracoli"
+DriversDisk="FTDI USB Drivers Disk - uracoli"
 PortsClassName = "Ports (COM & LPT)"
 VID_0403&PID_6001.DeviceDesc="USB Serial Port"
 VID_0403&PID_6010.DeviceDesc="USB Serial Port"
+VID_1CF1&PID_0001.DeviceDesc="Dresden Elektronik SensTermBoard"
+VID_03EB&PID_2109.DeviceDesc="Atmel STK541"
+
 SvcDesc="USB Serial Port Driver"
 SerEnum.SvcDesc="Serenum Filter Driver"

VCP Driver Licensing Conditions

The Website of FTDI states http://www.ftdichip.com/Drivers/VCP.htm (2009-02-03).

FTDI device drivers may be used only in conjunction with products based on FTDI parts.
The driver may be distributed in any form as long as our license information is not modified.
If a custom Vendor ID and/or Product ID, or description string are used, it is the responsibility of the product manufacturer to maintain any changes and subsequent WHQL re-certification as a result of using these changes.