Installing FTDIUSBSerialDriver

Expand the archive, then run the installer by double clicking on the
FTDIUSBSerialDriver.pkg icon. hen the installation is co!plete, reboot the
co!puter.
hen the co!puter has rebooted, plug"in the device. I# the device is
installed properly, you $ill see entries in the %dev directory &"
%dev%cu.usbserial"xxxxxxxx
%dev%tty.usbserial"xxxxxxxx
$here xxxxxxxx is either the device's serial nu!ber or, #or unseriali(ed
devices, a location string that depends on $hich USB port your device is
connected to.
I# you run the application Syste!)re#erences and select *et$ork, you should
see the text +*e$ )ort Detected+ and +usbserial"xxxxxxx"port+, and you can
setup the para!eters #or an Internet connection.
Troubleshooting
,. The device does not appear in the %dev directory or the text +*e$ )ort
Detected+ is not displayed in Syste!)re#erences"*et$ork.
FTDIUSBSerialDriver does not support your deviceID -.ID and )ID/. Disable
the EE)012 so that the device reverts to its de#ault deviceID, then replug.
To get support #or your deviceID built into FTDIUSBSerialDriver, contact FTDI
3uoting your deviceID and a description o# your device.
4. The device cannot be accessed a#ter the co!puter has rebooted.
FTDI0eEnu!erate is not setup correctly #or your deviceID. The background
to this proble! is that FTDIUSBSerialDriver has a dependency on
co!.apple.iokit.I1SerialFa!ily. This is an 5pple driver and it is not a 0oot
driver. This !eans that at +root+ -boot/ ti!e, the driver's dependencies
cannot be satis6ed, and the driver does not participate in the extension
loading process.
5pple's position on this proble! is as #ollo$s &"
+5pple $ill not -#or the #oreseeable #uture/ be able to provide a root
version o# co!.apple.iokit.I1SerialFa!ily. It depends on other co!ponents
that are not available at boot ti!e.+
7o$ever, there is a $orkaround. 5 script that #orces the device to re"
enu!erate is installed in the startup ite!s #older so that it runs every ti!e
the syste! is booted. The script is called FTDI0eEnu!erate, and it supports
FTDI's deviceID by de#ault, but it can be changed to support any other
deviceID.
8og in as root, then go to the directory at
%8ibrary%StartupIte!s%FTDI0eEnu!erate and edit FTDI0eEnu!erate. 2ove to
the line containing the text &"
%8ibrary%StartupIte!s%FTDI0eEnu!erate%0eEnu!erate "v9:9; "p<99,
"v introduces : hexadeci!al digits that represent the vendorID -.ID/ and
"p introduces : hexadeci!al digits that represent the productID -)ID/.
0eplace 9:9; $ith your device's .ID, and replace <99, $ith your device's
)ID. For exa!ple,
%8ibrary%StartupIte!s%FTDI0eEnu!erate%0eEnu!erate "v,4;: "pFED=
Save FTDI0eEnu!erate.
;. 1nly one device can be accessed a#ter the co!puter has rebooted.
I# you have di>erent devices using FTDIUSBSerialDriver, then
FTDI0eEnu!erate is not setup correctly #or your deviceIDs. The background
to this proble! is discussed in 4, and the solution is to edit FTDI0eEnu!erate
so that it supports all devices.
8og in as root, then go to the directory at
%8ibrary%StartupIte!s%FTDI0eEnu!erate and edit FTDI0eEnu!erate. 5dd a
line o# the #ollo$ing #or!at #or every deviceID that has to be supported &"
%8ibrary%StartupIte!s%FTDI0eEnu!erate%0eEnu!erate "vhhhh "phhhh
"v introduces : hexadeci!al digits that represent the vendorID -.ID/ and
"p introduces : hexadeci!al digits that represent the productID -)ID/.
For exa!ple, to support three devices,
%8ibrary%StartupIte!s%FTDI0eEnu!erate%0eEnu!erate "v9:9; "p<99,
%8ibrary%StartupIte!s%FTDI0eEnu!erate%0eEnu!erate "v,4;: "pFED=
%8ibrary%StartupIte!s%FTDI0eEnu!erate%0eEnu!erate "v,4;: "pB5?@
Save FTDI0eEnu!erate.
:. Device cannot be accessed even although the deviceID is supported in
FTDIUSBSerialDriver.
5n o$nership or per!issions proble! is preventing the syste! #ro! !aking
the device accessible.
=heck that the driver is o$ned by root and $heel. The !ost co!!on
sy!pto! is the group #or FTDIUSBSerialDriver is not $heel. To change the
group, login as root and per#or! the #ollo$ing script.
cd %syste!%library%extensions
chgrp "0 $heel FTDIUSBSerialDriver.kext
0eboot #or the change to take e>ect.
Contact FTDI
http&%%$$$.#tdichip.co!
supportA#tdichip.co!