Re: log usb device traffic, reverse engineer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Vladimir Komendantsky wrote:
> > Many M-Audio devices use DFU; in that case, the protocol is known.
> > Please show the output of "lsusb -v".
> 
>       ...
>       bInterfaceClass       254 Application Specific Interface
>       bInterfaceSubClass      1 Device Firmware Update

This is indeed DFU.  The specification can be found at
<http://www.usb.org/developers/devclass_docs/DFU_1.1.pdf>.

There is a DFU downloading tool for other M-Audio devices:
<http://usb-midi-fw.cvs.sourceforge.net/viewvc/usb-midi-fw/madfu-firmware/madfuload.c?view=markup>

There might be a .bin file in the Windows upgrade package that you
could use directly.  However, I don't know if this device has any
quirks that would make it incompatible.

> > Is it class compliant?
> 
> It's said to be in the manual. In jack, it announces itself as
> "20:ProKeys Sono 88" with two input ports "MIDI 1" and "MIDI 2" and
> one output port "MIDI 1". However, the manual also describes an audio
> input port (a USB audio connection from a computer to the keyboard).

According to the descriptors, it has both audio playback and capture.

> So far I cannot connect it.

Does it show up in the output of "aplay -l" and "arecord -l"?
Does playing/recording with these tools work?


Best regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux