CP2102 OSX drivers? [solved: make sure your USB cable is OK] #2
Comments
|
@squix78 Apparently you've got this working – any details? Did it just work OOTB? What OSX version? What model of Mac? Do you see the kext being loaded in |
|
SiLabs' drivers worked out of the box for me (OS X Yosemite). They are signed so there's no need to turn off checks in the OS. There's some issues I've had and I cannot say for sure if they are due to the drivers: I can use NodeMCU devkit 1.0 with screen and ESPlorer in general but I was not able to make it work with mini-com nor have I been able to flash it with esptool. These things worked for me onESP01 and different USB-serial adapter. |
|
@marcoskirsch Could you please paste what |
|
OS X Yosemite 10.10.4 (14E46) kextstat (scroll to the bottom): |
|
@marcoskirsch Thx, you do have the kext loaded… The question is: why is it not my case? How do I debug this? |
|
http://community.silabs.com/t5/Interface/OS-X-10-10-CP210x-VCP-Driver-Release-Candidate/td-p/138472 But it doesn't tell me anything… Edit: I did But it's not shown in the dev list: |
|
Does /dev/cu.SLAB_USBtoUART exist? Try the following: and upload diff-device.txt as a gist? There's also a ~known issue with some serial bridges where they have trouble on USB3 - the workaround is to plug in a USB1/USB2 hub in to the USB3 port and then plug your device in to the hub. |
Anyway, it works. I just had a bad cable (3 of them o.O). After I plugged in a borrowed Samsung's phone cable, it started working o.O I guess it's true that some USB cables are only for the power and not every USB cable can exchange data… :D |
MacDada
changed the title
|
Exact same problem here. I tried 2 cables already but no SiLabs com port yet.. Edit found more similar issues but no solution: |
|
I'm having the same problem on OSX 10.11.3. The cable is definitely good because it works perfectly fine in a Windows VM on the same machine. |
|
Not working in el capitan 10.11.3 !! :/ works perfectly on windows machine though |
|
I am also facing the exact same issue. It gets detected for the first time and then "error: cannot access /dev/cu.SLAB_USBtoUART" appears. After restarting laptop, it detects the /dev/cu.SLAB_USBtoUART and then exact same issue. |
|
Hi Guys, It looks like this is because the official driver is not signed and in 10.10 & 10.11 they have kext signing :-( The solution which worked for me is to install this driver from another vendor which is signed, but works just fine! http://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/ |
|
I am experiencing the same issue on OS X 10.11.5 (MacBook Pro (Retina, 15-inch, Mid 2014)), using a Wemos D1 Mini and an Amazon USB Cable. The kernel extension is loaded: But there is no /dev/tty.SLAB_USBtoUART: Under System Information the USB device (when attached) shows up as I have diff'd the results of https://gist.github.com/fadushin/d4c17e73be26cece8e8cddb6edd704bb I am disinclined to install an unsigned kernel extension or otherwise not readily downloadable from a reputable vendor, particularly if it is reported to cause kernel panics. And, hi, @bosschaert ! |
|
I installed the Arduino IDE with the ESP8266 addon (as described here https://learn.sparkfun.com/tutorials/esp8266-thing-hookup-guide/installing-the-esp8266-arduino-addon ) and the /dev/cu.SLAB_USBtoUART magically appeared for me. I'm unsure whether it came with the Arduino IDE or with the addon, but its now just working for me. PS hi @fadushin ! |
|
Silly me. My Wemos D1 Mini uses a CH340G chip, not the CP2102 (my son's magnifying glass comes in handy). Of course that driver won't work. Using the driver with the right chip actually works. NB. The CH340G driver can be found at http://www.wemos.cc/downloads/ And instructions are at http://kig.re/2014/12/31/how-to-use-arduino-nano-mini-pro-with-CH340G-on-mac-osx-yosemite.html |
|
If someone runs into such an issue, really DO check many cables. I have 2 Mac running Sierra and my ESP8266 works in one and not the other. I could validate a cable to be working on my iMac but it would not on my MBP2016. I tested randomly many cables, some work, some don´t. Most of those cables usually work fine. Conclusion: do test many cables.... |
|
Try to use a USB hub with a power source, like this one: https://i.stack.imgur.com/pzG2u.gif |
|
Guys, can you help me. I've just got my NODEMCU ESP-12e with CP2102 (1.0), I'm using a MAC AIR, but the device doesn't appear on the PORT list, as some of the guys above. I'be tried different cables as well a USB interface that allows me to input an extra 5V DC PSU to feed the NODEMCU, no response at all. The Blink sketch compiles OK, the board is correctly set for NODEMCU 1.0 (ESP-12e Module), but no way to make it works. I heard that I should download a driver for CP2102, is it right? If so, where can I find it? Any help? Thanks! |
|
I just experienced this exact same issue. It ended up taking me a couple hours to figure it out, but I established a highly technical definition of the problem: My cable was bad 🤦♂️ |
|
TL;DR: Use a short fat cable I'm going to go ahead and say it is a cable problem, but not a bad cable. I had to try every single one of the dozen or so that I have and I'm not throwing any of them away after this. Consistent with @chevdor, the short, fat cable did the trick, which would seem to suggest that for some reason the tiny voltage drop across a longer or thinner cable makes the signal from the CP2102 just too weak for the chipset on a mac to interpret, which is an absurd explanation. I suppose I could pull out the old oscilloscope to validate that but.... Anyways, I had to steal the cable from my wife so I'm ordering this one (https://www.amazon.com/gp/product/B013G4EAEI) off amazon. If it doesn't work I'm sure I'll be back with some oscilloscope tracings. Happy cable hunting! |
|
Same issues. Tried better cable. Thank you, all! |
|
What kind of cables are you guys using that are working? I'm having this issue right now, and the ~18" anker powerline cable (along with 3 or 4 others) are all not showing the device. Seems ridiculous that it could be this sensitive to which cable is needed |
|
@jacobtarter And it's because not all cables are equal. I can tell you with certainty that this is by FAAAAAAAR not the only tech that's picky about which cable you use. |
|
In the first place you should avoid using Anker cables made for CHARGING.
There is no reason why charging cables would be good with data
(unfortunately). Just buy 1 good quality cable that is also not too long.
Good luck. Those issues are annoying...
…On Mon, Sep 11, 2017, 12:44 Simon ***@***.***> wrote:
@jacobtarter <https://github.com/jacobtarter>
Well, depending on the issue, it might not be your cable.
After all the troubleshooting steps I followed, the cable ended up being
the issue for me.
And it's because not all cables are equal.
Some are cheap and good, some are cheap and bad;
Some are pricey and good, some are pricey and shit.
Some only do power, some do data but poorly.
I can tell you with certainty that this is by FAAAAAAAR not the only tech
that's picky about which cable you use.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAtFpI1yclYEfciwdzXpP1WnThiYsbswks5shQ77gaJpZM4FUW90>
.
|
|
The cable I was using wasn't a power only cable, although anker does make those (power line + I think theyre called). Anyway, I hooked it up to an older desktop running elementary os and it detected it immediately. |
|
Thanks @fadushin !! You opened my eyes too ! I have an esp32 by Wemos and it's the same chip as you .... |
|
So to be clear, NodeMCU ESP12E devkit boards (and others?) come with different USB Serial chips. You can tell which you have by a) looking at the top of the chip, or b) plugging the board into your Mac and then opening System Information. Go to Hardware -> USB. Find the USB2.0-Serial device, and look at the details. The latest Mac drivers for the CH340 can be found here direct from WCH (version 1.4 released Jan 2017): Most documentation seems to assume you have a SiLabs CP210x chip, so if you end up here because your USB serial driver isn't working (like I did), hopefully you'll find this useful. |
|
Thank you guys, solved this problem by reinstalling the driver. |
|
Checking back in. I still same problem with a new cable and reinstalled driver. It's intermittent so I suppose I'll just live with it... |
|
I am also having issues with this, have multiple boards, just one was presenting errors, tried different cables. Ultimately I decided to try a different USB port on my macbook pro - It worked! |
|
@Basirk thanks for your useful piece of information! Let me precise that it's responding through the Which won't let me use the board through the Arduino official IDE. I tried two cable made for data sharing (Android device official cable) and another one that reportedly worked on my friends MBA with the same chip (I've a MBP) |
|
For what it is worth I will add some information regarding this issue. Short story nodeMCU 1.0 devkit on mpb from 2013. Could not see any drivers in /dev folder. Only did see bluetooth entry in /dev/ from esplorer. So, the drivers from silabs was the problem. When you install something on high sierra (and before?) there is a security measure that won't allow unsigned drivers to install. Looking into it i found that I did not see any error when running the installer from silabs. But if you go to System preferences -> Security & Drivers there will be some information at the bottom of the screen regarding this. So, what I did was that I clicked on the link that is supplied in Security & Drivers to allow the driver to be installed (or if it is the installer that is allowed to run). THEN reinstalled the silabs driver but using the legacy drivers. Now, I had seen somewhere that you might had to run the installer twice. So I did that and that was it. Communication to the nodeMCU did work from inside esplorer.
|
|
@ericssonanders comment is spot-on. I'm on High-Sierra and after manually attempting a kext load via Here's the note from Apple describing why only some users are hitting this - if you had the driver installed from before upgrading to High Sierra it would have continued to work transparently for you |
|
Hello, I would like to share my experience. I went trought all recommendations no success. The result is wrong USB-C to USB 3.0 reduction. Interesting is that USB-C reduction is working for external HDD. Strange behaviour, do you have same experience? |
|
Just went through the steps above (including |
|
If you are having trouble on macOS... I wrestled with this issue for a couple days on and off. I finally fixed my issue, so I figured recounting my steps for all the other unfortunate sufferers would be worthwhile (even tho I am sure you have read 100 versions of solutions by now). First off, I followed most of the general recommendations and installed this SiLabs Driver - no luck. Then installed this CH34 driver - no luck (I didn't check to determine which chip I had, just kept trying solutions). When installing the driver(s), I saw the Security many have described, warning for a 3rd party developer trying to access some settings. I did what most suggested and went to System Preferences ➜ Security & Privacy ➜ General and made sure my allowing apps to be downloaded from "Mac App Store and identified developers" - which it was. Still - no luck. Then, after hitting issue after issue, I resorted to assuming I had bad Micro USB cables (charge only) - so I ordered a new USB Sync cable to remove that variable. I could never get my ESP8266 NodeMCU LUA CP2102 ESP-12E (made by HiLetgo) to show up under Tools > Port in the Arduino IDE (should see "/dev/cu.SLAB_USBtoUART"). After banging my head on it over and over, I tried re-installing the CH34 driver - which popped the security warning again (as described above). This time I clicked the "Goto Settings" button - which simply took me back tot the same System Prefs Security dialog I checked for the "allow apps" setting before. However, this time I noticed there was a subtle macOS option next to those "Allow apps downloaded from" section which said "Some system software was blocked from loading." and here was an "Allow" button. When I tapped the "Allow" button, it popped a dialog that showed both the SiLabs and Ch34 drivers unchecked, which I fixed. After that, voila! It all worked (and on all my USB cables no less). I cannot say which driver was my solution, but thought the important thing to point out to anyone struggling was to look for the Allow button in Security - I didnt notice it because all solutions I read just called out the "Mac App Store and identified developers" setting in that panel. I had that set before installing the driver and it DID NOT stop the drivers from being blocked, so check for that. Hopefully this helps someone else, what a pain... |
|
Thank you @haukeg for the new information. Do you happen to know the type of Mac used? I've seen slightly different problems between the 2016+ Macbook Pro laptops "with touchbar" versus "without", even when they're supposedly running the same version of MacOS. |
|
@haukeg had exactly the same problem, same solution. Allow your driver to run! MBR 15 touchbar 10.14.1 |
|
tried several times , normal, legacy cp2101, ch34, alert in security don't show, also disabled spctl kext-consent, tried several cables
` don't nkow what to do more... ` |
|
GUYS, REMEMBER TO TURN ON YOUR BOARD 😱 🤯 😭 |
and others
Where do I find working drivers for OSX 10.10 (Yosemite)?
10.10.3onMBP11,2There is a file/folder
/Library/Extensions/SiLabsUSBDriver.kext, but no serial port available for the device.No success with ESPlorer and Arduino IDE.
EDIT 1
Apparently it works for some people (?), but not for me: http://blog.squix.ch/2015/05/esp8266-flashing-nodemcu-v10-on-mac-os.html
EDIT 2:
It looks like the kext isn't loaded?
Edit 3:
Edit 4:
The device does work, as I can join its network and ping it.
The text was updated successfully, but these errors were encountered: