libusb-win32-devel

Re: [Libusb-win32-devel] driver, not device, installation

[Chris E <sp...@gm...>]

Sorry, by "the SDK" in my last email, I meant "the libusbK SDK".  Within
Inf Wizard, you can select an option to use libusb0.

On Fri., 7 Sep. 2018, 2:36 am Tyler Bell, <mrb...@gm...> wrote:

> First, let me apologize for opening this ticket(
> https://sourceforge.net/p/libusb-win32/bugs/84/) rather than using the
> mailing list.
>
> Second, let me apologize for being dense, but the suggestion "You need to
> install the base package (libusb installer or libusbk installer) to install
> libusb0.sys into the system." isn't quite clear to me.
> The only "base package" installer I can find is for the development kits,
> which isn't something we should be putting on customer machines. If, on the
> other hand, you are saying I need to create my own installer, that's
> probably fair, but also a fair amount of work w/ the 32/64-bit divide that
> has already been solved in the existing libusb device installers. It's
> unfortunate that it's not easily reusable.
>
> Any advice would be appreciated.
>
> Thanks,
> Tyler
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] driver, not device, installation

[Chris E <sp...@gm...>]

There should be software included in the SDK called "inf wizard".  Type in
a bit of information and it spits out driver installers for your device, in
both 32 and 64 bit format.  Takes all of 2 minutes; fantastic software.

Cheers,
-Chris

On Fri., 7 Sep. 2018, 2:36 am Tyler Bell, <mrb...@gm...> wrote:

