libusb-win32-devel

Re: [Libusb-win32-devel] usb_bulk_read return -22

[Ze H. Z. <ze....@ma...>]

Hi Xiaofan
I open and received device handler, and be able to use usb_control_msg to
send and receive data.  also checked device interface endpoints, but I
can’t use usb_bulk_read to read big buffer from device which supposed to be
ready
Thanks

On Fri 3 Apr 2020 at 03:28, Xiaofan Chen <xia...@gm...> wrote:

> On Thu, Apr 2, 2020 at 1:00 AM Ze Hou Zhang <ze....@ma...> wrote:
> >
> > Hi All
> > I dont have a lot experience for developping embedded system.
> > I encounter this problem
> > My hardware is :
> >         int vid = 0x24aa;
> >         int pid = 0x1000;
> >         std::string firmwarePartNum = "170003";
> >         std::string firmwareDesc = "FX2 USB Board";
> >         bool isSupported;
> >         unsigned int defaultPixels = 1024;
> >         unsigned int spectraBlockSize = 1024 * 2;
> >         unsigned int usbDelayMS = 0;
> >         bool hasDefaultTECSetpointDegC = false;
> >         int defaultTECSetpointDegC = 0;
> > =============================================================
> >            int size = 512;
> >             char* buf = new char[size];
> >             int endpoint = 130;
> >             int timeout = 150;
> >
> >             int isok = usb_bulk_read(*deviceHandle, endpoint, bytes,
> size, timeout);
> >
> >            Output:  ok = -22
> > Thanks
> >
>
> You have to know the communication protocol of the device in order
> to use libusb-win32. In your case, you need to make sure your device
> is sending data.
>
>
> --
> Xiaofan
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

-- 
__

Séanadh Ríomhphoist/_

Email Disclaimer__
**

Tá an ríomhphost seo agus 
aon chomhad a sheoltar leis faoi rún agus is lena úsáid ag an seolaí agus 
sin amháin é. Is féidir tuilleadh a léamh anseo. 
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>  
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>*
_

This e-mail and any 
files transmitted with it are confidential and are intended solely for use 
by the addressee. Read more here. 
<https://www4.dcu.ie/iss/email-disclaimer.shtml> _
*_

Re: [Libusb-win32-devel] usb_bulk_read return -22

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

On Thu, Apr 2, 2020 at 1:00 AM Ze Hou Zhang <ze....@ma...> wrote:
>
> Hi All
> I dont have a lot experience for developping embedded system.
> I encounter this problem
> My hardware is :
>         int vid = 0x24aa;
>         int pid = 0x1000;
>         std::string firmwarePartNum = "170003";
>         std::string firmwareDesc = "FX2 USB Board";
>         bool isSupported;
>         unsigned int defaultPixels = 1024;
>         unsigned int spectraBlockSize = 1024 * 2;
>         unsigned int usbDelayMS = 0;
>         bool hasDefaultTECSetpointDegC = false;
>         int defaultTECSetpointDegC = 0;
> =============================================================
>            int size = 512;
>             char* buf = new char[size];
>             int endpoint = 130;
>             int timeout = 150;
>
>             int isok = usb_bulk_read(*deviceHandle, endpoint, bytes, size, timeout);
>
>            Output:  ok = -22
> Thanks
>

You have to know the communication protocol of the device in order
to use libusb-win32. In your case, you need to make sure your device
is sending data.


-- 
Xiaofan

[Libusb-win32-devel] usb_bulk_read return -22

[Ze H. Z. <ze....@ma...>]

Hi All
I dont have a lot experience for developping embedded system.
I encounter this problem
My hardware is :
        int vid = 0x24aa;
        int pid = 0x1000;
        std::string firmwarePartNum = "170003";
        std::string firmwareDesc = "FX2 USB Board";
        bool isSupported;
        unsigned int defaultPixels = 1024;
        unsigned int spectraBlockSize = 1024 * 2;
        unsigned int usbDelayMS = 0;
        bool hasDefaultTECSetpointDegC = false;
        int defaultTECSetpointDegC = 0;
=============================================================
           int size = 512;
            char* buf = new char[size];
            int endpoint = 130;
            int timeout = 150;

            int isok = usb_bulk_read(*deviceHandle, endpoint, bytes, size,
timeout);

           Output:  ok = -22
Thanks

-- 
__

Séanadh Ríomhphoist/_

Email Disclaimer__
**

Tá an ríomhphost seo agus 
aon chomhad a sheoltar leis faoi rún agus is lena úsáid ag an seolaí agus 
sin amháin é. Is féidir tuilleadh a léamh anseo. 
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>  
<https://www4.dcu.ie/iss/seanadh-riomhphoist.shtml>*
_

This e-mail and any 
files transmitted with it are confidential and are intended solely for use 
by the addressee. Read more here. 
<https://www4.dcu.ie/iss/email-disclaimer.shtml> _
*_

Re: [Libusb-win32-devel] [libusb-win32:bugs] Moderation action required

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

Hi all,

Please use github for bugs report in the future.

Thanks.
Xiaofan

On Wed, Sep 25, 2019, 2:33 PM karthiga <kar...@us...>
wrote:

> The following submission requires approval at
> https://sourceforge.net/p/libusb-win32/bugs/_discuss/moderate before it
> can be approved for posting:
>
> Hi Peter,
>
> I finally successed to sign with EV certificate and the device works
> properly with verifier activated with code integrity checks and is
> recognized as complaint with windows 10 HCVI mode by the Device Guard and
> Credential Guard hardware readiness tool .
>
> Thanks again for your great work and prompt release !
>
> Karthiga.
>
>
> ---
>
> Sent from sourceforge.net because you indicated interest in <
> https://sourceforge.net/p/libusb-win32/bugs/85/>
>
>
>
> To unsubscribe from further messages, please visit <
> https://sourceforge.net/auth/subscriptions/>
>

Re: [Libusb-win32-devel] Query : Necessity of Signing LibUsb driver

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

Hi Rinkesh,

On Thu, 2019-09-19 at 18:54 +0000, Rinkesh Patel via Libusb-win32-
devel 
wrote:
> I figured out that we need to SignIn LibUsb driver to install and use
> it on windows10.
> My question is, can I use Libraries of LibUSB directly in my Project
> and bind them statically compile time.
> 1)      Will this approach work on all Windows OSs I mentioned above?
> Or
> 2)      Do I still need to sign in LibUSB driver for Windows-10.
> 3)      Do I also need to sign-in for Other than Windows10 OSes as
> well?

1) Yes, you can link the library part of libusb-win32 statically to
your project, if your project is open source. If not, you need to link
to it dynamically. I am not a legal expert, but i am fairly sure that
is the limitation of LGPL v2. Consult your legal team for advice on
this.

2) Yes, always if you use the driver libusb0.sys. You can also use
WinUsb or LibUsbK.

3) That depends if you want to use it with other OSes. Windows 10 can
be attestation signed, and previous versions cannot. For win7 and win8
you need to pass the test suite from MS and upload the results to their
portal. If you pass all the tests for win7,win8 & win10 you can sign
the driver once and for all.

Additionally, to sign for Win10 you need an EV cert, as a normal cert
will not do.

