> T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=08e3 ProdID=fffb Rev= 0.00 > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > I: If#= 0 Alt= 1 #EPs=13 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=10ms > [...] > E: Ad=0a(O) Atr=01(Isoc) MxPS= 16 Ivl=1ms > I: If#= 0 Alt= 2 #EPs=13 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > E: Ad=81(I) Atr=03(Int.) MxPS= 64 Ivl=10ms > [...] > E: Ad=0a(O) Atr=01(Isoc) MxPS= 16 Ivl=1ms
This looks very much like an EZ-USB chip in pre-enumerated state. These chips (Cypress AN2131) load their firmware via USB into internal RAM and re-enumerate with different descriptors.
See http://www.linux-usb.org/ezusb/ for details.
I.e. without the firmware the unit is absolutely useless (except for hacking, of course :-) Maybe the vendor is willing to provide the firmware as a separate file so you can download it with the help of fxload (see http://linux-hotplug.sourceforge.net/?selected=usb) or the Ezusb-2131 driver from http://ezusb2131.sourceforge.net/
Alternatively, you could trace the firmware download from within Windows with USBsnoopy.
Once you have the firmware running, you can start to figure out the real protocol of this unit.
Hope this helps
Arnim
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