> First, let me apologize for opening this ticket(
> https://sourceforge.net/p/libusb-win32/bugs/84/) rather than using the
> mailing list.
>
> Second, let me apologize for being dense, but the suggestion "You need to
> install the base package (libusb installer or libusbk installer) to install
> libusb0.sys into the system." isn't quite clear to me.
> The only "base package" installer I can find is for the development kits,
> which isn't something we should be putting on customer machines. If, on the
> other hand, you are saying I need to create my own installer, that's
> probably fair, but also a fair amount of work w/ the 32/64-bit divide that
> has already been solved in the existing libusb device installers. It's
> unfortunate that it's not easily reusable.
>
> Any advice would be appreciated.
>
> Thanks,
> Tyler
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

[Libusb-win32-devel] driver, not device, installation

[Tyler B. <mrb...@gm...>]

First, let me apologize for opening this ticket(
https://sourceforge.net/p/libusb-win32/bugs/84/) rather than using the
mailing list.

Second, let me apologize for being dense, but the suggestion "You need to
install the base package (libusb installer or libusbk installer) to install
libusb0.sys into the system." isn't quite clear to me.
The only "base package" installer I can find is for the development kits,
which isn't something we should be putting on customer machines. If, on the
other hand, you are saying I need to create my own installer, that's
probably fair, but also a fair amount of work w/ the 32/64-bit divide that
has already been solved in the existing libusb device installers. It's
unfortunate that it's not easily reusable.

Any advice would be appreciated.

Thanks,
Tyler

Re: [Libusb-win32-devel] libusbK examples not working for me.

[Stuart F. <smf...@nt...>]

On 21/08/18 00:17, Chris E wrote:
> Have you used inf wizard to generate a driver for your Camera device?
> Have you used Zadig to ensure that the device is using the LibusbK driver?
>
> Welcome to Windows.
>
> On Tue, 21 Aug 2018 at 08:22, Stuart Foster via Libusb-win32-devel 
> <lib...@li... 
> <mailto:lib...@li...>> wrote:
>
>     Hi, I am trying some of the code from the libusbK examples
>     package. The
>     package has installed OK and I can successfully build the examples
>     with
>     vcpp.
>
>     However of the two examples I have tried non has detected my test
>     device
>     (USB Compact Camera).
>
>     Under debug enum_descriptors with pid=32ab and vid=04a9 (recovered
>     from
>     USB\VID_04A9&PID_32AB) has function LstK_Count returning 0.
>
>     Also hot-plug-monitor using
>     strcpy(hotParams.PatternMatch.DeviceInterfaceGUID,
>     "{EEC5AD98-8080-425f-922A-DABF3DE3F69A}"); (DeviceInterfaceGUID
>     recovered via regedit.)
>
>     reports nothing when device is inserted/removed.
>
>     In both cases windows reports the presence/absence of my test device.
>
>     Any suggestions has to what I may be doing wrong (I have many years
>     c/c++ knowledge in the Linux arena but limited windows/vcpp
>     experience).
>
>     Thanks
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>     _______________________________________________
>     Libusb-win32-devel mailing list
>     Lib...@li...
>     <mailto:Lib...@li...>
>     https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
Thanks for the heads up Chris both my test programs are now working.

Re: [Libusb-win32-devel] libusbK examples not working for me.

[Chris E <sp...@gm...>]

Have you used inf wizard to generate a driver for your Camera device?
Have you used Zadig to ensure that the device is using the LibusbK driver?

Welcome to Windows.

On Tue, 21 Aug 2018 at 08:22, Stuart Foster via Libusb-win32-devel <
lib...@li...> wrote:

> Hi, I am trying some of the code from the libusbK examples package. The
> package has installed OK and I can successfully build the examples with
> vcpp.
>
> However of the two examples I have tried non has detected my test device
> (USB Compact Camera).
>
> Under debug enum_descriptors with pid=32ab and vid=04a9 (recovered from
> USB\VID_04A9&PID_32AB) has function LstK_Count returning 0.
>
> Also hot-plug-monitor using
> strcpy(hotParams.PatternMatch.DeviceInterfaceGUID,
> "{EEC5AD98-8080-425f-922A-DABF3DE3F69A}"); (DeviceInterfaceGUID
> recovered via regedit.)
>
> reports nothing when device is inserted/removed.
>
> In both cases windows reports the presence/absence of my test device.
>
> Any suggestions has to what I may be doing wrong (I have many years
> c/c++ knowledge in the Linux arena but limited windows/vcpp experience).
>
> Thanks
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

[Libusb-win32-devel] libusbK examples not working for me.

[Stuart F. <smf...@nt...>]

Hi, I am trying some of the code from the libusbK examples package. The 
package has installed OK and I can successfully build the examples with 
vcpp.

However of the two examples I have tried non has detected my test device 
(USB Compact Camera).

Under debug enum_descriptors with pid=32ab and vid=04a9 (recovered from 
USB\VID_04A9&PID_32AB) has function LstK_Count returning 0.

Also hot-plug-monitor using 
strcpy(hotParams.PatternMatch.DeviceInterfaceGUID, 
"{EEC5AD98-8080-425f-922A-DABF3DE3F69A}"); (DeviceInterfaceGUID 
recovered via regedit.)

reports nothing when device is inserted/removed.

In both cases windows reports the presence/absence of my test device.

Any suggestions has to what I may be doing wrong (I have many years 
c/c++ knowledge in the Linux arena but limited windows/vcpp experience).

Thanks

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

On Fri, Jun 29, 2018 at 9:44 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Thu, Jun 28, 2018 at 7:51 PM, Xiaofan Chen <xia...@gm...> wrote:
>>> And when I use xusb.exe to check the device's descriptor, it can't open the
>>> device like below shows:
>>
>> Then I think your FW has an issue. Read the above libwdi wiki page
>> and see if you can learn something there.
>>
>>> And then I debug into the source code of LibUsbk's example "open-device", in the
>>> function l_EnumKey_Instances() at lusbk_device_list.c file. When enum
>>> DeviceInterface, got an error code 259(No more data is available) like below shows:
>>
>> As mentioned in the previous email, libusbK has a problem -- it will not work
>> for your use case unfortunately even if you fix your FW.
>>
>> You may want to try out libusb Windows -- still you need to fix your FW.

Since your FW is already using "DeviceInterfaceGUIDs", the libusbK issue
does not affect you. Your FW has an issue.

>>> So I guess maybe my FW is missing DeviceInterfaceGUID handling like your
>>> previous mail said. But I'm not the expert of device FW, so I'm not sure about this.
>>> Do you agree with me or have some other advice?
>
> You can take a look here at this firmware. It should work with both
> libusbK and xusb.
> https://github.com/TravisRo/libusb_stm32/blob/master/demo/winusb_loop.c
>

Ref: https://github.com/pbatard/libwdi/wiki/WCID-Devices#Defining_a_Device_Interface_GUID_or_other_device_specific_properties

One item that may be of interest to you, with regards to WCID devices,
is the provision
of additional device registry settings and especially the provision of
the Device Interface
GUID that you want your device to be accessed with. Just like with the
Compatible ID,
this too is done through a Feature Descriptor, called Extended
Properties Feature
Descriptor and located at wIndex = 0x0005. However, as opposed to the
Compatible ID,
this should be queried using an Interface Request with the full
bmRequestType being
set to 0xC1.

Your FW needs to handle this.

And if you are using Windows XP SP3/Vista/Windows 7, I hear reports
sometimes it has
a problem, you can test with Windows 10 first.

-- 
Xiaofan

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

On Thu, Jun 28, 2018 at 7:51 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Thu, Jun 28, 2018 at 10:08 AM, Chengda Guo
> <che...@ca...> wrote:
>>
>> Hi Xiaofan,
>>
>> My WCID device's descriptor like below shows:
>>
>
> That is not really the descriptor. You should have something like this.
> http://janaxelson.com/files/ms_os_10_descriptors.c
>
> More explanation here.
> https://github.com/pbatard/libwdi/wiki/WCID-Devices
>
>
>> And when I use xusb.exe to check the device's descriptor, it can't open the
>> device like below shows:
>
> Then I think your FW has an issue. Read the above libwdi wiki page
> and see if you can learn something there.
>
>> And then I debug into the source code of LibUsbk's example "open-device", in the
>> function l_EnumKey_Instances() at lusbk_device_list.c file. When enum
>> DeviceInterface, got an error code 259(No more data is available) like below shows:
>
> As mentioned in the previous email, libusbK has a problem -- it will not work
> for your use case unfortunately even if you fix your FW.
>
> You may want to try out libusb Windows -- still you need to fix your FW.
>
>> So I guess maybe my FW is missing DeviceInterfaceGUID handling like your
>> previous mail said. But I'm not the expert of device FW, so I'm not sure about this.
>> Do you agree with me or have some other advice?

You can take a look here at this firmware. It should work with both
libusbK and xusb.
https://github.com/TravisRo/libusb_stm32/blob/master/demo/winusb_loop.c


-- 
Xiaofan

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

Hi Chengda,

BTW, are you using Windows 7? If yes, you may want to try out Windows 10 to see
if the situation changes. Thanks.


-- 
Xiaofan

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

On Thu, Jun 28, 2018 at 10:08 AM, Chengda Guo
<che...@ca...> wrote:
>
> Hi Xiaofan,
>
> My WCID device's descriptor like below shows:
>

That is not really the descriptor. You should have something like this.
http://janaxelson.com/files/ms_os_10_descriptors.c

More explanation here.
https://github.com/pbatard/libwdi/wiki/WCID-Devices


> And when I use xusb.exe to check the device's descriptor, it can't open the
> device like below shows:

Then I think your FW has an issue. Read the above libwdi wiki page
and see if you can learn something there.

> And then I debug into the source code of LibUsbk's example "open-device", in the
> function l_EnumKey_Instances() at lusbk_device_list.c file. When enum
> DeviceInterface, got an error code 259(No more data is available) like below shows:

As mentioned in the previous email, libusbK has a problem -- it will not work
for your use case unfortunately even if you fix your FW.

You may want to try out libusb Windows -- still you need to fix your FW.

> So I guess maybe my FW is missing DeviceInterfaceGUID handling like your
> previous mail said. But I'm not the expert of device FW, so I'm not sure about this.
> Do you agree with me or have some other advice?
>


-- 
Xiaofan

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

[Chengda G. <che...@ca...>]

Hi Xiaofan,

My WCID device's descriptor like below shows:




And when I use xusb.exe to check the device's descriptor, it can't open 
the device like below shows:





And then I debug into the source code of LibUsbk's example "open-device", 
in the function l_EnumKey_Instances() at lusbk_device_list.c file. When 
enum DeviceInterface, got an error code 259(No more data is available) 
like below shows:




So I guess maybe my FW is missing DeviceInterfaceGUID handling like your 
previous mail said. But I'm not the expert of device FW, so I'm not sure 
about this.
Do you agree with me or have some other advice?


Thanks a lot!

Chengda Guo




From:   Xiaofan Chen <xia...@gm...>
To:     lib...@li...
Date:   2018/06/27 21:21
Subject:        Re: [Libusb-win32-devel] About auto install WinUsb driver 
and use LibusbK to access device



On Tue, Jun 26, 2018 at 9:42 AM, Chengda Guo <che...@ca...> 
wrote:
> Hi Xiaofan,
>
> I'm so sorry for my delays in replying to your letter. Your advice is 
very
> helpful. I debug the source code of LibUsbK in my application, and I 
find
> that DeviceInterfaceGUID is missing. I will check the configuration of 
my
> WCID device according to your advice.
>

For the record, I think it is a libusbK bug.

I have reproduce this bug from my side using a defaut Microchip USB
demo firmware.

c:\libusbK-dev-kit>klist

Loading USB ID's maintained by Stephen J. Gowdy 
<lin...@gm...>..

No devices found.

c:\libusbK-dev-kit>c:\work\libusb\bin-1.0.22\examples\bin64\xusb.exe 
04d8:0053
Using libusb v1.0.22.11312

Opening device 04D8:0053...

Reading device descriptor:
            length: 18
      device class: 0
               S/N: 0
           VID:PID: 04D8:0053
         bcdDevice: 0000
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

Reading BOS descriptor: no descriptor

Reading first configuration descriptor:
             nb interfaces: 1
              interface[0]: id = 0
interface[0].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: FF.FF.FF
       endpoint[0].address: 01
           max packet size: 0040
          polling interval: 01
       endpoint[1].address: 81
           max packet size: 0040
          polling interval: 01

Claiming interface 0...

Reading string descriptors:
   String (0x01): "Microchip Technology Inc."
   String (0x02): "Microchip Vendor Example Device"

Reading Extended Compat ID OS Feature Descriptor (wIndex = 0x0004):

  00000000  28 00 00 00 00 01 04 00 01 00 00 00 00 00 00 00 
(...............
  00000010  00 01 57 49 4e 55 53 42 00 00 00 00 00 00 00 00 
..WINUSB........
  00000020  00 00 00 00 00 00 00 00                          ........

Reading Extended Properties OS Feature Descriptor (wIndex = 0x0005):
   Failed: Pipe error
Releasing interface 0...
Closing device...


-- 
Xiaofan

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

On Tue, Jun 26, 2018 at 9:42 AM, Chengda Guo <che...@ca...> wrote:
> Hi Xiaofan,
>
> I'm so sorry for my delays in replying to your letter. Your advice is very
> helpful. I debug the source code of LibUsbK in my application, and I find
> that DeviceInterfaceGUID is missing. I will check the configuration of my
> WCID device according to your advice.
>

For the record, I think it is a libusbK bug.

I have reproduce this bug from my side using a defaut Microchip USB
demo firmware.

c:\libusbK-dev-kit>klist

Loading USB ID's maintained by Stephen J. Gowdy <lin...@gm...>..

No devices found.

c:\libusbK-dev-kit>c:\work\libusb\bin-1.0.22\examples\bin64\xusb.exe 04d8:0053
Using libusb v1.0.22.11312

Opening device 04D8:0053...

Reading device descriptor:
            length: 18
      device class: 0
               S/N: 0
           VID:PID: 04D8:0053
         bcdDevice: 0000
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

Reading BOS descriptor: no descriptor

Reading first configuration descriptor:
             nb interfaces: 1
              interface[0]: id = 0
interface[0].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: FF.FF.FF
       endpoint[0].address: 01
           max packet size: 0040
          polling interval: 01
       endpoint[1].address: 81
           max packet size: 0040
          polling interval: 01

Claiming interface 0...

Reading string descriptors:
   String (0x01): "Microchip Technology Inc."
   String (0x02): "Microchip Vendor Example Device"

Reading Extended Compat ID OS Feature Descriptor (wIndex = 0x0004):

  00000000  28 00 00 00 00 01 04 00 01 00 00 00 00 00 00 00  (...............
  00000010  00 01 57 49 4e 55 53 42 00 00 00 00 00 00 00 00  ..WINUSB........
  00000020  00 00 00 00 00 00 00 00                          ........

Reading Extended Properties OS Feature Descriptor (wIndex = 0x0005):
   Failed: Pipe error
Releasing interface 0...
Closing device...


-- 
Xiaofan

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

[Chengda G. <che...@ca...>]

Hi Xiaofan,

I'm so sorry for my delays in replying to your letter. Your advice is very 
helpful. I debug the source code of LibUsbK in my application, and I find 
that DeviceInterfaceGUID is missing. I will check the configuration of my 
WCID device according to your advice. 

Thank you very much! 


Chengda 



From:   Xiaofan Chen <xia...@gm...>
To:     lib...@li...
Date:   2018/06/25 20:05
Subject:        Re: [Libusb-win32-devel] About auto install WinUsb driver 
and use LibusbK to access device



On Mon, Jun 25, 2018 at 7:45 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Sat, Jun 23, 2018 at 10:24 AM, Xiaofan Chen <xia...@gm...> 
wrote:
>> On Fri, Jun 22, 2018 at 4:33 PM, Chengda Guo 
<che...@ca...> wrote:
>>> I had used the libusbk and winUsb driver which created by the 
libusbk-inf-wizard.exe
>>> for installing my device, both of them are OK. And I can access the 
device by
>>> LibUsbk.dll in my application. Now I would like to automatically 
install winusb driver
>>> by Windows OS when the device plug into the system, and then use 
LibUsbk.dll
>>> to access the device in my application. The first step automatically 
install winusb
>>> driver was successful like below screen shot shows.
>>> But in my application, the device can't be accessed by 
LibUsbk.dll(Din't find
>>> the device, LstK_Init() succeed, but LstK_Count() return 0 device 
count).
>>>
>>> Whether this way is feasible or not? What do I need to pay attention 
to?
>>> Look forward to your kind advice. Thank you very much!
>>>
>>
>> A few questions.
>> 1) What is the OS version?
>>
>> 2) How do you automatically install WinUSB driver by Windows OS?
>> If you use the Windows OS Descriptor, please check the following. You
>> can post the whole USB Descriptor of your device.
>> https://github.com/pbatard/libwdi/wiki/WCID-Devices
>>
>> 3) As the above website suggests, you can download libusb-1.0 Windows
>> binary and use xusb to test your WCID device.
>> https://github.com/libusb/libusb/releases
>>
>
> One thing you can try.
> 
https://github.com/BrandonLWhite/Stellaris-LaunchPad-UsbDevBulk-AutoWinusbInstall

>
> It could be libusbK is the same as libusbdotnet. I need to check.
> ...
> So I changed the firmware to instead send DeviceInterfaceGUIDs 
REG_MULTI_SZ
> with just the one GUID. LibUsbDotNet worked perfectly after that.
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The other possibility is that your FW is missing DeviceInterfaceGUID 
handling.
Windows may be able to install the device but libusbK or other 
applications will
not be able to find it.

Ref:
http://www.microchip.com/forums/m802958.aspx
http://www.microchip.com/forums/m790429.aspx

-- 
Xiaofan

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

On Mon, Jun 25, 2018 at 7:45 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Sat, Jun 23, 2018 at 10:24 AM, Xiaofan Chen <xia...@gm...> wrote:
>> On Fri, Jun 22, 2018 at 4:33 PM, Chengda Guo <che...@ca...> wrote:
>>> I had used the libusbk and winUsb driver which created by the libusbk-inf-wizard.exe
>>> for installing my device, both of them are OK. And I can access the device by
>>> LibUsbk.dll in my application. Now I would like to automatically install winusb driver
>>> by Windows OS when the device plug into the system, and then use LibUsbk.dll
>>> to access the device in my application. The first step automatically install winusb
>>> driver was successful like below screen shot shows.
>>> But in my application, the device can't be accessed by LibUsbk.dll(Din't find
>>> the device, LstK_Init() succeed, but LstK_Count() return 0 device count).
>>>
>>> Whether this way is feasible or not? What do I need to pay attention to?
>>> Look forward to your kind advice. Thank you very much!
>>>
>>
>> A few questions.
>> 1) What is the OS version?
>>
>> 2) How do you automatically install WinUSB driver by Windows OS?
>> If you use the Windows OS Descriptor, please check the following. You
>> can post the whole USB Descriptor of your device.
>> https://github.com/pbatard/libwdi/wiki/WCID-Devices
>>
>> 3) As the above website suggests, you can download libusb-1.0 Windows
>> binary and use xusb to test your WCID device.
>> https://github.com/libusb/libusb/releases
>>
>
> One thing you can try.
> https://github.com/BrandonLWhite/Stellaris-LaunchPad-UsbDevBulk-AutoWinusbInstall
>
> It could be libusbK is the same as libusbdotnet. I need to check.
> ...
> So I changed the firmware to instead send DeviceInterfaceGUIDs REG_MULTI_SZ
> with just the one GUID. LibUsbDotNet worked perfectly after that.
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

