search

WCHSoftGroup / ch34xser_macos

MacOS USB driver for USB to serial chip ch340, ch341, ch342, ch343, ch344, ch9101, ch9102, ch9103, etc
313 stars 25 forks source link

Driver CH340G not working Mac M1 chip #2

Open rohaizanr opened 3 years ago

rohaizanr commented 3 years ago

Hello,

After following the step, it is still not working on my MacBook Air (M1, 2020).

In the System Information, it is showing USB2.0-Ser!

Screenshot 2021-11-05 at 4 30 03 PM

I've already tried uninstalling and installing many time, is there a manual way to do this?

Thanks

Lanjelin commented 3 years ago

Been emailing WCH on the issue, and recieved the following file yesterday. CH34xVCPDriver.zip I've not had much time to test, but I was able to communicate/ use serial monitor with a CH340K chip.

rohaizanr commented 3 years ago

Hi @Lanjelin, it seems not working on CH340G. I had the same file given to me from https://github.com/WCHSoftGroup/ch34xser_macos

johnnymiranda commented 3 years ago

I am having the same issue as @izandotnet. I am really new to the Apple M1 chip so I am not sure if there is a work around via emulation.

deepbluese commented 3 years ago

Is there a solution for Macs with M1?

WCHSoftGroup commented 3 years ago

The driver supports: OS X 10.9 to OS X 10.15 OS X 11.0(Big Sur) and above

WCHSoftGroup commented 3 years ago

@izandotnet It seems that the cable works now, and the device is named "tty.wchusbserialxxx"

deepbluese commented 3 years ago

And what's about the architecture? Arm? M1 is arm and this don’t work already!

Von meinem iPhone gesendet

Am 15.11.2021 um 13:09 schrieb WCHSoftGroup @.***>:

 The driver supports: OS X 10.9 to OS X 10.15 OS X 11.0(Big Sur) and above

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

rohaizanr commented 3 years ago

@izandotnet It seems that the cable works now, and the device is named "tty.wchusbserialxxx"

In the System Information, it is showing USB2.0-Ser!

Screenshot 2021-11-15 at 8 23 26 PM
rohaizanr commented 3 years ago

And what's about the architecture? Arm? M1 is arm and this don’t work already! Von meinem iPhone gesendet … Am 15.11.2021 um 13:09 schrieb WCHSoftGroup @.***>:  The driver supports: OS X 10.9 to OS X 10.15 OS X 11.0(Big Sur) and above — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

How do you know this?

deepbluese commented 3 years ago

Because of: (https://user-images.githubusercontent.com/77930305/141809687-8374fb44-a8d0-4089-81a2-895d5acb04dc.png)> > …

Am 15.11.2021 um 13:09 schrieb WCHSoftGroup @.***>:  The driver supports: OS X 10.9 to OS X 10.15 OS X 11.0(Big Sur) and above — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

How do you know this?

DataCerealz commented 3 years ago

Same issue here. Using an M1 Mac on Monterey 12.0.1 the driver doesn't work. I tried the one from the official website as well as the driver from this repository without any success; following exactly the instructions of the pdf. It creates files in /var/db/receipts/ but no files in /dev/ or in /Library/Extensions/.

I tried rebooting and reinstalling several times with no success; using 1.1, 1.4, 1.5, and this repo.

lptr commented 3 years ago

I'm having the same issue, but with an Intel MacBook Pro (15-inch, 2019). The same setup works fine on my Intel iMac (2020).

Both machines are on Monterey 12.0.1.

The installation of the driver goes fine, I click "allow" in security preferences, reboot, but there is no kernel extension:

$ kextstat | grep -v com.apple                       

Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  120    0 0xffffff7f997cf000 0x2000     0x2000     com.intel.driver.EnergyDriver (3.6.0) CF3549FA-B79E-34E2-BF25-6C5FEF5EF262 <9 7 6 3>

Nor do I see any tty.wch* devices:

$ ls -l /dev/tty.*
crw-rw-rw-  1 root  wheel  0x9000000 Nov 26 11:27 /dev/tty.BLTH
crw-rw-rw-  1 root  wheel  0x9000002 Nov 26 11:27 /dev/tty.Bluetooth-Incoming-Port
lptr commented 3 years ago

OK, I tried using the same USB cable that works on the iMac, and now it works on the MBP as well. I have no idea what the difference between the cables are.

DataCerealz commented 3 years ago

@lptr Wait; so you still don't have a kernel extension nor a dev entry and it's still working just with a different cable?! Where does this driver even get installed? Did you use some sort of USB-C to USB-B cable or do you still have a Hub in between?

lptr commented 3 years ago

I don't have a kernel extension:

$ kextstat | grep -v com.apple
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  124    0 0xffffff7f997cf000 0x2000     0x2000     com.intel.driver.EnergyDriver (3.6.0) CF3549FA-B79E-34E2-BF25-6C5FEF5EF262 <9 7 6 3>

But I do have the USB device when using the right cable:

$ ls -l /dev/tty.*
crw-rw-rw-  1 root  wheel  0x9000000 Nov 26 11:39 /dev/tty.BLTH
crw-rw-rw-  1 root  wheel  0x9000002 Nov 26 11:39 /dev/tty.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel  0x9000006 Nov 26 13:23 /dev/tty.usbmodem52780134231
crw-rw-rw-  1 root  wheel  0x9000004 Nov 26 13:23 /dev/tty.wchusbserial52780134231

I'm using an USB-C to USB-A dongle with a USB-A to micro USB-2A cable.

lptr commented 3 years ago

TIL about charge-only USB cables:

Because the USB Implementers Forum doesn’t have any rule enforcing USB manufacturers to label or differentiate charge-only cables from data-transfer cables, it is almost impossible to tell them apart.

https://www.dignited.com/50330/usb-data-cable-vs-usb-charging-cable/

My best guess is that the cables I tried on my MBP that didn't work were charge-only.

🤦

DataCerealz commented 3 years ago

Now that's crazy. So I copied your setup and tried with a really old blackberry cable.

It generated the dev files as expected:

ls /dev/*usb*         
/dev/cu.usbserial-10
/dev/tty.usbserial-10
/dev/cu.wchusbserial10
/dev/tty.wchusbserial10

The controller is still not recognised by the Arduino IDE; but having Arduino agent installed (well, installation crashed with an error message but it's still running and doing it's job somehow) the Arduino Web IDE recognised the controller and I could upload code flawlessly.

I am still kind of confused. So I already shared your theory about no data lanes in my cables; but I was so sure that I also used the other ones for data before....and I mean I tired quite a few. But I could be wrong here and it really was just me being unlucky for always picking power-only cables out of my storage box ;)

Feeling stupid right now.

lptr commented 3 years ago

Feeling stupid right now.

Same. 🤷 But glad that it works for you too now! :)

andypiper commented 2 years ago

What is the conclusion here for M1 / Apple Silicon Macs?

smilodonis commented 2 years ago

What is the conclusion here for M1 / Apple Silicon Macs?

Still not working for me on M1 Mac.

helmiattastify commented 1 year ago

try to use V1.1 instead of another driver version after plug the device please wait little bit longer maybe 20seconds.

if you cannot see the usb serial port, check on serial monitor

I'm using M1 (13.1)

Screenshot 2023-01-09 at 09 20 36