The following sentence may need some modification for Mac OS X 10.9 users. "If you use an FTDI-based adapter and have the FTDI kext installed, you will need to unload it prior to using OpenOCD: sudo kextunload FTDIUSBSerialDriver.kext"
Ref: Technical Note TN2315 Introducing the Apple AppleUSBFTDI kernel driver https://developer.apple.com/library/mac/technotes/tn2315/_index.html So the kernel kext can come from FTDI or Apple (10.9 or later). Maybe the following changes are good to have. "If you use an FTDI-based adapter and have the FTDI or Apple kext installed, you will need to unload the kext prior to using OpenOCD: For FTDI kext sudo kextunload FTDIUSBSerialDriver.kext For Apple kext ( Mac OS X 10.9 or later) sudo kextunload -b com.apple.driver.AppleUSBFTDI" A codeless kext may not be as easy as before under Mac OS X 10.9. Please refer to the above mentioned Apple Technical Note. " Under OS X Mavericks, the official location for third party Extension files, is in/Library/Extensions/. OS X Mavericks requires that the kext be signed using a special Developer ID. See the readme file for instructions on requesting this special Developer ID." This is a problem for libusb and libusb based application when there is already an Apple provided kernel driver. -- Xiaofan ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