The other possibility is that your FW is missing DeviceInterfaceGUID handling.
Windows may be able to install the device but libusbK or other applications will
not be able to find it.

Ref:
http://www.microchip.com/forums/m802958.aspx
http://www.microchip.com/forums/m790429.aspx

-- 
Xiaofan

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

On Sat, Jun 23, 2018 at 10:24 AM, Xiaofan Chen <xia...@gm...> wrote:
> On Fri, Jun 22, 2018 at 4:33 PM, Chengda Guo <che...@ca...> wrote:
>> I had used the libusbk and winUsb driver which created by the libusbk-inf-wizard.exe
>> for installing my device, both of them are OK. And I can access the device by
>> LibUsbk.dll in my application. Now I would like to automatically install winusb driver
>> by Windows OS when the device plug into the system, and then use LibUsbk.dll
>> to access the device in my application. The first step automatically install winusb
>> driver was successful like below screen shot shows.
>> But in my application, the device can't be accessed by LibUsbk.dll(Din't find
>> the device, LstK_Init() succeed, but LstK_Count() return 0 device count).
>>
>> Whether this way is feasible or not? What do I need to pay attention to?
>> Look forward to your kind advice. Thank you very much!
>>
>
> A few questions.
> 1) What is the OS version?
>
> 2) How do you automatically install WinUSB driver by Windows OS?
> If you use the Windows OS Descriptor, please check the following. You
> can post the whole USB Descriptor of your device.
> https://github.com/pbatard/libwdi/wiki/WCID-Devices
>
> 3) As the above website suggests, you can download libusb-1.0 Windows
> binary and use xusb to test your WCID device.
> https://github.com/libusb/libusb/releases
>

