Mac OSX Yosemite no serial ports showing for Uno R3
I have a MacBook Pro running OS X Yosemite (10.10.3). I connected my Arduino UNO R3 to my computer for the first time after the Yosemite upgrade - it worked fine before this!
When I opened the Arduino IDE I selected Tools > Board > "Arduino UNO", but when I try to choose a Serial Port the only options are:
/dev/tty.Bluetooth-Incoming-Port /dev/cu.Bluetooth-Incoming-Port /dev/tty.Bluetooth-Modem /dev/cu.Bluetooth-Modem
I have followed several tutorials and threads on how to 'fix' this issue, all to no avail:
I've installed the latest version of the FTDI drivers (even though, from what I recall the UNO doesn't even need them): FTDIUSBSerialDriver_v2_3.dmg
Downgraded to a prev. version of the FTDI driver hoping that would clear it up: /Volumes/FTDIUSBSerialDriver_v2_2_18
I followed a tutorial of how to remove the existing Apple drivers and removed the kext files, etc...
Tried connecting arduino to both USB ports.
Tried various cables, including the one that a I used before the Yosemite upgrade.
Tried installing updated Silabs drivers: Arduino compatible's serial port not showing Mac OSX
Walked through the entire Arduino Mac OSX guide: http://www.arduino.cc/en/guide/macOSX
After looking into the system info of my Macbook Pro, I can see the USB Controller is Broadcom based, in case that helps. I searched for Broadcom USB drivers but got hits for Silabs one instead.
Under my Tools > Port menu.. I can see these options: clicking the Serial Ports option doesn't do anything.
ls -1 /dev/tty.*or
ls -l /dev/tty.usb*from terminal gives me:
The Board does NOT show up under system networking (as it has for others), so it's not recognized as an incorrect device.
I'm at a complete loss. The board powers up... but I cannot connect to it.
SIDE NOTE: This is a legit Uno R3, not a clone.
If it is a legitimate Uno, then all of the FTDI and SiLabs efforts are an irrelevant distraction at best. Ideally, test the board and cable on an another machine to make sure it has not been damaged in the meantime, and try a different USB port on the Mac (especially try connecting through a keyboard or hub if you tried directly, or directly if you had tried a hub). I believe if you look in system information you can get a listing of all USB devices, which would be good to include in your post.
That's what I was thinking - regarding the FTDI drivers - but those were the only solutions I could find claiming to 'solve' this issue. I have tried other USB ports on the Macbook and will fire up my Apple keyboard since it has a USB port and reply back. I did write in my post the USB devices recognized in terminal.
Moved the Apple USB Keyboard back to my iMac and tried to connect to Uno there.. selected Uno from the Board menu and still only shows bluetooth modems from the Serial Port menu.
After updating the Arduino app to 1.6.4 the Port menu now shows the same options as my Macbook (shown in the image in Orig. Post)
You really should look not just in the Arduino IDE but in system information or whatever they call it (get there from the about this mac, and advanced, etc) and see what USB devices it is seeing. And again, test the board on another machine to make sure it is still good.
1) I've checked for 'visible' USB devices in both the System Info screen and via the Terminal.. both show the same.. and only bluetooth are present (aside from keyboard and my external HDD). 2) I have now tried this on both my Mackbook Pro and my iMac .. neither of which 'see' the USB connection.
Post a complete list of the raw USB (not serial) devices (ie, VID/PID) the system (not IDE) sees connected.
I did. I copied the LS from Terminal as well as identified, through the system settings screen, that there are only the USB to Bluetooth, Keyboard and Internal Memory Card controller. I checked both the IDE and the System screen after: 1) changing cables, 2) adding an Apple USB keyboard and using it;s USB port, 3) trying the same sequence on my iMac (keyboard usb and main usb).. nothing. The board is not listed. Period.
@ChrisStratton If there is another way to do this, to get the info you're asking for.. please let me know. But at this point, I've looked/checked everywhere that I know how to.
Until you have demonstrated that the board still works on *some* system (at this point probably not a Mac) you will have to consider it to be damaged.
Well, looks like the board might very well be shot. I fired up my wifes Windows laptop, installed Arduino, etc.. attached power and USB to Uno and it doesn't show in either the Arduino app or File Explorer. Not sure what/how it happened as the board was stored in an air tight, dry, cool container within a static free bag - the one it shipped it. And, I'd already ran this sketch once to perfection... bummer. Any other thoughts or possibilities?
After reading this I just tried out some of my Arduino machines, which worked properly so far, and indeed after upgrading to Yosemite yesterday, now none of my machines and none of my cables are recognized. I suspect a driver incompatibility...
Just wanted to add that I was having this same issue and switching to a different USB cable worked for me. I did not even know there was such a thing as a power-only USB!
I come back to the first question. I think I have the same problem. Basically I tried to install FTDIUSBSerialDriver v2_3.dmg on OS X Yosemite 10.10.5 The installation succeed But if I am looking in the /System/Library/Extensions/ I can see no FTDIUSBSerialDriver.kext if I go ls /dev |grep usbserial no cu.usbserial-A9GBBDLL or tty.usbserial-A9GBBDLL Please help
This posted question has shown me the truth after a good 12 hours of absolute bupkis trying to get my V3 to show up in the serial ports. Thank you OP, for the release from hell.
This is the best solution and drivers I've found: https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver
Probably, you have Chinese Uno analog which works on CH340 USB-to-serial chip, so you need to install driver for it.
Steps to fix:
- Install the CH340 driver
- Run the command in Terminal:
sudo nvram boot-args="kext-dev-mode=1"(disable kext signing introduced in Mac OS X 10.9 Yosemite)
Also you're right according to Uno and FDTI:
Differences with other boards
The Uno differs from all preceding boards in that it does not use the FTDI USB-to-serial driver chip. Instead, it features the Atmega16U2 (Atmega8U2 up to version R2) programmed as a USB-to-serial converter.
On OSX 10.11.6, installing the driver and rebooting solved this for me. No need for step 2.
This worked on 10.9.4 without step 2. Now I expect my private SSH keys to be located on some chinese servers though :)
Unfortunately the driver causes a kernel panic as soon as I plug in the Arduino. I'm on macOS Sierra 10.12.2.
@Ronny-AndréBendiksen No I didn't get it working. I just moved the upload step to my Raspberry Pi. :P
OSX 10.12.4 gives the following error when trying "sudo nvram boot-args="kext-dev-mode=1" " => nvram: Error setting variable - 'boot-args': (iokit/common) general error
If you're on Sierra, use this patched version of the driver. Worked like a charm: https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver
When I run `nvram`, I get an error: **nvram: Error setting variable - 'boot-args': (iokit/common) general error**
@IgorGanapolsky - Starting with macOS Sierra, you must be booted to the recovery partition to run the nvram command.
This solution didn't fix the problem for me. However, since it seems to work for some people, the new v1.4 version of the driver that supposedly works for High Sierra is here. : https://drive.google.com/file/d/1lUYkw-mCOekJjY1MVA5YuEbERHNWNCZW/view?usp=sharing
I was able to get a new `/dev/cu.wchusbserial1410` to show up by following the instructions from https://github.com/adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver , didn't need nvram. Thanks for the link
I get the following after installing the driver from github.com/adrianmihalko and executing the `sudo kextload /Library/Extensions/usbserial.kext` step. Then I get this: `/Library/Extensions/usbserial.kext failed to load - (libkern/kext) system policy prevents loading; check the system/kernel logs for errors or try kextutil(8).`
The cable that shipped with my Arduino Uno worked for power but not data transmission so the /dev/tty.usbmodem was not showing up in the Tools --> Port menu. After I switched to a different cable, the /dev/tty.usbmodem port showed up and it worked beautifully.
The same thing happened to me. I was trying to connect my Arduino with a power-only cable. Once I switched USB cables, the USB device appeared.
This site fixed the problem for me:
...somebody else has made an alternative to the ftdi drivers, and this website show you how to install them correctly.
This fixed the problem for me:
... and the direct link to download.
EDIT: I have one of the cheap clones with a CH340 USB chip. So this might not solve your problem, but could be beneficial to others.
The question however, is quite specific about which board is involved, and it is quite specifically one which *does not* have a ch340. The poster is answering a different question than the one which was asked.
Good point. I edited my answer with a clarification. I wanted to post it anyway though, because I spent a lot of time googling for a solution to my problem and stumbled onto this thread among the rest. Maybe it'll help others.
This is the answer I was looking for, unaware that my cheap clone had a different chip from the genuine Arduino.
Yosemite 10.9 (and OS X 10.10 and newer) requires a signed USB driver kext (kernel extension). You can find one on the FTDI web site here: http://www.ftdichip.com/Drivers/VCP.htm
Use version 2.3 for 64-bit OS X 10.9 or later. Install and reboot.
Plug in your Arduino, and the Terminal command:
/usr/sbin/kextstat | grep FTDI
will tell you if the FTDI VCP driver actually loaded.
Also a /dev/tty.usbserial-xxxxxxxx entry should appear in your /dev directory.
If not, the Mac USB port isn't talking to your Arduino. So it's no use trying the Arduino IDE application.
Also make sure your USB cable isn't for power only, but fully connected.
This exact same thing happen to me on my mac running the same operating system. I had to restart this system a few times to get it to work. I restarted it with the arduino plugged in; and that worked rather than my previous attempts when i rebooted then plugged in.
I have an osepp r3, seemingly an accurate clone. Computer is Mac os10.10.5.
A lot of sites claimed that the mac osx.* does not require FTDI drivers, but.....
After an awkward, google searching beginning, where the board only accepted a new sketch after being physically unplugged and replugged, I downloaded the latest FTDI driver, installed, and RESTARTED the mac. Now, joy and peace reigns. No side-effects with other mac functions, thankfully. Hope this helps.