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: Mayur P. <may...@gm...> - 2018-02-28 08:56:34
|
Hello Jonathan, Thank you very much for the reply. I tried the way you suggested. However I am still getting the same error on windows 10. It is that I need it to be attested from Windows Hardware Developer Center? Can this driver be submitted to the Windows Hardware Developer Center as this is licenced under General Public License? Thanks.. ~Mayur On Tue, Feb 27, 2018 at 11:08 PM, Carter, Jonathan <Jon...@id...> wrote: > Here’s how I signed mine… > > First I made a CAT file for the INF because the one the wizard made was > empty: > > - Get Windows Driver Kit > > - cd C:\Program Files (x86)\Windows Kits\10\bin\x86 > > - Inf2Cat /driver:C:\pathToYourINF /os:10_X64,10_X86,6_3_X64,6_3_ > X86,8_X64,8_X86,7_X64,7_X86 > > - This makes it valid for all windows versions > > > > Then I put that with my INF and signed the package. > > You should be able to right click it and install but you can also use > DPINST > > > > Good luck > > > > *From:* Mayur Purandare [mailto:may...@gm...] > *Sent:* Monday, February 26, 2018 11:21 PM > *To:* Lib...@li... > *Subject:* [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows > 10. > > > > Hello, > > > > We are using libusb-win32 driver to communicate with our hardware. > > > > When we installed it on Windows 7, it showed a warning message for unknown > published. > > > > To remove this warning we signed the driver with commercial certificate > and the warning did not come thereafter. > > > > However, when we tried to deploy the same driver on Windows 10, it is > showing the Error : "The windows cannot verify the digital signature for > this device" code 52. > > > > Request you to please help on this. > > > > thank you.. > > > > > > Regards > > > > Mayur > > ------------------------------------------------------------ > ------------------ > 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 > > |
|
From: Carter, J. <Jon...@id...> - 2018-02-27 17:38:53
|
Here’s how I signed mine… First I made a CAT file for the INF because the one the wizard made was empty: - Get Windows Driver Kit - cd C:\Program Files (x86)\Windows Kits\10\bin\x86 - Inf2Cat /driver:C:\pathToYourINF /os:10_X64,10_X86,6_3_X64,6_3_X86,8_X64,8_X86,7_X64,7_X86 - This makes it valid for all windows versions Then I put that with my INF and signed the package. You should be able to right click it and install but you can also use DPINST Good luck From: Mayur Purandare [mailto:may...@gm...] Sent: Monday, February 26, 2018 11:21 PM To: Lib...@li... Subject: [Libusb-win32-devel] Code 52 Error for libusb-win32 on windows 10. Hello, We are using libusb-win32 driver to communicate with our hardware. When we installed it on Windows 7, it showed a warning message for unknown published. To remove this warning we signed the driver with commercial certificate and the warning did not come thereafter. However, when we tried to deploy the same driver on Windows 10, it is showing the Error : "The windows cannot verify the digital signature for this device" code 52. Request you to please help on this. thank you.. Regards Mayur |
|
From: Mayur P. <may...@gm...> - 2018-02-27 07:21:39
|
Hello, We are using libusb-win32 driver to communicate with our hardware. When we installed it on Windows 7, it showed a warning message for unknown published. To remove this warning we signed the driver with commercial certificate and the warning did not come thereafter. However, when we tried to deploy the same driver on Windows 10, it is showing the Error : "The windows cannot verify the digital signature for this device" code 52. Request you to please help on this. thank you.. Regards Mayur |
|
From: Børge Strand-B. <bor...@gm...> - 2018-02-24 09:36:34
|
Thank you! Best, Børge On Saturday, February 24, 2018, Xiaofan Chen <xia...@gm...> wrote: > Hi all, > > If I look at the following site, there are still significant download > count for libusb-win32, especially 1.2.6.0. > https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/ > > The problem is the inf driver wizard is old and it does not work > with Windows 8/8.1/10. > > You may want to download libusbK release binary which is includes > both libusb-win32 and libusbK binaries. > > https://sourceforge.net/projects/libusb-win32/files/libusbK-release/ > Specifically most of the users should download the file with the name > libusbK-3.0.7.0-setup.exe > > You may also look at Zadig for the driver installation. > http://zadig.akeo.ie/ > > -- > Xiaofan > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: Xiaofan C. <xia...@gm...> - 2018-02-24 04:01:44
|
Hi all, If I look at the following site, there are still significant download count for libusb-win32, especially 1.2.6.0. https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/ The problem is the inf driver wizard is old and it does not work with Windows 8/8.1/10. You may want to download libusbK release binary which is includes both libusb-win32 and libusbK binaries. https://sourceforge.net/projects/libusb-win32/files/libusbK-release/ Specifically most of the users should download the file with the name libusbK-3.0.7.0-setup.exe You may also look at Zadig for the driver installation. http://zadig.akeo.ie/ -- Xiaofan |
|
From: Cilambarasan R. (RBEI/EAC1) <Cil...@in...> - 2017-12-22 04:49:25
|
Hi, I am using the libusbk. My usb device is cdc type uses bulk transfer. I tried to read my device using the EP_Address 0x81 with xfer-async-loop example. Getting the following error. Libusbk version 3.0.7 running in Windows 7 OS. Error code obtained as following. I browsed to find the similar issue reported https://github.com/mcuee/libusbk/issues/2 in 3.0.4. But I find this happens in the 3.0.7 as well. Failed getting i/o results. ErrorCode: 000004C7h Failed getting i/o results. ErrorCode: 000004C7h Failed getting i/o results. ErrorCode: 000004C7h C:\Users\rca1cob\Downloads\libusbK-3.0.7.0-bin\examples\xfer-async-loop\Debug\Wi n32> Best regards Cimbu RBEI/EAC Tel. +91(422)67-64672 |
|
From: Xiaofan C. <xia...@gm...> - 2017-11-25 02:27:23
|
Just an update -- pyusb has a new admin now. Regards, Xiaofan On Sat, Oct 21, 2017 at 10:16 AM, Xiaofan Chen <xia...@gm...> wrote: > Just wondering if anyone is interested here. IMHO it is a a nice project. > > Regards, > Xiaofan > > ---------- Forwarded message ---------- > From: Wander Lairson Costa <wan...@gm...> > Date: Fri, Oct 6, 2017 at 12:23 AM > Subject: [pyusb-users] Looking for a new maintainer > To: pyusb-users <pyu...@li...> > > > Hi there all, > > A few months I sent a message explaining why PyUSB has been steady for > such a long time. Although my health has strongly improved since then, > things are still ongoing, I don't have time to work as a maintainer > anymore and as such, I am looking a volunteer to take the leadership > of the project. > > That said, I don't intend to be a complete strange in the project, I > still intend to participate as an occasional contributor, I just can't > handle the burden of being a maintainer of the project. This has not > only have to do with my health issues but also because I am working > with stuff unrelated to the project nowadays. > > I am going to update website and README soon with this new information. > > -- > Best Regards, > Wander Lairson Costa > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users > > > -- > Xiaofan -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2017-10-21 02:16:23
|
Just wondering if anyone is interested here. IMHO it is a a nice project. Regards, Xiaofan ---------- Forwarded message ---------- From: Wander Lairson Costa <wan...@gm...> Date: Fri, Oct 6, 2017 at 12:23 AM Subject: [pyusb-users] Looking for a new maintainer To: pyusb-users <pyu...@li...> Hi there all, A few months I sent a message explaining why PyUSB has been steady for such a long time. Although my health has strongly improved since then, things are still ongoing, I don't have time to work as a maintainer anymore and as such, I am looking a volunteer to take the leadership of the project. That said, I don't intend to be a complete strange in the project, I still intend to participate as an occasional contributor, I just can't handle the burden of being a maintainer of the project. This has not only have to do with my health issues but also because I am working with stuff unrelated to the project nowadays. I am going to update website and README soon with this new information. -- Best Regards, Wander Lairson Costa ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ pyusb-users mailing list pyu...@li... https://lists.sourceforge.net/lists/listinfo/pyusb-users -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2017-06-28 11:58:45
|
On Tue, Jun 6, 2017 at 10:03 AM, John Semrau <4jo...@gm...> wrote: > unsubscribe me > You can do that here. https://sourceforge.net/projects/libusb-win32/lists/libusb-win32-devel -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2017-06-28 11:57:52
|
On Mon, May 29, 2017 at 2:16 AM, archy taylor <tay...@gm...> wrote: > Is libusb-win32 Windows 10 compatible? How do I get a signed version for > Windows 10? I've heard people have trouble installing r libusb-win32 in > Windows 10 with inf-wizard.exe. > > libusb-win32 is still quite popular with ~400 downloads a day. > I missed this email. You should not use inf-wizard.exe which has been known not to work under Windows 8/8.1/10. You should use Zadig or libusbK's inf-wizard under Windows 10. -- Xiaofan |
|
From: John S. <4jo...@gm...> - 2017-06-06 02:03:33
|
unsubscribe me On Sun, May 28, 2017 at 2:16 PM, archy taylor <tay...@gm...> wrote: > Is libusb-win32 Windows 10 compatible? How do I get a signed version for > Windows 10? I've heard people have trouble installing r libusb-win32 in > Windows 10 with inf-wizard.exe. > > libusb-win32 is still quite popular with ~400 downloads a day. > > Thanks, > > Archy > > ------------------------------------------------------------ > ------------------ > 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 > |
|
From: archy t. <tay...@gm...> - 2017-05-28 18:17:01
|
Is libusb-win32 Windows 10 compatible? How do I get a signed version for Windows 10? I've heard people have trouble installing r libusb-win32 in Windows 10 with inf-wizard.exe. libusb-win32 is still quite popular with ~400 downloads a day. Thanks, Archy |
|
From: Mirco S. g. <mir...@gm...> - 2017-03-09 18:55:13
|
Xiaofan Chen,
Hi,
>
> Ref: I said the following at that time (more than five year ago).
> "There is a hack to get libusb-win32 to work with such device
> (to replace bulk with interrupt transfer in the driver level)
> but it is much better that you change the firmware to <---------------------------------
> be compliant with the USB specifications.
I'm neither a device driver developer nor a hardware expert, however, changing the firmware is a very interesting thing:
in many USBDM/BDM support docs it is stated that it is possible to upgrade JB16 devices (inside my Axiom BDM-CF pod
there is a WC9JB16FAE chip, probably a 28 pin MC68HC908JB16 presenting himself to windows 7 usb interface as
USB\VID_0425&PID_1001&REV_0001) with a freshen firmware using USBICP program. The details on the entire procedure sound
to me as "mystical", I mean something like this (just an example, with a different PID):
...
You must use 32-bit Windows XP to perform this
2. You must have Office 2010 installed - evaluation version is enough as it's only required for some unresolved
dependency of USBICP.EXE
3. You can't use latest USBDM as support for JB16 has been broken for quite a while
4. USBDM developer has nuked all old versions from Sourceforge. I've proved links to working versions below.
You can't use latest USBDM as support for JB16 has been broken for quite a while
4. USBDM developer has nuked all old versions from Sourceforge. I've proved links to working versions below.
* Download and install USBDM 4.9.5 with default settings
http://files.mpoli.fi/sekalaiset/usbdm/ ... 5b_Win.msi <http://files.mpoli.fi/sekalaiset/usbdm/USBDM_4_9_5b_Win.msi>
* Download USBDM_Win32_4_6a.zip from
http://files.mpoli.fi/sekalaiset/usbdm/ ... 2_4_6a.zip <http://files.mpoli.fi/sekalaiset/usbdm/USBDM_Win32_4_6a.zip>
* Extract USBDM_Win32_4_6a.zip
* Plugin Wayengineer TBDM while pulling pin 10 of MON08 connector GND to initiate ICP mode
Pin 10 is also known as MON_DATA, see "C:\Program Files\pgo\USBDM 4.9.5\FlashImages\JB16\OSBDMe.pdf" included in
USBDM 4.9.5 package for pinout if necessary.
* Install USBICP driver from USBDM_Win32_4_6a.zip "Win32\Freescale ICP Files"
* TBDM should be detected as USB\VID_0425&PID_ff02 "Motorola JB16/JG16 ICP Device"
* If it comes up as USB\VID_0425&PID_1000 then you failed to initiate ICP mode
* Launch USBDM_Win32_4_6a\Win32\Freescale ICP Files\USBICP.EXE
* Select "Initial_Programming_MassErase.imp" when asked to open file
* Next browse to "C:\Program Files\pgo\USBDM 4.9.5\FlashImages\JB16" and select USBDM_JB16.s19
* Go thru Erase, Program, Verify and close USBICP
* Unplug TBDM
* Uninstall USBDM 4.9.5
* Download and install 4.9.4 as it's last version with working JB16 support
http://files.mpoli.fi/sekalaiset/usbdm/ ... 4b_Win.msi <http://files.mpoli.fi/sekalaiset/usbdm/USBDM_4_9_4b_Win.msi>
* Plug TBDM back without grounding pin 10
* New device will be detected, point driver install wizard to
"C:\Program Files\pgo\USBDM 4.9.4\USBDM_Drivers\Drivers"
* New USB ID should be VID_16D0&PID_0567 and name "USBDM BDM Interface"
* You can now follow regular USBDM docs. Programmer will also work with 32-bit and 64-bit Win7 now.
...
So I wonder if someone could explain to me exactly how to "upgrade" my Turbo BDM Light Coldfire" in order to have it
working as a "new" BDM device.
I'll be glad forever.
Thank you very much for your suggestions.
Mirco
|
|
From: Xiaofan C. <xia...@gm...> - 2017-03-04 09:59:50
|
Interesting stuff: https://blogs.msdn.microsoft.com/windows_hardware_certification/2015/04/01/driver-signing-changes-in-windows-10/ https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/ Both are Windows 10 and yet they are different. The good thing is that existing driver will still work. "What about existing drivers? Do I need to re-sign these drivers to get them to work with Windows 10, version 1607? No. Existing drivers do not need to be re-signed. To ensure backwards compatibility, drivers which are properly signed by a valid cross-signing certificate issued prior to July 29th, 2015 will continue to pass signing checks on Windows 10, version 1607." In reality Windows 10 code signing becomes more and more complicated and there are many discussions in OSR NTDEV here. https://www.osronline.com/showlists.cfm?list=ntdev -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2017-03-04 09:48:33
|
On Tue, Feb 28, 2017 at 7:18 PM, Mirco Salvador gmail <mir...@gm...> wrote: > It would be wonderful if somebody could sign the driver with a valid > certificate, so it is not necessary to enable TESTSIGNING in order to use > the driver. > If you can find someone to sign it and you want to distribute it, make sure to make the modified source codes for libusb-win32 available as well. The driver portion is under GPL license which require you to do so when you modify the driver. Actually it is the same for the library since it is under LGPL. -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2017-03-04 09:23:18
|
On Tue, Feb 28, 2017 at 7:18 PM, Mirco Salvador gmail <mir...@gm...> wrote: > The only thing I had to do is to get libusb-win32 driver 1.2.6.0, change > set_configuration.c in order to replace bulk with interrupt transfer in the > driver, then compile and install it, at voilà, now I can use both eclipse > ide and CF Flasher 3.1. > It would be wonderful if somebody could sign the driver with a valid > certificate, so it is not necessary to enable TESTSIGNING in order to use > the driver. > This is refer to an very old thread. https://sourceforge.net/p/libusb-win32/mailman/message/28511143/ In general I myself are not supportive of USB device bluntly violating USB specifications. And I think non-compliant device like AVR FW Based USB device should not be forgotten already since there are many cheap USB device readily available now. Ref: I said the following at that time (more than five year ago). "There is a hack to get libusb-win32 to work with such device (to replace bulk with interrupt transfer in the driver level) but it is much better that you change the firmware to be compliant with the USB specifications. Ref: http://www.recursion.jp/avrcdc/" The avrcdc page now said "The back door to the low-speed bulk transfer is gradually closing on the newer OS. After enjoying this USB technology, switch to the HID protocol or to MCU having on-chip USB controller." -- Xiaofan |
|
From: Mirco S. g. <mir...@gm...> - 2017-02-28 11:16:55
|
On Thu, Dec 8, 2011 at 11:30 AM, David Kobe <dkobe@...> wrote: > Wow. Thank you for figuring that out. I searched for hours and was unable > to locate an explanation for the problem. > I am glad to know that it isn't anything that I did but not so happy that I > will need an old PC with XP to make it work. A second PC with XP is of course an option. On the other hand, there are other solutions. If you are using Windows 7 Professional/Enterprise/Ultimate Version, you can download XP Mode for free and it should work as well. http://www.microsoft.com/windows/virtual-pc/download.aspx Home Premium version can be upgraded for a fee. http://windows.microsoft.com/en-US/windows7/products/windows-anytime-upgrade If not, you can try VirtualBox. https://www.virtualbox.org/ -- Xiaofan Above instructions are not always applicable, at least, not on my Windows 7 64 bit HP EliteBook, because for some usb port virtualization does not work. The only thing I had to do is to get libusb-win32 driver 1.2.6.0, change set_configuration.c in order to replace bulk with interrupt transfer in the driver, then compile and install it, at voilà, now I can use both eclipse ide and CF Flasher 3.1. It would be wonderful if somebody could sign the driver with a valid certificate, so it is not necessary to enable TESTSIGNING in order to use the driver. Ratavanax |
|
From: Xiaofan C. <xia...@gm...> - 2017-02-01 02:52:39
|
Hi all, Just FYI, Travis has added Frederik Carlier as the admin of libusbdotnet. New repo in github: https://github.com/corecompat/libusbdotnet Ref: https://github.com/libusb/libusb/issues/253 There are already quite some changes including .Net Core compatibility. -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2017-01-14 02:01:42
|
On Mon, Nov 28, 2016 at 1:18 PM, Xiaofan Chen <xia...@gm...> wrote: > On Sat, Nov 5, 2016 at 10:29 AM, Xiaofan Chen <xia...@gm...> wrote: >> I closed libusb github ticket #224 since it is not really part of libusb >> project. On the other hand, maybe there are people who are interested >> in .Net Core wrapper for libusb. >> >> Ticket: >> https://github.com/libusb/libusb/issues/224 >> >> .Net Core >> https://www.microsoft.com/net/core > > There is a pre-release version here. > https://www.nuget.org/packages/CoreCompat.LibUsbDotNet/2.2.8-r101 > > I have not tried it though. As per the discussions in libusb project Ticket 253, the pre-release port does not work under Linux. Ref: https://github.com/libusb/libusb/issues/253 -- Xiaofan |
|
From: diabolo <dia...@ya...> - 2016-11-28 07:37:38
|
Good that you figure out things ;) those are just usb basic
> One thing @diabolo said is incorrect though. The STM32F4 device is not a LS
(Low Speed) device. It is a inherently a FS (Full Speed) device, which can
even work as HS (High Speed) if we can connect separate PHY chip. Please
correct me if I'm wrong.
Right some STM32F4 device have dual usb controller 1st HS+FS capable with ext phy and second one FS only but some STM32F4 has FS onlyAnyway based on the issue it was obvious you were in case FS ;)
Note that to be 100% the packet size issue 64, 512 or 1024 could show even for SS or HS device plug behind a "slower" hub if device is ok to work in such configuration.
Typically if you plug an USB3.0 device on a USB 2 or usb 2 or 3 dev on usb 1 hub So both host s/w and device f/w shall take this into account it's ie take car of running config and look at ep descriptor instead of hardcoding value of 64,512 or 1024.
Le Dimanche 27 novembre 2016 13h09, "lib...@li..." <lib...@li...> a écrit :
Send Libusb-win32-devel mailing list submissions to
lib...@li...
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
or, via email, send a message with subject or body 'help' to
lib...@li...
You can reach the person managing the list at
lib...@li...
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Libusb-win32-devel digest..."
Today's Topics:
1. Re: LibusbK Read Pipe timeout but all the (Pradeepa Senanayake)
----------------------------------------------------------------------
Message: 1
Date: Sun, 27 Nov 2016 07:07:35 +0530
From: Pradeepa Senanayake <pra...@gm...>
Subject: Re: [Libusb-win32-devel] LibusbK Read Pipe timeout but all
the
To: lib...@li...
Message-ID:
<CA+...@ma...>
Content-Type: text/plain; charset="utf-8"
Hello Guys,
Thank you very much for your answers. After going through the USB2.0
specification I figured out the changes I need to do.
USB2.0 Specification
Section 5.8.3: Bulk Transfer Packet Size Constraints
An endpoint must always transmit data payloads with a data field less than
or equal to the endpoint?s reported wMaxPacketSize value. When a bulk IRP
involves more data than can fit in one maximum-sized data payload, all data
payloads are required to be maximum size except for the last data payload,
which will contain the remaining data. A bulk transfer is complete when the
endpoint does one of the following:
? Has transferred exactly the amount of data expected
? Transfers a packet with a payload size less than wMaxPacketSize or
transfers a zero-length packet
This is the same thing diabolo suggested.
Now how handle this condition is, if the last packet I send to host is same
as wMaxPacketSize a commit another ZLP to inform the host to terminate the
bulk read.
One thing @diabolo said is incorrect though. The STM32F4 device is not a LS
(Low Speed) device. It is a inherently a FS (Full Speed) device, which can
even work as HS (High Speed) if we can connect separate PHY chip. Please
correct me if I'm wrong.
@Xiaofan's suggestions are also important. But they have already been
addressed in our source.
The issue is fixed now. Thanks again.
Best Regards,
Pradeepa Senanayake.
On Fri, Nov 25, 2016 at 6:45 PM, Xiaofan Chen <xia...@gm...> wrote:
> On Fri, Nov 25, 2016 at 9:11 PM, Xiaofan Chen <xia...@gm...> wrote:
> > On Fri, Nov 25, 2016 at 3:53 PM, diabolo <dia...@ya...> wrote:
> >> I use stm32 with libusbk back-end and I nevr seen this:
> >> But device f/w never send a multiple of 64 byte youc an do it by
> sending a
> >> zlp after data on te stm32 side
> >> but that's not convenient
> >> I always managed to send short packet and prefer to send one extra byte
> if
> >> payload is nx64 but if it the max size I ever send (ie 1024 in most of
> my
> >> app)
> >>
> >
> > Not so sure if setting the pipe policy will help.
> >
> > https://msdn.microsoft.com/en-us/library/windows/hardware/
> ff728833(v=vs.85).aspx
> >
> > http://libusbk.sourceforge.net/UsbK3/group__usbk.html#
> ga10f9e367e4241c431edc2cecd1bb827e
> > UsbK_SetPipePolicy
> >
> > SHORT_PACKET_TERMINATE (0x01)
> > PIPE_TRANSFER_TIMEOUT (0x03)
> >
> Also ALLOW_PARTIAL_READS (0x05).
>
> Ref: http://permalink.gmane.org/gmane.comp.lib.libusbx.devel/1245
>
> --
> Xiaofan
>
> ------------------------------------------------------------
> ------------------
> _______________________________________________
> Libusb-win32-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Lib...@li...
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
End of Libusb-win32-devel Digest, Vol 118, Issue 8
**************************************************
|
|
From: Xiaofan C. <xia...@gm...> - 2016-11-28 05:18:54
|
On Sat, Nov 5, 2016 at 10:29 AM, Xiaofan Chen <xia...@gm...> wrote: > I closed libusb github ticket #224 since it is not really part of libusb > project. On the other hand, maybe there are people who are interested > in .Net Core wrapper for libusb. > > Ticket: > https://github.com/libusb/libusb/issues/224 > > .Net Core > https://www.microsoft.com/net/core There is a pre-release version here. https://www.nuget.org/packages/CoreCompat.LibUsbDotNet/2.2.8-r101 I have not tried it though. -- Xiaofan |
|
From: Pradeepa S. <pra...@gm...> - 2016-11-27 01:37:46
|
Hello Guys, Thank you very much for your answers. After going through the USB2.0 specification I figured out the changes I need to do. USB2.0 Specification Section 5.8.3: Bulk Transfer Packet Size Constraints An endpoint must always transmit data payloads with a data field less than or equal to the endpoint’s reported wMaxPacketSize value. When a bulk IRP involves more data than can fit in one maximum-sized data payload, all data payloads are required to be maximum size except for the last data payload, which will contain the remaining data. A bulk transfer is complete when the endpoint does one of the following: • Has transferred exactly the amount of data expected • Transfers a packet with a payload size less than wMaxPacketSize or transfers a zero-length packet This is the same thing diabolo suggested. Now how handle this condition is, if the last packet I send to host is same as wMaxPacketSize a commit another ZLP to inform the host to terminate the bulk read. One thing @diabolo said is incorrect though. The STM32F4 device is not a LS (Low Speed) device. It is a inherently a FS (Full Speed) device, which can even work as HS (High Speed) if we can connect separate PHY chip. Please correct me if I'm wrong. @Xiaofan's suggestions are also important. But they have already been addressed in our source. The issue is fixed now. Thanks again. Best Regards, Pradeepa Senanayake. On Fri, Nov 25, 2016 at 6:45 PM, Xiaofan Chen <xia...@gm...> wrote: > On Fri, Nov 25, 2016 at 9:11 PM, Xiaofan Chen <xia...@gm...> wrote: > > On Fri, Nov 25, 2016 at 3:53 PM, diabolo <dia...@ya...> wrote: > >> I use stm32 with libusbk back-end and I nevr seen this: > >> But device f/w never send a multiple of 64 byte youc an do it by > sending a > >> zlp after data on te stm32 side > >> but that's not convenient > >> I always managed to send short packet and prefer to send one extra byte > if > >> payload is nx64 but if it the max size I ever send (ie 1024 in most of > my > >> app) > >> > > > > Not so sure if setting the pipe policy will help. > > > > https://msdn.microsoft.com/en-us/library/windows/hardware/ > ff728833(v=vs.85).aspx > > > > http://libusbk.sourceforge.net/UsbK3/group__usbk.html# > ga10f9e367e4241c431edc2cecd1bb827e > > UsbK_SetPipePolicy > > > > SHORT_PACKET_TERMINATE (0x01) > > PIPE_TRANSFER_TIMEOUT (0x03) > > > Also ALLOW_PARTIAL_READS (0x05). > > Ref: http://permalink.gmane.org/gmane.comp.lib.libusbx.devel/1245 > > -- > Xiaofan > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |
|
From: Xiaofan C. <xia...@gm...> - 2016-11-25 13:15:34
|
On Fri, Nov 25, 2016 at 9:11 PM, Xiaofan Chen <xia...@gm...> wrote: > On Fri, Nov 25, 2016 at 3:53 PM, diabolo <dia...@ya...> wrote: >> I use stm32 with libusbk back-end and I nevr seen this: >> But device f/w never send a multiple of 64 byte youc an do it by sending a >> zlp after data on te stm32 side >> but that's not convenient >> I always managed to send short packet and prefer to send one extra byte if >> payload is nx64 but if it the max size I ever send (ie 1024 in most of my >> app) >> > > Not so sure if setting the pipe policy will help. > > https://msdn.microsoft.com/en-us/library/windows/hardware/ff728833(v=vs.85).aspx > > http://libusbk.sourceforge.net/UsbK3/group__usbk.html#ga10f9e367e4241c431edc2cecd1bb827e > UsbK_SetPipePolicy > > SHORT_PACKET_TERMINATE (0x01) > PIPE_TRANSFER_TIMEOUT (0x03) > Also ALLOW_PARTIAL_READS (0x05). Ref: http://permalink.gmane.org/gmane.comp.lib.libusbx.devel/1245 -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2016-11-25 13:11:16
|
On Fri, Nov 25, 2016 at 3:53 PM, diabolo <dia...@ya...> wrote: > I use stm32 with libusbk back-end and I nevr seen this: > But device f/w never send a multiple of 64 byte youc an do it by sending a > zlp after data on te stm32 side > but that's not convenient > I always managed to send short packet and prefer to send one extra byte if > payload is nx64 but if it the max size I ever send (ie 1024 in most of my > app) > Not so sure if setting the pipe policy will help. https://msdn.microsoft.com/en-us/library/windows/hardware/ff728833(v=vs.85).aspx http://libusbk.sourceforge.net/UsbK3/group__usbk.html#ga10f9e367e4241c431edc2cecd1bb827e UsbK_SetPipePolicy SHORT_PACKET_TERMINATE (0x01) PIPE_TRANSFER_TIMEOUT (0x03) -- Xiaofan |
|
From: diabolo <dia...@ya...> - 2016-11-25 07:53:57
|
STM32F4 is a LS device so it's packet size is 64 byte.SO if your Host request (read pipe) is are less than what the device is sending but is nx64 it is normal that it time out An usb bulk request only end if all the requested data is received (request 128 and get 128 ) or the last receive packet is less than 64 or 0 (is a short or ZLP)ie if your request is 1024 long but device send 64,128,... it will time out if thsiis what happen the issue is how your f/w and app communicates I use stm32 with libusbk back-end and I nevr seen this:But device f/w never send a multiple of 64 byte youc an do it by sending a zlp after data on te stm32 side but that's not convenient I always managed to send short packet and prefer to send one extra byte if payload is nx64 but if it the max size I ever send (ie 1024 in most of my app) From: Pradeepa Senanayake <pra...@gm...> Subject: [Libusb-win32-devel] LibusbK Read Pipe timeout but all the data is received To: lib...@li... Message-ID: <CA+1tQ70hKGTk=LRS...@ma...> Content-Type: text/plain; charset="utf-8" Hello All, I have been using libusbK with WinUSB for a long time now. Recently we found out a bug which had slipped away from us and has been in the source for 2 years. The issue is, when we call ReadPipe to read a bulk in endpoint sometimes we get a timeout. When we investigated more we found out that the issue comes only when our reply data amount is a multiple of 64 bytes. Nevertheless, when we get a timeout if I checked the transferred byte amount and the content, it has all the data the device had committed. I'm a bit perplexed at the moment due to this behavior. We have a STM32F4 IC in the device. It seems like it's committing all the data to the USB controller properly. Is there any one who had faced something similar? Or if this is a known issue can someone suggest a workaround? Thank you, Best Regards, Pradeepa Senanayake. |
50 messages has been excluded from this view by a project administrator.
