How to get USB/serial drivers working on M1 mini?
I've tried a few different ways to get each of the FTDI and Prolific drivers working on my new M1 but no luck. Can anybody help with specifics?
Mac mini, macOS 11.2
You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
I've tried a few different ways to get each of the FTDI and Prolific drivers working on my new M1 but no luck. Can anybody help with specifics?
Mac mini, macOS 11.2
FWIW, the FTDI devices I have I have checked them out
on my M1 MacBook Air using the Apple USB-C to USB-A
connector. Both the FTDI USB-COM485-PLUS1 and the
USB-COM422-PLUS1 connect and enumerate properly
with no additional drivers. They also work when connected
to my USB hub as well. In addition, I am working on some
embedded design using an STM32 Nucleo-F767ZI development
board and the USB port that I used as a terminal interface
worked immediately, i.e. recognized the USB CDC port
with no additional Mac side drivers.
In all cases they were enumerated and could be found in
the /dev directory. With my STM32 work, I have been using
the app Cool Term for my terminal interface to my development
board. It also displays as a port choice any of the above mentioned
USB CDC devices.
FWIW, I began avoiding Prolific based devices as it seemed
any time I bought a new computer, I had to by a new
adapter because its firmware wasn't compatible regardless
of what drivers I would install. It wasn't just Macs either.
With all that said, I assume you are directly connecting to one of
the USB ports? Also, are you trying to use the FTDI device for
other than USB CDC, i.e. their direct driver interface?
FWIW, the FTDI devices I have I have checked them out
on my M1 MacBook Air using the Apple USB-C to USB-A
connector. Both the FTDI USB-COM485-PLUS1 and the
USB-COM422-PLUS1 connect and enumerate properly
with no additional drivers. They also work when connected
to my USB hub as well. In addition, I am working on some
embedded design using an STM32 Nucleo-F767ZI development
board and the USB port that I used as a terminal interface
worked immediately, i.e. recognized the USB CDC port
with no additional Mac side drivers.
In all cases they were enumerated and could be found in
the /dev directory. With my STM32 work, I have been using
the app Cool Term for my terminal interface to my development
board. It also displays as a port choice any of the above mentioned
USB CDC devices.
FWIW, I began avoiding Prolific based devices as it seemed
any time I bought a new computer, I had to by a new
adapter because its firmware wasn't compatible regardless
of what drivers I would install. It wasn't just Macs either.
With all that said, I assume you are directly connecting to one of
the USB ports? Also, are you trying to use the FTDI device for
other than USB CDC, i.e. their direct driver interface?
Thanks for your help. It turns out that both devices Prolific and FTDI are registering, once I figured out how to get `screen` running (new to Mac OS). My problem looks now to be a different issue which is I'm running Parallels and have Windows where I want the device to show up as a COM port since I have a Windows-only application I need to run, but the driver is showing up as unrecognized. I am following Parallels instructions to set it up as a serial port but Windows doesn't recognize it.
Any advice or experience for this case?
You need to connect the devices as USB devices to Parallels
and then let the Windows VM do the USB enumeration.
I haven't used Parallels in a while but there should be a
USB dropdown menu or dialog allowing to attach the
USB devices to the VM.
How to get USB/serial drivers working on M1 mini?