One thing you can try.
https://github.com/BrandonLWhite/Stellaris-LaunchPad-UsbDevBulk-AutoWinusbInstall

It could be libusbK is the same as libusbdotnet. I need to check.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
####DeviceInterfaceGUIDs vs. DeviceInterfaceGUID In my original
firmware, I had it sending
DeviceInterfaceGUID (REG_SZ) to the host when asked for the Microsoft
Extended Properties
Feature Descriptor just like the MSDN docs say to do. When trying to
use LibUsbDotNet,
I immediately ran into problems getting it to find my device. It turns
out that LibUsbDotNet is
hardcoded to look for DeviceInterfaceGUIDs as part of locating WinUSB
devices. As such,
it won't identify a WinUSB device that sends DeviceInterfaceGUID.

What I learned is that in the years prior, whenever you created an
.INF file to load
WinUSB the old way, you included something like this:

[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{6E45736A-2B1B-4078-B772-B3AF2B6FDE1C}"

That's actually straight out of the TI usb_dev_bulk.inf file, but
there's plenty of examples
out there doing the same thing. So it's perfectly normal, in fact I'll
go so far as to say
de facto, that you specify the multiple-form
DeviceInterfaceGUIDscontaining exactly
one GUID.

So I changed the firmware to instead send DeviceInterfaceGUIDs REG_MULTI_SZ
with just the one GUID. LibUsbDotNet worked perfectly after that.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



-- 
Xiaofan

Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

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

On Fri, Jun 22, 2018 at 4:33 PM, Chengda Guo <che...@ca...> wrote:
> I had used the libusbk and winUsb driver which created by the libusbk-inf-wizard.exe
> for installing my device, both of them are OK. And I can access the device by
> LibUsbk.dll in my application. Now I would like to automatically install winusb driver
> by Windows OS when the device plug into the system, and then use LibUsbk.dll
> to access the device in my application. The first step automatically install winusb
> driver was successful like below screen shot shows.
> But in my application, the device can't be accessed by LibUsbk.dll(Din't find
> the device, LstK_Init() succeed, but LstK_Count() return 0 device count).
>
> Whether this way is feasible or not? What do I need to pay attention to?
> Look forward to your kind advice. Thank you very much!
>

