Re: About auto install WinUsb driver and use LibusbK to access device
"Chengda Guo" <[email protected]> Tue, 26 Jun 2018 09:42:25 +0800
| Newsgroups | gmane.comp.lib.libusb.devel.windows |
|---|---|
| Message-ID | <OF00A0CA63.AEE42EEF-ON002582B8.000886D6-482582B8.00096068@notes.na.collabserv.com> |
This is a multipart message in MIME format. --===============8302591752474249159== Content-Type: multipart/alternative; boundary="=_alternative 00096008482582B8_=" This is a multipart message in MIME format. --=_alternative 00096008482582B8_= Content-Type: text/plain; charset="US-ASCII" 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 <[email protected]> To: [email protected] 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 <[email protected]> wrote: > On Sat, Jun 23, 2018 at 10:24 AM, Xiaofan Chen <[email protected]> wrote: >> On Fri, Jun 22, 2018 at 4:33 PM, Chengda Guo <[email protected]> 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 [email protected] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel --=_alternative 00096008482582B8_= Content-Type: text/html; charset="US-ASCII" <font size=2 face="sans-serif">Hi Xiaofan,</font> <br> <br><font size=2 face="sans-serif">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 </font><tt><font size=2>DeviceInterfaceGUID</font></tt><font size=2 face="sans-serif"> is missing. I will check the configuration of my WCID device according to your advice. </font> <br> <br><font size=2 face="sans-serif">Thank you very much! </font> <br> <br> <br><font size=1 face="Arial">Chengda </font> <br> <br> <br> <br><font size=1 color=#5f5f5f face="sans-serif">From: </font><font size=1 face="sans-serif">Xiaofan Chen <[email protected]></font> <br><font size=1 color=#5f5f5f face="sans-serif">To: </font><font size=1 face="sans-serif">[email protected]</font> <br><font size=1 color=#5f5f5f face="sans-serif">Date: </font><font size=1 face="sans-serif">2018/06/25 20:05</font> <br><font size=1 color=#5f5f5f face="sans-serif">Subject: </font><font size=1 face="sans-serif">Re: [Libusb-win32-devel] About auto install WinUsb driver and use LibusbK to access device</font> <br> <hr noshade> <br> <br> <br><tt><font size=2>On Mon, Jun 25, 2018 at 7:45 PM, Xiaofan Chen <[email protected]> wrote:<br> > On Sat, Jun 23, 2018 at 10:24 AM, Xiaofan Chen <[email protected]> wrote:<br> >> On Fri, Jun 22, 2018 at 4:33 PM, Chengda Guo <[email protected]> wrote:<br> >>> I had used the libusbk and winUsb driver which created by the libusbk-inf-wizard.exe<br> >>> for installing my device, both of them are OK. And I can access the device by<br> >>> LibUsbk.dll in my application. Now I would like to automatically install winusb driver<br> >>> by Windows OS when the device plug into the system, and then use LibUsbk.dll<br> >>> to access the device in my application. The first step automatically install winusb<br> >>> driver was successful like below screen shot shows.<br> >>> But in my application, the device can't be accessed by LibUsbk.dll(Din't find<br> >>> the device, LstK_Init() succeed, but LstK_Count() return 0 device count).<br> >>><br> >>> Whether this way is feasible or not? What do I need to pay attention to?<br> >>> Look forward to your kind advice. Thank you very much!<br> >>><br> >><br> >> A few questions.<br> >> 1) What is the OS version?<br> >><br> >> 2) How do you automatically install WinUSB driver by Windows OS?<br> >> If you use the Windows OS Descriptor, please check the following. You<br> >> can post the whole USB Descriptor of your device.<br> >> </font></tt><a href="https://github.com/pbatard/libwdi/wiki/WCID-Devices"><tt><font size=2>https://github.com/pbatard/libwdi/wiki/WCID-Devices</font></tt></a><tt><font size=2><br> >><br> >> 3) As the above website suggests, you can download libusb-1.0 Windows<br> >> binary and use xusb to test your WCID device.<br> >> </font></tt><a href=https://github.com/libusb/libusb/releases><tt><font size=2>https://github.com/libusb/libusb/releases</font></tt></a><tt><font size=2><br> >><br> ><br> > One thing you can try.<br> > </font></tt><a href="https://github.com/BrandonLWhite/Stellaris-LaunchPad-UsbDevBulk-AutoWinusbInstall"><tt><font size=2>https://github.com/BrandonLWhite/Stellaris-LaunchPad-UsbDevBulk-AutoWinusbInstall</font></tt></a><tt><font size=2><br> ><br> > It could be libusbK is the same as libusbdotnet. I need to check.<br> > ...<br> > So I changed the firmware to instead send DeviceInterfaceGUIDs REG_MULTI_SZ<br> > with just the one GUID. LibUsbDotNet worked perfectly after that.<br> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br> <br> The other possibility is that your FW is missing DeviceInterfaceGUID handling.<br> Windows may be able to install the device but libusbK or other applications will<br> not be able to find it.<br> <br> Ref:<br> </font></tt><a href=http://www.microchip.com/forums/m802958.aspx><tt><font size=2>http://www.microchip.com/forums/m802958.aspx</font></tt></a><tt><font size=2><br> </font></tt><a href=http://www.microchip.com/forums/m790429.aspx><tt><font size=2>http://www.microchip.com/forums/m790429.aspx</font></tt></a><tt><font size=2><br> <br> -- <br> Xiaofan<br> <br> ------------------------------------------------------------------------------<br> Check out the vibrant tech community on one of the world's most<br> engaging tech sites, Slashdot.org! </font></tt><a href=http://sdm.link/slashdot><tt><font size=2>http://sdm.link/slashdot</font></tt></a><tt><font size=2><br> _______________________________________________<br> Libusb-win32-devel mailing list<br> [email protected]<br> </font></tt><a href="https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel"><tt><font size=2>https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel</font></tt></a><tt><font size=2><br> </font></tt> <br> --=_alternative 00096008482582B8_=-- --===============8302591752474249159== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot --===============8302591752474249159== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Libusb-win32-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel --===============8302591752474249159==--