Menu
▾
▴
libusb-win32-devel
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(27) |
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(19) |
Mar
(13) |
Apr
(15) |
May
(11) |
Jun
(17) |
Jul
(31) |
Aug
(45) |
Sep
(10) |
Oct
(40) |
Nov
(39) |
Dec
(45) |
| 2005 |
Jan
(113) |
Feb
(45) |
Mar
(38) |
Apr
(53) |
May
(11) |
Jun
(42) |
Jul
(56) |
Aug
(50) |
Sep
(32) |
Oct
(32) |
Nov
(47) |
Dec
(22) |
| 2006 |
Jan
(19) |
Feb
(32) |
Mar
(40) |
Apr
(40) |
May
(41) |
Jun
(44) |
Jul
(37) |
Aug
(51) |
Sep
(30) |
Oct
(30) |
Nov
(51) |
Dec
(20) |
| 2007 |
Jan
(7) |
Feb
(20) |
Mar
(17) |
Apr
(67) |
May
(13) |
Jun
(73) |
Jul
(16) |
Aug
(58) |
Sep
(29) |
Oct
(5) |
Nov
(74) |
Dec
(9) |
| 2008 |
Jan
(17) |
Feb
(12) |
Mar
(65) |
Apr
(22) |
May
(40) |
Jun
(32) |
Jul
(11) |
Aug
(8) |
Sep
(3) |
Oct
(41) |
Nov
(34) |
Dec
(12) |
| 2009 |
Jan
(44) |
Feb
(33) |
Mar
(16) |
Apr
(109) |
May
(11) |
Jun
(22) |
Jul
(21) |
Aug
(37) |
Sep
(5) |
Oct
(23) |
Nov
(7) |
Dec
(7) |
| 2010 |
Jan
(36) |
Feb
(40) |
Mar
(35) |
Apr
(45) |
May
(42) |
Jun
(104) |
Jul
(135) |
Aug
(50) |
Sep
(65) |
Oct
(110) |
Nov
(129) |
Dec
(75) |
| 2011 |
Jan
(105) |
Feb
(48) |
Mar
(93) |
Apr
(166) |
May
(169) |
Jun
(188) |
Jul
(106) |
Aug
(33) |
Sep
(85) |
Oct
(46) |
Nov
(102) |
Dec
(105) |
| 2012 |
Jan
(81) |
Feb
(115) |
Mar
(56) |
Apr
(93) |
May
(56) |
Jun
(77) |
Jul
(88) |
Aug
(52) |
Sep
(72) |
Oct
(16) |
Nov
(70) |
Dec
(70) |
| 2013 |
Jan
(23) |
Feb
(85) |
Mar
(38) |
Apr
(48) |
May
(40) |
Jun
(49) |
Jul
(33) |
Aug
(28) |
Sep
(66) |
Oct
(28) |
Nov
(28) |
Dec
(16) |
| 2014 |
Jan
(33) |
Feb
(58) |
Mar
(17) |
Apr
(50) |
May
(16) |
Jun
(24) |
Jul
(19) |
Aug
(32) |
Sep
(10) |
Oct
(10) |
Nov
(4) |
Dec
(10) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
(14) |
May
(1) |
Jun
(6) |
Jul
(16) |
Aug
(29) |
Sep
(6) |
Oct
(26) |
Nov
(10) |
Dec
|
| 2016 |
Jan
|
Feb
(20) |
Mar
(6) |
Apr
|
May
(3) |
Jun
(3) |
Jul
|
Aug
(16) |
Sep
(6) |
Oct
|
Nov
(15) |
Dec
|
| 2017 |
Jan
(1) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2018 |
Jan
|
Feb
(8) |
Mar
(10) |
Apr
(16) |
May
|
Jun
(15) |
Jul
|
Aug
(3) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(6) |
Oct
(2) |
Nov
(4) |
Dec
|
| 2022 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(1) |
May
(11) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
|
From: Xiaofan C. <xia...@gm...> - 2021-09-15 09:33:40
|
Just wondering if anyone here has tested Zadig or libusbk-inf-wizard under the upcoming Windows 11. As per Pete (author of libwdi/Zadig), Zadig does not work now. libusbk-inf-wizard will be in the same boat as it uses libwdi as well. Ref: https://community.osr.com/discussion/293115/windows-11-and-alternative-driver-installation-method-in-libwdi -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-09-15 01:55:34
|
I believe this is not possible based on the current codes. What you can try is to create the first application as a Windows service, and then the second application uses that Windows service. Best regards, Xiaofan On Sun, Sep 12, 2021 at 8:43 PM G. Foersler <gfo...@gm...> wrote: > > Hello everyone, > > I am using LibUSB-Win32 in order to communicate with a USB device. At first, the device is searched for, then it is opened and some settings for the device are transferred using control messages. This is done using a small application written in c++, which is called from a main application (written in another language) via cmd.exe. > Another small application is used to transfer data over a bulk endpoint, which may be running in the background after it is started, and a third small application shall be used for further control messages if needed. > Is it possible to store the device handle obtained in the first application and share it with the other applications? Like having the first app give the handle to the calling main app, which then shares the handle with the other apps so they can access the USB device without having to search for and open the device by themselves every time they are called. > If this is possible, how can the handle be transferred or stored? > > Thanks! |
|
From: G. F. <gfo...@gm...> - 2021-09-12 12:42:33
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hello everyone,</div> <div> </div> <div> <div>I am using LibUSB-Win32 in order to communicate with a USB device. At first, the device is searched for, then it is opened and some settings for the device are transferred using control messages. This is done using a small application written in c++, which is called from a main application (written in another language) via cmd.exe.</div> <div>Another small application is used to transfer data over a bulk endpoint, which may be running in the background after it is started, and a third small application shall be used for further control messages if needed.</div> <div>Is it possible to store the device handle obtained in the first application and share it with the other applications? Like having the first app give the handle to the calling main app, which then shares the handle with the other apps so they can access the USB device without having to search for and open the device by themselves every time they are called.</div> <div>If this is possible, how can the handle be transferred or stored?</div> <div> </div> <div>Thanks!</div> </div></div></body></html> |
|
From: Xiaofan C. <xia...@gm...> - 2021-07-20 03:16:19
|
I am pleased to announce the release of libusbk 3.1.0.0, thanks to the great efforts of Travis Robinson, the developer of libusbk. https://sourceforge.net/projects/libusbk/files/libusbK-release/3.1.0.0/ Please take note that libusbk.sys is the same as the 3.0.7.0 release as it has been signed previously and will continue to work. The main updates are with the library (libusbk.dll) and the driver installer. The most significant new feature is the isochronous support for WinUSB LIBUSBK RELEASE NOTES V3.1.0.0 (07/19/2021) ============================================== - Added isochronous support for WinUSB - Added BOS descriptors - Added MS OS V1.0 Descriptors - Added MS OS V2.0 Descriptors - Added 'DeviceInterfaceGUIDs' property to libusb0 .inf template - Fixed issues causing missing devices in the device list when then DeviceInterfaceGUIDs property is missing - Added BOS and MS descriptor reporting to kList - Added FX3 benchmark test firmware Best regards, Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-07-05 06:55:46
|
Travis has created a development branch for libusbk here. It adds WinUSB isochronous transfer support. New benchmark FW for Cypress EZ-USB FX3 super speed usb device controller has been added. libusbk library and kbench now have better support of isochronous transfer for both libusbk driver and WinUSB driver. https://github.com/mcuee/libusbk/tree/WinUSB-ISO You can see the impressive results from kbench from Travis using the Cypress CYUSB3KIT-003 EZ-USB® FX3™ SuperSpeed Explorer Kit. https://github.com/mcuee/libusbk/tree/WinUSB-ISO/BmFW/CYPRESS_FX3 https://www.cypress.com/documentation/development-kitsboards/cyusb3kit-003-ez-usb-fx3-superspeed-explorer-kit I have also got the same Cypress board and I can verify the results from Travis. -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-07-03 01:56:13
|
I know this should be a really niche use case and you should really use libusb-1.0 as the cross platform API. However, just in case that you have used libusb-win32 async API under Windows and want to use the same code base under Linux and macOS, you may want to take a look at the following work done by Travis Robinson in 2012. https://github.com/mcuee/libusbm -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-06-20 02:39:41
|
Other than Sourceforge, you can also download the release from github. Sourceforge download: https://sourceforge.net/projects/libusbk/files/libusbK-release/3.0.8.0/ github download: https://github.com/mcuee/libusbk/releases -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-06-20 02:37:36
|
On Sun, Jun 20, 2021 at 7:34 AM Pete Batard <pe...@ak...> wrote: > > Congrats on the new release! > > I'll update Zadig to use the new version when I get a chance, but it > will probably be a few weeks. > No problem, take your time. -- Xiaofan |
|
From: Pete B. <pe...@ak...> - 2021-06-20 00:01:34
|
Congrats on the new release! I'll update Zadig to use the new version when I get a chance, but it will probably be a few weeks. Regards, /Pete On 2021.06.19 05:11, Xiaofan Chen wrote: > I am pleased to announce the release of libusbk 3.0.8.0, thanks to the > great efforts of Travis Robinson, the developer of libusbk. > > https://sourceforge.net/projects/libusbk/files/libusbK-release/3.0.8.0/ > <https://sourceforge.net/projects/libusbk/files/libusbK-release/3.0.8.0/> > > Please take note that libusbk.sys is the same as the 3.0.7.0 release as > it has been signed previously and will continue to work. The main > updates are with the library (libusbk.dll) and the driver installer. > > You can also choose to use Zadig to install the libusbk driver and then > manually upgrade libusbk.dll. I expect Zadig to be updated as well in > the future. > > Best regards, > Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-06-19 04:11:30
|
I am pleased to announce the release of libusbk 3.0.8.0, thanks to the great efforts of Travis Robinson, the developer of libusbk. https://sourceforge.net/projects/libusbk/files/libusbK-release/3.0.8.0/ Please take note that libusbk.sys is the same as the 3.0.7.0 release as it has been signed previously and will continue to work. The main updates are with the library (libusbk.dll) and the driver installer. You can also choose to use Zadig to install the libusbk driver and then manually upgrade libusbk.dll. I expect Zadig to be updated as well in the future. Best regards, Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-06-07 05:15:47
|
On Wed, Jan 20, 2021 at 9:41 AM Xiaofan Chen <xia...@gm...> wrote: > > Hi all, > > FYI I have marked libusbk as unmaintained as Travis is no longer > active in maintaining the project. > > Ref: > https://github.com/mcuee/libusbk > > Status: unmaintained and with limited support as lack of developers > to take over > But if any of you are interested, please send me an email. Thanks. -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-01-20 01:42:27
|
Hi all, FYI I have marked libusbk as unmaintained as Travis is no longer active in maintaining the project. Ref: https://github.com/mcuee/libusbk Status: unmaintained and with limited support as lack of developers to take over -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2021-01-20 01:39:58
|
Windows 1703 may be too old and no longer supported by Microsoft. Anyway, you may get better support from libwdi. Please create an issue there. Thanks. Best regards, Xiaofan On Mon, Jan 18, 2021 at 8:34 PM Ariel Alejandro Cambria <ari...@ho...> wrote: > > Dear Xiofan, > > My Windows version is 1703 > It is wrong? > > I ll try fromy the link you send me. > Thanks! > > Best Regards, > Ariel > > |
|
From: Ariel A. C. <ari...@ho...> - 2021-01-18 12:33:05
|
Dear Xiofan, My Windows version is 1703 It is wrong? I ll try fromy the link you send me. Thanks! Best Regards, Ariel ________________________________ De: Xiaofan Chen <xia...@gm...> Enviado: lunes, 18 de enero de 2021 06:52 Para: lib...@li... <lib...@li...> Asunto: Re: [Libusb-win32-devel] Drivers installation error What is the detailed Windows version like 2004 or 20H2? https://en.wikipedia.org/wiki/Windows_10_version_history Zadig is supposed to be the right tool, not so sure about NS USBloader. You can also try to raise an issue here as Zadig is a separate project from libusb-win32 and libusbK. https://github.com/pbatard/libwdi/issues Best regards, Xiaofan On Mon, Jan 18, 2021 at 12:42 PM Ariel Alejandro Cambria <ari...@ho...<mailto:ari...@ho...>> wrote: Dear All, I have a issue when I try to install Ibusbk V 3. 0. 7.0 by using NS USBloader (I tried installing the drivers) or Zadig. Mi computer doesnt allow to install them or recognize the USB to link my Nintendo Switch. PC: WIn10pro 64bit The message error are "The installation cannot be done": What can I do? Thanks a lot! Best regards, Ariel |
|
From: Xiaofan C. <xia...@gm...> - 2021-01-18 09:53:16
|
What is the detailed Windows version like 2004 or 20H2? https://en.wikipedia.org/wiki/Windows_10_version_history Zadig is supposed to be the right tool, not so sure about NS USBloader. You can also try to raise an issue here as Zadig is a separate project from libusb-win32 and libusbK. https://github.com/pbatard/libwdi/issues Best regards, Xiaofan On Mon, Jan 18, 2021 at 12:42 PM Ariel Alejandro Cambria < ari...@ho...> wrote: > Dear All, > > I have a issue when I try to install Ibusbk V 3. 0. 7.0 by using NS > USBloader (I tried installing the drivers) or Zadig. > Mi computer doesnt allow to install them or recognize the USB to link my > Nintendo Switch. > > PC: WIn10pro 64bit > > The message error are "The installation cannot be done": > > What can I do? > > Thanks a lot! > Best regards, > > Ariel > |
|
From: Ariel A. C. <ari...@ho...> - 2021-01-18 04:41:15
|
Dear All, I have a issue when I try to install Ibusbk V 3. 0. 7.0 by using NS USBloader (I tried installing the drivers) or Zadig. Mi computer doesnt allow to install them or recognize the USB to link my Nintendo Switch. PC: WIn10pro 64bit The message error are "The installation cannot be done": [cid:7420fc1c-bc60-4786-9018-27be55628dd5] What can I do? Thanks a lot! Best regards, Ariel |
|
From: anshu p. <pan...@gm...> - 2020-07-27 11:35:19
|
Hi Team, Thanks for your reply. Yes scanner is developed by my compnay partner ,so we are trying to get the communication document how the scanner works. Once I will get ,will get back to you. Thanks Anshul On Sat, 25 Jul 2020, 17:28 Xiaofan Chen, <xia...@gm...> wrote: > On Thu, Jul 23, 2020 at 12:52 PM anshu panwar <pan...@gm...> > wrote: > > This is my current project so I need to work with a sensor(scanner) > device. > > In that case, you are supposed to know the communication > protocol of the scanner. You can not just anyhow write the code and > expect it to work. > > Is the scanner developed by your company? > > -- > Xiaofan > > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: Xiaofan C. <xia...@gm...> - 2020-07-25 11:57:39
|
On Thu, Jul 23, 2020 at 12:52 PM anshu panwar <pan...@gm...> wrote: > This is my current project so I need to work with a sensor(scanner) device. In that case, you are supposed to know the communication protocol of the scanner. You can not just anyhow write the code and expect it to work. Is the scanner developed by your company? -- Xiaofan |
|
From: anshu p. <pan...@gm...> - 2020-07-23 04:51:53
|
Hi Team, This is my current project so I need to work with a sensor(scanner) device.Now I have changed a little bit but writepipe has gone into blocking state neither application responding nor device . Changes are: 1-if (!Usb.SetAltInterface(usbHandle, (UCHAR)0, (UCHAR)0, ALT_SETTING_NUMBER)) now set the interface to 0x01 to use bulk pipe 2-Usb.QueryPipe(usbHandle, (UCHAR)ALT_SETTING_NUMBER, (UCHAR)iEndpoint, &pipeInfo); ALT_SETTING_NUMBER =0x01(i want to work with bulk pipe) 8-Usb.WritePipe(usbHandle, 0x01, cmdBuffer, sizeof(cmdBuffer), (PUINT)&lengthTransferred, NULL); After changing the ALT_SETTING_NUMBER 0x0 to 0x01 writepipe has gone into blocking state. Please find attached screenshot of wireshark of setting interface and writepipe. Here I have a query regarding the destination address that has changed 2.1.0 to 2.1.1 when writepipe is called. Is this correct? I am confused at this point why the destination address changed when the writepipe is called. Thanks, Anshul On Thu, Jul 23, 2020 at 7:25 AM Xiaofan Chen <xia...@gm...> wrote: > On Wed, Jul 22, 2020 at 11:13 PM anshu panwar <pan...@gm...> > wrote: > > > > Hi Team, > > Thanks for the reply. > > I have followed this link > https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/winusb-installation > to make my device as winusb without installing a custom driver. > > After doing the above step my device(scanner device) is working as a > winusb device and also i have downloaded libusbK-3.0.7.0-setup to work with > this device. > > > > I have followed the steps below: > > 1-LstK_Init > > 2-LstK_Count > > 3-LstK_FindByVidPid > > 4-!LibK_LoadDriverAPI(Usb, deviceInfo->DriverID) > > KUSB_DRVID_WINUSB: > > printf("WinUSB driver api loaded!\n"); > > 5-!Usb.Init(usbHandle, deviceInfo) > > 6-!Usb.QueryInterfaceSettings(usbHandle, 0x0, &interfaceInfo) > > 7-Usb.QueryPipe(usbHandle, (UCHAR)ALT_SETTING_NUMBER, (UCHAR)iEndpoint, > &pipeInfo); > > ALT_SETTING_NUMBER =0x01(i want to work with bulk pipe) > > 8-Usb.WritePipe(usbHandle, 0x01, cmdBuffer, sizeof(cmdBuffer), > (PUINT)&lengthTransferred, NULL); > > BYTE cmdBuffer[8+1] = {0x00,0x00,0x00, 0x01}; > > > > till the 7 steps everything is successfully done but writepipe is not > working . > > > > Is these steps are enough to understand or i should forward all the code > which I am using currently. > > Please update me about this. > > Step 8 is the most important, you can not just anyhow send to the > device and expect > the device to understand the command. > > You need to know the communication protocol in order to be able to > communicate > with the device. > > Is this a real project or you want to learn to use libusbk? If you > just want to learn > to use libusb or libusbk, then a scanner is not a good device to use. > It is better > to use a MCU development kit, like those Arm Cortex M0/M3/M4/etc > development > kit, from STM or other vendors. > > > > -- > Xiaofan > > > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: Xiaofan C. <xia...@gm...> - 2020-07-23 01:54:47
|
On Wed, Jul 22, 2020 at 11:13 PM anshu panwar <pan...@gm...> wrote: > > Hi Team, > Thanks for the reply. > I have followed this link https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/winusb-installation to make my device as winusb without installing a custom driver. > After doing the above step my device(scanner device) is working as a winusb device and also i have downloaded libusbK-3.0.7.0-setup to work with this device. > > I have followed the steps below: > 1-LstK_Init > 2-LstK_Count > 3-LstK_FindByVidPid > 4-!LibK_LoadDriverAPI(Usb, deviceInfo->DriverID) > KUSB_DRVID_WINUSB: > printf("WinUSB driver api loaded!\n"); > 5-!Usb.Init(usbHandle, deviceInfo) > 6-!Usb.QueryInterfaceSettings(usbHandle, 0x0, &interfaceInfo) > 7-Usb.QueryPipe(usbHandle, (UCHAR)ALT_SETTING_NUMBER, (UCHAR)iEndpoint, &pipeInfo); > ALT_SETTING_NUMBER =0x01(i want to work with bulk pipe) > 8-Usb.WritePipe(usbHandle, 0x01, cmdBuffer, sizeof(cmdBuffer), (PUINT)&lengthTransferred, NULL); > BYTE cmdBuffer[8+1] = {0x00,0x00,0x00, 0x01}; > > till the 7 steps everything is successfully done but writepipe is not working . > > Is these steps are enough to understand or i should forward all the code which I am using currently. > Please update me about this. Step 8 is the most important, you can not just anyhow send to the device and expect the device to understand the command. You need to know the communication protocol in order to be able to communicate with the device. Is this a real project or you want to learn to use libusbk? If you just want to learn to use libusb or libusbk, then a scanner is not a good device to use. It is better to use a MCU development kit, like those Arm Cortex M0/M3/M4/etc development kit, from STM or other vendors. -- Xiaofan |
|
From: anshu p. <pan...@gm...> - 2020-07-22 15:12:07
|
Hi Team, Thanks for the reply. I have followed this link https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/winusb-installation to make my device as winusb without installing a custom driver. After doing the above step my device(scanner device) is working as a winusb device and also i have downloaded libusbK-3.0.7.0-setup to work with this device. I have followed the steps below: 1-LstK_Init 2-LstK_Count 3-LstK_FindByVidPid 4-!LibK_LoadDriverAPI(Usb, deviceInfo->DriverID) KUSB_DRVID_WINUSB: printf("WinUSB driver api loaded!\n"); 5-!Usb.Init(usbHandle, deviceInfo) 6-!Usb.QueryInterfaceSettings(usbHandle, 0x0, &interfaceInfo) 7-Usb.QueryPipe(usbHandle, (UCHAR)ALT_SETTING_NUMBER, (UCHAR)iEndpoint, &pipeInfo); ALT_SETTING_NUMBER =0x01(i want to work with bulk pipe) 8-Usb.WritePipe(usbHandle, 0x01, cmdBuffer, sizeof(cmdBuffer), (PUINT)&lengthTransferred, NULL); BYTE cmdBuffer[8+1] = {0x00,0x00,0x00, 0x01}; till the 7 steps everything is successfully done but writepipe is not working . Is these steps are enough to understand or i should forward all the code which I am using currently. Please update me about this. Thanks, Anshul On Wed, Jul 22, 2020 at 7:47 PM Xiaofan Chen <xia...@gm...> wrote: > Please provide more details, what is the device? OS version? And provide > the minimum code snippets to cause the error. > > - > Xiaofan > > On Wed, Jul 22, 2020, 6:15 PM anshu panwar <pan...@gm...> wrote: > >> Hi Team, >> I am facing issues in writepipe/readpipe after successfully open the >> device handle. >> Currently 87 error is return from writepipe using libusbk lib for winusb >> device. >> >> Thanks, >> Anshul >> _______________________________________________ >> Libusb-win32-devel mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel >> > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: Xiaofan C. <xia...@gm...> - 2020-07-22 14:16:22
|
Please provide more details, what is the device? OS version? And provide the minimum code snippets to cause the error. - Xiaofan On Wed, Jul 22, 2020, 6:15 PM anshu panwar <pan...@gm...> wrote: > Hi Team, > I am facing issues in writepipe/readpipe after successfully open the > device handle. > Currently 87 error is return from writepipe using libusbk lib for winusb > device. > > Thanks, > Anshul > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: anshu p. <pan...@gm...> - 2020-07-22 10:14:24
|
Hi Team, I am facing issues in writepipe/readpipe after successfully open the device handle. Currently 87 error is return from writepipe using libusbk lib for winusb device. Thanks, Anshul |
|
From: Ze H. Z. <ze....@ma...> - 2020-04-08 11:45:46
|
Hi All
I made mistake on claim usb interface
{
int state = usb_set_configuration(*deviceHandle, configurationValue);
return state<0? usb_claim_interface(*deviceHandle, interfaceid):state;
}
fixed, bulk_read works fine
On Wed, 1 Apr 2020 at 17:28, 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
>
--
__
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> _
*_
|
|
From: Ze H. Z. <ze....@ma...> - 2020-04-08 10:29:59
|
Hi Xiaofan I made mistake on claim usb interface after i fix it, I keep receiving timeout on bulk read Are there any suggestions? 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> _ *_ |
50 messages has been excluded from this view by a project administrator.
