47

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: enter image description here clicking the Serial Ports option doesn't do anything.

Running ls -1 /dev/tty.* or ls -l /dev/tty.usb* from terminal gives me:

/dev/tty.Bluetooth-Incoming-Port
/dev/tty.Bluetooth-Modem

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.

revive
  • 571
  • 1
  • 4
  • 3

11 Answers11

44

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:

  1. Install the CH340 driver
  2. Run the command in Terminal: sudo nvram boot-args="kext-dev-mode=1" (disable kext signing introduced in Mac OS X 10.9 Yosemite)
  3. Reboot

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.

Tensho
  • 541
  • 4
  • 3
15

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.

cnanders
  • 151
  • 3
6

This fixed the problem for me:

http://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/

... 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.

Stefano Masini
  • 169
  • 1
  • 2
5

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.

hotpaw2
  • 287
  • 4
  • 11
5

This site fixed the problem for me:

http://kiguino.moos.io/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html

...somebody else has made an alternative to the ftdi drivers, and this website show you how to install them correctly.

Gary
  • 59
  • 1
  • 1
4

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.

1

Check this video https://www.youtube.com/watch?v=0zuRukW7o0A

  • Reboot and press CMD+R immediately after reboot to enter in Recovery Mode
  • Open Terminal from Recovery mode
  • Run the command csrutil enable --without kext
  • Reboot
  • Install driver
Vitalij
  • 21
  • 2
1

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.

dpickell
  • 11
  • 1
0

Stumbled across this. It worked for Mac OS X Yosemite 10.10.5

install the CH340 driver Run the command in Terminal: sudo nvram boot-args="kext-dev-mode=1" Reboot

However, I installed: MAC system:www.wch.cn/downfile/178

so YMMV

a user here: http://forum.makeblock.cc/t/mac-os-x-yosemite-arduino-1-0-6-doesnt-recognize-makeblock-orion/728

found the solution, there: http://forum.arduino.cc/index.php?topic=261375.15

so kudos - to all that sweated out the driver, uninstall, install, and activation...

Ted

0

In my case, there was some kind of incompatibility with the ESP8266 connected to the Nano board. As soon as I removed it the Serial Port appeared again.

Tomas
  • 11
0

First, check the USB cable - I had the same problem. If you have checked it, try the HoodLoader2:

I am using it and it works with Arduino Leonardo.