How to Install FTDI Drivers; How to Install FTDI Drivers. You may need to visit FTDI’s VCP Drivers page for the latest download of the Mac OS X FTDI Driver. Ftdi Driver Install Windows 7 However, if there was a problem with the installation and you don’t see any options that include ‘usbserial’ under the ‘Tools -> Serial Port’ menu, then you will need to install In preveious version of OS X, the defualt was set to Anywhere.
Just got the Propeller Activity board and want to use the SimpleIDE on my Macbook w/ OSX 10.75. I have never installed USB drivers before on a MAC. I downloaded and installed the FTDIUSBSerialDriver_10_4_10_5_10_6.pkg, I assume it will work on 10.75. I also downloaded the D2xx driver but I am not having any luck installing it. Terminal commands are giving problems. Any advice or help with installation of the drivers would be appreciated. The SimpleIDE installed without problems.
Thanks Mikes I'm running Mac OS X 10.8.4 (It uses the same driver as for 10.7 versions of the OS). Are you downloading the 'FTDIUSBSerialDriver_v2_2_18' (note the version: 2.2.18) from the following URL? That one is definitely meant for 10.3 - 10.7.
It contains 'FTDIUSBSerialDriver_10_4_10_5_10_6_10_7.mpkg', which is the proper package to install. You mention using Terminal commands, but I'm not sure why. You should NOT need to do anything more than the following, unless you need to remove a non-functioning older driver: Note: If you had already installed an earlier version of the driver, it may cause problems. You'll find it located at the following path on your hard drive: '/System/Library/Extensions/FTDIUSBSerialDriver.kext'. Move it to the Trash. You can do this simply with a 'Control-click' on its file/icon in the Finder, which provides a menu that includes 'Move to Trash'.
This will require authorization of a known admin user ID and password, of course. Once you have removed the older driver the following should allow installation of the new driver: 1. Download the 2.2.18 VCP driver from: 2. In your Downloads folder, you should see a file named something like: 'FTDIUSBSerialDriver_v2_2_18.dmg'.
You have been successfully subscribed to the Notification List for this product and will therefore receive an e-mail from us when it is back in stock! For security reasons, an e-mail has been sent to you acknowledging your subscription. Please remember that this subscription will not result in you receiving any e-mail from us about anything other than the restocking of this item. If, for any reason, you would like to unsubscribe from the Notification List for this product you will find details of how to do so in the e-mail that has just been sent to you!
There are several options for connecting to an FTDI device from a Mac, depending on OS version and driver choice. Some of the techniques have been covered in other stackoverflow questions. One technique has not yet been covered (as far as I can tell), so I'm hoping someone can help with this last technique. The current options for connecting are as follows: • (pre-Mavericks only) Include the.dylib and header files from the FTDI driver directly in your Xcode project (no driver installation needed), as described in. This technique breaks under OSX Mavericks and later. • (Mavericks & later) Use the pre-installed. It's poorly documented, and seems a lot harder to use than the.
This technique won't work if you wish to support pre-Mavericks operating systems. • (Mavericks & later), and then use technique #1, above. Not a good option if you plan on distributing your app to non-tech-savvy customers. Also, it's not a permanent solution for Mavericks+ as the kext will have a tendency to re-appear.
• (Any mac version) Implement a codeless kext, that will have a higher match priority than the Apple's kext, thus, preventing Apple's driver from hijacking the connection to your device. Then use technique #1, above. This is one of the techniques suggested by and by the comments in. It's meant to be used for apps that use a custom connection solution, but it also works for those who just want to include FTDI's dylib and headers directly in their projects. • (Any mac version) Install the original (as opposed to simply referencing the.dylib and headers in your project).
This is, obviously, harder than technique #1, especially when it comes to building an installer for your app, but it has the benefit of working on any Mac version. Also, like #4, it is a technique supported.
Techniques 1-4 have been covered in other Stackoverflow questions (as noted inline). I'm trying to figure out how to do #5. According to the ReadMe that comes with the, 'installing' simply means plopping the.dylib in the /usr/local/lib/ directory and the.h files in the /usr/local/lib/ directory. I've been able to get this technique to work, but ONLY if I also unload Apple's kext. However, according to Apple's documentation, I shouldn't need to unload Apple's kext when using this technique. From: 'the Apple driver intentionally sets a lesser probe score match to ensure that the FTDI Interface driver matches, when present' So, apparently, 'install the FTDI driver' means something different to Apple than it means to FTDI. Does anyone know how to 'install the FTDI driver' in the way that Apple's documentation intends, such that it will have a 'higher probe score match' than Apple's kext and, thus, will not require me to unload Apple's kext?