libusb-win32-devel

Re: [Libusb-win32-devel] Cannot retrieve configuration descriptor

[Winge M. <mic...@fr...>]

Thanks Dan I will try this.
=20

Best regards/Mit freundlichen Gr=FCssen

Michael Winge

MSG EMEA General Applications

Tel:       +44(0)1355355547
Mobile:  +44(0)7834020228
Email:    mic...@fr... =
<mailto:mic...@fr...>  =
<mailto:mic...@fr...>=20

Registered address:
Freescale Semiconductor UK Ltd
Colvilles Road
East Kilbride
Glasgow
Scotland
G75 OTG

Registration number: SC262720
VAT number: GB831329053

This mail is classified:
Freescale Confidential Proprietary ( )
Freescale Internal Use Only        (X)
General Business Information      ( )=20

=20

________________________________

From: lib...@li... =
[mailto:lib...@li...] On Behalf Of =
Dan Ellis
Sent: 24 January 2008 16:55
To: lib...@li...
Subject: Re: [Libusb-win32-devel] Cannot retrieve configuration =
descriptor


Hi Michael,

The value should get set during this function:

void usb_fetch_and_parse_descriptors(usb_dev_handle *udev)
{
  struct usb_device *dev =3D udev->device;
  int i;

  if (dev->descriptor.bNumConfigurations > USB_MAXCONFIG) {
    if (usb_debug >=3D 1)
      fprintf(stderr, "Too many configurations (%d > %d)\n", =
dev->descriptor.bNumConfigurations, USB_MAXCONFIG);
    return;
  }

  if (dev->descriptor.bNumConfigurations < 1) {
    if (usb_debug >=3D 1)
      fprintf(stderr, "Not enough configurations (%d < %d)\n", =
dev->descriptor.bNumConfigurations, 1);
    return;
  }

  dev->config =3D (struct usb_config_descriptor =
*)malloc(dev->descriptor.bNumConfigurations * sizeof(struct =
usb_config_descriptor));
  if (!dev->config) {
    if (usb_debug >=3D 1)
      fprintf(stderr, "Unable to allocate memory for config =
descriptor\n");
    return;
  }
  ...


So I can only see it going wrong if the device descriptor doesn't have =
the correct value for bNumConfigurations. Anyway, you may find more =
information if you set the environment variable USB_DEBUG to 3 before =
calling your code which links with the DLL.=20

regards,

Dan.

Winge Michael wrote:=20

	Hi Dan,
	=20
	I do not have problem with the usb_get_descriptor command. This works =
find. I have a problem that the driver cannot access the configuration =
of my device with the  "config" pointer in "struct usb_device". The =
"config" pointer is always zero. I guess this pointer will be assigned =
during the call of usb_get_busses(). The problem I think is somewhere =
there.
	=20
	My call of usb_get_descriptor is
	usb_get_descriptor(JM128MMT_devh,2,1,Buff,25);
	=20
	=20
	Micha

	Best regards/Mit freundlichen Gr=FCssen

	Michael Winge
=09
	MSG EMEA General Applications

	Tel:       +44(0)1355355547
	Mobile:  +44(0)7834020228
	Email:    mic...@fr... =
<mailto:mic...@fr...>=20
=09
	Registered address:
	Freescale Semiconductor UK Ltd
	Colvilles Road
	East Kilbride
	Glasgow
	Scotland
	G75 OTG

	Registration number: SC262720
	VAT number: GB831329053
=09
	This mail is classified:
	Freescale Confidential Proprietary ( )
	Freescale Internal Use Only        (X)
	General Business Information      ( )=20

	=20

________________________________

	From: lib...@li... =
[mailto:lib...@li...] On Behalf Of =
Dan Ellis
	Sent: 24 January 2008 16:09
	To: lib...@li...
	Subject: Re: [Libusb-win32-devel] Cannot retrieve configuration =
descriptor
=09
=09
	What is the syntax of the usb_get_descriptor command you are using? =
What is the index of the configuration, and what is the bValue in the =
configuration when you retrieve it? There was a bug in libusb around how =
these values were used which was fixed sometime over a year ago.
=09
	Dan.
=09
	Winge Michael wrote:=20

		I still face the same problem which I have mention in the email with =
the subject " Problem with libusb driver version 0.1.12.1" to the =
lib...@li... email list.
		=20
		I installed my device driver (*.inf) and test my driver with =
TestLibUsb. TestLibUsb displays idVendor and idProduct. That means to me =
that the device is working since driver has access to the device =
descriptor. The problem is that the driver cannot retrieve the =
configuration of my device.
		During debugging my application I found out that "config" pointer in =
"struct usb_device" is 0.
		=20
		I changed my window application so that I try to get the configuration =
with the libusb API "usb_get_descriptor" and it works. I get the =
configuration interface and endpoint descriptors.
		=20
		What could be the reason why libusb driver assign 0 to the "config" =
pointer in "struct usb_device"?
		=20
		Thank you for your help!
		=20
		Micha
		=20

		Best regards/Mit freundlichen Gr=FCssen

		Michael Winge
	=09
		MSG EMEA General Applications

		Tel:       +44(0)1355355547
		Mobile:  +44(0)7834020228
		Email:    mic...@fr... =
<mailto:mic...@fr...>=20
	=09
		Registered address:
		Freescale Semiconductor UK Ltd
		Colvilles Road
		East Kilbride
		Glasgow
		Scotland
		G75 OTG

		Registration number: SC262720
		VAT number: GB831329053
	=09
		This mail is classified:
		Freescale Confidential Proprietary ( )
		Freescale Internal Use Only        (X)
		General Business Information      ( )=20

		=20

Re: [Libusb-win32-devel] Cannot retrieve configuration descriptor

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

Hi Michael,

The value should get set during this function:

void usb_fetch_and_parse_descriptors(usb_dev_handle *udev)
{
  struct usb_device *dev = udev->device;
  int i;

  if (dev->descriptor.bNumConfigurations > USB_MAXCONFIG) {
    if (usb_debug >= 1)
      fprintf(stderr, "Too many configurations (%d > %d)\n", 
dev->descriptor.bNumConfigurations, USB_MAXCONFIG);
    return;
  }

  if (dev->descriptor.bNumConfigurations < 1) {
    if (usb_debug >= 1)
      fprintf(stderr, "Not enough configurations (%d < %d)\n", 
dev->descriptor.bNumConfigurations, 1);
    return;
  }

  dev->config = (struct usb_config_descriptor 
*)malloc(dev->descriptor.bNumConfigurations * sizeof(struct 
usb_config_descriptor));
  if (!dev->config) {
    if (usb_debug >= 1)
      fprintf(stderr, "Unable to allocate memory for config descriptor\n");
    return;
  }
  ...


So I can only see it going wrong if the device descriptor doesn't have 
the correct value for bNumConfigurations. Anyway, you may find more 
information if you set the environment variable USB_DEBUG to 3 before 
calling your code which links with the DLL.

regards,

Dan.

Winge Michael wrote:
> Hi Dan,
>  
> I do not have problem with the usb_get_descriptor command. This works 
> find. I have a problem that the driver cannot access the configuration 
> of my device with the  "config" pointer in "struct usb_device". 
> The "config" pointer is always zero./ /I guess this pointer will be 
> assigned during the call of usb_get_busses(). The problem I think is 
> somewhere there.
>  
> My call of usb_get_descriptor is
> usb_get_descriptor(JM128MMT_devh,2,1,Buff,25);
>  
>  
> Micha
>
> Best regards/Mit freundlichen Grüssen
>
> Michael Winge
>
> MSG EMEA General Applications
>
> Tel:       +44(0)1355355547
> Mobile:  +44(0)7834020228
> Email:    mic...@fr... <mailto:mic...@fr...>
>
> Registered address:
> Freescale Semiconductor UK Ltd
> Colvilles Road
> East Kilbride
> Glasgow
> Scotland
> G75 OTG
>
> Registration number: SC262720
> VAT number: GB831329053
>
> This mail is classified:
> Freescale Confidential Proprietary ( )
> Freescale Internal Use Only        (X)
> General Business Information      ( )
>
>  
>
> ------------------------------------------------------------------------
> *From:* lib...@li... 
> [mailto:lib...@li...] *On Behalf 
> Of *Dan Ellis
> *Sent:* 24 January 2008 16:09
> *To:* lib...@li...
> *Subject:* Re: [Libusb-win32-devel] Cannot retrieve configuration 
> descriptor
>
> What is the syntax of the usb_get_descriptor command you are using? 
> What is the index of the configuration, and what is the bValue in the 
> configuration when you retrieve it? There was a bug in libusb around 
> how these values were used which was fixed sometime over a year ago.
>
> Dan.
>
> Winge Michael wrote:
>> I still face the same problem which I have mention in the email with 
>> the subject " Problem with libusb driver version 0.1.12.1" to the 
>> lib...@li... 
>> <mailto:lib...@li...> email list.
>>  
>> I installed my device driver (*.inf) and test my driver with 
>> TestLibUsb. TestLibUsb displays idVendor and idProduct. That means to 
>> me that the device is working since driver has access to the device 
>> descriptor. The problem is that the driver cannot retrieve the 
>> configuration of my device.
>> During debugging my application I found out that "config" pointer in 
>> "struct usb_device" is 0.
>>  
>> I changed my window application so that I try to get the 
>> configuration with the libusb API "usb_get_descriptor" and it works. 
>> I get the configuration interface and endpoint descriptors.
>>  
>> What could be the reason why libusb driver assign 0 to the "config" 
>> pointer in "struct usb_device"?
>>  
>> Thank you for your help!
>>  
>> Micha
>>  
>>
>> Best regards/Mit freundlichen Grüssen
>>
>> Michael Winge
>>
>> MSG EMEA General Applications
>>
>> Tel:       +44(0)1355355547
>> Mobile:  +44(0)7834020228
>> Email:    mic...@fr... 
>> <mailto:mic...@fr...>
>>
>> Registered address:
>> Freescale Semiconductor UK Ltd
>> Colvilles Road
>> East Kilbride
>> Glasgow
>> Scotland
>> G75 OTG
>>
>> Registration number: SC262720
>> VAT number: GB831329053
>>
>> This mail is classified:
>> Freescale Confidential Proprietary ( )
>> Freescale Internal Use Only        (X)
>> General Business Information      ( )
>>
>>  
>

Re: [Libusb-win32-devel] Cannot retrieve configuration descriptor

[Winge M. <mic...@fr...>]

Hi Dan,
=20
I do not have problem with the usb_get_descriptor command. This works =
find. I have a problem that the driver cannot access the configuration =
of my device with the  "config" pointer in "struct usb_device". The =
"config" pointer is always zero. I guess this pointer will be assigned =
during the call of usb_get_busses(). The problem I think is somewhere =
there.
=20
My call of usb_get_descriptor is
usb_get_descriptor(JM128MMT_devh,2,1,Buff,25);
=20
=20
Micha

Best regards/Mit freundlichen Gr=FCssen

Michael Winge

MSG EMEA General Applications

Tel:       +44(0)1355355547
Mobile:  +44(0)7834020228
Email:    mic...@fr... =
<mailto:mic...@fr...>  =
<mailto:mic...@fr...>=20

Registered address:
Freescale Semiconductor UK Ltd
Colvilles Road
East Kilbride
Glasgow
Scotland
G75 OTG

Registration number: SC262720
VAT number: GB831329053

This mail is classified:
Freescale Confidential Proprietary ( )
Freescale Internal Use Only        (X)
General Business Information      ( )=20

=20

________________________________

From: lib...@li... =
[mailto:lib...@li...] On Behalf Of =
Dan Ellis
Sent: 24 January 2008 16:09
To: lib...@li...
Subject: Re: [Libusb-win32-devel] Cannot retrieve configuration =
descriptor


What is the syntax of the usb_get_descriptor command you are using? What =
is the index of the configuration, and what is the bValue in the =
configuration when you retrieve it? There was a bug in libusb around how =
these values were used which was fixed sometime over a year ago.

Dan.

Winge Michael wrote:=20

	I still face the same problem which I have mention in the email with =
the subject " Problem with libusb driver version 0.1.12.1" to the =
lib...@li... email list.
	=20
	I installed my device driver (*.inf) and test my driver with =
TestLibUsb. TestLibUsb displays idVendor and idProduct. That means to me =
that the device is working since driver has access to the device =
descriptor. The problem is that the driver cannot retrieve the =
configuration of my device.
	During debugging my application I found out that "config" pointer in =
"struct usb_device" is 0.
	=20
	I changed my window application so that I try to get the configuration =
with the libusb API "usb_get_descriptor" and it works. I get the =
configuration interface and endpoint descriptors.
	=20
	What could be the reason why libusb driver assign 0 to the "config" =
pointer in "struct usb_device"?
	=20
	Thank you for your help!
	=20
	Micha
	=20

	Best regards/Mit freundlichen Gr=FCssen

	Michael Winge
=09
	MSG EMEA General Applications

	Tel:       +44(0)1355355547
	Mobile:  +44(0)7834020228
	Email:    mic...@fr... =
<mailto:mic...@fr...>=20
=09
	Registered address:
	Freescale Semiconductor UK Ltd
	Colvilles Road
	East Kilbride
	Glasgow
	Scotland
	G75 OTG

	Registration number: SC262720
	VAT number: GB831329053
=09
	This mail is classified:
	Freescale Confidential Proprietary ( )
	Freescale Internal Use Only        (X)
	General Business Information      ( )=20

	=20

Re: [Libusb-win32-devel] Cannot retrieve configuration descriptor

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

What is the syntax of the usb_get_descriptor command you are using? What 
is the index of the configuration, and what is the bValue in the 
configuration when you retrieve it? There was a bug in libusb around how 
these values were used which was fixed sometime over a year ago.

Dan.

Winge Michael wrote:
> I still face the same problem which I have mention in the email with 
> the subject " Problem with libusb driver version 0.1.12.1" to the 
> lib...@li... 
> <mailto:lib...@li...> email list.
>  
> I installed my device driver (*.inf) and test my driver with 
> TestLibUsb. TestLibUsb displays idVendor and idProduct. That means to 
> me that the device is working since driver has access to the device 
> descriptor. The problem is that the driver cannot retrieve the 
> configuration of my device.
> During debugging my application I found out that "config" pointer in 
> "struct usb_device" is 0.
>  
> I changed my window application so that I try to get the configuration 
> with the libusb API "usb_get_descriptor" and it works. I get the 
> configuration interface and endpoint descriptors.
>  
> What could be the reason why libusb driver assign 0 to the "config" 
> pointer in "struct usb_device"?
>  
> Thank you for your help!
>  
> Micha
>  
>
> Best regards/Mit freundlichen Grüssen
>
> Michael Winge
>
> MSG EMEA General Applications
>
> Tel:       +44(0)1355355547
> Mobile:  +44(0)7834020228
> Email:    mic...@fr... <mailto:mic...@fr...>
>
> Registered address:
> Freescale Semiconductor UK Ltd
> Colvilles Road
> East Kilbride
> Glasgow
> Scotland
> G75 OTG
>
> Registration number: SC262720
> VAT number: GB831329053
>
> This mail is classified:
> Freescale Confidential Proprietary ( )
> Freescale Internal Use Only        (X)
> General Business Information      ( )
>
>  

[Libusb-win32-devel] Cannot retrieve configuration descriptor

[Winge M. <mic...@fr...>]

I still face the same problem which I have mention in the email with the =
subject " Problem with libusb driver version 0.1.12.1" to the =
lib...@li... email list.
=20
I installed my device driver (*.inf) and test my driver with TestLibUsb. =
TestLibUsb displays idVendor and idProduct. That means to me that the =
device is working since driver has access to the device descriptor. The =
problem is that the driver cannot retrieve the configuration of my =
device.
During debugging my application I found out that "config" pointer in =
"struct usb_device" is 0.
=20
I changed my window application so that I try to get the configuration =
with the libusb API "usb_get_descriptor" and it works. I get the =
configuration interface and endpoint descriptors.
=20
What could be the reason why libusb driver assign 0 to the "config" =
pointer in "struct usb_device"?
=20
Thank you for your help!
=20
Micha
=20

Best regards/Mit freundlichen Gr=FCssen

Michael Winge

MSG EMEA General Applications

Tel:       +44(0)1355355547
Mobile:  +44(0)7834020228
Email:    mic...@fr... =
<mailto:mic...@fr...>  =
<mailto:mic...@fr...>=20

Registered address:
Freescale Semiconductor UK Ltd
Colvilles Road
East Kilbride
Glasgow
Scotland
G75 OTG

Registration number: SC262720
VAT number: GB831329053

This mail is classified:
Freescale Confidential Proprietary ( )
Freescale Internal Use Only        (X)
General Business Information      ( )=20

=20

[Libusb-win32-devel] Problem with usb_get_descriptor.

[jr j. <jr...@gm...>]

I am using libusb in windows. I can detect the device after installing the
inf files created. When i try to get all the descriptors, the interface and
endpoint descriptors all show zeros, but are actually having values.
usb_get_descriptor returns zero for both of these. Can get the values of
device and configuration descriptors. I cant figure out why this happens.

While trying to get the configuration descriptor, the interface does points
to an address but the numsetting and altsetting values shows error values.
Actually can anyone tell me what happens at _usb_get_descriptor?

I am stuck with this problem and cant move forward. Hope anyone will be able
to help me out. Thanks in advance.

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

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

I will be out of the office starting  15.12.2007 and will not return un=
til
01.01.2008.

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] Solution to V0.1.12.1 and HCFR device

[Graeme G. <gr...@ar...>]

A while ago I mentioned that I was unable to upgrade from
an earlier version of libusb-win32, because one device
didn't work with V0.1.12.1.

That device is the HCFR <http://www.homecinema-fr.com/colorimetre/index_en.php>,
and I've had a chance to investigate what's changed between earlier
versions and V0.1.12.1.

It seems that the HCFR doesn't properly connect unless
a set_configuration() is done on IRP_MN_START_DEVICE.

Without this it constantly cycles through IRP_MN_START_DEVICE and
then IRP_MN_SURPRISE_REMOVAL. Exactly why would take some
more investigation.

Presumably the set_configuration() in IRP_MN_START_DEVICE
in pnp.c was removed for a reason, but the HCFR starts working
again if I uncomment this code.

Graeme Gill.

Re: [Libusb-win32-devel] problem with usb_control_msg

[Xiaofan C. <xia...@gm...>]

On Dec 14, 2007 9:48 PM, Stephan Meyer <Ste...@ia...> wrote:
> > I am facing some problem while calling 'usb_control_msg' function
> > with data length more than 4K. When 'usb_control_msg' is called with
> > data more than 4K it returns error code -10 and there is no activity
> > on bus. Is there a limitation that application cannot read / write
> > data more than 4K in a single go using libusb.
> > An early reply will be helpful.
>
> Control transfers are limited to 4k on Windows.
>
> See http://support.microsoft.com/kb/832430/en-us

Linux seems to do the same.
http://www.mail-archive.com/lin...@li.../msg38412.html

Re: [Libusb-win32-devel] problem with usb_control_msg

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

Control transfers are limited to 4k on Windows.

See http://support.microsoft.com/kb/832430/en-us

Stephan



> Hello,
> 
> I am facing some problem while calling 'usb_control_msg' function 
> with data length more than 4K. When 'usb_control_msg' is called with
> data more than 4K it returns error code -10 and there is no activity
> on bus. Is there a limitation that application cannot read / write 
> data more than 4K in a single go using libusb.
> An early reply will be helpful.
> 
> Regards,
> Waqar
> 
> 
> 
> 
____________________________________________________________________________________
> Looking for last minute shopping deals? 
> Find them fast with Yahoo! Search.  http://tools.search.yahoo.
> com/newsearch/category.php?category=shopping
> 
> 
-------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> 
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

[Libusb-win32-devel] problem with usb_control_msg

[Waqar A. <waq...@ya...>]

Hello,

I am facing some problem while calling 'usb_control_msg' function with data length more than 4K. When 'usb_control_msg' is called with data more than 4K it returns error code -10 and there is no activity on bus. Is there a limitation that application cannot read / write data more than 4K in a single go using libusb.
An early reply will be helpful.

Regards,
Waqar


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

[Libusb-win32-devel] Initial import of the homepage to Wiki

[Xiaofan C. <xia...@gm...>]

http://libusb-win32.wiki.sourceforge.net/

I took the liberty of importing the original homepage to the Wiki and
made some minor changes. Please check if there are mistakes.

Xiaofan
http://mcuee.blogspot.com

Re: [Libusb-win32-devel] Error while loading shared library LibusbJNI.dll : C:\Program Files\Java\jre1.6.0\bin\LibusbJNI.dll: The operating system cannot run %1

[Xiaofan C. <xia...@gm...>]

On Dec 8, 2007 5:03 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Dec 8, 2007 3:42 PM, syed aleem <sye...@gm...> wrote:
> > Hi,
> >
> >     I have installed libusb-win32  and have put following jar's in ClassPath
> > ( C:\Program Files\Java\jre1.6.0\lib )
> >
> >       javax.usb.properties,  jsr80.jar,  jsr80_ri.jar,   jsr80_windows.jar
> >
> >
> >      Also Libusb.dll and libusb0.dll in classpath ( C:\Program
> > Files\Java\jre1.6.0\bin )
> >
> >    now am getting following error , please help me out of it.
> >
>
> I do not know about the Java wrapper of libusb but I think
> the following forum might help you better.
> http://sourceforge.net/forum/forum.php?forum_id=660151
>

Google found this and it seems it is a Java problem.
http://forum.java.sun.com/thread.jspa?threadID=770138

Re: [Libusb-win32-devel] Error while loading shared library LibusbJNI.dll : C:\Program Files\Java\jre1.6.0\bin\LibusbJNI.dll: The operating system cannot run %1

[Xiaofan C. <xia...@gm...>]

On Dec 8, 2007 3:42 PM, syed aleem <sye...@gm...> wrote:
> Hi,
>
>     I have installed libusb-win32  and have put following jar's in ClassPath
> ( C:\Program Files\Java\jre1.6.0\lib )
>
>       javax.usb.properties,  jsr80.jar,  jsr80_ri.jar,   jsr80_windows.jar
>
>
>      Also Libusb.dll and libusb0.dll in classpath ( C:\Program
> Files\Java\jre1.6.0\bin )
>
>    now am getting following error , please help me out of it.
>

I do not know about the Java wrapper of libusb but I think
the following forum might help you better.
http://sourceforge.net/forum/forum.php?forum_id=660151

[Libusb-win32-devel] Error while loading shared library LibusbJNI.dll : C:\Program Files\Java\jre1.6.0\bin\LibusbJNI.dll: The operating system cannot run %1

[syed a. <sye...@gm...>]

Hi,

    I have installed libusb-win32  and have put following jar's in ClassPath
( C:\Program Files\Java\jre1.6.0\lib )

      javax.usb.properties,  jsr80.jar,  jsr80_ri.jar,   jsr80_windows.jar


     Also Libusb.dll and libusb0.dll in classpath ( C:\Program
Files\Java\jre1.6.0\bin )

   now am getting following error , please help me out of it.

    *

javax.usb.UsbException*: Error while loading shared library LibusbJNI.dll :
C:\Program Files\Java\jre1.6.0\bin\LibusbJNI.dll: The operating system
cannot run %1

at com.mcreations.usb.windows.JavaxUsb.loadLibrary(*JavaxUsb.java:400*)

at com.mcreations.usb.windows.JavaxUsb.initialise(*JavaxUsb.java:329*)

at com.mcreations.usb.windows.WindowsUsbServices.<init>(*
WindowsUsbServices.java:46*)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(*Native Method*)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at javax.usb.UsbHostManager.createUsbServices(Unknown Source)

at javax.usb.UsbHostManager.getUsbServices(Unknown Source)

at MainFrame.<init>(*MainFrame.java:20*)

at MainFrame.main(*MainFrame.java:12*)

**

Thanks in advance

with Regards

Syed

**

[Libusb-win32-devel] usb_reap: timeout error

[Vishal V. <vis...@gm...>]

hi,

Am using LibUSB for windows (ver 0.1.12.1)
and I am getting this error "usb_reap: timeout error" while using bulk read
or interrupt read.

The write operation is working without any error.

here is the code: -


byte[] readData = new byte[12];
      while(true) {

         try {
              dev.open(1, 0, -1);
              int ir = dev.readInterrupt(0x81, readData, readData.length,
2000, false);
              logData(readData);
              dev.close();
        } catch (Exception e) {

        }

      }

can anybody help here?

-- 
~vishal.

Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 18, Issue 22

[Hai S. <leo...@ya...>]

I have figured out how to get the return value. After reading more about control transfer I then understand that the return value will be kept in buffer. so, this is what I did;

In Main Code;
Dim buf(256) as byte
UsbControlMsg(my_handle, "C0", "01", "0000",  "0000", buf(0), "0100", "1000")
label1 = hex(buf(0))  ' label1 will be the return value in hex

In Module;
Declare Function UsbControlMsg Lib "libusbvb0.dll" _
  Alias "vb_usb_control_msg" ( _
  ByVal dev As Long, _
  ByVal requesttype As Long, _
  ByVal request As Long, _
  ByVal value As Long, _
  ByVal index As Long, _
  ByRef buf As Byte, _     ' notice that i change it to ByRef instead of ByVal
  ByVal size As Long, _
  ByVal timeout As Long) As Long

It works for me after made the changes above. I would like to thank you Stephan Meyer for sharing the code and Stephan Hart for your advice.


       
---------------------------------
Get easy, one-click access to your favorites.  Make Yahoo! your homepage.

Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 18, Issue 22

[Hai S. <leo...@ya...>]

Thanks for replying. From the code below, it seems using Bulk transfer to get the return value? I prefer to use control transfer code given by Stephan Meyer.

I have monitored using BusHound Capture and whenever I run "UsbControlMsg(my_handle, "C0", "01", "0000",  "0000", buf , 
> "0100", timeout)", it shows "0e" in return, which is correct. 

But how to get the return value in VB? Any luck for me?


Stephen Hart <sj...@ko...> wrote: 
  This is some code that shows how to get a string from a returned value.
The 2 important things are the function "VarPtr" to get a pointer to a
buffer declared in VB and to use "byval" for each parameter when calling
libusb functions.


Private Const clSmallBufferSize As Long = 512

' Declare this as a module variable, not a local variable in a sub or
function
Private mabytSmallBufferRead(0 To clSmallBufferSize) As Byte
Private mlCurDeviceHandle as long

' ...

mlCurDeviceHandle = UsbOpen( ... )

' ...

Private Sub TestRead(byref rsStringFound as string)
 dim plBufferStartLoc as long
 dim plNrBytesRead as long
 dim pbytCurByte as byte
 dim psMyString as String
 dim pbEndReached as Boolean

   plBufferStartLoc = VarPtr( mabytSmallBufferRead(0))

    ' Use "byval" so that things are not auto-converted to pointers to long
   plNrBytesRead = UsbBulkRead( ByVal mlCurDeviceHandle, _
         ByVal clMy_USB_ENDPOINT_CommandRead, _
         ByVal plBufferStartLoc, _
         ByVal clSmallBufferSize, _
         ByVal clMy_USB_CommandTimeout )

   If (0 = plNrBytesRead) Then
      'nothing read
       rsStringFound  = ""
   Else
       psMyString =""
       pbEndReached = false

       for plArrayLoc = 0 to  ( plNrBytesRead -1 )
          pbytCurByte = mabytSmallBufferRead( plArrayLoc )
          psMyString = psMyString & Chr( pbytCurByte )
       Next plArrayLoc

       rsStringFound = psMyString
   Endif

End Sub



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


       
---------------------------------
Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.

Re: [Libusb-win32-devel] Visual Basic 6.0 - How to access the libusb (ong leonall)

[Stephen H. <sj...@ko...>]

  This is some code that shows how to get a string from a returned value.
The 2 important things are the function "VarPtr" to get a pointer to a
buffer declared in VB and to use "byval" for each parameter when calling
libusb functions.


Private Const clSmallBufferSize As Long = 512

' Declare this as a module variable, not a local variable in a sub or
function
Private mabytSmallBufferRead(0 To clSmallBufferSize) As Byte
Private mlCurDeviceHandle as long

' ...

mlCurDeviceHandle = UsbOpen( ... )

' ...

Private Sub TestRead(byref rsStringFound as string)
 dim plBufferStartLoc as long
 dim plNrBytesRead as long
 dim pbytCurByte as byte
 dim psMyString as String

   plBufferStartLoc = VarPtr( mabytSmallBufferRead(0))

    ' Use "byval" so that things are not auto-converted to pointers to long
   plNrBytesRead = UsbBulkRead( ByVal mlCurDeviceHandle, _
         ByVal clMy_USB_ENDPOINT_CommandRead, _
         ByVal plBufferStartLoc, _
         ByVal clSmallBufferSize, _
         ByVal clMy_USB_CommandTimeout )

   If (0 = plNrBytesRead) Then
      'nothing read
       rsStringFound  = ""
   Else
       psMyString =""

       for plArrayLoc = 0 to  ( plNrBytesRead -1 )
          pbytCurByte = mabytSmallBufferRead( plArrayLoc )
          psMyString = psMyString & Chr( pbytCurByte )
       Next plArrayLoc

       rsStringFound = psMyString
   Endif

End Sub

Re: [Libusb-win32-devel] which usb driver?

[Xiaofan C. <xia...@gm...>]

On 11/15/07, Ronny Obstei <ob...@vh...> wrote:
> Hi guys,
>
> which usb driver should I use? I want to operate with an FT2232D from FTDI.
>
> When using FTDI's D2XX driver testlibusb-win.exe works fine.
>
> The generation of the libusb-driver was a bit tricky, because the
> FT2232D has two channels. inf-wizard.exe generates one driver, which
> couldn't be installed.
> Then I created two different drivers out of the one inf-file with some
> information gained from the hardware manager by modifying the [Devices]
> block.
> After installing each driver testlibusb-win.exe worked also fine.
>
> So which driver will be the best for proceeding?
>

I believe you are using libusb-win32 in the wrong place. The
easiest and the better solution is to forget about libusb-win32
since the FTDI driver works fine. And if you want cross-platform
functionality, I think it also works under Linux.

Xiaofan

Re: [Libusb-win32-devel] Libusb-win32-devel Digest, Vol 18, Issue 22

[Stephen H. <sj...@ko...>]

  This is some code that shows how to get a string from a returned value.
The 2 important things are the function "VarPtr" to get a pointer to a
buffer declared in VB and to use "byval" for each parameter when calling
libusb functions.


Private Const clSmallBufferSize As Long = 512

' Declare this as a module variable, not a local variable in a sub or
function
Private mabytSmallBufferRead(0 To clSmallBufferSize) As Byte
Private mlCurDeviceHandle as long

' ...

mlCurDeviceHandle = UsbOpen( ... )

' ...

Private Sub TestRead(byref rsStringFound as string)
 dim plBufferStartLoc as long
 dim plNrBytesRead as long
 dim pbytCurByte as byte
 dim psMyString as String
 dim pbEndReached as Boolean

   plBufferStartLoc = VarPtr( mabytSmallBufferRead(0))

    ' Use "byval" so that things are not auto-converted to pointers to long
   plNrBytesRead = UsbBulkRead( ByVal mlCurDeviceHandle, _
         ByVal clMy_USB_ENDPOINT_CommandRead, _
         ByVal plBufferStartLoc, _
         ByVal clSmallBufferSize, _
         ByVal clMy_USB_CommandTimeout )

   If (0 = plNrBytesRead) Then
      'nothing read
       rsStringFound  = ""
   Else
       psMyString =""
       pbEndReached = false

       for plArrayLoc = 0 to  ( plNrBytesRead -1 )
          pbytCurByte = mabytSmallBufferRead( plArrayLoc )
          psMyString = psMyString & Chr( pbytCurByte )
       Next plArrayLoc

       rsStringFound = psMyString
   Endif

End Sub

Re: [Libusb-win32-devel] Visual Basic 6.0 - How to access the libusb

[ong l. <leo...@ya...>]

Thanks. I tried as you told and after a little adjustment, it works. 
However, how to display the data in VB?

I mean in my case, "C0 01 0000 0000 0100" will return a data of "0e", which is correct, but how to put the data output to a variable in VB?

Any luck for me?



Stephan Meyer <Ste...@ia...> wrote: > Hi Stephan,
> 
> Please ignore my first reply, control and interrupt is absolutely 
> different format. So, I tried the using control transfer instead. If
> i want to send "C0 01 0000 0000 0100 (Type Req Value Index Length), 
> is what I did below correct?
> 
> Dim my_handle
> my_handle = UsbOpen(0, &H192F, &H216)
> If my_handle = 0 Then Debug.Print " No such device "
> 
> text1 = UsbControlMsg(my_handle, "C0", "01", "0000", "0000", buf , 
> "0100", timeout)
> 
> What should be filled for "buf" and "timeout"? Thanks.
> 

The Parameters must be numbers, not strings:

UsbControlMsg(my_handle, &HC0, 1, 0, 0, buf, size, 1000)

'size' must either be &H0100 or &H1 depending on what "0100"
means (little or big endian format?)
'buf' must point to a array of size 'size' (I don't know how
this is expressed in VB).

 
> 
> 
> 
> 
> 
> 
> 
> ong leonall  wrote:
> Hi Stephan,
> 
> I'm truly thankful for the code. I tried it and it works well and 
> able to detect my device. If you don't mind, I would like to ask a 
> question on interrupt transfer.
> 
> I tried the usb_open code and it is able to get a handle on my 
> device. After usb_open, let's say I want to call a custom command like 
below;
> 
> Type   Req   Value   Index   Length
> C0      01     00 00    00 00   01 00 
> 
> How can I do that using "vb_usb_interrupt_read (dev, ep, buf, size, 
timeout)"?
> 
> 
> Stephan Meyer  wrote:
> I wrote a libusb VB6 module a while ago (see attachement).
> It's not well tested and might contain bugs but you can
> use it as a basis for your development.
> 
> Please note that you can't access libusb0.dll from VB
> directly, you have to access the DLL through libusbvb0.dll
> contained in the zip-file. The reason for this is that 
> all libusb0.dll functions use the 'cdecl' calling convention,
> whereas VB only supports 'stdcall'.
> 
> Stephan
> 
> 
> 
> 
> 
> > Dear All,
> > 
> > I’m looking for information on how to use VB6.0 to communicate with 

