libusb-win32-devel

[Libusb-win32-devel] Documentaion

[Peer R. <Nig...@gm...>]

Hello,

I have to write my Diplomwork for my studies. So i am interrested in writing
a German Documentation about the LIBUSB. The Thema should be mostly about
the Win32 Version. Is there Code and UML documentation is this work to do? I
would give my work then free to the Projekt. Are You interested on this?
When this work is done before, i have to choose another Theme for my work. 

Sorry about my bad English.


Grettings Peer

-- 
Echte DSL-Flatrate dauerhaft für 0,- Euro*!
"Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl

Re: [Libusb-win32-devel] Problem with usb_set_configuration

[Stephan M. <ste...@we...>]

> Hi,
>   My device is working fine under Linux. Using the exact same source code, I have a problem 
> when I call the usb_set_configuration() function. I observed that this function never returns.

The function should time out after 5s and cancel the request. 
Which version are you using? Can you try the latest version 
from the CVS?


> 
>   But what is strange is that as soon as my device is ready to transfer data to the PC 
> (responding to an external event not related to the PC), the function then unfreeezes and return 
> correctly. After that, each time I run my application, the function usb_set_configuration() returns 
> properly. But if I turn-off and then on my device, the problem re-appears.
> 
>   What can be wrong with my setup?
> 
>   Hugo Villeneuve.
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

RE: [Libusb-win32-devel] Problem with usb_set_configuration

[Dan E. <Dan...@ne...>]

Hugo Villeneuve wrote:
> Hi,
>   My device is working fine under Linux. Using the exact same source
> code, I have a problem when I call the usb_set_configuration()
> function. I observed that this function never returns. =20
>=20
>   But what is strange is that as soon as my device is ready to
> transfer data to the PC (responding to an external event not related
> to the PC), the function then unfreeezes and return correctly. After
> that, each time I run my application, the function
> usb_set_configuration() returns properly. But if I turn-off and then
> on my device, the problem re-appears.    =20
>=20
>   What can be wrong with my setup?

Sounds like you device is NAKing the set configuration request until the
external event occurs. I haven't checked, but maybe there's a timeout on
the linux one which there isn't on the PC.

Also I think there's a difference with respect to how linux and windows
deals with zero length packets. I think I remember seeing linux actually
sending a zero length packet on control transfers with a length of zero,
whereas I'm pretty sure windows doesn't. The device will see this
slightly differently.

Dan.

[Libusb-win32-devel] Problem with usb_set_configuration

[Hugo V. <hu...@hu...>]

Hi,
  My device is working fine under Linux. Using the exact same source code, I have a problem when I call the usb_set_configuration() function. I observed that this function never returns.

  But what is strange is that as soon as my device is ready to transfer data to the PC (responding to an external event not related to the PC), the function then unfreeezes and return correctly. After that, each time I run my application, the function usb_set_configuration() returns properly. But if I turn-off and then on my device, the problem re-appears.

  What can be wrong with my setup?

  Hugo Villeneuve.

RE: [Libusb-win32-devel] libusb win32 and bulk endpoints

[Dan E. <Dan...@ne...>]

