TASCAM US-122mkII
Hi!
The good news is that I have 122mkII to play with, the bad news is that it doesn't work with the snd_usb_122l driver.
The probe function fails most likely in usb_stream_start(&us122l->sk),
The dmesg output:
...
status=-2
status=-2us122l_start error -14
snd-usb-us122l: probe of 1-2:1.1 failed with error -22
usbcore: registered new interface driver snd-usb-us122l
...
I've set up a windows machine with usbsnoop and captured the init log (I could upload it somewhere if anybody is interested). I would probably be able to help fix/write the driver with some guidance. Just now I'm trying to understand the log...
PS: I've send this mail to alsa-devel a couple of days ago, but without
being subscribed, does anybody do the screening on incomming mails?
Signature · 1 line
Cyril Hrubis
Quoted 3 lines · Cyril Hrubis
Hi!
The good news is that I have 122mkII to play with, the bad news is that it doesn't work with thesnd_usb_122ldriver.
IIRC, the 122mkII implements an entirely different USB protocol compared to its former version. Can you send your "lsusb -v" output?
Daniel
Hi!
Quoted 5 lines
Quoted 2 lines
The good news is that I have 122mkII to play with, the bad news is that it doesn't work with the
snd_usb_122ldriver.IIRC, the 122mkII implements an entirely different USB protocol compared to its former version. Can you send your "lsusb -v" output?
Attached.
As far as I understand it, there are two endpoints for audio and two for MIDI. The MIDI part seems to be initalized fine although I don't have any MIDI device to test it.
And in the log from windows machine the audio part does some intialization and then only buch of isochronous transfers.
Signature · 1 line
Cyril Hrubis
Bus 001 Device 005: ID 0644:8021 TEAC Corp. TASCAM US-122mkII Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0644 TEAC Corp. idProduct 0x8021 TASCAM US-122mkII bcdDevice 1.00 iManufacturer 1 TASCAM iProduct 2 US-122 MKII iSerial 3 no serial number bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 72
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 480mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x004e 1x 78 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 5
Transfer Type Isochronous
Synch Type Asynchronous
Usage Type Data
wMaxPacketSize 0x004e 1x 78 bytes
bInterval 1
bRefresh 0
bSynchAddress 0
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 4
bRefresh 0
bSynchAddress 0
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 4
bRefresh 0
bSynchAddress 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
Quoted 8 lines · Cyril Hrubis
Hi!
Quoted 5 lines
Quoted 2 lines
The good news is that I have 122mkII to play with, the bad news is that it doesn't work with the
snd_usb_122ldriver.IIRC, the 122mkII implements an entirely different USB protocol compared to its former version. Can you send your "lsusb -v" output?
Attached.
Ok, nothing that even remotely looks like class compliant descriptors.
Quoted 6 lines
As far as I understand it, there are two endpoints for audio and two for MIDI. The MIDI part seems to be initalized fine although I don't have any MIDI device to test it.
And in the log from windows machine the audio part does some intialization and then only buch of isochronous transfers.
Hmm, so it seems that our only option is really to look at these Windows dumps and reverse-engineer the protocol.
Daniel
Hi!
Quoted 9 lines
Quoted 6 lines
As far as I understand it, there are two endpoints for audio and two for MIDI. The MIDI part seems to be initalized fine although I don't have any MIDI device to test it.
And in the log from windows machine the audio part does some intialization and then only buch of isochronous transfers.
Hmm, so it seems that our only option is really to look at these Windows dumps and reverse-engineer the protocol.
Looks so, anybody could lend a helping hand (or a good HOWTO), I'm still new to USB, kernel USB subsystem and alsa.
Signature · 1 line
Cyril Hrubis
Hi!
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
And in the log from windows machine the audio part does some intialization and then only buch of isochronous transfers.
Hmm, so it seems that our only option is really to look at these Windows dumps and reverse-engineer the protocol.
Looks so, anybody could lend a helping hand (or a good HOWTO), I'm still new to USB, kernel USB subsystem and alsa.
Should be: "could anybody ... ?"
Signature · 1 line
Cyril Hrubis
Am Freitag, den 19.08.2011, 13:46 +0200 schrieb Daniel Mack:
Quoted 1 line · Cyril Hrubis
[…]
Quoted 9 lines
Quoted 6 lines
As far as I understand it, there are two endpoints for audio and two for MIDI. The MIDI part seems to be initalized fine although I don't have any MIDI device to test it.
And in the log from windows machine the audio part does some intialization and then only buch of isochronous transfers.
Hmm, so it seems that our only option is really to look at these Windows dumps and reverse-engineer the protocol.
Is there a chance to talk to the manufacturer or are they known to not cooperate? Cyril, did you contact their support?
Thanks,
Paul
Hi!
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
As far as I understand it, there are two endpoints for audio and two for MIDI. The MIDI part seems to be initalized fine although I don't have any MIDI device to test it.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
And in the log from windows machine the audio part does some intialization and then only buch of isochronous transfers.
Hmm, so it seems that our only option is really to look at these Windows dumps and reverse-engineer the protocol.
Is there a chance to talk to the manufacturer or are they known to not cooperate? Cyril, did you contact their support?
Hmm, haven't though of this, but that may be worth of try.
Signature · 1 line
Cyril Hrubis
Hi!
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
As far as I understand it, there are two endpoints for audio and two for MIDI. The MIDI part seems to be initalized fine although I don't have any MIDI device to test it.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
And in the log from windows machine the audio part does some intialization and then only buch of isochronous transfers.
Hmm, so it seems that our only option is really to look at these Windows dumps and reverse-engineer the protocol.
Is there a chance to talk to the manufacturer or are they known to not cooperate? Cyril, did you contact their support?
FYI: Wrote to their support more than a week ago and got no response
so far.
Signature · 1 line
Cyril Hrubis
Hi!
But still there are some good news. I've examined the pcb a bit and the USB interface is ISP1583 connected to the ATmega162 which is driving DA converters. So at least there is a documentation for the USB chip. And there seems to be ISP header for ATmega programming. And the ATmega code may be ripped of their firmware update binaries. Looks like I'll have some fun.
Signature · 1 line
Cyril Hrubis