Most of the time, when you install Arduino on Mac OS X, the drivers are installed automatically. However, if there was a problem with the installation and you don't see any options that include 'usbserial' under the 'Tools -> Serial Port' menu, then you will need to install the drivers. You may also need to install the full FTDI drivers if you are running OSX 10.10 or later. The factory drivers are not complete.
a.) OS X 10.9 (Mavericks) or above: Download this driver. Locate the file FTDIUSBSerialDriver_v2_4.2.dmg file that was downloaded to your computer, and double click on it to open \ run it.
b.) OS X 10.8 (Mountain Lion) or lower: Download this driver. Locate the file FTDIUSBSerialDriver_v2_2_18.dmg file that was downloaded to your computer, and double click on it to open \ run it.
If you are using the driver for OS X 10.8 (Mountain Lion) or older, you will see two files. Open up the driver file that corresponds with your operating system. For most users, it will be the second file:
On newer versions of OS X, when you double-click the install packages inside the FTDI disk image, you may be presented with a very Windows-esque type error about not being able to open the files because they are not from an identified developers. This is very similar to the unsigned driver issue in Windows 8.
With Mac OS 10.9 (Mavericks) and later, Apple has built their own version of the FTDI VCP driver into the operating system (AN134). However, there seems to be some conflict between drivers from FTDIchip.com and the ones inherent to Apple. Luckily, there is a solution to this problem, and it comes from FTDI directly.
If you are trying to use the FTDI VCP Driver in your applications, it will not work due to a conflict between the VCP and D2XX drivers. In order to get around this, the Apple supplied Driver must be uninstalled. Plug in the FTDI device in question, and type the following command in a Terminal window:
When I upgraded to Mojave, allofasudden I could not see the serial port of my Nano ... it wasn't showing up in /dev at all. So I did the usual ... downloaded the latest CH340 drivers, then removed the .kext files from /Library etc. and re-installed the drivers and still it would not work.
I cant attest to that ... and whats worse, is after a couple of hours, the device was no longer recognized and I was only to get it back after re-installing then re-deleting the driver ... until it got to a point where I cant get it back at all ... this is entirely frustrating to say the least.
Well, it appears that ultimately, I'm an idiot... I obviously failed to perform a thorough analysis of my situation because the moment I took my USB hub out of the equation, everything works properly ... and that is WITH the drivers installed ... so it looks like this post was pre-mature...
Hey guys... I do have fairly convincing proof that Mojave includes the working drivers for CH340 (and FTDI) as I just go a MBPro and did a clean install of the latest (OS X 10.14.2). I did not attempt to install any drivers and with a fresh install of the Arduino IDE, I was immediately able to program some Nano boards and use the Serial Monitor. Works great!
Hi.I think it may be an issue regarding CH340 drivers and MACOS.Can you please read the following article and see if it helps: thingsmatic.com/2017/08/07/using-ch340-devices-with-osx/Regards,Sara
Firstly regards the crash make sure you installed the 1.3 version of the driver, not the old one. You could download it directly from the Manufacturers Website in case they have issued an update since I wrote this page.
Operating Systems: Mac OS X 10.8, Mac OS X 10.9, Mac OS X 10.10, Mac OS X 10.11, Mac OS X 10.12, Mac OS X 10.13, Mac OS X 10.14 File Name: arduino-1.8.9-macosx.zip, Size: 181MB
Apple are moving from what are called Kernel Extentions (.kexts) to what are called Driver Extensions (.dexts) for the implementation of drivers starting in macOS Catalina (10.15). Currently .kexts are still supported in macOS Catalina, however after the beta release they issued an update which stopped our driver from loading. This update required our driver (FTDIUSBSerialDriver.kext) to be re-signed and notarized, we completed this process with an updated Apple Developer ID (as they lapse every two years). Unfortunately when Apple issued our new Developer ID to re-sign and notarize the driver package they did so without the .kext support option enabled (as .kexts are being deprecated it is no longer automatically included). This is why there is a code signature issue with our driver, currently we are waiting on Apple issuing us with the correct Developer ID to be able to sign .kexts for macOS Catalina.
Then I came across this post: =427825.0 where the user is having this same problem with MacOS Sierra. He suggested we remove the FTDI drivers and rely on Apple's drivers. So I removed the FTDI drivers from my Mac so it will use Apple's drivers.
The CP210x USB to UART Bridge Virtual COM Port (VCP) drivers are required for device operation as a Virtual COM Port to facilitate host communication with CP210x products. These devices can also interface to a host using the direct access driver.
The CP210x Manufacturing DLL and Runtime DLL have been updated and must be used with v 6.0 and later of the CP210x Windows VCP Driver. Application Note Software downloads affected are AN144SW.zip, AN205SW.zip and AN223SW.zip. If you are using a 5.x driver and need support you can download Legacy OS Software.
Extracting manual-install-spresense-arduino-windows-latest.zip may cause an error, the file path name is too long.Therefore, the procedure described here extracts the zip file to a folder with a short path name such as c:\temp.
These instructions describe an installation of the Arduino Software and drivers for an Arduino Uno on Mac OS X Lion, but will work the same for Leopard, Snow Leopard and Mountain Lion. Previous operating systems may require you to search the web for your specific situation.
Many instructions down below were written for the old driver, which was not signed, and therefore was not working out of the box on OS-X Yosemite and El Capitan. The latest driver appears to be signed, and should work out the box. The new driver is here: CH34x_Install.zip (111Kb).
Right, so why do we need this driver? Well the Arduino clones can be purchased on eBay for about $4.50 delivered, this makes them 80% cheaper than a "genuine" Arduino and they perform the all of the same functions as an officially branded Arduino.
The cloned Arduino uses a serial to USB chip to make the Arduino work with computers over USB. The chip that the developers of this cloned board used is called a CH340 chip and it does not want to talk to a Mac unless it has the proper driver. Most serial to USB chips are made by a company called FTDI and they are the most common and universally recognized chips and work with all* computers automatically, but because these inexpensive boards don't have FTDI chips we will need a driver.
So Apple, in the latest OS X update, El Capitan, and in all future updates has made it so that all drivers installed on Macs need to be "signed" by Apple. This signing process makes sure that no malicious code makes it on to your computer.
Note: the FTDI USB Drivers are from Arduino. But when you install drivers for other Controllers, such as Xadow Main Board, Seeeduino Clio, Seeeduino Lite, you need to download corresponding driver file and save it. And select the driver file you have downloaded.
Copy the Arduino application into the Applications folder (or elsewhere on your computer). If you're using an Arduino Uno or Mga 2560, you don't have any drivers to install. Skip ahead to the next step.
you will need to install the drivers for the FTDI chip on the board. Double-click the FTDIUSBSerialDriver_10_4_10_5_10_6.mpkg icon and follow the instructions in the installer. You'll need to restart your computer after installing the drivers. (The latest version of the drivers can be found on the FTDI website.)
Your computer running MATLAB® Support Package for Arduino Hardware automatically detects the supported official Arduino boards. However, if you are using an unofficial (clone) board of Arduino, you need to first install the required device drivers manually before connecting the board and identifying the port number. In general, if you are not able to find the port name after connecting an official Arduino board or an unofficial (clone) board by following the steps mentioned in the below sections, ensure that you first check with the vendor and install the required driver or update the driver software.
There are two choices for Windows version of L: Installer or ZIP file. You're recommended to use the Installer since it will automatically install the driver for Arduino IDE installation. So you can just download it and run the executable file to begin installation. If you download the zip file, you need to unzip the file and install the driver by yourself.
If you downloaded the installer, upon your connecting the board to the computer, the system will help you install the driver automatically. After a while, a prompt may appear in the taskbar indicating the driver is installed successfully. It depends on computers. So if you don't see it in yours, it's still OK.
D: A window pops up then. Click Browse. Then go to the folder where you just extracted the file. Go to the drivers folder and click OK -> Next. It may need a sec. Then the system prompts you the driver has been installed successfully. And the driver is for Uno. So the computer can recognize the board now. Click Close. 2b1af7f3a8