CHIRP

h1. RTSystemsCablesAndMavericks

RTSystems usb cables are a branded (i.e., customized) FTDI cable. They simply have different USB Vendor (VID) and Product IDs (PID) from generic FTDI USB adapters.

Apple OSX 10.9.x aka Mavericks now has a built in FTDI Driver, com.apple.driver.AppleUSBFTDI.
However, it does not load by default because it does not recognized the custom VID/PID combos that RTSystems cables use.

Many folks have been simply loading the FTDI OEM driver (

h2. Steps

stop using and unplug all FTDI usb adapters

unload existing FTDI OEM driver (if applicable):
@
sudo kextunload -b com.FTDI.driver.FTDIUSBSerialDriver
@

Disable FTDI OEM driver (if applicable):
@
sudo mv -v /System/Library/Extensions/FTDIUSBSerialDriver.kext/ /System/Library/Extensions/FTDIUSBSerialDriver.kext_disabled
@

check to see that there are no FTDI drivers loaded:
@
kextstat |grep -i ftdi
@
(should not show anything)

Add RTSystems VID/PIDs to Apple FTDI driver:
@
sudo nano /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBFTDI.kext/Contents/Info.plist
@

add following to IOKitPersonalities section:
@ AppleUSBFTDI-RTSystems

CFBundleIdentifier
com.apple.driver.AppleUSBFTDI
IOClass
AppleUSBFTDI
IOProviderClass
IOUSBInterface
InputBuffers
8
OutputBuffers
16
bConfigurationValue
1
bInterfaceNumber
0
idProduct
0x9000
idProductMask
0x9000
idVendor
0x2100

@

plug in your rtsystems ftdi usb adapter

Force load of Apple FTDI driver:
@
sudo kextload -b com.apple.driver.AppleUSBFTDI
@

verify Apple FTDI driver is loaded:
@
hackpro:~ jens$ kextstat |grep -i ftdi
129 0 0xffffff7f826d0000 0x7000 0x7000 com.apple.driver.AppleUSBFTDI (1.0.1b3) <77 36 5 4 3>
hackpro:~ jens$
@

Verify Apple FTDI device node is created:
@
ls -l /dev/cu.usbserial-*
@

good result: should list a device file
bad result: "no such file or directory"

h3. Note

You may need to repeat these steps if Apple updates FTDI driver (such as in a Combo Update aka Minor update release)