A few questions.
1) What is the OS version?

2) How do you automatically install WinUSB driver by Windows OS?
If you use the Windows OS Descriptor, please check the following. You
can post the whole USB Descriptor of your device.
https://github.com/pbatard/libwdi/wiki/WCID-Devices

3) As the above website suggests, you can download libusb-1.0 Windows
binary and use xusb to test your WCID device.
https://github.com/libusb/libusb/releases



-- 
Xiaofan

[Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device

[Chengda G. <che...@ca...>]

Hi libusb-win32-devel,

I had used the libusbk and winUsb driver which created by the 
libusbk-inf-wizard.exe for installing my device, both of them are OK. And 
I can access the device by LibUsbk.dll in my application. Now I would like 
to automatically install winusb driver by Windows OS when the device plug 
into the system, and then use LibUsbk.dll to access the device in my 
application. The first step automatically install winusb driver was 
successful like below screen shot shows.
But in my application, the device can't be accessed by LibUsbk.dll(Din't 
find the device, LstK_Init() succeed, but LstK_Count() return 0 device 
count). 

Whether this way is feasible or not? What do I need to pay attention to? 
Look forward to your kind advice. Thank you very much!




Thanks!
Chengda Guo

Re: [Libusb-win32-devel] Crash in reads with short timeout - race.