Thanks,

/pedro

[Libusb-win32-devel] Query : Necessity of Signing LibUsb driver

[Rinkesh P. <rin...@ta...>]

Hello,

We are planning to use LibUsb for one of our commercial application to be supported on Windows-7, Windows-8, Windows-8.1 and  Windows-10.
I downloaded LibUsb package from below link
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/

I figured out that we need to SignIn LibUsb driver to install and use it on windows10.
My question is, can I use Libraries of LibUSB directly in my Project and bind them statically compile time.

1)      Will this approach work on all Windows OSs I mentioned above? Or

2)      Do I still need to sign in LibUSB driver for Windows-10.

3)      Do I also need to sign-in for Other than Windows10 OSes as well?

Best Regards,
Rinkesh Patel
TATA ELXSI
Tel +1 571 635 9590
www.tataelxsi.com<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tataelxsi.com%2F&data=02%7C01%7C%7C9706231530f5442fdc6a08d6335b67cd%7Cad6a39dd96b6436882daf2ec4d92e26a%7C0%7C0%7C636752864997026470&sdata=uOt83JqvD4Cq3h%2Bf1Zza8IHxJiC7o0YHemmXYYYTDsY%3D&reserved=0>


________________________________
Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message , or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibited. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability for any errors, omissions or contaminations in the contents of this message which might have occurred as a result of email transmission. If verification is required, please request for a hard-copy version.
________________________________

Re: [Libusb-win32-devel] Error: unable to open ftdi device

[<Pet...@t-...>]

Hello Xiaofan,

in the meantime I´ve already recognized my fault. I´ve told that question to the OpenOCD mailing list, and I´ve got a very good support by Paul Fertser. But thank you for your comment: now it is clear for me.

Best regards,
Peter

-----Original-Nachricht-----
Betreff: Re: [Libusb-win32-devel] Error: unable to open ftdi device
Datum: 2019-04-07T05:26:05+0200
Von: "Xiaofan Chen" <xia...@gm...>
An: "Pet...@t-..." <Pet...@t-...>, "lib...@li..." <lib...@li...>

In order to use OpenOCD under Windows you have to use a supported driver.

For FTDI device, the recommended driver is to use WinUSB and use libusb-1.0
Windows (libusb-1.0.dll) and not libusb-win32 together with OpenOCD. Yet
another possibility is usbdk driver, again with libusb-1.0 Windows and not
libusb-win32.

You should ask for more help in OpenOCD mailing list. This is the wrong
mailing list for OpenOCD. This is also not the correct mailing list for
libusb-1.0 Windows.

Regards,
Xiaofan

On Wed, Mar 27, 2019 at 6:41 PM Pet...@t-...
<Pet...@t-...> wrote:
>
> Hello all,
>
>
>
> I waant to use a mikrocontroller board communicatin by OpenOCD via USB. I´ve installed
>
> https://sourceforge.net/projects/libusb-win32/
>
>
>
> And when I connect that device at USB I see two entries
>
> USB Serial Converter A (Interface 0)
>
> USB Serial Converter B (Interface 1)
>
>
>
> Both with Driver libusb0 (v1.2.6.0)
>
> USB ID 0403 6010 00
>
>
>
> I use a config file thm_arduino.cfg with the follwoing entries:
>
>
>
> interface ftdi
> ftdi_device_desc "OOCDLink"
> ftdi_vid_pid 0x0403 0x6010
>
>
>
> and run on console of my Windows Vista Business Service Pack 2 (latest version)
>
>
>
> openocd -f C:\Users\oehler\workspace\Labor3\interface\thm_arduino.cfg -f C:\Users\oehler\workspace\Labor3\mrt\board\thm_arduino.cfg
>
>
>
> But I am getting always the message:
>
>
>
> Error: no device found
>
> Error: unable to open ftdi device with vid 0403, pid 6010, description 'OOCDLink', serial '*' at bus location '*'
>
>
>
> Why OpenOCD can not find that device? What can I do to further check that the driver is correct installed?
>
>
>
> Best regards,
>
> Dr. Peter Oehler
>


Re: [Libusb-win32-devel] Error: unable to open ftdi device

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

In order to use OpenOCD under Windows you have to use a supported driver.

For FTDI device, the recommended driver is to use WinUSB and use libusb-1.0
Windows (libusb-1.0.dll) and not libusb-win32 together with OpenOCD. Yet
another possibility is usbdk driver, again with libusb-1.0 Windows and not
libusb-win32.

You should ask for more help in OpenOCD mailing list. This is the wrong
mailing list for OpenOCD. This is also not the correct mailing list for
libusb-1.0 Windows.

Regards,
Xiaofan

On Wed, Mar 27, 2019 at 6:41 PM Pet...@t-...
<Pet...@t-...> wrote:
>
> Hello all,
>
>
>
> I waant to use a mikrocontroller board communicatin by OpenOCD via USB. I´ve installed
>
> https://sourceforge.net/projects/libusb-win32/
>
>
>
> And when I connect that device at USB I see two entries
>
> USB Serial Converter A (Interface 0)
>
> USB Serial Converter B (Interface 1)
>
>
>
> Both with Driver libusb0 (v1.2.6.0)
>
> USB ID 0403 6010 00
>
>
>
> I use a config file thm_arduino.cfg with the follwoing entries:
>
>
>
> interface ftdi
> ftdi_device_desc "OOCDLink"
> ftdi_vid_pid 0x0403 0x6010
>
>
>
> and run on console of my Windows Vista Business Service Pack 2 (latest version)
>
>
>
> openocd -f C:\Users\oehler\workspace\Labor3\interface\thm_arduino.cfg -f C:\Users\oehler\workspace\Labor3\mrt\board\thm_arduino.cfg
>
>
>
> But I am getting always the message:
>
>
>
> Error: no device found
>
> Error: unable to open ftdi device with vid 0403, pid 6010, description 'OOCDLink', serial '*' at bus location '*'
>
>
>
> Why OpenOCD can not find that device? What can I do to further check that the driver is correct installed?
>
>
>
> Best regards,
>
> Dr. Peter Oehler
>

[Libusb-win32-devel] Error: unable to open ftdi device

[<Pet...@t-...>]

Hello all,
 
I waant to use a mikrocontroller board communicatin by OpenOCD via USB. 
I´ve installed
https://sourceforge.net/projects/libusb-win32/
<https://sourceforge.net/projects/libusb-win32/>
 
And when I connect that device at USB I see two entries
USB Serial Converter A (Interface 0)
USB Serial Converter B (Interface 1)
 
Both with Driver libusb0 (v1.2.6.0)
USB ID 0403 6010 00
 
I use a config file thm_arduino.cfg with the follwoing entries:
 
interface ftdi
ftdi_device_desc "OOCDLink"
ftdi_vid_pid 0x0403 0x6010
 
and run on console of my Windows Vista Business Service Pack 2 (latest 
version)
 
openocd -f C:\Users\oehler\workspace\Labor3\interface\thm_arduino.cfg -f 
C:\Users\oehler\workspace\Labor3\mrt\board\thm_arduino.cfg
 
But I am getting always the message:
 
