Hello, I'm trying to get my digisette AR100 mp3 player to work with linux and libusb and seem to have reached an impasse so I'm looking for suggestions on how to proceed. I had posted this message to the users mailing list, where a response from Brad Hards suggested that this list would be more appropriate.
I've saved off a few logs using snoopy pro and I'm trying to mimic them using libusb on linux. I couldn't use the usb robot script because it doesn't work with snoopy pro logs. I have to use snoopy pro because it seems to work with win XP which is the only win computer I have access to. What seems to be different about the USB device is that it first identifies it self as Vendor=05b4 ProdID=6001 Rev= 0.01 and then after a very specific sequence of 223 control transfers the device ProdID should change to 6002h. A number of the control transfers have bRequest as 4 (Reserved for future use?) Is the future now? Does this mean something? I got this sequence through snoopy pro and it seems to be identical every time. As a side note, it seems that the irock! 520 mp3 player uses the same chipset as the duo as it identifies it self the same way (Vendor=05b4 ProdID=6001 Rev= 0.01). Windows uses the "HMS30C6001" driver. This seems to belong to the Semiconductor Group of Hyundai Electronics Industries CO., LTD. After some extensive googling I came up with: http://www.hynix.com/eng/products/system_ic/sp/m_con/usb_1.jsp which actually states that the default is vendor=05b4 ID=6001 Anyway I wrote a script to extract the sequence of the 223 control transfers and generate c code in order to replay them back. It seems that everything works and all the usb_control_msg statements return numbs >= 0 but the ID of the device remains 6001 after all is said and done. I enabled debugging on libusb but didn't get much out of it. If someone wants to look at some of the log files I can tar up my work dir and send it off. I followed Brad's suggestion which was to look at ezUSB. Soft USB was kind of an eye opener for a novice like me and something like this might be happening here. However... I think the AR100 is more of a "set these registers and expect this behaviour" kind of device, configurable, as opposed to a programmable soft USB device like ezUSB. My questions: 1) What can I do next? Is there an easy way for me to get a "snoopy pro" like log file out of linux so I can compare the two? Any other suggestions? 2) In my snoopy log files several of the bRequests that are 0x04 have a length of 0, 8 or 12 yet I do not see a second data stage. I just see the status ack. Could snoopy pro be hiding the data stage because this is a reserved value? (I very very briefly looked at the snoopy pro source and saw nothing that corroborates that) 3) Is it possible that my 0x04 bRequests get filtered in Linux because they are reserved? I don't think so but I figured I'd ask anyway. I'm shooting in the dark here... Thanks, Sopho PS. Some more info I've managed to get about this device is here: http://mousikos.sourceforge.net/About_AR100.html __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
