Skip to contentSkip to conversation

M-Audio Sonica support

DISCUSSION Stephen Hassard 3 participants 8 messages Aug 28, 2002 – Sep 4, 2002 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

I was trying to get my M-Audio Sonica to work under Alsa. It's a nifty little single channel out 24/96 USB audio device. Here's the product
page: http://www.m-audio.com/products/consumer/sonica.php

I'm running the CVS version of Alsa from within the last hour.

snd-usb-audio modprobes fine and doesn't give me any errors. /dev/dsp doesn't get created properly (snd-pcm-oss is loaded properly), not does /proc/asound/cards list anything ('--- no soundcards ---'). The device is properly detected by the linux kernel, as I get properly connect/disconnect messages. I'm using kernel v2.4.20pre4. The device is plugged into a UHCI controller (it's a USB 2.0 NEC controller).

I was taking a look around the source to see if I could add the Sonica device ID, but I can't seem to find where to hack it (if it's even needed). Anyhow, the device ID for the Sonica is vend/prod 0x763/0x2805. Any help would be greatly appreciated.

Thanks,
Stephen Hassard

-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim

#1 lore raw

At Wed, 28 Aug 2002 07:33:07 -0700,

Quoted 16 lines · Stephen Hassard

Hi,

I was trying to get my M-Audio Sonica to work under Alsa. It's a nifty little single channel out 24/96 USB audio device. Here's the product
page: http://www.m-audio.com/products/consumer/sonica.php

I'm running the CVS version of Alsa from within the last hour.

snd-usb-audio modprobes fine and doesn't give me any errors. /dev/dsp doesn't get created properly (snd-pcm-oss is loaded properly), not does /proc/asound/cards list anything ('--- no soundcards ---'). The device is properly detected by the linux kernel, as I get properly connect/disconnect messages. I'm using kernel v2.4.20pre4. The device is plugged into a UHCI controller (it's a USB 2.0 NEC controller).

Quoted 4 lines

I was taking a look around the source to see if I could add the Sonica device ID, but I can't seem to find where to hack it (if it's even needed). Anyhow, the device ID for the Sonica is vend/prod 0x763/0x2805. Any help would be greatly appreciated.

please show the output of lsusb. it will show the description of the connected devices, so we can check whether the device is compliant to the normal usb audio protocol.

Takashi

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

A message that is not in the archive (sent off-list or not yet received): 000601c25299$6e8ec740$0500a8c0@shwxp

#3 lore raw

At Mon, 2 Sep 2002 08:57:25 -0700,

Quoted 45 lines · Stephen Hassard

Hi Takashi,

Here's the output from lsusb for the Midiman Sonica ..

Quoted 1 line
Quoted 1 line
Quoted 1 line

Bus 004 Device 002: ID 0763:2805 Midiman
Device Descriptor:

   bLength                18
   bDescriptorType         1
   bcdUSB               1.00
   bDeviceClass          254
   bDeviceSubClass         1
   bDeviceProtocol         0
   bMaxPacketSize0        64
   idVendor           0x0763 Midiman
   idProduct          0x2805
   bcdDevice            1.00
   iManufacturer           1 Unknown
   iProduct                2 Unknown
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength           25
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0x40
       Self Powered
     MaxPower              200mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           0
       bInterfaceClass       254
       bInterfaceSubClass      1
       bInterfaceProtocol      0
       iInterface              3 RAM
   unknown descriptor type: 07 21 05 00 01 40 00
   Language IDs: (length=4)
      0409 English(US)
Quoted 4 lines

<<<

Please let me know if their is anything else I can help out with ..

hmm, the descriptor is apprently broken.
usually you'll see the list of interfaces, terminals, formats, etc. there.
the device might be non-standard one. if so, the current driver doesn't support it, unfortuantely.

Takashi

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

#4 lore raw
Quoted 13 lines · Takashi Iwai
Quoted 11 lines · Stephen Hassard

Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254
bInterfaceSubClass 1
bInterfaceProtocol 0
iInterface 3 RAM
unknown descriptor type: 07 21 05 00 01 40 00

Quoted 5 lines

hmm, the descriptor is apprently broken.
usually you'll see the list of interfaces, terminals, formats, etc. there.
the device might be non-standard one. if so, the current driver doesn't support it, unfortuantely.

bInterfaceClass 254 = "Application-Specific"
bInterfaceSubClass 1 = "Device Firmware Update"

And they bothered to give the interface a name ("RAM"). :-)

If it were a broken descriptor, it would be easy to make the correct information available with a quirk. In this case, however, we need the firmware and a loader.

The download protocol is described in the "USB Device Firmware Upgrade Specification". A loader might already exist, or is (relatively) easy to write.

For the firmware, we could _try_ to ask Midiman. But I think a USB snoop log from the Windows driver would have a higher probability of success. (Unfortunately, the bmAttributes field in the DFU functional descriptor indicates that the device is only capable of downloading, not uploading.)
If we have luck, the firmware is stored in a DFU file (not necessarily with that name).

HTH
Clemens

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

#5 lore raw

At Mon, 02 Sep 2002 19:24:14 +0200,

Quoted 21 lines · Clemens Ladisch
Quoted 13 lines · Takashi Iwai
Quoted 11 lines · Stephen Hassard

Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254
bInterfaceSubClass 1
bInterfaceProtocol 0
iInterface 3 RAM
unknown descriptor type: 07 21 05 00 01 40 00

