This page pertains to Windows operating systems.

The FTDI drivers which were previously delivered on the product CD, and which are available at "PlugComputer Software & Design Information - Revision 1.2" (in the SWsupportPackageWindowsHost1.2.zip) are version 2.04.16. This version seems to work without a problem. However, the current driver version is 2.08.08. Installing the newer version might prevent some potential errors.

This installation is not difficult, but it does require some minor file editing.

Download New Driver Files

1. The drivers are available at http://www.ftdichip.com/Drivers/VCP.htm .
2. Unzip the downloaded file

Two of the files in the unzipped directory will be edited later.

Notes for 64-bit machines

The website given above has both 32-bit and 64-bit drivers. The 64-bit version sets up a serial port that works without any problem.

But, they do not seem to work with openOCD (it has been speculated that this is because openOCD is compiled in 32-bit). Most of the simplified kernel installation methods described in the wiki and the forum depend upon openOCD. Therefore, many of the kernel installation methods will not work with the 64-bit drivers.

It is not certain whether installing the 32-bit drivers on a 64-bit machine will fix this issue.

However, kernels can be installed fairly easily without the simplified method. There is also the option of using a Live Linux disk.

So, unless you have succeeded in wiping u-Boot and need to reinstall your bootloader; or are not willing to use a Live Linux disk, there is not an absolute need to use the 32-bit drivers on a 64-bit machine.

Uninstall Earlier Drivers

If you have not previously installed the FTDI ("Serial Port") drivers, then skip this part.

You might be able to only update the drivers (instead of uninstall then reinstall), but there is some risk something will not be cleaned up, and there will be conflicts. This is made more likely because the FTDI Port sits on top of the Best to be sure and get to a clean start.

1. Connect the Plug to the host machine and power up the Plug.
2. On the Windows host machine, open the Control Panel, then the Device Manager. Look under "COM and LPT Ports to find the USB Serial Port.
3. Right-click on the USB Serial Port entry and select "Properties." Select the "Driver" tab, then click on the "Uninstall" button. If the confirmation message asks you if whether to delete the driver files on the system, check the box to cause the deletion.
4. There should be a message about needing to restart the machine. Disconnect the Plug from the host machine and restart the host.
5. After restart, again connect the Plug to the host and enter the Device Manager (steps 1 and 2)
6. Now under the USB controllers, look for USB Serial Converter A and USB Serial Converter B
7. Right-click on the USB Serial Converter A entry and select "Properties." Select the "Driver" tab, then click on the "Uninstall" button. If the confirmation message asks you if whether to delete the driver files on the system, check the box to cause the deletion.
8. Right-click on the USB Serial Converter B entry and select "Properties." Select the "Driver" tab, then click on the "Uninstall" button. If the confirmation message asks you if whether to delete the driver files on the system, check the box to cause the deletion.
9. Disconnect the Plug from the host machine and restart the host. (In theory, it might be possible to skip the first restart and only do this last one, but restarting twice is a little extra safety

Clean Starting State

The first time the Plug is connected, the Windows machine attempts to locate drivers for the device. Eventually, there will be a notice that drivers could not be found (see image for example). After uninstalling drivers, this message shows up again, it is a good sign that the machine is in a clean state.

This is the state from which installation of the new drivers begins for all.

Image showing no drivers found on a Windows 7 machine

Find the VID/PID of your Plug

You will need the VID/PID [Vendor Id/Product Id] for the next part. If you do not know them already, follow steps 4 and 5 from Finding the VidPid .

Image showing unrecognized SheevaPlug ports on a Windows 7 machine

Preparation

Edit the INF files

These changes are needed to support GlobalScale Plugs with VID/PID 0x9e88 / 0x9e8f. The reference document (below) states that they are also for Ionics Plugs with VID/PID 0x1c0c / 0x0102 (the writer is unable to confirm, but following the file format should make adding any device's ids easy).

VID 0x0403, with PIDs 0x6010 and 0x6011 are already in the files, so for devices with those numbers this step can be skipped.

The files which must be edited will be in the topmost directory of the unzipped drivers package (from the Download step, above).

In both of these files there are lines which must be added. (If you decide to remove lines, you are on your own.)

The lines must be put into the correct section. The order within the section is not so important, so add them first or last, as you wish. The sections named "FtdiHw.NTamd64" (one in each file) seem to be for 64-bit machines. So, it is possible they might be omitted on 32-bit machines.

In these examples the VID/PID of 0x9e88 0x9e8f is used. Do not include the preface "0x" which is used to identify hex numbers.

These formats are for driver version v2.08.08.

Edit ftdibus.inf

[FtdiHw]
%USB\VID_9E88&PID_9E8F.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F
%USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F&MI_00
%USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_9E88&PID_9E8F&MI_01

[FtdiHw.NTamd64]
%USB\VID_9E88&PID_9E8F.DeviceDesc%=FtdiBus.NTamd64,USB\VID_9E88&PID_9E8F
%USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_9E88&PID_9E8F&MI_00
%USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_9E88&PID_9E8F&MI_01

[Strings]
USB\VID_9E88&PID_9E8F.DeviceDesc="USB Serial Converter"
USB\VID_9E88&PID_9E8F&MI_00.DeviceDesc="USB Serial Converter A"
USB\VID_9E88&PID_9E8F&MI_01.DeviceDesc="USB Serial Converter B"

Edit ftdiport.inf

[FtdiHw]
%VID_9E88&PID_9E8F.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_9E88&PID_9E8F

[FtdiHw.NTamd64]
%VID_9E88&PID_9E8F.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_9E88&PID_9E8F

[Strings]
VID_9E88&PID_9E8F.DeviceDesc="USB Serial Port"

Installing the New Drivers

1. Open the Device Manager and look under "Other Devices" for the unrecognized plug devices. (See example image)
2. Right-click on the entry for the first device (such as "SheevaPlug JTAGKey FT2232D B") and select "Update Driver Software"
3. Choose to load the driver from your machine
4. Browse to the unzipped directory created in the Downloads section (above)
5. Click Ok, and after a short wait there should be a message about a driver installed for "USB Serial Converter A"
6. Right-click on the entry for the remaining "Other device," and select "Update Driver Software"
7. Choose to load the driver from your machine
8. Browse to the unzipped directory created in the Downloads section (above)
9. Click Ok, and after a short wait there should be a message about a driver installed for "USB Serial Converter B"
10. There should now be a new entry under "Other Devices", named "USB Serial Port." If this is not present, disconnect the Plug, restart the machine, then re-enter the Device Manager.
11. Right-click on the entry for "USB Serial Port," and select "Update Driver Software"
12. Choose to load the driver from your machine
13. Browse to the unzipped directory created in the Downloads section (above)
14. Click Ok, and after a short wait there should be a message about a driver installed. Notice also the message about the driver not working until after a restart.
15. Look under "Ports (COM & LPT)", for the new device -- "USB Serial Port (COM8)" (The COM number may be different on your machine.) Make note of this number, it is the COM port used by PuTTY and other serial programs to connect to the Plug.
16. Disconnect the Plug, restart the host machine.

You should now be able to connect with the new drivers.

References

1. EISA Windows 7 Installation Guide (PDF 332KB) -- This document was the source of most of this page information, but it contains instructions for the v2.06.00 drivers. The format of the ftdiport.inf file has changed slightly in v2.08.08. The instructions above followed the format for the later version.