[Peter D. T. <don...@td...>]

Hi Travis/Xiaofan/libusb-win32

On Wed, 2018-04-25 at 02:26 +0200, Peter Dons Tychsen via Libusb-win32-
devel wrote:
> In any case, 1 second is a bit short, as that can be triggered on a
> fully loaded system with many USB devices attached via the libusb0
> driver. It should at least be 5-10 seconds to be on the safe side.

Have you decided on a fix? I do not see any commits to the repo. It
would be great if the master repo was updated with a fix for this.

Thanks,

/pedro

Re: [Libusb-win32-devel] USB3 Bulk stream support

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

On Tue, Jun 5, 2018 at 10:19 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Mon, Jun 4, 2018 at 9:33 PM, Stefan Battmer
> <ste...@ma...> wrote:
>> Hi everyone,
>>
>> are there any plans for supporting USB3 bulk streams in libusbK or is this
>> already possible today?
>
> Not supported and I think Travis has no plan to update libusbK to support
> this feature (or any other new features) now.
>
>>
>> If not, what would be an alternative?
> I do not know of any generic usb driver which fully supports this.
> Microsoft has the following documentation which seems to indicate you
> need to write your own driver.
> https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/how-to-open-streams-in-a-usb-endpoint

Google shows that Microsoft's sample usbsamp supports the feature. You can
give it a try. It is under the Microsoft Public License (MS-PL).
https://github.com/Microsoft/Windows-driver-samples/tree/master/usb/usbsamp

