Prior to Yosemite at least Mac OS included serial port driver for USB CDC ACM
device which automatically loaded and things 'just worked'.
I'm not 100% sure about Yosemite but since the port is recognized and works for
some time before it dies I expect that Yosemite has the driver too.
br Kusti
Darrik Spaude <mailto:[email protected]>
18 March 2015 15:39
Is there a driver that is supposed to load for that device? Do you
know if the driver is loading successfully in Yosemite?
Sent: Wednesday, March 18, 2015 5:41 AM
To: [email protected]
Subject: Yosemite USB CDC ACM
On a fresh install of Yosemite my USB CDC ACM device fails badly.
This is an open firmware/hardware CNC-controller called TOAD4
that I use in my EazyCNC software, more info here:
http://www.eazycnc.com
The controller presents itself as a USB CDC ACM to the OS.
The firmware has been stable for years and the communication
works without issues in several operating system, it has been tested
in numerous Linuxes, Windows XP, Windows 7 and Mac OS X Lion,
Mountain Lion (possibly/probably on Maverik too). I use it daily
on Mountain Lion without issues.
Now, on Yosemite it seems that within tens of seconds of opening
the virtual serial port a read timeouts and the device disappears
from the /dev directory. And it won't reappear there even after
re-pluggin the device although the device is still running according
to the external signs I can observer on the device. I need to
physically reset the device to make it re-appear in the /dev directory.
Now the fact that it won't re-appear after re-plugging, suggest something
is wrong on the device side firmware. With every other (than Yosemite)
operating system I've tested the system the OS has no problem enumerating
the device after a re-plug.
However the primary problem is that something goes south during
normal communication and this I'm not convinced is a device side
issue. Of course it can be a device side firmware issue, not denying that.
The USB CDC ACM 'stack' on the device is
a bare minimum supporting only the absolutely mandatory features
as per the USB spec. Googling around I see that several virtual devices
both custom driver based (FTDI) and Apple driver based (ie real USB CDC
ACM devices) have experienced problems with Yosemite.
Now I'm looking for ideas on how to debug this further and also fishing
for info on what has changed on Yosemite and hunches about what
could be the problem.
br Kusti
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/usb/eazycnc%40eazycnc.com
This email sent to [email protected]
Kustaa Nyholm <mailto:[email protected]>
18 March 2015 12:40
On a fresh install of Yosemite my USB CDC ACM device fails badly.
This is an open firmware/hardware CNC-controller called TOAD4
that I use in my EazyCNC software, more info here:
http://www.eazycnc.com
The controller presents itself as a USB CDC ACM to the OS.
The firmware has been stable for years and the communication
works without issues in several operating system, it has been tested
in numerous Linuxes, Windows XP, Windows 7 and Mac OS X Lion,
Mountain Lion (possibly/probably on Maverik too). I use it daily
on Mountain Lion without issues.
Now, on Yosemite it seems that within tens of seconds of opening
the virtual serial port a read timeouts and the device disappears
from the /dev directory. And it won't reappear there even after
re-pluggin the device although the device is still running according
to the external signs I can observer on the device. I need to
physically reset the device to make it re-appear in the /dev directory.
Now the fact that it won't re-appear after re-plugging, suggest something
is wrong on the device side firmware. With every other (than Yosemite)
operating system I've tested the system the OS has no problem enumerating
the device after a re-plug.
However the primary problem is that something goes south during
normal communication and this I'm not convinced is a device side
issue. Of course it can be a device side firmware issue, not denying
that.
The USB CDC ACM 'stack' on the device is
a bare minimum supporting only the absolutely mandatory features
as per the USB spec. Googling around I see that several virtual devices
both custom driver based (FTDI) and Apple driver based (ie real USB CDC
ACM devices) have experienced problems with Yosemite.
Now I'm looking for ideas on how to debug this further and also fishing
for info on what has changed on Yosemite and hunches about what
could be the problem.
br Kusti
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/usb/eazycnc%40eazycnc.com
This email sent to [email protected]
--
Sent with Postbox <http://www.getpostbox.com>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/usb/archive%40mail-archive.com
This email sent to [email protected]