1. Your device or protocol is buggy and has caused a buffer overrun on
the host controller. You must ensure that your device never sends more
data than is requested either by your arrangement or by requesting a
multiple of the maxpacket size. This is how USB works.
=20
2. An issue you may find when using multiple threads (on Windows) is
that when a thread exits, any outstanding IO is cancelled. This can
cause undesirable effects. You must make sure any asynchronous USB
traffic has completed before allowing a thread to die. As far as other
thread issues go, I haven't tested it to death so I'm not sure.
=20
3. The device can never send more than the maxpacket size in a packet,
so requesting a transfer of the maxpacket size is never going to cause a
buffer overrun.
=20
4. libusb does exactly what you tell it to, and passes on the request to
the USB subsystem. If you want to be able to receive arbitrary sized
transfers they must be a multiple of the maxpacket size. You can't
asynchronously receive arbitrary sized data directly consequetively into
a buffer, you need bounce buffers, then copy the amount recieved into
the destination.
=20
e.g. say you have a buffer:
=20
char buf[128], *ptr =3D buf;
=20
which you want to receive data into at an arbitrary rate from a device.
Assume the device is going to send 5 bytes then 10 bytes (but you don't
know that). You could do:
(I've made up the usb functions for simplicity)
=20
ptr +=3D usb_rec_sync(ptr, 64);
ptr +=3D usb_rec_sync(ptr, 64);
=20
would end up with what you want (assuming a maxpacket size of 64).
=20
You can't do this using async calls, since you've no way of knowing
where the first transter has got to. You could do:
=20
t1 =3D usb_rec_async(ptr, 64);
t2 =3D usb_rec_async(ptr+64, 64);
usb_waiton(t2);
copy ptr+64 to end of t1.
=20
I hope you see what I mean.
=20
Dan.

________________________________

From: lib...@li...
[mailto:lib...@li...] On Behalf Of
Kjell Eirik Andersen
Sent: 20 March 2006 11:38
To: lib...@li...
Subject: [Libusb-win32-devel] libusb win32 and bulk endpoints



=20

Hi !

=20

I have problems implementing SW for bulk transfers (read).

=20

1.	If I try a bulk read of 10 bytes and the device has armed the
endpoint with more than 10 bytes, usb_bulk_read returns -EIO (-5). At
this point libusb is stuck and I can not find any method to clean up.=20
2.	I have tried to implement bulk reads in a separate thread. I
have seen some signs that libusb is not thread-safe. Does anybody know
if libusb is thread-safe ?=20
3.	One thing that seems to work pretty well is to always perform
bulk reads with a size equal to the endpoint size.=20
4.	Shouldn't libusb do buffering of data, to help in situations
described in 1. above ?=20

=20

Any help would be greatly appreciated !

=20

Regards,

Kjell Eirik Andersen

[Libusb-win32-devel] libusb win32 and bulk endpoints

[Kjell E. A. <kje...@ta...>]

=20

Hi !

=20

I have problems implementing SW for bulk transfers (read).

=20

1.	If I try a bulk read of 10 bytes and the device has armed the
endpoint with more than 10 bytes, usb_bulk_read returns -EIO (-5). At
this point libusb is stuck and I can not find any method to clean up.
2.	I have tried to implement bulk reads in a separate thread. I
have seen some signs that libusb is not thread-safe. Does anybody know
if libusb is thread-safe ?
3.	One thing that seems to work pretty well is to always perform
bulk reads with a size equal to the endpoint size.
4.	Shouldn't libusb do buffering of data, to help in situations
described in 1. above ?

=20

Any help would be greatly appreciated !

=20

Regards,

Kjell Eirik Andersen

[Libusb-win32-devel] =?iso-8859-15?Q?Re:_[Libusb-win32-devel]_64-bit_Windows_libusb_build_-?= =?iso-8859-15?Q?_anyone_done_it_yet=3F?=

[Stephan M. <ste...@we...>]

Check out the latest version from the CVS. This version can be
compiled using the Server 2003 DDK x64 build environments.

I don't know if the CVS code actually runs on 64-bit Windows
because I have no 64-bit system to test it on.

Let me know if it works,

Stephan


> Hi.  Has anyone ported libusb-win32 to 64-bit Windows?
> I would rather not re-invent the wheel if I did not have to...
> 
> If anyone is willing to send me or point me to their code, 
> I would be very grateful.
> 
> I know that the big change in 64-bit Windows is that 
> pointers are now 64-bit.  But, many other data types are 
> still 32-bit...
> 
> Thanks,
> --Brian Hindman
> 
> > -----Original Message-----
> > From: lib...@li... 
> > [mailto:lib...@li...]On 
> > Behalf Of Peer Royla
> > Sent: Wednesday, March 01, 2006 3:59 AM
> > To: lib...@li...
> > Subject: [Libusb-win32-devel] compiling Error
> > 
> > 
> > Hello ,
> > 
> > I tried to compile the driver by WINDDK, wrote Makefile and SOURCES.
> > 
> > then type build and get 2000 errors like this:
> > 
> >  winddk\2600.1106\inc\ddk\wdm\wxp\usb100.h(137) : error 
> > C2061: syntax error
> > : identifier 'bDescriptorType'
> > 
> > dont know how to handle this.
> > 
> > Anybody know the Answer?
> > 
> > 
> > Peer
> > 
> > -- 
> > Telefonieren Sie schon oder sparen Sie noch?
> > NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
> > 
> > 
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking 
> > scripting language
> > that extends applications into web and mobile media. Attend 
> > the live webcast
> > and join the prime developer group breaking into this new 
> > coding territory!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
> dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.1.1/271 - Release Date: 2/28/2006
>  
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!		
Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130

[Libusb-win32-devel] libusb-win32 via #libusb

[Thomas S. <th...@th...>]

Hi all,

I've been trying to get a very simple example in c# to work with
libusb-win32.  I'm using the #libusb code from
http://www.icsharpcode.net/opensource/sharpusblib/.  The example is a
simple loop that iterates through the busses and prints out a bit of
info about each device.  It's very buggy.  Have you guys done any work
or had many requests for a .net wrapper for libusb-win32?  If so, can
you offer any suggestions for where the problem might be in the
example?  I downloaded the win32 source and compiled it with mingw and
tried some of the same stuff that is crashing the c# one, and it had NO
problems.  So, the problem appears to be with the c# code.  Do any of
you have any experience with getting .net to like libusb-win32?

T

[Libusb-win32-devel] 64-bit Windows libusb build - anyone done it yet?

[Brian H. <Bri...@da...>]

Hi.  Has anyone ported libusb-win32 to 64-bit Windows?
I would rather not re-invent the wheel if I did not have to...

If anyone is willing to send me or point me to their code, 
I would be very grateful.

I know that the big change in 64-bit Windows is that 
pointers are now 64-bit.  But, many other data types are 
still 32-bit...

Thanks,
--Brian Hindman

> -----Original Message-----
> From: lib...@li... 
> [mailto:lib...@li...]On 
> Behalf Of Peer Royla
> Sent: Wednesday, March 01, 2006 3:59 AM
> To: lib...@li...
> Subject: [Libusb-win32-devel] compiling Error
> 
> 
> Hello ,
> 
> I tried to compile the driver by WINDDK, wrote Makefile and SOURCES.
> 
> then type build and get 2000 errors like this:
> 
>  winddk\2600.1106\inc\ddk\wdm\wxp\usb100.h(137) : error 
> C2061: syntax error
> : identifier 'bDescriptorType'
> 
> dont know how to handle this.
> 
> Anybody know the Answer?
> 
> 
> Peer
> 
> -- 
> Telefonieren Sie schon oder sparen Sie noch?
> NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking 
> scripting language
> that extends applications into web and mobile media. Attend 
> the live webcast
> and join the prime developer group breaking into this new 
> coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&
dat=121642
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.1.1/271 - Release Date: 2/28/2006
 

[Libusb-win32-devel] Karl Achter is out of the office.

[<Kar...@pr...>]

I will be out of the office starting  08.03.2006 and will not return un=
til
09.03.2006.

I will respond to your message when I return. In urgent matter  please
contact  Markus Kraus
 (mar...@pr... ) or Johann Loesl
(joh...@pr...).

Ich bin zur Zeit nicht im B=FCro und werde Ihre Email nach meiner R=FCc=
kkehr
als bald als m=F6glich beantworten. In dringenden F=E4llen wenden Sie s=
ich
bitte an Herrn Kraus (mar...@pr...) oder Herrn L=F6sl
(Joh...@pr...).

Mit freundlichen Gr=FC=DFe
With best regards
Karl Achter



=

[Libusb-win32-devel] Looking 2GB and iPod Feel MP4, MP3 Player Buyer

[Cammy C. <ca...@ei...>]

Dear  Sir / Madam	
	
I would like to introduce myself as Stephen Y.K. Lee working in GoodsWell Limited which specializes
in MP3, MP4, HD Player.

You will be interested to hear that our EiONE MP3, MP4 with 2GB and iPod Feel Player, which is selling 
very strongly on the home market.

Because of its success in this country, we thought there might be sales potential abroad, and we would
welcome your advice as to whether, in your opinion, there is a market in your district.

If you were interested in our EiONE MP3, MP4 and HD Player or inspect the full range of our products.
please visit our web site or contact us for more information.	

Cammy Chan
Sales

Messenger ID:
Skype: goodswell
Yahoo: stephen_mail2002
MSN: st...@go...

Hong Kong Office:
Tel: +852 2139-5781
Fax: +852 2139-5782

Factory in China:
Tel: +86 755 61287071
Fax: +86 755 61287072

GoodsWell Limited
EiONE Digital

Send Date/Time: 7/3/2006 19:26:27

Re: [Libusb-win32-devel] Full speed bandwidth?

[Black M. <bla...@ho...>]

Thanks, i'll try messing around with the pics buffering some more


>From: Stephan Meyer <ste...@we...>
>Reply-To: lib...@li...
>To: lib...@li...
>Subject: Re: [Libusb-win32-devel] Full speed bandwidth?
>Date: Mon, 06 Mar 2006 19:44:53 +0100
>
>
>Here are some values I get with one of my test programs using
>the synchronous API and an old 8051 Cypress full speed chip
>(double buffering enabled, 64 bytes endpoint buffer):
>
>- the second column is the transfer size in bytes
>- the third column is the throughput in kbytes/s
>
>
>bulk write      |     64 |   32
>bulk write      |    640 |  312
>bulk write      |   6400 |  892
>bulk write      |  64000 | 1041
>bulk write      | 640000 | 1031
>bulk read       |     64 |   31
>bulk read       |    640 |  312
>bulk read       |   6400 |  893
>bulk read       |  64000 | 1041
>bulk read       | 640000 | 1031
>interrupt write |     64 |   32
>interrupt write |    640 |   56
>interrupt write |   6400 |   61
>interrupt write |  64000 |   62
>interrupt write | 640000 |   62
>interrupt read  |     64 |   31
>interrupt read  |    640 |   56
>interrupt read  |   6400 |   61
>interrupt read  |  64000 |   62
>interrupt read  | 640000 |   62
>
> >
> > Hi, im trying to do large bulk transfers to a full speed USB device 
>(12mbit)
> > Yet even in a dead loop, at best iv gotten 1.6mbps (yes, bits per 
>second)
> > with 2k transfer sizes. Think I might get any better with async? My 
>device
> > atm is a pic18f4550 without ping pong buffers enabled but id assume I 
>should
> > get better then 1.6mbps even without them (Unless maybe its stalling?) 
>and
> > the pic isent actualy doing anything with the data. 64byte buffer on the 
>pic
> > side
> > Is async even complete enough to use at all? When is 1.0 due out anyway? 
>And
> > I can't even seem to find any documenation about async :( I really don't
> > want to have to go to using the DDK directly.
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by xPML, a groundbreaking scripting 
>language
> > that extends applications into web and mobile media. Attend the live 
>webcast
> > and join the prime developer group breaking into this new coding 
>territory!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
>
>______________________________________________________________
>Verschicken Sie romantische, coole und witzige Bilder per SMS!
>Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by xPML, a groundbreaking scripting language
>that extends applications into web and mobile media. Attend the live 
>webcast
>and join the prime developer group breaking into this new coding territory!
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>_______________________________________________
>Libusb-win32-devel mailing list
>Lib...@li...
>https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] Full speed bandwidth?