> libusb. 
> > What I can find from the internet that works;
> > Declare Sub usb_init Lib "libusb0.dll" ()
> > Declare Function usb_find_busses Lib "libusb0.dll" () As Integer
> > Declare Function usb_find_devices Lib "libusb0.dll" () As Integer
> > usb_init()
> > nBusses = usb_find_busses()
> > nDevices = usb_find_devices()
> > Label1.Text = "Devices " & nDevices
> > Label2.Text = "Busses " & nBusses
> > 
> > Is there anyone out there that has successfully done it in VB6.0 to 
> > call other functions, especially “usb_open”, 
“USB_Interrupt_Read” 
> > and “USB_Interrupt_Write”?
> > I would appreciate for any advice or sharing of the code (if any, 
> > please send to me leo...@ya...). 
> > Thank you.
> > 
> > Get easy, one-click access to your favorites. Make Yahoo! your 
> homepage. 
> > 
> 
-------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Libusb-win32-devel mailing list
> > Lib...@li...
> > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> 
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.
> 
com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
> 
> Get easy, one-click access to your favorites. Make Yahoo! your homepage. 

> 
>  Get easy, one-click access to your favorites. Make Yahoo! your 
homepage. 


       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.

Re: [Libusb-win32-devel] Visual Basic 6.0 - How to access the libusb