> If you are using Linux (and macOS), then you can use libusb which has
> this support.
>



-- 
Xiaofan

Re: [Libusb-win32-devel] USB3 Bulk stream support

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

On Mon, Jun 4, 2018 at 9:33 PM, Stefan Battmer
<ste...@ma...> wrote:
> Hi everyone,
>
> are there any plans for supporting USB3 bulk streams in libusbK or is this
> already possible today?

Not supported and I think Travis has no plan to update libusbK to support
this feature (or any other new features) now.

>
> If not, what would be an alternative?
I do not know of any generic usb driver which fully supports this.
Microsoft has the following documentation which seems to indicate you
need to write your own driver.
https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/how-to-open-streams-in-a-usb-endpoint

If you are using Linux (and macOS), then you can use libusb which has
this support.

-- 
Xiaofan

[Libusb-win32-devel] USB3 Bulk stream support

[Stefan B. <ste...@ma...>]

Hi everyone,

are there any plans for supporting USB3 bulk streams in libusbK or is 
this already possible today?

If not, what would be an alternative?

Thanks,

Mit freundlichen Grüssen / Best regards

Stefan Battmer
____________________________________________________

Entwicklung / Development

MATRIX VISION GmbH
Talstr. 16
D-71570 Oppenweiler
Tel.: +49-(0)7191-9432-0
Fax:  +49-(0)7191-9432-88
mail: ste...@ma...
web:  www.matrix-vision.de
____________________________________________________

-----------------------------------------------------------------
Upcoming Events:
19.-22. June: AUTOMATICA, Munich, Germany
06.-08. November: VISION, Stuttgart, Germany 
-----------------------------------------------------------------

MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Uwe Furtner

Re: [Libusb-win32-devel] Intel Bluetooth replaced with libusbk driver not responding after sleep/restart

[Luke L. <lon...@ho...>]

Hi,
thank you for the answer.

I have a Wiimote Plus compatible controller, which is more problematic than the original Wiimote. It is not detected at all by standard bluetooth drivers, at least not by the Intel models I have on Lenovo machines, but also my Asus Zenfone 2 can't detect it.

I also tested the Toshiba stack on a Windows 7 machine, but it could not detect it, as well. The only working method is the passthrough mode, which suffers from that issue at PC sleep/restart. The best solution could be an external bluetooth dongle, that can be easily reset just by detaching it.

Regards,
Luke
________________________________________
From: Xiaofan Chen <xia...@gm...>
Sent: Tuesday, April 24, 2018 12:22 PM
To: lib...@li...
Subject: Re: [Libusb-win32-devel] Intel Bluetooth replaced with libusbk driver not responding after sleep/restart

