Table of Contents
OpenDCC & BiDiB
Linux
Linux maps the OpenDCC USB out of the box:
lsusb
Bus 003 Device 005: ID 0403:bfd8 Future Technology Devices International, Ltd Bus 002 Device 007: ID 0403:bfdd Future Technology Devices International, Ltd
Messages
Mar 19 10:10:04 rocbuntu kernel: [ 1172.952065] usb 3-2: new full speed USB device using uhci_hcd and address 6 Mar 19 10:10:04 rocbuntu kernel: [ 1173.149326] usb 3-2: configuration #1 chosen from 1 choice Mar 19 10:10:04 rocbuntu kernel: [ 1173.160195] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected Mar 19 10:10:04 rocbuntu kernel: [ 1173.160234] usb 3-2: Detected FT232RL Mar 19 10:10:04 rocbuntu kernel: [ 1173.160237] usb 3-2: Number of endpoints 2 Mar 19 10:10:04 rocbuntu kernel: [ 1173.160240] usb 3-2: Endpoint 1 MaxPacketSize 64 Mar 19 10:10:04 rocbuntu kernel: [ 1173.160243] usb 3-2: Endpoint 2 MaxPacketSize 64 Mar 19 10:10:04 rocbuntu kernel: [ 1173.160245] usb 3-2: Setting MaxPacketSize 64 Mar 19 10:10:04 rocbuntu kernel: [ 1173.163969] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
Mac OS X
Install the device driver
Info.plist
Add following section as super user into the file:
sudo vi /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist
bellow the following key and dict:
<key>IOKitPersonalities</key> <dict>
Z1
<key>USB-IF OpenDCC Z1</key> <dict> <key>CFBundleIdentifier</key> <string>com.FTDI.driver.FTDIUSBSerialDriver</string> <key>IOClass</key> <string>FTDIUSBSerialDriver</string> <key>IOProviderClass</key> <string>IOUSBInterface</string> <key>bConfigurationValue</key> <integer>1</integer> <key>bInterfaceNumber</key> <integer>0</integer> <key>idProduct</key> <integer>49112</integer> <key>idVendor</key> <integer>1027</integer> </dict>
GBMBoost Master
<key>USB-IF BiDiB GBMBoost Master</key> <dict> <key>CFBundleIdentifier</key> <string>com.FTDI.driver.FTDIUSBSerialDriver</string> <key>IOClass</key> <string>FTDIUSBSerialDriver</string> <key>IOProviderClass</key> <string>IOUSBInterface</string> <key>bConfigurationValue</key> <integer>1</integer> <key>bInterfaceNumber</key> <integer>0</integer> <key>idProduct</key> <integer>49117</integer> <key>idVendor</key> <integer>1027</integer> </dict>
Reload kernel extension:
sudo kextload /System/Library/Extensions/FTDIUSBSerialDriver.kext
The device(s):
ls /dev/tty.* /dev/tty.usbserial-FTT1Y40V /dev/tty.usbserial-A9WNTKDT
Auto load
Start in Safe Mode
The first thing to try is to boot into Safe Mode, which will clear the dynamic loader shared cache and potentially clear pauses at the blue screen before the system either logs in or presents the log-in window. Booting to Safe Mode just requires holding the Shift key immediately after hearing the boot chimes when starting or restarting your computer.
After this is done, the system will present the log-in window (regardless of whether you have automatic log-in enabled), and since there is no need to log in, you can immediately restart the system.
Rebuild kernel extension caches
Use only if you are familiar with system administration tasks. |
Though you can use a number of maintenance utilities to clear and rebuild the kernel extensions caches, another approach is to run these commands manually in the Terminal. Doing so ensures you know exactly what commands are being run, and also allows you to customize them if needed.
First ensure the system root is owned by "root" and that the group is set to "admin" by running the following command in the Terminal:
sudo chown root:admin
After this is done, update the prelinked kernel for the system, which will ensure that all previously used kernel extensions are quickly loaded at boot. This will grab any new kernel extensions used for added system hardware and include them when prelinking the kernel.
sudo kextcache -system-prelinked-kernel
After this command is done, rebuild the cache for the kernel extensions by running the following command:
sudo kextcache -system-caches