USB Adapter for XM Direct

timekiller · 10-15-2007, 09:31 PM

Anyone buy the mp3car usb adapter for xm ? I just bought both units and am having trouble getting my linux both to recognize it. I tried it in winblows and it seems to work (and seems to use the ftdi usb-serial driver). I have ftdi compiled into my kernel, but my system is not associating the device with the driver. I have manually loaded the module, but when I plug in the device in, this is all i get in dmesg:

-- modprobe ftdi_sio --
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
-- plug in the unit --
usb 2-2: new full speed USB device using ohci_hcd and address 5
usb 2-2: configuration #1 chosen from 1 choice

Notice no /dev/ttyUSB creation ? lsusb -v gives me this:

Bus 002 Device 005: ID 6846:0002
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x6846
idProduct 0x0002
bcdDevice 6.00
iManufacturer 1 Mp3Car
iProduct 2 Mp3Car USB Adapter for XM Direct
iSerial 3 A1PRFSIQ
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 Mp3Car USB Adapter for XM Direct
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0

So I know the device is there, I think I just need to know how to make the kernel know the unit is an ftdi device.

So - anyone else try this ?

timekiller · 10-15-2007, 11:21 PM

I love answering my own questions. Here is how you make the mp3car usb module work in linux

(requires recompiling the ftdi kernel module):

2 files to edit :
ftdi_sio.h
ftdi_sio.c

located in /usr/src/linux/drivers/usb/serial (your path may vary)

You have to 'tell' ftdi the vendor and product ID of the device (look at my lsusb output above). Here's a patch to add the lines you need:

diff -ru linux-2.6.20-gentoo-r8/drivers/usb/serial/ftdi_sio.c linux-2.6.20-gentoo-r8-xmpatch/drivers/usb/serial/ftdi_sio.c
--- linux-2.6.20-gentoo-r8/drivers/usb/serial/ftdi_sio.c 2007-10-15 23:15:20.000000000 -0400
+++ linux-2.6.20-gentoo-r8-xmpatch/drivers/usb/serial/ftdi_sio.c 2007-10-15 22:13:57.000000000 -0400
@@ -495,6 +495,7 @@
{ USB_DEVICE(FTDI_VID, FTDI_ATIK_ATK16HRC_PID) },
{ USB_DEVICE(KOBIL_VID, KOBIL_CONV_B1_PID) },
{ USB_DEVICE(KOBIL_VID, KOBIL_CONV_KAAN_PID) },
+ { USB_DEVICE(XMD1000_VID, XMD1000_PID) },
{ USB_DEVICE(POSIFLEX_VID, POSIFLEX_PP7000_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_TTUSB_PID) },
{ USB_DEVICE(FTDI_VID, FTDI_ECLO_COM_1WIRE_PID) },
diff -ru linux-2.6.20-gentoo-r8/drivers/usb/serial/ftdi_sio.h linux-2.6.20-gentoo-r8-xmpatch/drivers/usb/serial/ftdi_sio.h
--- linux-2.6.20-gentoo-r8/drivers/usb/serial/ftdi_sio.h 2007-10-15 23:15:09.000000000 -0400
+++ linux-2.6.20-gentoo-r8-xmpatch/drivers/usb/serial/ftdi_sio.h 2007-10-15 22:04:02.000000000 -0400
@@ -166,6 +166,12 @@
#define KOBIL_CONV_KAAN_PID 0x2021 /* KOBIL_Konverter for KAAN */

/*
+ * Mp3Car Usb XM Direct
+ */
+#define XMD1000_VID 0x6846
+#define XMD1000_PID 0x0002
+
+/*
* Icom ID-1 digital transceiver
*/

once the patch is applied, recompile either the whole kernel, or just the module and install it. now reboot (to make sure the new kernel works) and plug in the usb line. dmesg should show that /dev/ttyUSB0 was created. Then you can use xmpcr2 http://www.files-library.com/files/XMPCR2.html to control the xm direct unit.

Put another check in the column of carpc hardware that works in linux

I'll be updating my carpc page with a more detailed write up if anyone needs it.