[Stephan M. <ste...@we...>]

Here are some values I get with one of my test programs using 
the synchronous API and an old 8051 Cypress full speed chip 
(double buffering enabled, 64 bytes endpoint buffer):

- the second column is the transfer size in bytes
- the third column is the throughput in kbytes/s


bulk write      |     64 |   32
bulk write      |    640 |  312
bulk write      |   6400 |  892
bulk write      |  64000 | 1041
bulk write      | 640000 | 1031
bulk read       |     64 |   31
bulk read       |    640 |  312
bulk read       |   6400 |  893
bulk read       |  64000 | 1041
bulk read       | 640000 | 1031
interrupt write |     64 |   32
interrupt write |    640 |   56
interrupt write |   6400 |   61
interrupt write |  64000 |   62
interrupt write | 640000 |   62
interrupt read  |     64 |   31
interrupt read  |    640 |   56
interrupt read  |   6400 |   61
interrupt read  |  64000 |   62
interrupt read  | 640000 |   62

> 
> Hi, im trying to do large bulk transfers to a full speed USB device (12mbit)
> Yet even in a dead loop, at best iv gotten 1.6mbps (yes, bits per second) 
> with 2k transfer sizes. Think I might get any better with async? My device 
> atm is a pic18f4550 without ping pong buffers enabled but id assume I should 
> get better then 1.6mbps even without them (Unless maybe its stalling?) and 
> the pic isent actualy doing anything with the data. 64byte buffer on the pic 
> side
> Is async even complete enough to use at all? When is 1.0 due out anyway? And 
> I can't even seem to find any documenation about async :( I really don't 
> want to have to go to using the DDK directly.
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

