Thank You for Helping us Maintain CNET's Great Community, !
Ftdi Drivers For Windows 7
FTDI USB Driver for Mac OS X. There are different drivers depending on the version of OS X you are using; make sure to select the correct one. These drivers are required for any Board of Education USB, Propeller development board, or other USB-based Parallax hardware. The USB interface uses an FTDI chip. The generic driver for that can be downloaded from their Virtual Com Drivers. The default driver does not know the product ID. There is a different driver version for Mac 10.3-10.8 and Mac OS 10.9 and above. Make sure you select the proper one for your OS. When working with most of our FTDI products you are going to be using the FTDI as a “Virtual Com Port” or VCP.
General | |
|---|---|
| Publisher | FTDI |
| Publisher web site | http://www.ftdichip.com/index.html |
| Release Date | February 04, 2004 |
| Date Added | February 04, 2004 |
| Version | 1.0.2151.0 |
Category | |
|---|---|
| Category | Drivers |
| Subcategory | USB Drivers |
Operating Systems | |
|---|---|
| Operating Systems | Windows 98/NT/2000/XP |
| Additional Requirements | |
Download Information | |
|---|---|
| File Size | Not Available |
| File Name | External File |
Popularity | |
|---|---|
| Total Downloads | 3,948 |
| Downloads Last Week | 5 |
Pricing | |
|---|---|
| License Model | Free |
| Limitations | Not available |
| Price | Free |
I am trying to work with a custom PCB that uses an FTDI FT232RL to talk to my computer (MacBookPro running OSX 10.11 El Capitan) for a hardware project. I am using Matlab to send serial commands, running into some problems there with ClearToSend (CTS) pin apparently 'high' (off), but that's another story.
However my problem right now is that my Mac won't 'release' (not sure what else to call this) the device after I unplug it. I can unplug the device and put it on another USB bus, but I can really only do this once, because the same thing happens again if I unplug -- this makes my development difficult, because the only way I've found to fix this is to restart the whole computer. How can I release/reset/clear these devices?
If I open System Information>Hardware>USB, I can essentially see the same device listed twice on the device tree.
Ftdi Led Driver
This makes it so that when I try ls /dev/tty.* (in either Matlab or Terminal) the device is not listed, it's essentially blocked, even though it's plugged in and shows up twice on the device tree. What should I do?
I have installed the version 2.3 FTDI driver, and it seems to work otherwise. Please let me know what other information I can provide to get to the bottom of this. Thanks
4 Answers
I had the same issue, albeit on Sierra, talking to an Arduino Nano clone (which also uses a FTDI FT232RL bridge).
What seems to have worked for me is actually removing the FTDI driver (/Library/Extensions/FTDIUSBSerialDriver.kext), after finding that Apple ships an FTDI driver with the OS itself (/System/Library/Extensions/AppleUSBFTDI.kext).
I think having both drivers active at the same time causes a conflict, which ties up the USB port.
PROBLEM: FTDI devices not usable in MacOS High Sierra. In my own case, I was having trouble connecting FT232R chip devices to my 2016 Macbook Pro with C-Ports. The devices appeared in my USB device tree (System Information -> Hardware -> USB), but did not show up as a serial device using Arduino, or Coolterm. - NOTE: they did not appear either when in Terminal with the command (ls /dev/cu*) or (ls /dev/tty*)
SOLUTION:
3) Download the 2.4.2 drivers from FTDI's website http://www.ftdichip.com/Drivers/VCP.htm and install. The install will succeed, BUT due to Apples built-in FTDI drivers they will not work.
2) Reboot computer and enter recovery mode Via powering down and holding down CMD + R on reboot.
3) In recovery mode open terminal from utilities at the top of the screen and type the following to tempraily disable System Integrity Protection:
csrutil disable
The computer will prompt you to reboot to make changes take effect.
4) On reboot we now need to disable the Apple FTDI drivers (NOTE: this can be reversed at any time so do not worry). - open Terminal and type the following.
sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled
sudo touch /System/Library/Extensions
chgrp -R wheel FTDIUSBSerialDriver.kext
Ftdi Driver Download Exe
sudo mv D2zzHelper.kext D2xxHelper.disabled
Ftdi Driver For Mac
Now you will have successfuly have disabled Apple's built-in FTDI drivers and replaced them with FTDI v2.4.
5) Restart your computer in recovery mode. Shutdown, hold Command + R and open terminal in the Utilities tab. Enter the following to reenable Apple's System Integrity Protection
csrutil enable
**NOTE: I have tested this on a 2016 Macbook Pro with MacOS 10.13.3 on the following devices/apps: 1) Screen from within terminal, CoolTerm, Bus Pirate V3.6, JTAGulator, Arduino Uno, Adafruit Mega AT, Arduino Mega clone.
I'd like to provide an additional answer that solves one more piece of the puzzle that I had. Even following Garrett Johnson's excellent answer above, my FTDI driver was still not working. It turned out that - and I know this sounds insane - that my System Preferences 'Security & Privacy' tab was not accepting my trackpad's click on the 'Allow' button that would allow the driver to load. I got down this path after seeing this message in install log:
Of course, I clicked 'Allow' in there, but nothing seemed to happen. The button registered the click, but I didn't have any window pop up or anything else for some form of confirmation. Searching around the Internets, I discovered this lengthy thread on Karabiner's github page discussing several solutions for forcing System Preferences to permit the mouse click:
Install Ftdi Driver
Apparently I had some software running that was intercepting the trackpad activity. It wasn't chrome in my case, unlike several people on that list. I have no clue what it was, which is a little concerning. The solution that worked for me was to enable Mouse Keys, then push 'I' to click the mouse over the 'Allow' button. At that point, a window popped up, and I was able to permit the FTDI driver to load.
Vag Com Ftdi Driver For Mac
I'm still shaking my head!
I had the same problem. I had installed the FTDI drivers via a link from the Creality Ender 3 installation notes, and the link installed version 2.2.18, which is for OS X 10.8 and below. (I'm running Sierra, 10.12). The driver worked, but would not release. I deleted the driver using sudo rm /System/Library/Extensions/FTDIUSBSerialDriver.kext/ and then downloaded and installed version 2.4.2. All working now.
protected by Community♦Aug 17 at 7:58
Ftdi Driver Linux
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?