Date: Tue, 10 Nov 2015 11:28:57 -0500 From: Burton Sampley <bsmply@gmail.com> To: freebsd-usb@freebsd.org Subject: How to access a FTDI usb device with a custom vendor and product id's Message-ID: <CANV5k3rW62rGoXKD4m5meegEJ04T4b_v=QGCqBV5wuGxZjzCbg@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Greetings, I am a long time FreeBSD user (started with FreeBSD 2.1.5R). I took a break with FreeBSD for a while with a Linux desktop, but have recently returned. I am now running a 10.2R desktop. I am having problems getting a a FTDI based USB to serial cable to provide CAT control to my Yaesu FT-897d amateur radio. The cable is made by RT-Systems with vendor ID 0x2100 and a product ID 0x9e56. In Linux, using a udev rule, the cable works correctly with a command like the following: modprobe ftdi_sio vendor=0x2100 product=0x9e56 or a udev rule similar to the following: SYSFS{idVendor}=="2100", SYSFS{idProduct}=="9e56", RUN+="/sbin/modprobe -q ftdi_sio vendor=0x2100 product=0x9e56" How do I accomplish the same in FreeBSD? When the cable is plugged in, I get the following in /var/log/messages: Nov 10 08:17:58 kernel: ugen2.3: <RT Systems> at usbus2 (disconnected) Nov 10 08:18:06 kernel: ugen2.3: <RT Systems> at usbus2 Nov 10 08:18:06 devd: Executing 'logger Unknown USB device: vendor 0x2100 product 0x9e56 bus uhub4' Nov 10 08:18:06 root: Unknown USB device: vendor 0x2100 product 0x9e56 bus uhub4 Nov 10 08:47:31 devd: Executing 'logger Unknown USB device: vendor 0x2100 product 0x9e56 bus uhub4' Nov 10 08:47:31 root: Unknown USB device: vendor 0x2100 product 0x9e56 bus uhub4 and usbconfig shows the following: $ /usr/local/bin/sudo /usr/sbin/usbconfig -d ugen2.3 dump_device_desc ugen2.3: <CT-62B Radio Cable RT Systems> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (90mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x2100 idProduct = 0x9e56 bcdDevice = 0x0600 iManufacturer = 0x0001 <RT Systems> iProduct = 0x0002 <CT-62B Radio Cable> iSerialNumber = 0x0003 <RTUI129S> bNumConfigurations = 0x0001 $ I have installed devel/libftdi from the ports collection, but I have not found documentation on how to configure my system to be able to use this device. Once this issue is resolved, I want to use hamlib or FLRIG and FLDIGI for amateur radio digital communications. I have been searching for days to find documentation on what I need to do to make this work and have struck out. Regards, -Burton -- Your mind is like a parachute, it works much better when it is open.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANV5k3rW62rGoXKD4m5meegEJ04T4b_v=QGCqBV5wuGxZjzCbg>