RE: [Libusb-win32-devel] Full speed bandwidth?

[Dan E. <Dan...@ne...>]

Black Moon wrote:
> Hi, im trying to do large bulk transfers to a full speed USB device
> (12mbit) Yet even in a dead loop, at best iv gotten 1.6mbps (yes,
> bits per second) with 2k transfer sizes. Think I might get any better
> with async? My device atm is a pic18f4550 without ping pong buffers
> enabled but id assume I should get better then 1.6mbps even without
> them (Unless maybe its stalling?) and the pic isent actualy doing
> anything with the data. 64byte buffer on the pic side Is async even
> complete enough to use at all? When is 1.0 due out anyway? And I
> can't even seem to find any documenation about async :( I really
> don't want to have to go to using the DDK directly.        =20

Sounds like there's something wrong with your setup. You should get
better performance than that. I'd definitely try enabling ping pong
buffers though. The host will be trying to send the next packet
immediately and your device won't be able to receive it because it's
only just got the last one. This will immediately halve your rate, and
possibly worse if the host backs off on the endpoint.

Dan.

[Libusb-win32-devel] Full speed bandwidth?

[Black M. <bla...@ho...>]

Hi, im trying to do large bulk transfers to a full speed USB device (12mbit)
Yet even in a dead loop, at best iv gotten 1.6mbps (yes, bits per second) 
with 2k transfer sizes. Think I might get any better with async? My device 
atm is a pic18f4550 without ping pong buffers enabled but id assume I should 
get better then 1.6mbps even without them (Unless maybe its stalling?) and 
the pic isent actualy doing anything with the data. 64byte buffer on the pic 
side
Is async even complete enough to use at all? When is 1.0 due out anyway? And 
I can't even seem to find any documenation about async :( I really don't 
want to have to go to using the DDK directly.

