/dev/cu.usbserial-14120
Success uploading to ESP8266!!!
Thank you so much for your post and help. I can now continue to use the Mac for development.
As an explanation of what I struggled with - I kept looking to connect to a device ‘cu.wchusbserial14120’. I was thinking the Apple driver would implement the dual scheme for the serial port that I was used to seeing… [BTW The Arduino IDE 1.8.10 is unable to obtain board info through this driver.]
Thank you.
If two drivers for the same device are installed, they both create an entry in /dev. But only one will work.
/dev/cu.wchusbserial14120 is the defunct one. I suggest you uninstall the WCH drivers at /Library/Extensions/usbserial.kext.
Then only one entry will be created and PlatformIO will likely pick the right one automatically.
Driver removed. Thank you.
Thanks for excellent write up. Unfortunately its not working for me on macOS Catalina 10.15.7. I’m trying to connect Platform IO to Wemos D1 Mini PRO which has an CH340C. The board is not visible at all under /dev/cu… I cannot find Apple’s driver AppleUSBCHCOM.kext under /System/Library/Extensions and I don’t have any additional drivers installed. it seems Apple made some changes here?
On macOS Cataling already, the driver is under /System/Library/DriverExtensions/com.apple.DriverKit-AppleUSBCHCOM.dext. I’m sure you’ll find it on your system as well.
Since it’s not working, try:
Thanks appreciate the help. I flashed the device using Platform IO on a PC so got the software running with no issues. Based on your advice I gave mac another try and I can locate the driver on my system and after connecting the board I can also see the device under System Report. It also shows up under /dev. Must have been an unfortunate combination of two faulty USB cables because I tried connecting using two different mac both running 10.15.7 Catalina and none of them found the device and I was careful not to use a power only USB cable. Anyway I’m back on track now 
Let me try sir! thank you for the knowledge!!!
Hi, a really well written FAQ.
But It is not working for me… damn…
So, I updated my mac from Catalina to Big Sur.
In my
/Library/Extensions/
I removed usbserial.kext. There isn’t file like osx-ch341.kext.
But I’m still not have a /dev/cu.usbserial-1410
Please help me.
Other information:
1] I can see in System Information under USB an idem USBasp.
2] UsbAsp is directly connected to mac using a usb->usbc
3] kernet stat:
➜ ~ kextstat | grep usb
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
20 11 0xffffff80019e2000 0x4000 0x4000 com.apple.driver.usb.AppleUSBCommon (1.0) 62FE0E66-DCCA-3443-B01E-0F0FAB0A820D <6 5 3 1>
62 1 0xffffff80030f0000 0x4f000 0x4f000 com.apple.driver.usb.AppleUSBXHCI (1.2) D623BBDD-59E1-3494-BE57-0F4AFD1CF853 <22 20 13 8 7 6 5 3 1>
63 0 0xffffff8003148000 0x28000 0x28000 com.apple.driver.usb.AppleUSBXHCIPCI (1.2) 279DC1E0-EDF4-3931-83DC-CF11DC249E98 <62 22 20 14 13 8 7 6 5 3 1>
72 3 0xffffff80019e7000 0x6000 0x6000 com.apple.driver.usb.AppleUSBVHCICommon (1.0) AF314B32-BF81-3386-9D5D-9CBE97F38A48 <22 20 8 6 5 3 1>
73 1 0xffffff80030cb000 0x1e000 0x1e000 com.apple.driver.usb.AppleUSBVHCI (1.2) 630BF562-58F3-38DE-B1D7-C96F93B822B4 <72 22 20 8 7 6 5 3 1>
74 1 0xffffff80019ee000 0xb000 0xb000 com.apple.driver.usb.AppleUSBVHCICommonBCE (1.0) 556E19FE-3DA5-3780-A5C9-CB649031C9B8 <72 69 20 8 6 5 3 1>
75 0 0xffffff80030ee000 0x1000 0x1000 com.apple.driver.usb.AppleUSBVHCIBCE (1.2) C28DAF11-2F78-319A-BCEC-82463267126A <74 73 72 69 22 20 13 8 7 6 5 3 1>
106 2 0xffffff8003048000 0x3000 0x3000 com.apple.driver.usb.AppleUSBHostCompositeDevice (1.2) E262EB63-C5DE-39E7-81A8-7D392721EF73 <22 20 7 6 5 3 1>
107 2 0xffffff8001a2a000 0x2000 0x2000 com.apple.driver.usb.networking (5.0.0) 9B5DD9DF-9A0D-31C5-80E0-670D6AFD6EF5 <22 7 6 5 3 1>
108 1 0xffffff80019de000 0x2000 0x2000 com.apple.driver.usb.cdc (5.0.0) B246DA0A-7913-37F2-AB4E-38CD5B154A19 <107 106 22 6 5 3 1>
109 0 0xffffff8001a21000 0x7000 0x7000 com.apple.driver.usb.cdc.ncm (5.0.0) CD9A1845-EEE9-39FF-A333-D36D98037AEB <108 107 106 46 42 22 7 6 5 3 1>
111 0 0xffffff8003052000 0x2b000 0x2b000 com.apple.driver.usb.AppleUSBHub (1.2) 7699C6C9-BEF3-358D-817A-C2F1C8D0DEDD <22 20 13 6 5 3 1>
113 0 0xffffff8003045000 0x2000 0x2000 com.apple.driver.usb.AppleUSBHostBillboardDevice (1.0) 83258EC3-7FF2-36E4-8979-A68499E7BE0B <22 20 6 5 3 1>
114 0 0xffffff8001a2d000 0x3000 0x3000 com.apple.driver.usb.realtek8153patcher (5.0.0) 0C58685F-3662-3A4D-AF8C-8B0AA87D046D <22 6 5 3 1>
It sounds as if you have an USBasp programmer, not a serial-to-USB converter using the CH340G chip.
The USBasp programmer does not offer a serial connection and therefore does not appear as /dev/cu.usb....
What’s the exact hardware you have and what do you want to use it for?
Hi, and thank you very much for your answer.
Using this UsbAsp with other old mac and this drivers GitHub - adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver: CH340G CH34G CH34X Mac OS X driver everything works well.
It’s quite difficult for me describe exactly what hardware is, I attached a pic for more detail.
But looking better I cannot find CH340.
This is for a project commissioned me by my kid and I need to program an ATMEGA328P.
Thanks for your help.
looking for other USBasp on amazon or ebay I cannot recognize CH340… I’m quite disoriented…
You have an USBasp. It’s even labelled near the USB connector. And it’s the right tool to program an ATMEGA328P.
On macOS, no drivers or driver configurations are needed.
In PlatformIO, just add the below lines to platformio.ini and you’re good to go:
upload_tool = usbasp
upload_flags = -e
Remove any other upload options (like upload_port) if you have them in platformio.ini.
My MacOS Big Sur cannot detect the USB. Yes, I can see these drivers: /System/Library/DriverExtensions
com.apple.DriverKit-AppleUSBCHCOM.dextcom.apple.DriverKit-AppleUSBFTDI.dextcom.apple.DriverKit-AppleUSBSLCOM.dextMy cable work with other ESP32 modules
In the Hardware->USB, I got this output:
| Product ID: | 0x7522 |
|---|---|
| Vendor ID: | 0x1a86 |
| Version: | 2.64 |
| Speed: | Up to 12 Mb/s |
| Location ID: | 0x14200000 / 3 |
| Current Available (mA): | 500 |
| Extra Operating Current (mA): | 0 |
Before using your approach, I install other USB drivers and already uninstall all of them using your guide
Wemos D1 which use CH340C works. But LilyGo T-io Mac OS, Linux driver for CH340K · Issue #3 · LilyGO/LILYGO-T-OI · GitHub which uses CH340K doesn’t work
It looks as if you are out of luck: CH340K uses a different product ID (though it uses most likely the same protocol) and is neither supported by Apple’s driver nor by WCH driver on macOS.
Need to wait for Mr. Apple to add it. Thanks
So here’s a fun one. Tried to install CH34x_install_v1.5 on my late 2008 Alu MacBook (10.11.6), and it installed fine, but…. Completely disabled the native keyboard and touchpad. Didn’t even get to check if it connected to the board. I had to uninstall it, remove the battery and eventually keyboard worked again. Been told this may be a usb addressing thing, but… any advice?
These symptoms don’t sound familiar.
There used to be issues with WCH drivers when macOS Sierra was introduced. But macOS 10.11.6 is macOS “El Capitan”. That’s even older and predates the problem. You might want to go back to older drivers version like v1.3 (available on GitHub - adrianmihalko/ch340g-ch34g-ch34x-mac-os-x-driver: CH340G CH34G CH34X Mac OS X driver)
RE: Big Sur
FYI, I just spent hours chasing this down. The board wasn’t showing up under USB devices. Turns out that I was plugging into the USB 3.0 port on my MacBook. Switched to the port on the other side and the device showed up in this list of connected devices. Went back to PlatformIO and uploaded the sketch without issue. I didn’t need to change/add anything in the platformio.ini.
HTH
Is there any progress regarding the driver for the CH340K ? Aint have no time to wait for Apples coding boys…
Want a solution right now? Use linux. (Mac OS, Linux driver for CH340K · Issue #3 · LilyGO/LILYGO-T-OI · GitHub).