1

I'm exchanging data between a bare-bone Arduino and openFrameworks via a serial UART FTDI connection. I'm using a patched FTDI driver to achieve higher BAUD rates on OSX. FTDIChip calls it "Aliasing VCP Baud Rates".

See:

This worked until recently. Since upgrading to OSX 10.10 I have to manually unload and reload the kext to make it work:

sudo kextload -b com.FTDI.driver.FTDIUSBSerialDriver
sudo kextunload -b com.FTDI.driver.FTDIUSBSerialDriver

kextstat tells me that the kext is loaded. It just doesn't function correctly until I reload it. Has anyone had similar issues with kext-loading? Has anyone any idea what the problem could be?

Thanks! Armin

armin
  • 2,047
  • 3
  • 17
  • 19

1 Answers1

0

It would depend on the specifics of the kext in question, but generally speaking, it probably depends on a subsystem that isn't up yet by the time it gets matched to the hardware. For example, the BSD subsystem might be required to present the device file for the serial port, but the kext gets loaded before then; if that's the case, you can instruct the system to only create an instance of your driver once BSD is up using a IOResourceMatch property of IOBSD in your personality's dictionary in the Info.plist. (don't forget to re-codesign the kext after modifying the Info.plist)

pmdj
  • 22,018
  • 3
  • 52
  • 103