[Libusb-win32-devel] Sutter?

[Black M. <bla...@ho...>]

Hi, im new to using libusb, but under windows I tryed the following code

int readval = usb_bulk_read(udev, 0x83, buff,64, 10);

(yadayadayada, some other code that has a timeout of 10ms)
And.. it causes my whole PC to 'stutter' even winamp has audio suttering 
artifacts. Thread was started with 'THREAD_PRIORITY_IDLE' and while it 
doesnt affect all mp3's it sure screws up alot of them, even tho I have a 
giant 300ms buffer set in winamp. So basicly I was wondering was A: is there 
a way to prevent this stuttering. B: is there a way to see if a read is even 
avilable before doing an actual read request? my device rarely sends 
packets, but when it does they have to be received asap. Iv commented out 
that line and the stuttering goes away. I realise this may be a problem with 
the win32 port of it, but I think an 'isdataavilable' sorta function might 
help in the core API. (Please don't use my nameing, I suck at nameing 
things!)

[Libusb-win32-devel] re:compiling error

[Peer R. <Nig...@gm...>]

Hope that will help,

Thanks Peer

-- 
Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer!
Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer

Re: [Libusb-win32-devel] compiling Error

[Robert M. <mar...@co...>]

Peer Royla wrote:


>  winddk\2600.1106

