FTDI based debug adapters do not show up correctly in the XMOS tools by default on OSX 10.9.
How do I enable XMOS boards with FTDI debug adapters on OSX Topic is solved
-
XMatt
- XCore Addict
- Posts: 147
- Joined: Tue Feb 23, 2010 6:55 pm
-
XMatt
- XCore Addict
- Posts: 147
- Joined: Tue Feb 23, 2010 6:55 pm
In order to allow FTDI based debug adapters to be visible on OSX the following instructions need to be followed.
These instructions have been taken from the following FTDI installation guide and verified to work on OSX 10.9 with release 13.0.0.
http://www.ftdichip.com/Support/Documen ... AC_OSX.pdf
7 OS X 10.9 (Mavericks)
7.1 Using VCP or D2XX with OSX 10.9
The VCP driver is provided as part of the kernel in OSX 10.9, therefore no driver installation is required to
create a virtual COM port in Mavericks. If D2XX operation is desired, then the built-in VCP driver must be
disabled before the D2XX driver can be used. To do this, the relevant kext file needs to be renamed by
following the procedure below:
Start a terminal session (Go > Applications > Utilities > Terminal) and copy/paste the following text to
the command prompt:
cd /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins
sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
sudo touch /System/Library/Extensions
As an alternative, the kextunload command can be used instead of copying the kext directory:
sudo kextunload –b com.apple.driver.AppleUSBFTDI
The kextunload and kextunload commands can be run in any directory.
Reboot the system once the above commands have been executed.
Now proceed as before with the instructions as per section 3.2 to symbolically link your dll.
To re-enable VCP, rename AppleUSBFTDI.disabled back to AppleUSBFTDI.kext
cd /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins
sudo mv AppleUSBFTDI.disabled AppleUSBFTDI.kext
sudo touch /System/Library/Extensions
If the driver was disabled via the kextunload command, use kextload as follows:
sudo kextload –b com.apple.driver.AppleUSBFTDI
NOTE: If your VCP devices and D2xx devices have mutually exclusive VID/PID then both VCP and D2xx
can be active at the same time.
These instructions have been taken from the following FTDI installation guide and verified to work on OSX 10.9 with release 13.0.0.
http://www.ftdichip.com/Support/Documen ... AC_OSX.pdf
7 OS X 10.9 (Mavericks)
7.1 Using VCP or D2XX with OSX 10.9
The VCP driver is provided as part of the kernel in OSX 10.9, therefore no driver installation is required to
create a virtual COM port in Mavericks. If D2XX operation is desired, then the built-in VCP driver must be
disabled before the D2XX driver can be used. To do this, the relevant kext file needs to be renamed by
following the procedure below:
Start a terminal session (Go > Applications > Utilities > Terminal) and copy/paste the following text to
the command prompt:
cd /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins
sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
sudo touch /System/Library/Extensions
As an alternative, the kextunload command can be used instead of copying the kext directory:
sudo kextunload –b com.apple.driver.AppleUSBFTDI
The kextunload and kextunload commands can be run in any directory.
Reboot the system once the above commands have been executed.
Now proceed as before with the instructions as per section 3.2 to symbolically link your dll.
To re-enable VCP, rename AppleUSBFTDI.disabled back to AppleUSBFTDI.kext
cd /System/Library/Extensions/IOUSBFamily.kext/Contents/Plugins
sudo mv AppleUSBFTDI.disabled AppleUSBFTDI.kext
sudo touch /System/Library/Extensions
If the driver was disabled via the kextunload command, use kextload as follows:
sudo kextload –b com.apple.driver.AppleUSBFTDI
NOTE: If your VCP devices and D2xx devices have mutually exclusive VID/PID then both VCP and D2xx
can be active at the same time.