Quoted 5 lines

hmm, the descriptor is apprently broken.
usually you'll see the list of interfaces, terminals, formats, etc. there.
the device might be non-standard one. if so, the current driver doesn't support it, unfortuantely.

Quoted 4 lines

bInterfaceClass 254 = "Application-Specific"
bInterfaceSubClass 1 = "Device Firmware Update"

And they bothered to give the interface a name ("RAM"). :-)

yep :)

Quoted 9 lines

If it were a broken descriptor, it would be easy to make the correct information available with a quirk. In this case, however, we need the firmware and a loader.

The download protocol is described in the "USB Device Firmware Upgrade Specification". A loader might already exist, or is (relatively) easy to write.

For the firmware, we could _try_ to ask Midiman.

this is not bad idea - midiman / m-audio has been enough friendly to us, so far...

Quoted 2 lines

But I think a USB snoop log from the Windows driver would have a higher probability of success.

or, a higher rate of success :)

Quoted 5 lines

(Unfortunately, the bmAttributes field in the
DFU functional descriptor indicates that the device is only capable of downloading, not uploading.)
If we have luck, the firmware is stored in a DFU file (not necessarily with that name).

Stephen, could you check whether any possible file eixsts on windows?

ciao,

Takashi

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

#6 lore raw
Quoted 7 lines
Quoted 4 lines

(Unfortunately, the bmAttributes field in the
DFU functional descriptor indicates that the device is only capable of downloading, not uploading.)
If we have luck, the firmware is stored in a DFU file (not

necessarily

Quoted 1 line

with that name).

Stephen, could you check whether any possible file eixsts on windows?

The closest thing in the archive seems to be a 6k binary, although I'm not exactly sure what I'm looking for :P

I've placed it here: http://hassard.net/ma005101.bin

You can download the Windows 2000/XP drivers here:
http://www.midiman.net/support/drivers/new/sonica_websetup.exe

If you take a look in your temp files directory while running the installer, it seems to have extracted the entire driver (mixed with the installed files).

later,
Steve

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390

#7 lore raw
In reply to Takashi Iwai
Quoted 5 lines · Takashi Iwai
Quoted 2 lines · Clemens Ladisch

If we have luck, the firmware is stored in a DFU file (not necessarily with that name).

Stephen, could you check whether any possible file eixsts on windows?

ma005101.bin (obviously ;-)

The following looks like standard USB audio descriptors (but I don't have the device to test it):

000620: 12 01 10 01 00 .....
000630: 00 00 08 63 07 05 20 01 01 01 02 00 01 09 02 15 ...c.. ......... 000640: 01 02 01 00 80 64 09 04 00 00 00 01 01 00 02 09 .....d.......... 000650: 24 01 00 01 28 00 01 01 0C 24 02 01 01 01 00 02 $...(....$...... 000660: 03 00 00 00 0A 24 06 02 01 01 01 02 02 00 09 24 .....$.........$ 000670: 03 03 01 03 00 02 00 09 04 01 00 00 01 02 00 00 ................ 000680: 09 04 01 01 01 01 02 00 00 07 24 01 01 01 01 00 ..........$..... 000690: 26 24 02 01 02 03 18 0A 40 1F 00 11 2B 00 E0 2E &$......@...+... 0006A0: 00 22 56 00 C0 5D 00 00 7D 00 44 AC 00 80 BB 00 ."V..]..}.D..... 0006B0: 88 58 01 00 77 01 09 05 03 09 40 02 01 00 00 07 .X..w.....@..... 0006C0: 25 01 01 01 DC 05 09 04 01 02 01 01 02 00 00 07 %............... 0006D0: 24 01 01 01 01 00 26 24 02 01 02 02 10 0A 40 1F $.....&$......@. 0006E0: 00 11 2B 00 E0 2E 00 22 56 00 C0 5D 00 00 7D 00 ..+...."V..]..}. 0006F0: 44 AC 00 80 BB 00 88 58 01 00 77 01 09 05 03 09 D......X..w..... 000700: 80 01 01 00 00 07 25 01 01 01 DC 05 09 04 01 03 ......%......... 000710: 01 01 02 00 00 07 24 01 01 01 01 20 26 24 02 03 ......$.... &$.. 000720: 02 02 10 0A 40 1F 00 11 2B 00 E0 2E 00 22 56 00 ....@...+...."V. 000730: C0 5D 00 00 7D 00 44 AC 00 80 BB 00 88 58 01 00 .]..}.D......X.. 000740: 77 01 09 05 03 09 80 01 01 00 00 07 25 01 01 01 w...........%... 000750: DC 05_12 01 00 01 FE 01 00 08 63 07 FF FF 01 01 ..........c..... 000760: 01 02 00 01 09 02 19 00 01 01 00 40 00 09 04 02 ...........@.... 000770: 00 00 FE 01 00 00 07 21 05 FF FF 20 00 04 03 09 .......!... .... 000780: 04 10 03 4D 00 2D 00 41 00 75 00 64 00 69 00 6F ...M.-.A.u.d.i.o
000790: 00 0E 03 53 00 6F 00 6E 00 69 00 63 00 61 00 ...S.o.n.i.c.a.

Now we need a DFU loader. The loader at http://at76c503a.sourceforge.net/
looks promising. I think I'll be able to munge it into a generic DFU loader.

HTH
Clemens

-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390