Get the current DDK.

 > The initial release of the Kernel-Mode Driver Framework is now 
available at
 > http://www.microsoft.com/whdc/default.mspx

This also contains the current DDK and is downloadable.

[Libusb-win32-devel] compiling Error

[Peer R. <Nig...@gm...>]

Hello ,

I tried to compile the driver by WINDDK, wrote Makefile and SOURCES.

then type build and get 2000 errors like this:

 winddk\2600.1106\inc\ddk\wdm\wxp\usb100.h(137) : error C2061: syntax error
: identifier 'bDescriptorType'

dont know how to handle this.

Anybody know the Answer?


Peer

-- 
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie

-- 
"Feel free" mit GMX FreeMail!
Monat für Monat 10 FreeSMS inklusive! http://www.gmx.net

Re: [Libusb-win32-devel] compiling Error

[Stephan M. <Ste...@ia...>]

Get the latest development snapshot. It has full DDK support
(including DDK Makefiles).
See file readme.txt in the ddk_make folder for details.

Stephan


> Hello ,
> 
> I tried to compile the driver by WINDDK, wrote Makefile and SOURCES.
> 
> then type build and get 2000 errors like this:
> 
>  winddk\2600.1106\inc\ddk\wdm\wxp\usb100.h(137) : error C2061: syntax 
error
> : identifier 'bDescriptorType'
> 
> dont know how to handle this.
> 
> Anybody know the Answer?
> 
> 
> Peer
> 
> -- 
> Telefonieren Sie schon oder sparen Sie noch?
> NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
language
> that extends applications into web and mobile media. Attend the live 
webcast
> and join the prime developer group breaking into this new coding 
territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Libusb-win32-devel] compiling Error

[Peer R. <Nig...@gm...>]

Hello ,

I tried to compile the driver by WINDDK, wrote Makefile and SOURCES.

then type build and get 2000 errors like this:

 winddk\2600.1106\inc\ddk\wdm\wxp\usb100.h(137) : error C2061: syntax error
: identifier 'bDescriptorType'

dont know how to handle this.

Anybody know the Answer?


Peer

-- 
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie

[Libusb-win32-devel] =?iso-8859-15?Q?Re:_[Libusb-win32-devel]_Newbie_question,_how_do_you_d?= =?iso-8859-15?Q?etect_the_availability_of_the_USB_device_for_extended_?= =?iso-8859-15?Q?period=3F?=

[Stephan M. <ste...@we...>]

> Is there a function like bool usb_ready() which returns true when the USB 
> device is okay and returns false when the USB device gets stuck?

Use usb_control_msg() to send a GET_STATUS request to the endpoint. 
See USB specification, section 9.4.5 for details.

Stephan

> 
> Thanks
>                                                                                         
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

[Libusb-win32-devel] Newbie question, how do you detect the availability of the USB device for extended period?

[chen h. <ch...@xa...>]

Hi, forks:

I've been using libusb win32 0.1.10 for last couple of months. It works great, while with a few problems.

Since our USB device needs to work for long period time, sometimes it seems the USB connection gets lost or stall.
I know we can call usb_rest(), usb_clear() to clear the thing up. But how do you detect there's a need for that?

Is there a function like bool usb_ready() which returns true when the USB device is okay and returns false when the USB device gets stuck?

Thanks
                                                                                        

RE: [Libusb-win32-devel] High Speed Bandwidth Capabilities

[Dan E. <Dan...@ne...>]

Maxpacket size varies for different endpoints and is specified in the
descriptors returned from the device. 512 bytes is that largest that a
bulk endpoint can be, and they usually are.
=20

        Hmm.  double buffering.  Are you talking device or host here?
Device has a 2K FIFO for usb outputs - We DMA directly from a FPGA Fifo
to the Device FIFO.=20
=20
 Host. Regardless of what the device is doing, if you haven't got data
queued in the system on the PC, there will be a gap when you are
informed that the previous transfer has finished and you queue the next
one.
 =20
          I've attempted with 4 buffers on the host.  We have a test set
