Menu
I have a USB Z-Wave stick from Sigma Designs that I want to use in a linux guest (debian).In the OSX System Report it shows up in the USB Device Tree as 'Communication Device':Code: Communication Device:Product ID: 0x0200Vendor ID: 0x0658 (Sigma Designs, Inc.)Version: 0.00Speed: Up to 12 Mb/secLocation ID: 0x14500000 / 28Current Available (mA): 500Current Required (mA): 100I've also found that it creates a serial device at /dev/tty.usbmodem1411 which I've confirmed works by using it in z-wave applications.I am however not able to pass the usb device through to my debian guest. I've tried both adding a USB filter for 'Unknown device 0658:0200' and empty filter (which should match any device?).In the linux guest I get the same output from lsusb -command with/without these filters active:Code: root@core /dev# lsusbBus 001 Device 002: ID 80ee:0021 VirtualBox USB TabletBus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hubAny ideas? Posts: 9 Joined: 2. Feb 2010, 10:56 Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: Debian Jessie. Could it be that osx has already 'grabbed' the usb device when it exposed it as a serial device? I remember having a similar issue with an older version of Virtualbox on a Linux host which auto-mounted a usb hard drive that I wanted to pass through. Back then I simply solved it by un-mounting the usb hard drive on the host.
I don't know how to do the same for a serial device in osx though. Posts: 9 Joined: 2. Feb 2010, 10:56 Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: Debian Jessie. So I've managed to find a workaround by using the ser2net application.1. First I installed ser2net and added this line to vi /usr/local/etc/ser2net.confCode: 3001:raw:0:/dev/tty.usbmodem1411:115200 NONE 1STOPBIT LOCALmake sure port 3001 is not in use, or select another one.(find your serial device by executing 'ls /dev/tty.' - it changes id depending on what usb port I plug it into)2. Start ser2netCode: /usr/local/opt/ser2net/sbin/ser2net -uNote: without the -u flag it will have problems creating a lock file, even though running as root.3.
Configure serial port in VirtualBoxUSB Serial PortsCheck 'Enable serial port'Port Number: COM1Port Mode: TCPPath/address: localhost:30014. Start up the VM/dev/tty.usbmodem1411 on host is now available as /dev/ttyS0 on the guest. Posts: 9 Joined: 2. Feb 2010, 10:56 Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: Debian Jessie. Dmesg output:Code: 0 Level 5 com.apple.message.domain com.apple.commssw.cdc.device com.apple.message.signature AppleUSBCDCACMData com.apple.message.signature2 0x658 com.apple.message.signature3 0x200AppleUSBCDCACMData: Version number - 4.2.2b5, Input buffers 8, Output buffers 16AppleUSBCDC: Version number - 4.2.2b5not sure on how to unload that though, will have to read up a bit. Posts: 9 Joined: 2.
Networkers, I've used a Keyspan/Trip-Lite USA-19HS USB-to-Serial adapter to access device consoles from my Mac for many many years. Often, but not always, MacOS upgrades require a new driver from Trip-Lite but I noticed they haven't published one for 10.15 yet. Sun's VirtualBox is a slick new virtualization alternative to VMWare Fusion, Parallels, and the like. For some of us, we not only need to run a Windows app, but that app requires a connection to a serial device. Here's what I did just now to get my Keyspan USA-19HS USB-to-Serial adapter working in VirtualBox under Windows XP.
Feb 2010, 10:56 Primary OS: Mac OS X other VBox Version: OSE other Guest OSses: Debian Jessie. Hey everyone, I just created an Oracle account so I could respond to this thread because I think I encountered the same problem as geirgp but I was able to figure it out.
I'm using a Cypress CY7C64225 based USB to serial adapter, but I'm guessing that this would apply to other cases as well.So initially I tried to pass through the serial port with Path/Address: /dev/tty.usbmodem641but this was crashing VirtualBox just like geirgp experienced.I tried using a tool called 'CoolTerm' to be sure that the serial port was working properly in Mac OS at all. When I opened CoolTerm, I found that it was not using /dev/tty.usbmodem641, but instead /dev/cu.usbmodem641.After entering this new device path in the VirtualBox serial port configuration, the virtual machine started right up and the USB serial adapter worked perfectly. Posts: 1 Joined: 12. Sep 2017, 21:50.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |