/dev/tty.Serial* Missing in MacOS 10.9 (Mavericks)

13,255

I have been able to get my FTDI Serial Cable to work by reinstalling the driver and rebooting the computer. This has not seemed to work for all cables, but at least it worked for one with an FTDI chip...

This TTL-232R-5V-AJ cable gave me the following messages in /var/log/system.log

Oct 29 18:22:27 doc com.apple.kextd[12]: kext com.FTDI.driver.FTDIUSBSerialDriver  202189000 is in exception list, allowing to load
Oct 29 18:22:27 doc kernel[0]: FTDIUSBSerialDriver:        0  4036001 start - ok

And:

crw-rw-rw- 1 root wheel 19, 12 Oct 29 18:22 /dev/tty.usbserial-FTWWVW3A
Share:
13,255
Yuri Green
Author by

Yuri Green

By day: San Francisco Bay Area native super-nerd fostering the inevitable obsoletion of our species via personally advancing computing scope and ability. By night: ^ -"As the sands of hesitation bleach the bones of countless millions, when on the dawn of victory laid down to rest. And resting, died."

Updated on July 26, 2022

Comments

  • Yuri Green
    Yuri Green almost 2 years

    I'm not sure if this was as a result of a recent update to OSX 10.9, but for some reason, all the /dev/tty.Serial* and /dev/cu.Serial* targets are now missing, making serial communication with a connected USB device impossible, programatically.

    I can see the USB device connecting in the "System Information" screens, and the device will connect appropriately with an installed instance of Windows running in a VMWare Fusion VM, but for the life of me, OSX will not give me a I/O-able target in /dev for the USB device. Did Apple move where the old /dev/tty.Serial* devices now hook into the system, or is this in fact just broken. I'm dead in the water until I can figure this out.

  • Yuri Green
    Yuri Green over 10 years
    My problem is either over time, or as a result of system update, I've lost ALL targets in /dev that look like "/dev/tty.usbserial-". What happened to them? I clearly still have serial ports, but now how are we supposed to interface to them or do any I/O with them? All thats left are the /dev/tty.Bluetooth-, which is clearly not the target we're interested in...