up with a 3 MByte transaction to transfer from Device to host on an BULK
(or INTERRUPT) IN endpoint.  I'm not doing any processing with the data
just, handling the transactions and then queueing up another request.
I'm currently queueing up 4 separate asynch calls, each with a 64K
buffer.  Still haven't seen a performance change here.  I've never seen
a saturated bus as far as I can tell.  Is there a magic number for
packet size vs. request size that would optimize my throughput?  I
suppose I could still have a problem on my device end, but I think I can
handle the 20MByte/sec bandwidth easily.=20
=20
What sized packets is your device returning? Are the buffers always full
when you come to read them? You would probably benefit greatly by
looking at the data transfer on a USB analyzer.
=20
Dan.=20

Re: [Libusb-win32-devel] High Speed Bandwidth Capabilities

[Brett S. <bre...@ae...>]

Dan Ellis wrote:
> Brett Swimley wrote:
>   
>> Hi All,
>>
>> We have been using libusb-win32 with great success to communicate
>> with a high speed USB device based on the Freescale MCF547x processor
>> family.  
>> Now, we're to the point where we're trying to maximize the bandwidth
>> between the PC-host and the device. 
>>
>> I have a Bulk IN Endpoint with a packet size of 512 Bytes, which
>> AFAIK is the maximum packet size allowed for High Speed USB.  I have
>> also tried configuring this endpoint as an Interrupt Endpoint with a
>> packet size of 1024 Bytes.  My device can handle either of these
>> packet sizes with no problem.
>>     
>
> Bulk give you better performance, as interrupt endpoints are only polled
> periodically, whereas bulk transactions will attempt to saturate the
> bus.
>   
That's what I understood as well. I would like to use bulk if possible.  
Is it true that max packet size is 512 bytes under USB 2.0?
>     
>   
>> It *appears* that we can obtain about a 10MByte/sec transfer only.  I
>> get USB requests going out approximately every 100 (down from 125
>> usec).  I have tried both the synchronous and asynchronous APIs and
>> they both yield about the same result.  Ideally, we would like to
>> double the bandwidth to 20 MByte/Sec.    
>>     
>
> We've achieved more than that on an OUT endpoint with our product using
> async calls. Are you double buffering and providing enough space?
>
>   
Hmm.  double buffering.  Are you talking device or host here?  Device 
has a 2K FIFO for usb outputs - We DMA directly from a FPGA Fifo to the 
Device FIFO.
>> Is this possible with libusb-win32?  Are there any configuration or
>> endpoint settings that I could change to optimize the bandwidth (I
>> have control over the device so can change things).  Or, is it
>> strictly a function of my hardware?  I'm currently testing on a Dell
>> Dimension 4600 with a 2.8 GHz Pentium4, and a fully patched version
>> of Windows XP Professional.     
>>
>> Would multiple IN endpoints help maximize the bandwidth?  I can add
>> another endpoint if this would help. 
>>     
>
> Make sure your device is always sending maxpacket sized packets whenever
> possible, the transfer will end on a partial one. Request more data than
> the maxpacket size, e.g. request 16kB at a time. This allows the host
> controller to back-to-back the transactions. If you get a partial or
> empty transaction the transfer will be retired early, so your device can
> signal immediate attention by doing this.
>
> You'll still get dips in transmission when the call returns and the next
> one is being queued up. You can reduce this by queueing up more than one
> buffer and using asynchronous calls.
>
> Dan.
>
>   
I've attempted with 4 buffers on the host.  We have a test set up with a 
3 MByte transaction to transfer from Device to host on an BULK (or 
INTERRUPT) IN endpoint.  I'm not doing any processing with the data 
just, handling the transactions and then queueing up another request. 
I'm currently queueing up 4 separate asynch calls, each with a 64K 
buffer.  Still haven't seen a performance change here.  I've never seen 
a saturated bus as far as I can tell.  Is there a magic number for 
packet size vs. request size that would optimize my throughput?  I 
suppose I could still have a problem on my device end, but I think I can 
handle the 20MByte/sec bandwidth easily.

Thanks for the response.

Brett

>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>