Feb 12, 2018 Hi Guys I'll become crazy with the same issues on my mac os x sierra. I've install the FTDI chip USB drivers but I can't connect my Prusa i3 with my mac.
Answer from codebender itself here: Unistall FTDI drivers In order to uninstall the FTDI drivers follow the steps below: Open a terminal and type: cd /System/Library/Extensions/ Verify that the.kext file is present: ls grep FTDIUSBSerialDriver.kext Output should be: FTDIUSBSerialDriver.kext Then type: sudo rm -R FTDIUSBSerialDriver.kext Verify that the.kext file has been removed: ls grep FTDIUSBSerialDriver.kext Output should be empty. After you should remove the files stored in receipts folder: cd /private/var/db/receipts/ Find the enties: ls grep FTDI Output should be: com.FTDI.ftdiusbserialdriverinstaller.FTDIUSBSerialDriver-2.pkg.bom com.FTDI.ftdiusbserialdriverinstaller.FTDIUSBSerialDriver-2.pkg.plist com.FTDI.ftdiusbserialdriverinstaller.postflight.pkg.bom com.FTDI.ftdiusbserialdriverinstaller.postflight.pkg.plist com.FTDI.ftdiusbserialdriverinstaller.preflight.pkg.bom com.FTDI.ftdiusbserialdriverinstaller.preflight.pkg.plist Remove each one of the files of the above list: sudo rm -rfilename. Shouldn't you be using pkgutil to forget installations? Depending on when the installation was made it might only show up in the database. I've got three related installation packages: com.FTDI.ftdiusbserialdriverinstaller.FTDIUSBSerialDriver-2.pkg, com.FTDI.ftdiusbserialdriverinstaller.postflight.pkg, com.FTDI.ftdiusbserialdriverinstaller.preflight.pkg (pkgutil -packages grep serial). None of them show up in /Library/Receipts. Pkgutil will allow you to 'forget' them, see the man page.
Use kextstat to determine if loaded, kextunload to unload if the driver is. – Jan 11 '15 at 19:36.
![Ftdi Driver For Mac Sierra Ftdi Driver For Mac Sierra](/uploads/1/2/5/4/125488170/631926376.png)
Thanks for your suggestion, I found what was the issue. I am using macOS Sierra 10.12.2. I had all the drivers installed correctly. But the VCP(Virtual Com Port) was blocked by my recent installation of D2xxHelper.
Thanks to documentation, I found how to disable D2xxHelper so that the VCP was no longer blocked. Here is the part of the document that resolved my problem: On OS X 10.11 or later, another possibility is that VCP has been blocked by installation of D2xxHelper bundled with an application. VCP and such an application are mutually exclusive. To force using VCP disable D2xxHelper: cd /Library/Extensions sudo mv D2xxHelper.kext D2xxHelper.disabled Then reboot. To force using D2xx again, rename D2xxHelper.disabled back to D2xxHelper.kext and reboot.
![Usb Usb](/uploads/1/2/5/4/125488170/445419196.jpg)
After reboot, I plugged in my board and the serial showed up in /dev/tty.usb. It is now couple of times that I am running into this problem. I was working just fine with the board (e.g I was able to program and debug the board), until this afternoon. Now when ever I try to program my board, I am getting the following error: Error: libusbclaiminterface failed with LIBUSBERRORACCESS. Error: unable to open ftdi device with vid 0403, pid 6010, description 'Dual RS232-HS', serial '.' at bus location '.'
But at the same time, in another terminal window, I am able to see print outs of my previous program being running on the board (I can see tty.usbserial-00001014B). The following is my ftdi setup: Hossein@/MyRepos/freedom-e-sdk -kextstat grep -i ftdi 152 0 0xffffff7f8330e000 0x7000 0x7000 com.FTDI.driver.FTDIUSBSerialDriver (2.3) ECC3AF36-431D-370D 86F2-5237785E9CF8 The interesting thing is that when I unload the FTDI driver and load apple driver using the following command: sudo kextutil -b com.apple.driver.AppleUSBFTDI -p AppleUSBEFTDI-6010-1 I will be able to program the board but the serial port doesn’t show up in the /dev/tty. So, I am kind of lost. This happened couple times before, but I managed to get it working by unload and loading the FTDI driver. But now, nothing works I have to mention that by default, I have setup FTDI driver to be picked up by osx and after a restart, the FTDI driver infact shows up. Also I am using openocd from homebrew.