Error: no device found
Error: unable to open ftdi device with vid 0403, pid 6010, description 
'OOCDLink', serial '*' at bus location '*'
 
Why OpenOCD can not find that device? What can I do to further check that 
the driver is correct installed?
 
Best regards,
Dr. Peter Oehler


Re: [Libusb-win32-devel] Re-packing installer fails - 7zip issues?

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

FYI, it is here.
https://github.com/mcuee/libusbk/issues/5

Regards,
Xiaofan

On Tue, Apr 10, 2018 at 6:12 AM Rafael Send <rs...@be...> wrote:
>
> I'll give this a shot, thanks for the pointer though.
>
> Should I file this somewhere?
>
> Cheers,
> R
>
> On Mon, Apr 9, 2018 at 3:01 PM, Travis <lib...@gm...> wrote:
>>
>> Greetings,
>>
>> Well that's annoying.  Apparently 7zip changed their syntax a good long while ago.
>>
>> Thankfully, You can still get the one you need!  Get version 9.20.
>> https://sourceforge.net/projects/sevenzip/files/7-Zip/9.20/
>>
>> Regards,
>> Travis
>>
>>
>> On 4/9/2018 12:43 PM, Rafael Send wrote:
>>>
>>> Hi,
>>> I'm attempting to use InfWizard to create an installer for a custom USB device (this alone works fine), but I need it to be silent. To that end I'm attempting to modify the dpinst.xml file with the silent option (which also works on its own), but I can't repackage an installer.
>>> The re-pack.cmd script always fails with a 7zip error ("-ai switch not valid for this command").
>>>
>>> I've tried manually performing that step, but I have not been able to repackage a working installer.
>>>
>>> Is this a known current bug?
>>>
>>> Cheers,
>>> Rafael

Re: [Libusb-win32-devel] re-pack-files.cmd

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

On Sat, Sep 22, 2018 at 3:02 AM diabolo via Libusb-win32-devel
<lib...@li...> wrote:
>
> try unix2dos the cmd file
> also you need a quite old 7za with command line
> rgds

Yes you need an old version of 7zip. Please refer to previous answer by Travis.

-- 
Xiaofan