On Tue, Apr 24, 2018 at 8:17 PM, Xiaofan Chen <xia...@gm...> wrote:

I am also feeling strange that you need to use libusbK. It is more meant for
generic device and not for bluetooth device. From the following it seems
that you can use the Windows bluetooth driver.
https://wiki.dolphin-emu.org/index.php?title=Wii_Remote_Plus_(RVL-CNT-01-TR)_Connection_Guide

--
Xiaofan

Re: [Libusb-win32-devel] Crash in reads with short timeout - race.

[Peter D. T. <don...@td...>]

Hi Travis,

Thanks for your review/input.

Sorry for late reply. Was traveling.

> Let's check the return code.  What about this:
> static int _usb_cancel_io(usb_context_t *context)
> {
>      int ret;
>      ret = _usb_abort_ep(context->dev, context-
> >req.endpoint.endpoint);
>      if (ret == 0)
>      {
>          WaitForSingleObject(context->ol.hEvent, 1000);
>      }
>      else
>      {
>          WaitForSingleObject(context->ol.hEvent, 0);
>      }
>      return ret;
> }

1) Yes, it should definately check the return code, and only change the
code path that succeeds. Good catch.

2) Normally i would agree that forever timeouts are dangerous, and can
lead to stalls. However, in this particular case the opposite is the
case. You can _not_ return without having completed the pending
read/write that has been cancelled (which is what WaitForSingleObject()
is waiting for).

If the timeout actually fires, the read/write completion would likely
trigger a crash as described in my original post. So it is not an
option that the programming calling this function can use for anything
useful. On the contrary, it can lead to strange memory corruption
issues. When _usb_cancel_io() returns you _must_ be able to rely on the
fact that you can free any resources which were used by the pending
transaction. And in the case where the resource is the local stack (as
my original problem was) the crash/corruption in unavoidable.

Further, the only way that the timeout can happen (if big enough), is
if the entire driver stack is deadlocked, which would probably lead to
something more colorful, like a BSOD.

So i would still argue that for this case the timeout needs to be
INFINITE (with a nice comment) even though it might feel wrong to do so
in other similar cases.

In any case, 1 second is a bit short, as that can be triggered on a
fully loaded system with many USB devices attached via the libusb0
driver. It should at least be 5-10 seconds to be on the safe side.

Thanks,

/pedro

Re: [Libusb-win32-devel] Crash in reads with short timeout - race.

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

On Sat, Apr 14, 2018 at 2:14 AM, Travis <lib...@gm...> wrote:
> Greetings,
>
> Let's check the return code.  What about this:
> static int _usb_cancel_io(usb_context_t *context)
> {
>     int ret;
>     ret = _usb_abort_ep(context->dev, context->req.endpoint.endpoint);
>     if (ret == 0)
>     {
>         WaitForSingleObject(context->ol.hEvent, 1000);
>     }
>     else
>     {
>         WaitForSingleObject(context->ol.hEvent, 0);
>     }
>     return ret;
> }
>
> Use 1000 ms I think.  That should always be plenty and it will keep it from
> dead locking.
>

Hi Peter,

Any updates?


-- 
Xiaofan

Re: [Libusb-win32-devel] Intel Bluetooth replaced with libusbk driver not responding after sleep/restart

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

On Tue, Apr 24, 2018 at 8:17 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Mon, Apr 23, 2018 at 4:02 AM, Luke Lone <lon...@ho...> wrote:
>> Hello,
>> I am just a user, not a developer.
>>
>> System configuration: Lenovo Thinkpad T470 with Intel Dual Band Wireless-AC
>> 8260 and Windows 10 x64.
>> I'm using the libusbk drivers 3.0.7.0 to connect a Wiimote Plus to the
>> Dolphin console emulator via Bluetooth.

I am also feeling strange that you need to use libusbK. It is more meant for
generic device and not for bluetooth device. From the following it seems
that you can use the Windows bluetooth driver.
https://wiki.dolphin-emu.org/index.php?title=Wii_Remote_Plus_(RVL-CNT-01-TR)_Connection_Guide


>> The driver is working perfectly after installation with Zadig utility, but
>> it stops working after the PC restarts or sleeps. I have to uninstall and
>> reinstall the driver in order to make it work again, which is quite
>> annoying.
>

-- 
Xiaofan