|
From: Dan M. <dan...@gm...> - 2007-04-11 21:13:43
|
Hello,
Stephan, thank you for all the information. I'll try to contact the
manufacturer as you suggested, but this will certainly take a lot of time.
Meanwhile, I'll try to workaround.
But I question raised in my mind: these devices have four endpoints. Two
isochronous (0x01) and two bulk (0x02), isn't that right? The endpoints I'm
using are isochronous and they work fine until I have the bandwidth issue.
But whenever I try to use the other two endpoints, the application just
freezes. There's no error message, no nothing. The program stops and I can't
even close it using Window's task manager. Do you have any idea why that
happens? If I could use the bulk endpoints, at least the bandwidth wouldn't
be a problem anymore, right?
here goes the testlib's log again:
bus/device idVendor/idProduct
bus-0/\\.\libusb0-0001--0x0547-0x1002 0547/1002
- Manufacturer : Micro-Star
- Product : USB TESTER
wTotalLength: 46
bNumInterfaces: 1
bConfigurationValue: 1
iConfiguration: 0
bmAttributes: 80h
MaxPower: 50
bInterfaceNumber: 0
bAlternateSetting: 0
bNumEndpoints: 4
bInterfaceClass: 255
bInterfaceSubClass: 0
bInterfaceProtocol: 0
iInterface: 0
bEndpointAddress: 02h
bmAttributes: 01h
wMaxPacketSize: 1024
bInterval: 1
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 04h
bmAttributes: 02h
wMaxPacketSize: 512
bInterval: 0
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 86h
bmAttributes: 01h
wMaxPacketSize: 1024
bInterval: 1
bRefresh: 0
bSynchAddress: 0
bEndpointAddress: 88h
bmAttributes: 02h
wMaxPacketSize: 512
bInterval: 0
bRefresh: 0
bSynchAddress: 0
Cheers!
Dan
On 4/11/07, Stephan Meyer <ste...@we...> wrote:
>
>
> > So, for what I understood, I only have two options:
> >
> > 1 - Get another EHCI Host controller, so I can split the devices.
> >
>
> That would be a workaround, but no solution. A new firmware would
> be a solution.
>
> > 2 - Fix the firmware, so that the default interface setting has non
> isochrounous endpoints.
> >
> > Is that correct?
> > If so, do you know any tool to edit the firmware? The hardware I'm using
> was not made by me, so I'll
> > something to change ther firmware.
>
> You need the firmware's source code to fix it, unless you want to spend
> endless
> hours reverse engineering hex files.
> Apart from that, by fixing the firmware on your own you will void the
> manufacturer's
> warranty.
>
> But, what about a third option?:
>
> Contact the manufacturer, tell them about the broken firmware and ask
> for a software update. If they won't do this, then send the device back
> and
> request a refund.
>
> Stephan
>
>
>
>
>
> _______________________________________________________________
> SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
> kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
|