Menu
▾
▴
libusb-win32-devel
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(27) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(19) |
Mar
(13) |
Apr
(15) |
May
(11) |
Jun
(17) |
Jul
(31) |
Aug
(45) |
Sep
(10) |
Oct
(40) |
Nov
(39) |
Dec
(45) |
| 2005 |
Jan
(113) |
Feb
(45) |
Mar
(38) |
Apr
(53) |
May
(11) |
Jun
(42) |
Jul
(56) |
Aug
(50) |
Sep
(32) |
Oct
(32) |
Nov
(47) |
Dec
(22) |
| 2006 |
Jan
(19) |
Feb
(32) |
Mar
(40) |
Apr
(40) |
May
(41) |
Jun
(44) |
Jul
(37) |
Aug
(51) |
Sep
(30) |
Oct
(30) |
Nov
(51) |
Dec
(20) |
| 2007 |
Jan
(7) |
Feb
(20) |
Mar
(17) |
Apr
(67) |
May
(13) |
Jun
(73) |
Jul
(16) |
Aug
(58) |
Sep
(29) |
Oct
(5) |
Nov
(74) |
Dec
(9) |
| 2008 |
Jan
(17) |
Feb
(12) |
Mar
(65) |
Apr
(22) |
May
(40) |
Jun
(32) |
Jul
(11) |
Aug
(8) |
Sep
(3) |
Oct
(41) |
Nov
(34) |
Dec
(12) |
| 2009 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(109) |
May
(11) |
Jun
(22) |
Jul
(21) |
Aug
(37) |
Sep
(5) |
Oct
(23) |
Nov
(7) |
Dec
(7) |
| 2010 |
Jan
(36) |
Feb
(40) |
Mar
(35) |
Apr
(45) |
May
(42) |
Jun
(104) |
Jul
(135) |
Aug
(50) |
Sep
(65) |
Oct
(110) |
Nov
(129) |
Dec
(75) |
| 2011 |
Jan
(105) |
Feb
(48) |
Mar
(93) |
Apr
(166) |
May
(169) |
Jun
(188) |
Jul
(106) |
Aug
(33) |
Sep
(85) |
Oct
(46) |
Nov
(102) |
Dec
(105) |
| 2012 |
Jan
(81) |
Feb
(115) |
Mar
(56) |
Apr
(93) |
May
(56) |
Jun
(77) |
Jul
(88) |
Aug
(52) |
Sep
(72) |
Oct
(16) |
Nov
(70) |
Dec
(70) |
| 2013 |
Jan
(23) |
Feb
(85) |
Mar
(38) |
Apr
(48) |
May
(40) |
Jun
(49) |
Jul
(33) |
Aug
(28) |
Sep
(66) |
Oct
(28) |
Nov
(28) |
Dec
(16) |
| 2014 |
Jan
(33) |
Feb
(58) |
Mar
(17) |
Apr
(50) |
May
(16) |
Jun
(24) |
Jul
(19) |
Aug
(32) |
Sep
(10) |
Oct
(10) |
Nov
(4) |
Dec
(10) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
(14) |
May
(1) |
Jun
(6) |
Jul
(16) |
Aug
(29) |
Sep
(6) |
Oct
(26) |
Nov
(10) |
Dec
|
| 2016 |
Jan
|
Feb
(20) |
Mar
(6) |
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
(16) |
Sep
(6) |
Oct
|
Nov
(15) |
Dec
|
| 2017 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
|
Feb
(8) |
Mar
(10) |
Apr
(16) |
May
|
Jun
(15) |
Jul
|
Aug
(3) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(6) |
Oct
(2) |
Nov
(4) |
Dec
|
| 2022 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(11) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
|
From: Thomas S. <th...@th...> - 2006-10-18 20:22:41
|
Ya, that did it. Thanks Stephan. T > -----Original Message----- > From: Stephan Meyer [mailto:ste...@we...] > Sent: Wednesday, October 18, 2006 10:44 AM > To: lib...@li... > Subject: Re: [Libusb-win32-devel] trouble installing libusb driver inf > > > Is this device a so called 'composite device' (a device > consisting of multiple interfaces / device nodes)? > If this is the case then you have to install libusb's driver > for the parent device node which is located in the device > manager under the 'USB Controller' section. The item is named > something like "USB composite device". > > Stephan > > > > I get an error when I try to install the device driver for > my device. By default it comes up as a USB Audio Device, but > I want to change it to a libusb driver, obviously. I do the > "update driver" from Device Manager and browse to the inf > file created with the inf-wizard, and then get this error: > > > > > > > > "specified location does not contain information about your > hardware" > > > > > > > > > > If I uninstall the device from the device manager, unplug > and plug it back in, it has an "!" for a little bit but then > returns to a USB audio device within 30 secs. > > > > Any ideas what's wrong? > > > > > > > > T > > |
|
From: Pavel S. <sav...@we...> - 2006-10-18 19:40:23
|
Hi2 all, i'm tryin to compile my programm with mingw32-g++ under WinXP, where i'm using libusb calls. The compilation and linking goes without errors or warnings. But my program cannot start and i dont know where is problem. Is there some known problems such types with libusb-win32 ??? Regards, Pavel |
|
From: Stephan M. <ste...@we...> - 2006-10-18 19:29:45
|
> I recently had a user ask for x64 USB support and shipped him off a new > *.inf file along with the x64 pieces from the 20060827 snapshot. He > reports that it works perfectly. The application is only 32 bit so I'm > not sure how much of libusb-win32-x64 we're actually exercising, but XP > was much happier with the updated .inf and x64 libs. Thanks! Sounds great! > > A question about building: I cross-build my app and all dependent > libraries from Linux using mingw. Until now I've happily been building > libusb-win32 as part of that process. But I notice the libusb Makefiles > don't seem to call for building the x64 components -- and I probably > don't have the right compiler available yet even if they did. The x64 version is currently build with Microsoft's compiler that comes with the DDK. As far as I know, neither mingw nor cygwin can be used to build native x64 apps. > > Any tips on how I might build the x64 pieces under mingw? For now I can > pull them out of the 20060827 snapshot release, but I'd like to get back > to my automated build-and-release script at some point... > > Thanks! > --Adam > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: Stephan M. <ste...@we...> - 2006-10-18 17:44:16
|
Is this device a so called 'composite device' (a device consisting of multiple interfaces / device nodes)? If this is the case then you have to install libusb's driver for the parent device node which is located in the device manager under the 'USB Controller' section. The item is named something like "USB composite device". Stephan > I get an error when I try to install the device driver for my device. By default it comes up as a USB Audio Device, but I want to change it to a libusb driver, obviously. I do the "update driver" from Device Manager and browse to the inf file created with the inf-wizard, and then get this error: > > > > "specified location does not contain information about your hardware" > > > > > If I uninstall the device from the device manager, unplug and plug it back in, it has an "!" for a little bit but then returns to a USB audio device within 30 secs. > > Any ideas what's wrong? > > > > T > > ----------------------------------------------------------------- > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > ----------------------------------------------------------------- > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: Stephan M. <ste...@we...> - 2006-10-18 17:28:31
|
>=20 > I'm looking at some SnoopyPro output, and (not being terribly > familiar with USB details), struggling to relate the information > it displays with either the USB spec., or the libusb interface. >=20 > An example transaction: >=20 > URB Header (length: 80) > SequenceNumber: 4 > Function: 0019 (VENDOR=5FENDPOINT) This is the URB function used by Microsoft's USB stack. Just ignore it, y= ou don't need it. >From ddk/usbdi.h: #define URB=5FFUNCTION=5FVENDOR=5FENDPOINT 0x0019 The packet you see is a CLEAR=5FFEATURE request (see USB spec, chapter 9). > PipeHandle: 00000000 >=20 > SetupPacket: > 0000: 00 01 00 00 01 00 00 00 > bmRequestType: 00 > DIR: Host-To-Device > TYPE: Standard > RECIPIENT: Device > bRequest: 01 > CLEAR=5FFEATURE >=20 > No TransferBuffer >=20 >=20 > Now things like bmRequestType and bRequest are explained directly > in the USB spec., but I can't find any reference to a "Function" code 0x= 19 > called VENDOR=5FENDPOINT (or any similar functions, such > as 0x00 SELECT=5FCONFIGURATION, 0x08 CONTROL=5FTRANSFER, > 0x0b GET=5FDESCRIPTOR=5FFROM=5FDEVICE etc.), nor can I see how one > would trigger such transactions using libusb. >=20 > How would I create a VENDOR=5FENDPOINT transaction above =3F >=20 > Can I do this with a call to usb=5Fcontrol=5Fmsg() =3F If so, > how do I setup for function 0x19, as the arguments to > usb=5Fcontrol=5Fmsg() seem to correspond to the bmRequestType > and bRequest fields documented in the USB spec., and > according to the above, have a value of 0x00 and 0x01, > rather than something like 0x42 and 0x01, that might seem > to be the right values for Vendor + Endpoint =3F How > would 0x42 relate to function 0x19 =3F >=20 > If not, what function call is appropriate =3F >=20 > Any help in pointing me in the right direction would > be much appreciated. >=20 > thanks, > Graeme Gill. >=20 >=20 > ------------------------------------------------------------------------= - > Using Tomcat but need to do more=3F Need to support web services, security= =3F > Get stuff done quickly with pre-integrated technology to make your job e= asier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geroni= mo > http://sel.as-us.falkag.net/sel=3Fcmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D121642= > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Viren-Scan f=FCr Ihren PC! Jetzt f=FCr jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/=3Fmc=3D022222 |
|
From: Thomas S. <th...@th...> - 2006-10-18 07:03:19
|
I get an error when I try to install the device driver for my device. By default it comes up as a USB Audio Device, but I want to change it to a libusb driver, obviously. I do the "update driver" from Device Manager and browse to the inf file created with the inf-wizard, and then get this error: "specified location does not contain information about your hardware" If I uninstall the device from the device manager, unplug and plug it back in, it has an "!" for a little bit but then returns to a USB audio device within 30 secs. Any ideas what's wrong? T |
|
From: Graeme G. <gr...@ar...> - 2006-10-18 05:18:13
|
I'm looking at some SnoopyPro output, and (not being terribly
familiar with USB details), struggling to relate the information
it displays with either the USB spec., or the libusb interface.
An example transaction:
URB Header (length: 80)
SequenceNumber: 4
Function: 0019 (VENDOR_ENDPOINT)
PipeHandle: 00000000
SetupPacket:
0000: 00 01 00 00 01 00 00 00
bmRequestType: 00
DIR: Host-To-Device
TYPE: Standard
RECIPIENT: Device
bRequest: 01
CLEAR_FEATURE
No TransferBuffer
Now things like bmRequestType and bRequest are explained directly
in the USB spec., but I can't find any reference to a "Function" code 0x19
called VENDOR_ENDPOINT (or any similar functions, such
as 0x00 SELECT_CONFIGURATION, 0x08 CONTROL_TRANSFER,
0x0b GET_DESCRIPTOR_FROM_DEVICE etc.), nor can I see how one
would trigger such transactions using libusb.
How would I create a VENDOR_ENDPOINT transaction above ?
Can I do this with a call to usb_control_msg() ? If so,
how do I setup for function 0x19, as the arguments to
usb_control_msg() seem to correspond to the bmRequestType
and bRequest fields documented in the USB spec., and
according to the above, have a value of 0x00 and 0x01,
rather than something like 0x42 and 0x01, that might seem
to be the right values for Vendor + Endpoint ? How
would 0x42 relate to function 0x19 ?
If not, what function call is appropriate ?
Any help in pointing me in the right direction would
be much appreciated.
thanks,
Graeme Gill.
|
|
From: Adam K. <akr...@ro...> - 2006-10-17 13:33:20
|
I recently had a user ask for x64 USB support and shipped him off a new *.inf file along with the x64 pieces from the 20060827 snapshot. He reports that it works perfectly. The application is only 32 bit so I'm not sure how much of libusb-win32-x64 we're actually exercising, but XP was much happier with the updated .inf and x64 libs. Thanks! A question about building: I cross-build my app and all dependent libraries from Linux using mingw. Until now I've happily been building libusb-win32 as part of that process. But I notice the libusb Makefiles don't seem to call for building the x64 components -- and I probably don't have the right compiler available yet even if they did. Any tips on how I might build the x64 pieces under mingw? For now I can pull them out of the 20060827 snapshot release, but I'd like to get back to my automated build-and-release script at some point... Thanks! --Adam |
|
From: amol s. <amo...@gm...> - 2006-10-16 21:38:35
|
Thanks, Stephan. It appears to be working fine as soon as I set the size to a multiple of 64 and increased the timeout. Amol On 10/15/06, Stephan Meyer <ste...@we...> wrote: > > > > 00000082 7.81223249 LIBUSB-DRIVER - transfer(): bulk or interrupt > transfer > > 00000083 7.81223631 LIBUSB-DRIVER - transfer(): direction in > > 00000084 7.81224346 LIBUSB-DRIVER - transfer(): endpoint 0x81 > > 00000085 7.81224823 LIBUSB-DRIVER - transfer(): size 4 > > Try setting size to 64. > > > 00000086 7.91219139 LIBUSB-DRIVER - transfer_complete(): 4 bytes > received > > 00000087 8.00169182 > > 00000088 8.00169849 > > 00000089 8.00170422 LIBUSB-DRIVER - transfer(): bulk or interrupt > transfer > > 00000090 8.00170898 LIBUSB-DRIVER - transfer(): direction in > > 00000091 8.00171471 LIBUSB-DRIVER - transfer(): endpoint 0x81 > > 00000092 8.00172043 LIBUSB-DRIVER - transfer(): size 1034 > > Try setting size to n * 64. > > > 00000093 8.10164165 LIBUSB-DRIVER - transfer_cancel(): timeout > error > > The request timed out (cancelled by the DLL). The device either didn't > send any data > or your timeout value was too low. > > > > 00000096 10.63291645 LIBUSB-DRIVER - get_descriptor(): buffer size > 21 > > 00000097 10.63292122 LIBUSB-DRIVER - get_descriptor(): type 0004 > > 00000098 10.63292408 LIBUSB-DRIVER - get_descriptor(): index 0000 > > 00000099 10.63293266 LIBUSB-DRIVER - get_descriptor(): language id > 0000 > > 00000100 10.63293743 LIBUSB-DRIVER - get_descriptor(): timeout > 1000 > > 00000101 10.63568306 LIBUSB-DRIVER - get_descriptor(): getting > descriptor failed: status: 0x0, urb-status: 0xc0000004 > > >From ddk/usbi.h: > #define USBD_STATUS_STALL_PID ((USBD_STATUS)0xC0000004L) > > > > > _____________________________________________________________________ > Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! > http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: Stephan M. <ste...@we...> - 2006-10-15 13:34:24
|
> 00000082 7.81223249 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer
> 00000083 7.81223631 LIBUSB-DRIVER - transfer(): direction in
> 00000084 7.81224346 LIBUSB-DRIVER - transfer(): endpoint 0x81
> 00000085 7.81224823 LIBUSB-DRIVER - transfer(): size 4
Try setting size to 64.
> 00000086 7.91219139 LIBUSB-DRIVER - transfer_complete(): 4 bytes received
> 00000087 8.00169182
> 00000088 8.00169849
> 00000089 8.00170422 LIBUSB-DRIVER - transfer(): bulk or interrupt transfer
> 00000090 8.00170898 LIBUSB-DRIVER - transfer(): direction in
> 00000091 8.00171471 LIBUSB-DRIVER - transfer(): endpoint 0x81
> 00000092 8.00172043 LIBUSB-DRIVER - transfer(): size 1034
Try setting size to n * 64.
> 00000093 8.10164165 LIBUSB-DRIVER - transfer_cancel(): timeout error
The request timed out (cancelled by the DLL). The device either didn't send any data
or your timeout value was too low.
> 00000096 10.63291645 LIBUSB-DRIVER - get_descriptor(): buffer size 21
> 00000097 10.63292122 LIBUSB-DRIVER - get_descriptor(): type 0004
> 00000098 10.63292408 LIBUSB-DRIVER - get_descriptor(): index 0000
> 00000099 10.63293266 LIBUSB-DRIVER - get_descriptor(): language id 0000
> 00000100 10.63293743 LIBUSB-DRIVER - get_descriptor(): timeout 1000
> 00000101 10.63568306 LIBUSB-DRIVER - get_descriptor(): getting descriptor failed: status: 0x0, urb-status: 0xc0000004
>From ddk/usbi.h:
#define USBD_STATUS_STALL_PID ((USBD_STATUS)0xC0000004L)
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
|
|
From: amol s. <amo...@gm...> - 2006-10-12 22:42:21
|
Hi Stephan,
Thanks for the reply. However, the first bulk_read is of =
4
bytes and that goes through without any problem. I am attaching my DebugVie=
w
log with this e-mail. I don't seem to understand why bulk transfer fails
though. The wMaxPacketSize of my BULK_IN Endpoint is 64 bytes.
00000014 2.10692835 LIBUSB-DRIVER - release_interface(): releasing al=
l
interfaces
00000015 2.11207414
00000016 2.11208963 LIBUSB-DRIVER - release_interface(): releasing al=
l
interfaces
00000017 2.11212420
00000018 2.11213517 LIBUSB-DRIVER - release_interface(): releasing al=
l
interfaces
00000019 2.11615133
00000020 2.11616182 LIBUSB-DRIVER - release_interface(): releasing al=
l
interfaces
00000021 2.12017155
00000022 2.12018180 LIBUSB-DRIVER - release_interface(): releasing al=
l
interfaces
00000023 2.12425089
00000024 2.12426281 LIBUSB-DRIVER - release_interface(): releasing al=
l
interfaces
00000025 2.12829304
00000026 2.12829566
00000027 2.12830019 LIBUSB-DRIVER - get_descriptor(): buffer size
256
00000028 2.12830448 LIBUSB-DRIVER - get_descriptor(): type 0003
00000029 2.12830806 LIBUSB-DRIVER - get_descriptor(): index 0000
00000030 2.12831187 LIBUSB-DRIVER - get_descriptor(): language id
0000
00000031 2.12831593 LIBUSB-DRIVER - get_descriptor(): timeout 1000
00000032 2.13291407
00000033 2.13291788
00000034 2.13292289 LIBUSB-DRIVER - get_descriptor(): buffer size
256
00000035 2.13292694 LIBUSB-DRIVER - get_descriptor(): type 0003
00000036 2.13293076 LIBUSB-DRIVER - get_descriptor(): index 0001
00000037 2.13293505 LIBUSB-DRIVER - get_descriptor(): language id
1033
00000038 2.13293934 LIBUSB-DRIVER - get_descriptor(): timeout 1000
00000039 2.14591622
00000040 2.14592028
00000041 2.14592648 LIBUSB-DRIVER - get_descriptor(): buffer size
256
00000042 2.14593196 LIBUSB-DRIVER - get_descriptor(): type 0003
00000043 2.14593673 LIBUSB-DRIVER - get_descriptor(): index 0000
00000044 2.14594245 LIBUSB-DRIVER - get_descriptor(): language id
0000
00000045 2.14594769 LIBUSB-DRIVER - get_descriptor(): timeout 1000
00000046 2.15092158
00000047 2.15092731
00000048 2.15093493 LIBUSB-DRIVER - get_descriptor(): buffer size
256
00000049 2.15094018 LIBUSB-DRIVER - get_descriptor(): type 0003
00000050 2.15094519 LIBUSB-DRIVER - get_descriptor(): index 0002
00000051 2.15095067 LIBUSB-DRIVER - get_descriptor(): language id
1033
00000052 2.15095592 LIBUSB-DRIVER - get_descriptor(): timeout 1000
00000053 2.16391397
00000054 2.16391802
00000055 2.16392303 LIBUSB-DRIVER - get_descriptor(): buffer size
256
00000056 2.16392708 LIBUSB-DRIVER - get_descriptor(): type 0003
00000057 2.16393137 LIBUSB-DRIVER - get_descriptor(): index 0000
00000058 2.16393518 LIBUSB-DRIVER - get_descriptor(): language id
0000
00000059 2.16393948 LIBUSB-DRIVER - get_descriptor(): timeout 1000
00000060 2.16890883
00000061 2.16891122
00000062 2.16891551 LIBUSB-DRIVER - get_descriptor(): buffer size
256
00000063 2.16891956 LIBUSB-DRIVER - get_descriptor(): type 0003
00000064 2.16892338 LIBUSB-DRIVER - get_descriptor(): index 0003
00000065 2.16892767 LIBUSB-DRIVER - get_descriptor(): language id
1033
00000066 2.16893196 LIBUSB-DRIVER - get_descriptor(): timeout 1000
00000067 2.18198442
00000068 2.18198848
00000069 2.18199253 LIBUSB-DRIVER - set_configuration(): configuratio=
n
1
00000070 2.18199682 LIBUSB-DRIVER - set_configuration(): timeout
5000
00000071 2.18200469
00000072 2.18200874 LIBUSB-DRIVER - claim_interface(): interface 0
00000073 6.45347595
00000074 6.45348120
00000075 6.45348740 LIBUSB-DRIVER - transfer(): bulk or interrupt
transfer
00000076 6.45349216 LIBUSB-DRIVER - transfer(): direction out
00000077 6.45349932 LIBUSB-DRIVER - transfer(): endpoint 0x02
00000078 6.45350456 LIBUSB-DRIVER - transfer(): size 3
00000079 6.45478201 LIBUSB-DRIVER - transfer_complete(): 3 bytes
transmitted
00000080 7.81221962
00000081 7.81222582
00000082 7.81223249 LIBUSB-DRIVER - transfer(): bulk or interrupt
transfer
00000083 7.81223631 LIBUSB-DRIVER - transfer(): direction in
00000084 7.81224346 LIBUSB-DRIVER - transfer(): endpoint 0x81
00000085 7.81224823 LIBUSB-DRIVER - transfer(): size 4
00000086 7.91219139 LIBUSB-DRIVER - transfer_complete(): 4 bytes
received
00000087 8.00169182
00000088 8.00169849
00000089 8.00170422 LIBUSB-DRIVER - transfer(): bulk or interrupt
transfer
00000090 8.00170898 LIBUSB-DRIVER - transfer(): direction in
00000091 8.00171471 LIBUSB-DRIVER - transfer(): endpoint 0x81
00000092 8.00172043 LIBUSB-DRIVER - transfer(): size 1034
00000093 8.10164165 LIBUSB-DRIVER - transfer_cancel(): timeout
error
00000094 10.63290405
00000095 10.63291073
00000096 10.63291645 LIBUSB-DRIVER - get_descriptor(): buffer size
21
00000097 10.63292122 LIBUSB-DRIVER - get_descriptor(): type 0004
00000098 10.63292408 LIBUSB-DRIVER - get_descriptor(): index 0000
00000099 10.63293266 LIBUSB-DRIVER - get_descriptor(): language id
0000
00000100 10.63293743 LIBUSB-DRIVER - get_descriptor(): timeout 1000
00000101 10.63568306 LIBUSB-DRIVER - get_descriptor(): getting
descriptor failed: status: 0x0, urb-status: 0xc0000004
00000102 13.12353706
00000103 13.12354660 LIBUSB-DRIVER - release_interface(): interface
0
00000104 13.12356758 LIBUSB-DRIVER - release_interface(): releasing
all interfaces
Can you see why?
Thanks,
Cheers
Amol
On 10/12/06, Stephan Meyer <ste...@we...> wrote:
>
>
>
> Hi,
> > My problem description is as follows:
> > My code bulk_writes once to the device and then bulk_reads twice
> from that device before writing to it again.
> > When I try reading the second time using usb_bulk_read, it returns
> an error message -116( when looked up in errno.h, it says "stale NFS file
> handle"). The first usb_bulk_read reads the data successfully. I must
> mention here that the second bulk_read requests a data 1034 bytes long. I
> don't know if this has anything to do with the problem.
>
> The error code 116 means ETIMEDOUT. This error is most likely caused by
> the data size of 1034 byte. Try setting the data size to a multiple of
> your endpoint
> descriptor's wMaxPacketSize value.
>
> >
> >
> > Does anyone know where I am going wrong?
> > Thanks,
> >
> > Cheers
> > Amol
> >
> > -----------------------------------------------------------------
> >
> -------------------------------------------------------------------------
> > 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=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> >
> > -----------------------------------------------------------------
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> >
>
>
> _______________________________________________________________________
> Viren-Scan f=FCr Ihren PC! Jetzt f=FCr jeden. Sofort, online und kostenlo=
s.
> Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=3D022222
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim=
o
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
|
|
From: Stephan M. <ste...@we...> - 2006-10-12 16:42:47
|
Hi, > My problem description is as follows: > My code bulk=5Fwrites once to the device and then bulk=5Freads twice fr= om that device before writing to it again.=20 > When I try reading the second time using usb=5Fbulk=5Fread, it returns = an error message -116( when looked up in errno.h, it says "stale NFS file = handle"). The first usb=5Fbulk=5Fread reads the data successfully. I must ment= ion here that the second bulk=5Fread requests a data 1034 bytes long. I don'= t know if this has anything to do with the problem. The error code 116 means ETIMEDOUT. This error is most likely caused by the data size of 1034 byte. Try setting the data size to a multiple of you= r endpoint descriptor's wMaxPacketSize value. >=20 >=20 > Does anyone know where I am going wrong=3F > Thanks, >=20 > Cheers > Amol >=20 > ----------------------------------------------------------------- > ------------------------------------------------------------------------= - > 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=3Fpage=3Djoin.php&p=3Dsourceforge&CID=3DDEVDE= V >=20 > ----------------------------------------------------------------- > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >=20 =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Viren-Scan f=FCr Ihren PC! Jetzt f=FCr jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/=3Fmc=3D022222 |
|
From: amol s. <amo...@gm...> - 2006-10-11 00:54:13
|
Hi,
My problem description is as follows:
My code bulk_writes once to the device and then bulk_reads twice from
that device before writing to it again.
When I try reading the second time using usb_bulk_read, it returns an
error message -116( when looked up in errno.h, it says "stale NFS file
handle"). The first usb_bulk_read reads the data successfully. I must
mention here that the second bulk_read requests a data 1034 bytes long. I
don't know if this has anything to do with the problem.
Does anyone know where I am going wrong?
Thanks,
Cheers
Amol
|
|
From: Stephan M. <ste...@we...> - 2006-10-09 17:24:49
|
To compile the driver follow these steps: 1.) download the driver's source code 2.) download an install MinGW and Msys 3.) open a Msys shell and type 'make' 4.) That's it! Stephan Hi, > I can't install libusb-win32 driver (version 0.1.10.1) on winXP when I compile it on my own pc(WinXP). It gives me error when I try to talk to it and also, when I view device manager, the device shows with a yellow tag. If I install binaries(version 0.1.10.1) downloaded from website, I can install the driver/device without any problem. Here are the details about the compilers I use: > > WINDDK 3790.1830 > BCC 5.5 (I don't know if I need this) > > MINGW 5.0.2 > > And finally, my observation when I run testlibusb_win.exe, the o/p is > > DLL version: 0.1.10.1 > Driver version: -1.-1.-1.-1 > > bus/device idVendor/idProduct > > This gives me a perfect o/p when I use already compiled/built binaries from libusb-win32 project. Can someone tell me where I am going wrong? > Thanks, > > Cheers > Amol > P.S.: It does get compiled successfully with the above libraries. > > ----------------------------------------------------------------- > ------------------------------------------------------------------------- > 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 > _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: Stephan M. <ste...@we...> - 2006-10-09 17:21:28
|
The documentation on the project web site is a bit outdated. To create an .inf file that matches your device just use the inf-wizard.exe tool that comes with the driver. Stephan >=20 > Hi, I need some help with the driver of the NXT, I bought it a week ago,= it's the Education set, I was about to buy the retail version, because of= the driver ( The education set has no software) but I noticed you have a = way to conect it to the computer, I am working on it, but I need some extr= a information or help with one step, and the next ones:=20 >=20 > Rename and edit the sample inf-file 'libusb.inf' to match your device(s)= (modify the vendor and product IDs, strings etc.). Create different inf-f= iles to install different types of devices (devices with different IDs).=20 >=20 > =20 >=20 >=20 > I think is a "c" file, but after scanning the usb ports I dont know what= to do with the information. Thx in advance.=20 >=20 > =20 >=20 > Mauricio=20 > Mexico >=20 > ----------------------------------------------------------------- > ------------------------------------------------------------------------= - > 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=3Fpage=3Djoin.php&p=3Dsourceforge&CID=3DDEVDE= V >=20 > ----------------------------------------------------------------- > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >=20 =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Viren-Scan f=FCr Ihren PC! Jetzt f=FCr jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/=3Fmc=3D022222 |
|
From: <hu...@ho...> - 2006-10-08 02:17:42
|
<html><div style='background-color:#ffffff'><DIV style="BACKGROUND-COLOR: #ffffff"> <P class=RTE>Hi, I need some help with the driver of the NXT, I bought it a week ago, it's the Education set, I was about to buy the retail version, because of the driver ( The education set has no software) but I noticed you have a way to conect it to the computer, I am working on it, but I need some extra information or help with one step, and the next ones: <BR></P> <UL> <LI> <DIV class=RTE><FONT color=#0000ff>Rename and edit the sample inf-file 'libusb.inf' to match your device(s) (modify the vendor and product IDs, strings etc.). Create different inf-files to install different types of devices (devices with different IDs). </FONT></DIV></LI></UL> <DIV class=RTE> </DIV> <DIV class=RTE><BR>I think is a "c" file, but after scanning the usb ports I dont know what to do with the information. Thx in advance. </DIV> <DIV class=RTE> </DIV> <DIV class=RTE>Mauricio <BR> Mexico</DIV></DIV></div></html> |
|
From: amol s. <amo...@gm...> - 2006-10-04 21:12:46
|
Hi,
I can't install libusb-win32 driver (version 0.1.10.1) on winXP when I
compile it on my own pc(WinXP). It gives me error when I try to talk to it
and also, when I view device manager, the device shows with a yellow tag. If
I install binaries(version 0.1.10.1) downloaded from website, I can install
the driver/device without any problem. Here are the details about the
compilers I use:
WINDDK 3790.1830
BCC 5.5 (I don't know if I need this)
MINGW 5.0.2
And finally, my observation when I run testlibusb_win.exe, the o/p is
DLL version: 0.1.10.1
Driver version: -1.-1.-1.-1
bus/device idVendor/idProduct
This gives me a perfect o/p when I use already compiled/built binaries
from libusb-win32 project. Can someone tell me where I am going wrong?
Thanks,
Cheers
Amol
P.S.: It does get compiled successfully with the above libraries.
|
|
From: Dan E. <Dan...@ne...> - 2006-09-29 08:59:23
|
This will only be a problem if you access the device through the handle yourself. I can't see anywhere in the code where this device pointer int the handle structure is accessed after the initial opening of the device. =20 I did think this was a problem at one point in time, but when I looked harder at the code I convinced myself it wasn't a problem and eventually tracked down the crash to something else. =20 Dan. ________________________________ From: lib...@li... [mailto:lib...@li...] On Behalf Of Mantz Steffen Sent: 28 September 2006 11:53 To: lib...@li... Subject: [Libusb-win32-devel] usb_find_devices invalidates usb_dev_handlewhen the device was removed Hi,=20 The problem arises in a multi threaded application. Thread #1 periodically checks for new and removed devices, while another thread handles an attached device. When a handled device is removed, usb_find_devices() deletes the devices. This invalidates the refrence to it in the usb_dev_handle, before the handler thread can be informed. Typically this leads to a crash. Any ideas? Thanks,=20 Steffen=20 |
|
From: Stephan M. <ste...@we...> - 2006-09-28 18:55:55
|
I tried the same on my system (WinXP, 2GHz CPU) and my test program
(code attached) consumes less than 5% of CPU resources.
But if I enable debugging by calling usb_set_debug(4) and if I connect
a tool such as DebugView to capture the debug messages then CPU
load goes up to 80%.
Try to disable debug messages by calling usb_set_debug(0) after usb_init().
My test program also calls usb_find_devices() from a seperate thread and
it doesn't crash (as you mentioned in your other mail). If I unplug my device
then the application just terminates.
The current DLL isn't fully thread safe but refreshing the device list from
a second thread shouldn't crash the DLL.
Which version of the DLL are you using? Have you tried one of the latest
development versions?
Stephan
>
> Hi,
>
>
> I'm encountering performance problems. The code below runs on a linux system with for abot 1400 cycles per second, not consuming a lot of CPU. This is near the theoretic maximum. Under windows it runs at less than 800 cycles, taking 70% of the CPU, mostly kernel times. Any ideas.
>
>
> for (;;) {
>
> while (usb_interrupt_read(MyHandle, 0x88, (char*)Buffer, sizeof(Buffer), 1000) < 0) ;
>
> // build Command
>
> usb_interrupt_write(MyHandle, 0x04, (char*)Command, 5, 1000);
>
> }
>
>
> Thanks,
>
> Steffen
>
> -----------------------------------------------------------------
> -------------------------------------------------------------------------
> 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
>
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
|
|
From: Mantz S. <sm...@ke...> - 2006-09-28 10:56:12
|
Hi,
I'm encountering performance problems. The code below runs on a linux
system with for abot 1400 cycles per second, not consuming a lot of CPU.
This is near the theoretic maximum. Under windows it runs at less than
800 cycles, taking 70% of the CPU, mostly kernel times. Any ideas.
for (;;) {
while (usb_interrupt_read(MyHandle, 0x88, (char*)Buffer,
sizeof(Buffer), 1000) < 0) ;
// build Command
usb_interrupt_write(MyHandle, 0x04, (char*)Command, 5, 1000);
}
Thanks,
Steffen
|
|
From: Mantz S. <sm...@ke...> - 2006-09-28 10:52:57
|
Hi, The problem arises in a multi threaded application. Thread #1 periodically checks for new and removed devices, while another thread handles an attached device. When a handled device is removed, usb_find_devices() deletes the devices. This invalidates the refrence to it in the usb_dev_handle, before the handler thread can be informed. Typically this leads to a crash. Any ideas? Thanks, Steffen |
|
From: <and...@nt...> - 2006-09-21 15:58:55
|
It is indeed a problem with the set_altinterface respectively with my = device! When I call set_altinterface only the first time, I can claim, = release, write and read as much as I want without problems. I think, there's some more firmware debugging to do... Thanks Stephan! Andreas -----Urspr=FCngliche Nachricht----- Von: lib...@li... = [mailto:lib...@li...] Im Auftrag von = Stephan Meyer Gesendet: Mittwoch, 20. September 2006 21:46 An: lib...@li... Betreff: Re: [Libusb-win32-devel] Read/write and release/claim_interface I don't think that your problems are cause by release/claim_interface. These commands don't send any data to the device. They just lock some = resources (the interfaces) in the driver. I think the problem seems to be the set_altinterface command. Does your firmware properly handle a set_interface request?=20 Does it reset the endpoint's data toggle bits when it receives such a = request? Stephan > Hi >=20 > I don't understand the behavior of subsequent read/write operations = when using usb_release_interface() and usb_claim_interface() between the = read/writes. > My test device is a AT90SUB1287 and loops the data from an OUT bulk = endpoint to an IN bulk endpoint. > I'm using the latest CVS source, but I had the same problem with the = official libusb-win32-snapshot 20060827. >=20 > This scenario works fine: > **************************** > - usb_open() > - usb_set_configuration() > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (multiple read/writes work fine) > - usb_bulk_read() > - usb_release_interface() > - usb_close() >=20 > This scenario gives me a timeout error, but read/write work after some = timeout errors again: > **************************** > - usb_open() > - usb_set_configuration() > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (works fine, I get the data on the device) > - usb_release_interface() > ** > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_read() (works fine, I get the data from the device) > - usb_release_interface() > ** > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (no failure (libusb), but I don't get any data on = the device) > - usb_release_interface() > ** > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (no failure (libusb), but I don't get any data on = the device) > - usb_bulk_read() (fails, timeout error) > - usb_bulk_write() (works fine, I get the data on the device) > - usb_bulk_read() (fails, timeout error) > - from now on all read/write are successful again > - usb_release_interface() > - usb_close() >=20 > **************************** >=20 > Is it not allowed to claim the interface again after release? > I'm wondering why writing to the device succeeds, although I don't get = any data on the device? I can write as many times as I want without = getting an error from libusb. The device can buffer only one transfer. > Strange is, that it starts working again after some subsequent = write/reads. >=20 > Any hints are appreciated! > Thanks, Andreas >=20 > ---------------------------------------------------------------------- > --- Take Surveys. Earn Cash. Influence the Future of IT Join=20 > SourceForge.net's Techsay panel and you'll get the chance to share=20 > your opinions on IT & business topics through brief surveys -- and=20 > earn cash=20 > = http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEV > DEV _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066 -------------------------------------------------------------------------= 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=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ Libusb-win32-devel mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
From: Stephan M. <ste...@we...> - 2006-09-20 19:45:58
|
I don't think that your problems are cause by release/claim_interface. These commands don't send any data to the device. They just lock some resources (the interfaces) in the driver. I think the problem seems to be the set_altinterface command. Does your firmware properly handle a set_interface request? Does it reset the endpoint's data toggle bits when it receives such a request? Stephan > Hi > > I don't understand the behavior of subsequent read/write operations when using usb_release_interface() and usb_claim_interface() between the read/writes. > My test device is a AT90SUB1287 and loops the data from an OUT bulk endpoint to an IN bulk endpoint. > I'm using the latest CVS source, but I had the same problem with the official libusb-win32-snapshot 20060827. > > This scenario works fine: > **************************** > - usb_open() > - usb_set_configuration() > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (multiple read/writes work fine) > - usb_bulk_read() > - usb_release_interface() > - usb_close() > > This scenario gives me a timeout error, but read/write work after some timeout errors again: > **************************** > - usb_open() > - usb_set_configuration() > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (works fine, I get the data on the device) > - usb_release_interface() > ** > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_read() (works fine, I get the data from the device) > - usb_release_interface() > ** > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (no failure (libusb), but I don't get any data on the device) > - usb_release_interface() > ** > - usb_claim_interface() > - usb_set_altinterface() > - usb_bulk_write() (no failure (libusb), but I don't get any data on the device) > - usb_bulk_read() (fails, timeout error) > - usb_bulk_write() (works fine, I get the data on the device) > - usb_bulk_read() (fails, timeout error) > - from now on all read/write are successful again > - usb_release_interface() > - usb_close() > > **************************** > > Is it not allowed to claim the interface again after release? > I'm wondering why writing to the device succeeds, although I don't get any data on the device? I can write as many times as I want without getting an error from libusb. The device can buffer only one transfer. > Strange is, that it starts working again after some subsequent write/reads. > > Any hints are appreciated! > Thanks, Andreas > > ------------------------------------------------------------------------- > 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 _____________________________________________________________________ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071&distributionid=000000000066 |
|
From: <and...@nt...> - 2006-09-20 09:57:25
|
Hi I don't understand the behavior of subsequent read/write operations when = using usb_release_interface() and usb_claim_interface() between the = read/writes. My test device is a AT90SUB1287 and loops the data from an OUT bulk = endpoint to an IN bulk endpoint. I'm using the latest CVS source, but I had the same problem with the = official libusb-win32-snapshot 20060827. This scenario works fine: **************************** - usb_open() - usb_set_configuration() - usb_claim_interface() - usb_set_altinterface() - usb_bulk_write() (multiple read/writes work fine) - usb_bulk_read() - usb_release_interface() - usb_close() This scenario gives me a timeout error, but read/write work after some = timeout errors again: **************************** - usb_open() - usb_set_configuration() - usb_claim_interface() - usb_set_altinterface() - usb_bulk_write() (works fine, I get the data on the device) - usb_release_interface() ** - usb_claim_interface() - usb_set_altinterface() - usb_bulk_read() (works fine, I get the data from the device) - usb_release_interface() ** - usb_claim_interface() - usb_set_altinterface() - usb_bulk_write() (no failure (libusb), but I don't get any data on = the device) - usb_release_interface() ** - usb_claim_interface() - usb_set_altinterface() - usb_bulk_write() (no failure (libusb), but I don't get any data on = the device) - usb_bulk_read() (fails, timeout error) - usb_bulk_write() (works fine, I get the data on the device) - usb_bulk_read() (fails, timeout error) - from now on all read/write are successful again - usb_release_interface() - usb_close() **************************** Is it not allowed to claim the interface again after release? I'm wondering why writing to the device succeeds, although I don't get = any data on the device? I can write as many times as I want without = getting an error from libusb. The device can buffer only one transfer. Strange is, that it starts working again after some subsequent = write/reads. Any hints are appreciated! Thanks, Andreas |
|
From: Peter F. (L. <las...@gm...> - 2006-09-19 19:38:45
|
Stephan Meyer wrote at 19.09.2006 : > What you're trying to do won't work, at least not with libusb. > libusb is not a USB filter or USB monitor. It's not possible to extract > data packets from a mouse's or any other device's data stream. > Take a look at Microsofts RawInput API, maybe this works: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/userinput/rawinput.asp > Stephan Thanks for your answer, now I can stop to fiddle around with the values from IconLib, to get only chrashes and mouse freeze. :-) Peter -- Newsreader: http://mesnews.net/index-gb.php Deutsche Hilfedatei: http://www.lastwebpage.de/download/mesnews-de.zip |
50 messages has been excluded from this view by a project administrator.