[ong l. <leo...@ya...>]

Thanks again, Stephan. I tried as you told and checked it with BusHound Capture and after a little adjustment, it works. However, how to display the output in VB?

I mean in my case, "C0 01 0000 0000 0100" will give output of "0e" in Bus Hound, which is correct, but how to put the output to a variable and display it as a label/text in VB?

       
---------------------------------
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.

Re: [Libusb-win32-devel] Visual Basic 6.0 - How to access the libusb

[ong l. <leo...@ya...>]

Thanks again, Stephan. I tried as you told and checked it with BusHound Capture and after a little adjustment, it works. However, how to display the output in VB?

I mean in my case, "C0 01 0000 0000 0100" will give output of "0e" in Bus Hound, which is correct, but how to put the output to a variable and display it as a label/text in VB?
       
---------------------------------
Get easy, one-click access to your favorites.  Make Yahoo! your homepage.

[Libusb-win32-devel] usb_bulk_read problem in bulk.c

[Ronny O. <ob...@vh...>]

Hi guys,

I'm using Win XP SP2 and libusb-win32-filter-bin-0.1.12.1.exe.

testlibusb-win.exe shows me the following infos:
DLL version:    0.1.12.1
Driver version:    0.1.12.1

bus/device  idVendor/idProduct
bus-0/\\.\libusb0-0006--0x0403-0x6010     0403/6010
- Manufacturer : FTDI
- Product      : DLP2232M
- Serial Number: FTP5E22V
  wTotalLength:         55
  bNumInterfaces:       2
  bConfigurationValue:  1
  iConfiguration:       0
  bmAttributes:         80h
  MaxPower:             45
    bInterfaceNumber:   0
    bAlternateSetting:  0
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         2
      bEndpointAddress: 81h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 02h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
    bInterfaceNumber:   1
    bAlternateSetting:  0
    bNumEndpoints:      2
    bInterfaceClass:    255
    bInterfaceSubClass: 255
    bInterfaceProtocol: 255
    iInterface:         2
      bEndpointAddress: 83h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0
      bEndpointAddress: 04h
      bmAttributes:     02h
      wMaxPacketSize:   64
      bInterval:        0
      bRefresh:         0
      bSynchAddress:    0

I've not installed the libusb-driver, but the FTDI's one seams to base 
on libusb too.

When modifying bulk.c using the testlibusb-win's info (check 
attachment), the program results in a bulk-read-error.
The usb chip is connected to a loopback device, wich works fine with 
another program (dlptest20h.exe).

So what else is to do for a working version of bulk.c?

Thanks in advance.

- Ronny