On Tue, Apr 10, 2018 at 6:02 AM Travis <lib...@gm...> wrote:
>
> Greetings,
>
> Well that's annoying.  Apparently 7zip changed their syntax a good long
> while ago.
>
> Thankfully, You can still get the one you need!  Get version 9.20.
> https://sourceforge.net/projects/sevenzip/files/7-Zip/9.20/
>
> Regards,
> Travis
>
> On 4/9/2018 12:43 PM, Rafael Send wrote:
> > Hi,
> > I'm attempting to use InfWizard to create an installer for a custom
> > USB device (this alone works fine), but I need it to be silent. To
> > that end I'm attempting to modify the dpinst.xml file with the silent
> > option (which also works on its own), but I can't repackage an installer.
> > The re-pack.cmd script always fails with a 7zip error ("-ai switch not
> > valid for this command").
> >
> > I've tried manually performing that step, but I have not been able to
> > repackage a working installer.
> >
> > Is this a known current bug?
> >
> > Cheers,
> > Rafael
> >

Re: [Libusb-win32-devel] re-pack-files.cmd

[diabolo <dia...@ya...>]

try unix2dos the cmd file 
also you need a quite old 7za with command line 
rgds

[Libusb-win32-devel] re-pack-files.cmd

[Ole J. <oa...@am...>]

Hi

I installed the_UsbK Development Kit_  and tried to run re-pack-files.cmd and it came with this error:

7Zip found at: "C:\Program Files\7-Zip\7z.exe"

7-Zip 18.05 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2018-04-30

Command Line Error:

-ai switch is not supported for this command

Failed re-packing.  Check your 7Zip installation at

"7z.exe"

Press any key to continue . . .

Is there an error in the re-pack-files.cmd source or in the 7z.exe ?
What should I do to get around this ?

Best regards Ole Jørgensen

Re: [Libusb-win32-devel] Please help installing libusb-32.

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

On Thu, Sep 13, 2018 at 3:07 AM Dmitry Donskoy <ad...@da...> wrote:
>
> Thanks! I tried to do this, but the log is not something I can
> understand... Can you have a look please, is there something that can
> lead to a conclusion?
>
> https://pastebin.com/fEWKmtwe
>

Please reply to the mailing list. Thanks.

Just one more suggestion, libusbK driver (libusbk.sys) is also compatible
with libusb-win32 library/API (libusb0.dll), you can try it to see if
that helps.


-- 
Xiaofan

Re: [Libusb-win32-devel] Please help installing libusb-32.

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

On Wed, Sep 12, 2018 at 4:08 PM Dmitry Donskoy <ad...@da...> wrote:
>
> Thanks! I tried to do this, but the log is not something I can
> understand... Can you have a look please, is there something that can
> lead to a conclusion?

Please reply to the mailing list. Thanks.

>From the debug log, the device is kicked out by Windows. So this
further conclues that the device is the problem.

00000150 35.34378433 libusb0-sys:dbg [dispatch_pnp]
IRP_MN_QUERY_CAPABILITIES: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000151 39.12704086 libusb0-sys:[dispatch_pnp]
IRP_MN_SURPRISE_REMOVAL: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000152 39.12715149 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=-1
00000153 39.12784195 libusb0-sys:[dispatch_pnp] IRP_MN_REMOVE_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002


*********************

00000001 0.00000000 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000002 0.21539547 [2128] UserNotificationThread::action() m_State=1 provMode=1
00000001 7.32802153 libusb0-sys:[DriverEntry] [loading-driver] v1.2.6.0
00000002 7.32823467 libusb0-sys:dbg [debug_show_devices]
[AttachedDevice #0] \Driver\DwDevGuard
00000003 7.32829523 libusb0-sys:[add_device] device #1 created for
usb\vid_0d9f&pid_0004&rev_0002
00000004 7.32833958 libusb0-sys:[reg_get_properties] using default
device interface guid.
00000005 7.32834959 libusb0-sys:dbg [reg_get_properties]
reg-key-name=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_0D9F&PID_0004\004-0D9F-000\Device
Parameters
00000006 7.32835770 libusb0-sys:wrn [add_device]
[FILTER-MODE-MISMATCH] device is reporting itself as normal when there
are already attached device(s).
00000007 7.32835865 usb\vid_0d9f&pid_0004&rev_0002
00000008 7.32851362 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=1
00000009 7.32854319 libusb0-sys:[add_device] updated interface
registry with LUsb0 direct-access symbolic link. id=0001
00000010 7.32855082 libusb0-sys:dbg [add_device] [normal-mode] id=#1
usb\vid_0d9f&pid_0004&rev_0002
00000011 7.32855320 libusb0-sys:[add_device] complete status=00000000
00000012 7.32896185 libusb0-sys:[dispatch_pnp] IRP_MN_START_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000013 7.32927561 libusb0-sys:dbg [on_start_complete] is-filter=N
usb\vid_0d9f&pid_0004&rev_0002
00000014 7.32929039 libusb0-sys:dbg [on_start_complete] applying
active configuration for usb\vid_0d9f&pid_0004&rev_0002
00000015 7.32929945 libusb0-sys:[set_configuration] setting
configuration index 0 timeout=5000libusb0-sys:[get_descriptor] buffer
size: 18 type: 0001 recipient: 0000 index: 0000 language id: 0000
timeout: 5000
00000016 7.33450222 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000017 7.33451462 libusb0-sys:[get_descriptor] buffer size: 9 type:
0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000018 7.33951044 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000019 7.33952093 libusb0-sys:[get_descriptor] buffer size: 34 type:
0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000020 7.34749603 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000021 7.34750175 libusb0-sys:[set_configuration] found interface 0
00000022 7.35051012 libusb0-sys:dbg [set_configuration] #1
usb\vid_0d9f&pid_0004&rev_0002 passing configuration request to
target-device.libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000023 7.35052967 libusb0-sys:[update_pipe_info] interface 0
00000024 7.35053492 libusb0-sys:[update_pipe_info] EP81h
maximum-packet-size=8 maximum-transfer-size=4194304
00000025 7.35053825 libusb0-sys:wrn [update_pipe_info] overriding
EP81h maximum-transfer-size=65536
00000026 7.35073996 libusb0-sys:dbg [dispatch_pnp]
IRP_MN_QUERY_CAPABILITIES: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000003 9.67733288 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000004 10.04938507 [2128] UserNotificationThread::action() m_State=1
provMode=1
00000027 11.10794640 libusb0-sys:[dispatch_pnp]
IRP_MN_SURPRISE_REMOVAL: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000028 11.10802174 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=-1
00000029 11.10856533 libusb0-sys:[dispatch_pnp] IRP_MN_REMOVE_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000030 11.10861778 libusb0-sys:[dispatch_pnp] deleting device #1
usb\vid_0d9f&pid_0004&rev_0002
00000031 11.10872364 libusb0-sys:[unload] [unloading-driver] v1.2.6.0
00000032 14.32586193 libusb0-sys:[DriverEntry] [loading-driver] v1.2.6.0
00000033 14.32618713 libusb0-sys:dbg [debug_show_devices]
[AttachedDevice #0] \Driver\DwDevGuard
00000034 14.32625580 libusb0-sys:[add_device] device #1 created for
usb\vid_0d9f&pid_0004&rev_0002
00000035 14.32630062 libusb0-sys:[reg_get_properties] using default
device interface guid.
00000036 14.32631016 libusb0-sys:dbg [reg_get_properties]
reg-key-name=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_0D9F&PID_0004\004-0D9F-000\Device
Parameters
00000037 14.32631969 libusb0-sys:wrn [add_device]
[FILTER-MODE-MISMATCH] device is reporting itself as normal when there
are already attached device(s).
00000038 14.32631969 usb\vid_0d9f&pid_0004&rev_0002
00000039 14.32650757 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=1
00000040 14.32653809 libusb0-sys:[add_device] updated interface
registry with LUsb0 direct-access symbolic link. id=0001
00000041 14.32654476 libusb0-sys:dbg [add_device] [normal-mode] id=#1
usb\vid_0d9f&pid_0004&rev_0002
00000042 14.32654858 libusb0-sys:[add_device] complete status=00000000
00000043 14.32714176 libusb0-sys:[dispatch_pnp] IRP_MN_START_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000044 14.32746792 libusb0-sys:dbg [on_start_complete] is-filter=N
usb\vid_0d9f&pid_0004&rev_0002
00000045 14.32747459 libusb0-sys:dbg [on_start_complete] applying
active configuration for usb\vid_0d9f&pid_0004&rev_0002
00000046 14.32748318 libusb0-sys:[set_configuration] setting
configuration index 0 timeout=5000libusb0-sys:[get_descriptor] buffer
size: 18 type: 0001 recipient: 0000 index: 0000 language id: 0000
timeout: 5000
00000047 14.33349800 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000048 14.33350563 libusb0-sys:[get_descriptor] buffer size: 9 type:
0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000049 14.33849907 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000050 14.33851051 libusb0-sys:[get_descriptor] buffer size: 34
type: 0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000051 14.34648705 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000052 14.34649372 libusb0-sys:[set_configuration] found interface 0
00000053 14.34950447 libusb0-sys:dbg [set_configuration] #1
usb\vid_0d9f&pid_0004&rev_0002 passing configuration request to
target-device.libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000054 14.34951687 libusb0-sys:[update_pipe_info] interface 0
00000055 14.34952068 libusb0-sys:[update_pipe_info] EP81h
maximum-packet-size=8 maximum-transfer-size=4194304
00000056 14.34952354 libusb0-sys:wrn [update_pipe_info] overriding
EP81h maximum-transfer-size=65536
00000057 14.34974384 libusb0-sys:dbg [dispatch_pnp]
IRP_MN_QUERY_CAPABILITIES: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000058 18.10996437 libusb0-sys:[dispatch_pnp]
IRP_MN_SURPRISE_REMOVAL: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000059 18.11004066 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=-1
00000060 18.11078644 libusb0-sys:[dispatch_pnp] IRP_MN_REMOVE_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000061 18.11085510 libusb0-sys:[dispatch_pnp] deleting device #1
usb\vid_0d9f&pid_0004&rev_0002
00000062 18.11095238 libusb0-sys:[unload] [unloading-driver] v1.2.6.0
00000005 19.68000603 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000006 20.05203819 [2128] UserNotificationThread::action() m_State=1
provMode=1
00000063 21.31895828 libusb0-sys:[DriverEntry] [loading-driver] v1.2.6.0
00000064 21.31919289 libusb0-sys:dbg [debug_show_devices]
[AttachedDevice #0] \Driver\DwDevGuard
00000065 21.31926537 libusb0-sys:[add_device] device #1 created for
usb\vid_0d9f&pid_0004&rev_0002
00000066 21.31930733 libusb0-sys:[reg_get_properties] using default
device interface guid.
00000067 21.31931686 libusb0-sys:dbg [reg_get_properties]
reg-key-name=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_0D9F&PID_0004\004-0D9F-000\Device
Parameters
00000068 21.31932640 libusb0-sys:wrn [add_device]
[FILTER-MODE-MISMATCH] device is reporting itself as normal when there
are already attached device(s).
00000069 21.31932640 usb\vid_0d9f&pid_0004&rev_0002
00000070 21.31948280 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=1
00000071 21.31951332 libusb0-sys:[add_device] updated interface
registry with LUsb0 direct-access symbolic link. id=0001
00000072 21.31952095 libusb0-sys:dbg [add_device] [normal-mode] id=#1
usb\vid_0d9f&pid_0004&rev_0002
00000073 21.31952286 libusb0-sys:[add_device] complete status=00000000
00000074 21.32005310 libusb0-sys:[dispatch_pnp] IRP_MN_START_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000075 21.32035446 libusb0-sys:dbg [on_start_complete] is-filter=N
usb\vid_0d9f&pid_0004&rev_0002
00000076 21.32035828 libusb0-sys:dbg [on_start_complete] applying
active configuration for usb\vid_0d9f&pid_0004&rev_0002
00000077 21.32036781 libusb0-sys:[set_configuration] setting
configuration index 0 timeout=5000libusb0-sys:[get_descriptor] buffer
size: 18 type: 0001 recipient: 0000 index: 0000 language id: 0000
timeout: 5000
00000078 21.32552147 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000079 21.32553291 libusb0-sys:[get_descriptor] buffer size: 9 type:
0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000080 21.33049393 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000081 21.33050346 libusb0-sys:[get_descriptor] buffer size: 34
type: 0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000082 21.33850098 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000083 21.33851814 libusb0-sys:[set_configuration] found interface 0
00000084 21.34150505 libusb0-sys:dbg [set_configuration] #1
usb\vid_0d9f&pid_0004&rev_0002 passing configuration request to
target-device.libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000085 21.34151649 libusb0-sys:[update_pipe_info] interface 0
00000086 21.34152222 libusb0-sys:[update_pipe_info] EP81h
maximum-packet-size=8 maximum-transfer-size=4194304
00000087 21.34152794 libusb0-sys:wrn [update_pipe_info] overriding
EP81h maximum-transfer-size=65536
00000088 21.34180069 libusb0-sys:dbg [dispatch_pnp]
IRP_MN_QUERY_CAPABILITIES: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000089 25.10994148 libusb0-sys:[dispatch_pnp]
IRP_MN_SURPRISE_REMOVAL: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000090 25.11001968 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=-1
00000091 25.11064339 libusb0-sys:[dispatch_pnp] IRP_MN_REMOVE_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000092 25.11069679 libusb0-sys:[dispatch_pnp] deleting device #1
usb\vid_0d9f&pid_0004&rev_0002
00000093 25.11077499 libusb0-sys:[unload] [unloading-driver] v1.2.6.0
00000094 28.32068634 libusb0-sys:[DriverEntry] [loading-driver] v1.2.6.0
00000095 28.32087708 libusb0-sys:dbg [debug_show_devices]
[AttachedDevice #0] \Driver\DwDevGuard
00000096 28.32093620 libusb0-sys:[add_device] device #1 created for
usb\vid_0d9f&pid_0004&rev_0002
00000097 28.32099152 libusb0-sys:[reg_get_properties] using default
device interface guid.
00000098 28.32100105 libusb0-sys:dbg [reg_get_properties]
reg-key-name=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_0D9F&PID_0004\004-0D9F-000\Device
Parameters
00000099 28.32101059 libusb0-sys:wrn [add_device]
[FILTER-MODE-MISMATCH] device is reporting itself as normal when there
are already attached device(s).
00000100 28.32101059 usb\vid_0d9f&pid_0004&rev_0002
00000101 28.32119560 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=1
00000102 28.32122803 libusb0-sys:[add_device] updated interface
registry with LUsb0 direct-access symbolic link. id=0001
00000103 28.32125473 libusb0-sys:dbg [add_device] [normal-mode] id=#1
usb\vid_0d9f&pid_0004&rev_0002
00000104 28.32125854 libusb0-sys:[add_device] complete status=00000000
00000105 28.32207680 libusb0-sys:[dispatch_pnp] IRP_MN_START_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000106 28.32253647 libusb0-sys:dbg [on_start_complete] is-filter=N
usb\vid_0d9f&pid_0004&rev_0002
00000107 28.32254219 libusb0-sys:dbg [on_start_complete] applying
active configuration for usb\vid_0d9f&pid_0004&rev_0002
00000108 28.32260895 libusb0-sys:[set_configuration] setting
configuration index 0 timeout=5000libusb0-sys:[get_descriptor] buffer
size: 18 type: 0001 recipient: 0000 index: 0000 language id: 0000
timeout: 5000
00000109 28.32851028 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000110 28.32852173 libusb0-sys:[get_descriptor] buffer size: 9 type:
0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000111 28.33350182 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000112 28.33350754 libusb0-sys:[get_descriptor] buffer size: 34
type: 0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000113 28.34148979 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000114 28.34149742 libusb0-sys:[set_configuration] found interface 0
00000115 28.34451294 libusb0-sys:dbg [set_configuration] #1
usb\vid_0d9f&pid_0004&rev_0002 passing configuration request to
target-device.libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000116 28.34452820 libusb0-sys:[update_pipe_info] interface 0
00000117 28.34453583 libusb0-sys:[update_pipe_info] EP81h
maximum-packet-size=8 maximum-transfer-size=4194304
00000118 28.34453964 libusb0-sys:wrn [update_pipe_info] overriding
EP81h maximum-transfer-size=65536
00000119 28.34478760 libusb0-sys:dbg [dispatch_pnp]
IRP_MN_QUERY_CAPABILITIES: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000007 29.68789864 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000008 30.05833435 [2128] UserNotificationThread::action() m_State=1
provMode=1
00000120 32.10197449 libusb0-sys:[dispatch_pnp]
IRP_MN_SURPRISE_REMOVAL: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000121 32.10205078 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=-1
00000122 32.10254288 libusb0-sys:[dispatch_pnp] IRP_MN_REMOVE_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000123 32.10257339 libusb0-sys:[dispatch_pnp] deleting device #1
usb\vid_0d9f&pid_0004&rev_0002
00000124 32.10263062 libusb0-sys:[unload] [unloading-driver] v1.2.6.0
00000125 35.32081223 libusb0-sys:[DriverEntry] [loading-driver] v1.2.6.0
00000126 35.32102203 libusb0-sys:dbg [debug_show_devices]
[AttachedDevice #0] \Driver\DwDevGuard
00000127 35.32108307 libusb0-sys:[add_device] device #1 created for
usb\vid_0d9f&pid_0004&rev_0002
00000128 35.32114029 libusb0-sys:[reg_get_properties] using default
device interface guid.
00000129 35.32114792 libusb0-sys:dbg [reg_get_properties]
reg-key-name=\REGISTRY\MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_0D9F&PID_0004\004-0D9F-000\Device
Parameters
00000130 35.32115936 libusb0-sys:wrn [add_device]
[FILTER-MODE-MISMATCH] device is reporting itself as normal when there
are already attached device(s).
00000131 35.32115936 usb\vid_0d9f&pid_0004&rev_0002
00000132 35.32132339 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=1
00000133 35.32136154 libusb0-sys:[add_device] updated interface
registry with LUsb0 direct-access symbolic link. id=0001
00000134 35.32136917 libusb0-sys:dbg [add_device] [normal-mode] id=#1
usb\vid_0d9f&pid_0004&rev_0002
00000135 35.32137299 libusb0-sys:[add_device] complete status=00000000
00000136 35.32196808 libusb0-sys:[dispatch_pnp] IRP_MN_START_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000137 35.32229233 libusb0-sys:dbg [on_start_complete] is-filter=N
usb\vid_0d9f&pid_0004&rev_0002
00000138 35.32229996 libusb0-sys:dbg [on_start_complete] applying
active configuration for usb\vid_0d9f&pid_0004&rev_0002
00000139 35.32233429 libusb0-sys:[set_configuration] setting
configuration index 0 timeout=5000libusb0-sys:[get_descriptor] buffer
size: 18 type: 0001 recipient: 0000 index: 0000 language id: 0000
timeout: 5000
00000140 35.32750702 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000141 35.32751465 libusb0-sys:[get_descriptor] buffer size: 9 type:
0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000142 35.33249664 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000143 35.33250427 libusb0-sys:[get_descriptor] buffer size: 34
type: 0002 recipient: 0000 index: 0000 language id: 0000 timeout: 5000
00000144 35.34049225 libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000145 35.34049606 libusb0-sys:[set_configuration] found interface 0
00000146 35.34352112 libusb0-sys:dbg [set_configuration] #1
usb\vid_0d9f&pid_0004&rev_0002 passing configuration request to
target-device.libusb0-sys:dbg [call_usbd_ex] status = 00000000h
00000147 35.34353256 libusb0-sys:[update_pipe_info] interface 0
00000148 35.34353638 libusb0-sys:[update_pipe_info] EP81h
maximum-packet-size=8 maximum-transfer-size=4194304
00000149 35.34354019 libusb0-sys:wrn [update_pipe_info] overriding
EP81h maximum-transfer-size=65536
00000150 35.34378433 libusb0-sys:dbg [dispatch_pnp]
IRP_MN_QUERY_CAPABILITIES: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000151 39.12704086 libusb0-sys:[dispatch_pnp]
IRP_MN_SURPRISE_REMOVAL: is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000152 39.12715149 libusb0-sys:[set_filter_interface_key] updated
interface registry with LUsb0 direct-access symbolic link. id=-1
00000153 39.12784195 libusb0-sys:[dispatch_pnp] IRP_MN_REMOVE_DEVICE:
is-filter=N usb\vid_0d9f&pid_0004&rev_0002
00000154 39.12790680 libusb0-sys:[dispatch_pnp] deleting device #1
usb\vid_0d9f&pid_0004&rev_0002
00000155 39.12796783 libusb0-sys:[unload] [unloading-driver] v1.2.6.0
00000009 39.69624710 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000010 40.06841278 [2128] UserNotificationThread::action() m_State=1
provMode=1
00000011 49.69895554 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000012 50.07113647 [2128] UserNotificationThread::action() m_State=1
provMode=1
00000013 59.98564148 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000014 60.48570633 [2128] UserNotificationThread::action() m_State=1
provMode=1
00000015 69.71500397 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000016 70.08701324 [2128] UserNotificationThread::action() m_State=1
provMode=1
00000017 79.72379303 [2128] provisioned=0, prevAMTState=AMT Awaiting
provisioning, newAMTState=AMT Awaiting provisioning
00000018 80.48637390 [2128] UserNotificationThread::action() m_State=1
provMode=1



-- 
Xiaofan

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

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

On Sat, Sep 15, 2018 at 5:11 AM Tyler Bell <mrb...@gm...> wrote:
>
> OK, I set up a new VM and it does indeed install correctly there, but does
> not on my normal dev machine. I guess I need to figure out why it's not
> installing on my normal machine.
>

Thanks for reporting back. Sorry I have not encountered this myself on real
Windows machine or VMs before so that I can not pinpoint out the direction
to debug.

Just to share some of my thoughts.
1) Make sure you run as the admin
2) You can try to use Process Monitor to see what is going on.
https://docs.microsoft.com/en-us/sysinternals/downloads/procmon


-- 
Xiaofan

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

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

On Thu, Sep 13, 2018 at 2:01 AM Tyler Bell <mrb...@gm...> wrote:
>
>> > Backing up a bit, I have to interface with a device that has a driver from the manufacturer(FTDI
>> > USB-serial cables). The OEM driver is limited(but also required) so I've augmented it w/ libusb.
>> > The best way to manage this on a client's machine that I can find is to use libusb as a filter driver.
>> > However, to install libusb as a filter driver for a device, libwdi assumes that libusb already exists
>> > on the client machine. This is not a good assumption to make for a client machine. Infwizard doesn't
>> > seem capable of creating an inf for filter driver mode and I'm not sure that, even if it did, it would copy
>> > the DLL&SYS files.
>>
>> If you use FTDI device, better way is to use libftdi-1.0 and it uses
>> libusb-1.0 API, there you
>> have the option of using different libusb-1.0 Windows backend, one of
>> the option is to use
>> usbdk (filter, similar to libusb-win32 filter but works better in new
>> Windows versions).
>
>
> I would love to use libftdi, but I am stuck w/ the stock driver from FTDI. That is why I'm trying to
> use libusb as a filter driver; I need to add a bit of functionality to one tool, but there are a
> handful of other tools that use the same FTDI device and those are built w/ the FTDI driver.

As answered below, you can use usbdk as a filter and use libftid, and
at the same time
keep the FTDI vendor driver as it is.

>> For usbdk, it is the same, you need to the 32bit/64bit installer first
>> (as admin) and then you
>> can use the command line to install/uninstall the filter.
>> https://github.com/daynix/UsbDk
>> https://github.com/daynix/UsbDk/releases
>>
>> You may need to use libusb-1.0.21 build with usbdk for now and not
>> libusb-1.0.22 due to
>> the following change. libftdi has not been updated to incorporate the change.
>> https://github.com/libusb/libusb/issues/443
>>
>> Leagacy libftdi-0.1 uses libusb-0.1 API and you can use libusb-win32
>> filter with it but libftdi-0.1
>> is no longer maintained.
>>




-- 
Xiaofan

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

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

OK, I set up a new VM and it does indeed install correctly there, but does
not on my normal dev machine. I guess I need to figure out why it's not
installing on my normal machine.

On Wed, Sep 12, 2018 at 1:00 PM Tyler Bell <mrb...@gm...> wrote:

>
> On Sun, Sep 9, 2018 at 8:55 PM Xiaofan Chen <xia...@gm...> wrote:
>
>> On Fri, Sep 7, 2018 at 10:38 PM Tyler Bell <mrb...@gm...> wrote:
>> >
>> > From what I can tell, that is not, what I need. That targets the driver
>> to a device,
>> > which is what the bug 84 conversation indicates I should not do. I only
>> want the .sys and .dll in
>> > the correct windows directories and registered to the system. This is
>> complicated by the need for
>> > UAC and 32/64 bit divide(a 32 bit app cannot install drivers on a
>> 64-bit machine and and 64-bit
>> > app cannot run on a 32-bit machine).
>> >  These are not huge issues, but as libusb has already nicely solved
>> these concerns for "primary
>> > driver" installation, it would be great(and, it seems, trivial?) if we
>> could reuse the existing code for
>> > filter driver installation.
>>
>> If you install this file libusb-win32-devel-filter-1.2.6.0.exe, it
>> will do the necessary for you to put
>> the libusb0.sys and libusb0.dll in the right place. And it will create
>> the start-up menu for the
>> inf-wizard (not working for new version of Windows, that is why I
>> added libusbk-inf-wizard.exe
>> here as well and filter wizard which still works for Windows 10.
>> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/
>>
>> Or if you install libusbK-3.0.7.0-setup.exe (recommended over the
>> above package), it will install
>> libusb0.sys/libusbk.sys/libusb0.dll/libusbk.dll in the right place.
>> And in the end it will run the
>> filter wizard for you as well.
>> https://sourceforge.net/projects/libusb-win32/files/libusbK-release/
>
>
> Neither of those are working on my system. If I use
> libusb-win32-devel-filter-1.2.6.0.exe, I only get stuff under C:\Program
> Files\LibUSB-Win32, the DLL/SYS are not in the Windows folder.
> Subsequently, trying to install an INF as a filter driver, the device fails.
>
>
>>
>>
>> > Backing up a bit, I have to interface with a device that has a driver
>> from the manufacturer(FTDI
>> > USB-serial cables). The OEM driver is limited(but also required) so
>> I've augmented it w/ libusb.
>> > The best way to manage this on a client's machine that I can find is to
>> use libusb as a filter driver.
>> > However, to install libusb as a filter driver for a device, libwdi
>> assumes that libusb already exists
>> > on the client machine. This is not a good assumption to make for a
>> client machine. Infwizard doesn't
>> > seem capable of creating an inf for filter driver mode and I'm not sure
>> that, even if it did, it would copy
>> > the DLL&SYS files.
>>
>> If you use FTDI device, better way is to use libftdi-1.0 and it uses
>> libusb-1.0 API, there you
>> have the option of using different libusb-1.0 Windows backend, one of
>> the option is to use
>> usbdk (filter, similar to libusb-win32 filter but works better in new
>> Windows versions).
>>
>
> I would love to use libftdi, but I am stuck w/ the stock driver from FTDI.
> That is why I'm trying to use libusb as a filter driver; I need to add a
> bit of functionality to one tool, but there are a handful of other tools
> that use the same FTDI device and those are built w/ the FTDI driver.
>
>
>>
>> For usbdk, it is the same, you need to the 32bit/64bit installer first
>> (as admin) and then you
>> can use the command line to install/uninstall the filter.
>> https://github.com/daynix/UsbDk
>> https://github.com/daynix/UsbDk/releases
>>
>> You may need to use libusb-1.0.21 build with usbdk for now and not
>> libusb-1.0.22 due to
>> the following change. libftdi has not been updated to incorporate the
>> change.
>> https://github.com/libusb/libusb/issues/443
>>
>> Leagacy libftdi-0.1 uses libusb-0.1 API and you can use libusb-win32
>> filter with it but libftdi-0.1
>> is no longer maintained.
>>
>> --
>> Xiaofan
>>
>>
>> _______________________________________________
>> Libusb-win32-devel mailing list
>> Lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>>
>

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

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

On Sun, Sep 9, 2018 at 8:55 PM Xiaofan Chen <xia...@gm...> wrote:

> On Fri, Sep 7, 2018 at 10:38 PM Tyler Bell <mrb...@gm...> wrote:
> >
> > From what I can tell, that is not, what I need. That targets the driver
> to a device,
> > which is what the bug 84 conversation indicates I should not do. I only
> want the .sys and .dll in
> > the correct windows directories and registered to the system. This is
> complicated by the need for
> > UAC and 32/64 bit divide(a 32 bit app cannot install drivers on a 64-bit
> machine and and 64-bit
> > app cannot run on a 32-bit machine).
> >  These are not huge issues, but as libusb has already nicely solved
> these concerns for "primary
> > driver" installation, it would be great(and, it seems, trivial?) if we
> could reuse the existing code for
> > filter driver installation.
>
> If you install this file libusb-win32-devel-filter-1.2.6.0.exe, it
> will do the necessary for you to put
> the libusb0.sys and libusb0.dll in the right place. And it will create
> the start-up menu for the
> inf-wizard (not working for new version of Windows, that is why I
> added libusbk-inf-wizard.exe
> here as well and filter wizard which still works for Windows 10.
> https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/
>
> Or if you install libusbK-3.0.7.0-setup.exe (recommended over the
> above package), it will install
> libusb0.sys/libusbk.sys/libusb0.dll/libusbk.dll in the right place.
> And in the end it will run the
> filter wizard for you as well.
> https://sourceforge.net/projects/libusb-win32/files/libusbK-release/


Neither of those are working on my system. If I use
libusb-win32-devel-filter-1.2.6.0.exe, I only get stuff under C:\Program
Files\LibUSB-Win32, the DLL/SYS are not in the Windows folder.
Subsequently, trying to install an INF as a filter driver, the device fails.


>
>
> > Backing up a bit, I have to interface with a device that has a driver
> from the manufacturer(FTDI
> > USB-serial cables). The OEM driver is limited(but also required) so I've
> augmented it w/ libusb.
> > The best way to manage this on a client's machine that I can find is to
> use libusb as a filter driver.
> > However, to install libusb as a filter driver for a device, libwdi
> assumes that libusb already exists
> > on the client machine. This is not a good assumption to make for a
> client machine. Infwizard doesn't
> > seem capable of creating an inf for filter driver mode and I'm not sure
> that, even if it did, it would copy
> > the DLL&SYS files.
>
> If you use FTDI device, better way is to use libftdi-1.0 and it uses
> libusb-1.0 API, there you
> have the option of using different libusb-1.0 Windows backend, one of
> the option is to use
> usbdk (filter, similar to libusb-win32 filter but works better in new
> Windows versions).
>

I would love to use libftdi, but I am stuck w/ the stock driver from FTDI.
That is why I'm trying to use libusb as a filter driver; I need to add a
bit of functionality to one tool, but there are a handful of other tools
that use the same FTDI device and those are built w/ the FTDI driver.


>
> For usbdk, it is the same, you need to the 32bit/64bit installer first
> (as admin) and then you
> can use the command line to install/uninstall the filter.
> https://github.com/daynix/UsbDk
> https://github.com/daynix/UsbDk/releases
>
> You may need to use libusb-1.0.21 build with usbdk for now and not
> libusb-1.0.22 due to
> the following change. libftdi has not been updated to incorporate the
> change.
> https://github.com/libusb/libusb/issues/443
>
> Leagacy libftdi-0.1 uses libusb-0.1 API and you can use libusb-win32
> filter with it but libftdi-0.1
> is no longer maintained.
>
> --
> Xiaofan
>
>
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>

Re: [Libusb-win32-devel] Please help installing libusb-32.

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

On Wed, Sep 12, 2018 at 3:05 PM Xiaofan Chen <xia...@gm...> wrote:
>
> On Wed, Sep 12, 2018 at 2:38 PM Dmitry Donskoy <ad...@da...> wrote:
> >
> > The thing is that before I install libusb-win32, Windows uses "HID UPS
> > Battery", that works stable (doesn't disconnect and connect), though it
> > doesn't work with NUT.
> >
>
> I understand -- this means that the NUT program and the "HID UPS Battery"
> application behaves differently and that probably affects the device to go
> into some kind of fault and then can not handling the Windows request
> properly. Still libusb-win32 itself can not help you -- it does not handling
> the Windows enumeration.
>
> BTW, I think NUT program should be upgraded to use HIDAPI
> instead of libusb-0.1 API or even libusb-1.0 API to be have better
> support under Windows and Mac OS X.
>

You can try some software or HW USB analyzer to debug the issue to
see why the device goes to fault.
https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-event-tracing-for-windows

libusb-win32 debug version may help a bit as well -- you need to use
Microsoft DebugView to see the se debug printout to see the communication
between NUT and the device.


-- 
Xiaofan

Re: [Libusb-win32-devel] Please help installing libusb-32.

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

On Wed, Sep 12, 2018 at 2:38 PM Dmitry Donskoy <ad...@da...> wrote:
>
> The thing is that before I install libusb-win32, Windows uses "HID UPS
> Battery", that works stable (doesn't disconnect and connect), though it
> doesn't work with NUT.
>

I understand -- this means that the NUT program and the "HID UPS Battery"
application behaves differently and that probably affects the device to go
into some kind of fault and then can not handling the Windows request
properly. Still libusb-win32 itself can not help you -- it does not handling
the Windows enumeration.

BTW, I think NUT program should be upgraded to use HIDAPI
instead of libusb-0.1 API or even libusb-1.0 API to be have better
support under Windows and Mac OS X.


-- 
Xiaofan

Re: [Libusb-win32-devel] Please help installing libusb-32.

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

On Wed, Sep 12, 2018 at 2:21 PM Dmitry Donskoy <ad...@da...> wrote:
>
> During my investigation of "Data stale" error of NUT, I open Device
> Manager and I see that "libusb-win32" device is disappearing and
> appearing again every 30 seconds approximately. It looks just like
> someone unplugs the UPS USB cable and plugs in again (but there is no
> indication of any actual disruption in physical connectivity).
>
> I do really need to use NUT with this UPS (PCM RPT-800A).
>
> How do I make this "libusb-win32" driver to be installed correctly so it
> won't disappear and appear in Device Manager by itself?


In this case, this has nothing to do with libusb-win32, Windows
handles the enumeration of the device and apparently the
device has some HW/FW issues that it got kicked out by
Windows.

You can try to have a better USB cable or change to a different
PC to see if that helps.

Ref: https://blogs.msdn.microsoft.com/usbcoreblog/2009/10/30/how-does-usb-stack-enumerate-a-device/

And new version of Windows are more strict than old version of Windows, if you
have problems with Windows 10, try Windows 7.

-- 
Xiaofan

[Libusb-win32-devel] Please help installing libusb-32.

[Dmitry D. <ad...@da...>]

Hello!

I have an UPS made by Powercom company; the model of the UPS is 
RPT-800A. This UPS has a USB port, which can be used to connect the UPS 
to a PC and read various data from the UPS (percentage of load, input 
voltage, output voltage, etc.).

There's an application called Network UPS Tools (NUT). NUT can be used 
to read data from the UPS.

So I download the NUT binary package for Windows, install and set it up 
using manual. Everything works fine for a few hours (I can get the data 
I need from my UPS using NUT).

And then NUT stops working. The error is "Data stale".

To read the data from UPS in Windows operating system (Windows OS), NUT 
uses the libusb-win32 library. When this library is installed, it 
substitutes the current USB device driver in Device Manager with its own 
custom libusb-win32 driver.

During my investigation of "Data stale" error of NUT, I open Device 
Manager and I see that "libusb-win32" device is disappearing and 
appearing again every 30 seconds approximately. It looks just like 
someone unplugs the UPS USB cable and plugs in again (but there is no 
indication of any actual disruption in physical connectivity).

I do really need to use NUT with this UPS (PCM RPT-800A).

How do I make this "libusb-win32" driver to be installed correctly so it 
won't disappear and appear in Device Manager by itself?

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

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

On Fri, Sep 7, 2018 at 10:38 PM Tyler Bell <mrb...@gm...> wrote:
>
> From what I can tell, that is not, what I need. That targets the driver to a device,
> which is what the bug 84 conversation indicates I should not do. I only want the .sys and .dll in
> the correct windows directories and registered to the system. This is complicated by the need for
> UAC and 32/64 bit divide(a 32 bit app cannot install drivers on a 64-bit machine and and 64-bit
> app cannot run on a 32-bit machine).
>  These are not huge issues, but as libusb has already nicely solved these concerns for "primary
> driver" installation, it would be great(and, it seems, trivial?) if we could reuse the existing code for
> filter driver installation.

If you install this file libusb-win32-devel-filter-1.2.6.0.exe, it
will do the necessary for you to put
the libusb0.sys and libusb0.dll in the right place. And it will create
the start-up menu for the
inf-wizard (not working for new version of Windows, that is why I
added libusbk-inf-wizard.exe
here as well and filter wizard which still works for Windows 10.
https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/

Or if you install libusbK-3.0.7.0-setup.exe (recommended over the
above package), it will install
libusb0.sys/libusbk.sys/libusb0.dll/libusbk.dll in the right place.
And in the end it will run the
filter wizard for you as well.
https://sourceforge.net/projects/libusb-win32/files/libusbK-release/

> Backing up a bit, I have to interface with a device that has a driver from the manufacturer(FTDI
> USB-serial cables). The OEM driver is limited(but also required) so I've augmented it w/ libusb.
> The best way to manage this on a client's machine that I can find is to use libusb as a filter driver.
> However, to install libusb as a filter driver for a device, libwdi assumes that libusb already exists
> on the client machine. This is not a good assumption to make for a client machine. Infwizard doesn't
> seem capable of creating an inf for filter driver mode and I'm not sure that, even if it did, it would copy
> the DLL&SYS files.

If you use FTDI device, better way is to use libftdi-1.0 and it uses
libusb-1.0 API, there you
have the option of using different libusb-1.0 Windows backend, one of
the option is to use
usbdk (filter, similar to libusb-win32 filter but works better in new
Windows versions).

For usbdk, it is the same, you need to the 32bit/64bit installer first
(as admin) and then you
can use the command line to install/uninstall the filter.
https://github.com/daynix/UsbDk
https://github.com/daynix/UsbDk/releases

You may need to use libusb-1.0.21 build with usbdk for now and not
libusb-1.0.22 due to
the following change. libftdi has not been updated to incorporate the change.
https://github.com/libusb/libusb/issues/443

Leagacy libftdi-0.1 uses libusb-0.1 API and you can use libusb-win32
filter with it but libftdi-0.1
is no longer maintained.

-- 
Xiaofan

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

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

>From what I can tell, that is not, what I need. That targets the driver to
a device, which is what the bug 84 conversation indicates I should not do.
I only want the .sys and .dll in the correct windows directories and
registered to the system. This is complicated by the need for UAC and 32/64
bit divide(a 32 bit app cannot install drivers on a 64-bit machine and and
64-bit app cannot run on a 32-bit machine).
 These are not huge issues, but as libusb has already nicely solved these
concerns for "primary driver" installation, it would be great(and, it
seems, trivial?) if we could reuse the existing code for filter driver
installation.

Backing up a bit, I have to interface with a device that has a driver from
the manufacturer(FTDI USB-serial cables). The OEM driver is limited(but
also required) so I've augmented it w/ libusb. The best way to manage this
on a client's machine that I can find is to use libusb as a filter driver.
However, to install libusb as a filter driver for a device, libwdi assumes
that libusb already exists on the client machine. This is not a good
assumption to make for a client machine. Infwizard doesn't seem capable of
creating an inf for filter driver mode and I'm not sure that, even if it
did, it would copy the DLL&SYS files.


On Thu, Sep 6, 2018 at 5:51 PM Chris E <sp...@gm...> wrote:

> 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
>>
>
> ------------------------------------------------------------------------------
> 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
>