On Thu, Jan 3, 2013 at 10:30 AM, Xiaofan Chen wrote:
> I run your program and I can not reproduce the issue with my device
> (ST-Link V2 debugger, default WinUSB driver from ST, 0483:3748). I
> just change the debug log level to 4 and change the vid/pid to
> suit my device and nothing else of your
On Wed, Jan 2, 2013 at 5:07 PM, Mohamed HAMZAOUI wrote:
> this is the log with level 4 verbosity :
> ...
> [ 0.165009] [0dfc] libusbx: debug [libusb_get_device_descriptor]
> 8086:27c9 (bus 3, device 1)
> [ 0.169009] [0dfc] libusbx: debug [libusb_get_device_descriptor]
> 8086:27cb (bus 5, d
I'll try to have a look at this issue by the end of the week.
Regards,
/Pete
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
this is the log with level 4 verbosity :
[timestamp] [threadID] facility level [function call]
[ 0.068004] [0dfc] libusbx: debug [libusb_get_device_list]
[ 0.072004] [23cc] libusbx: debug [windows_clock_getti
On Wed, Jan 2, 2013 at 4:27 PM, Mohamed HAMZAOUI wrote:
> Hi,
> I use libusb1.0.14/WinUSB (v6.1.7600.16385)
> This is a simple program which can reproduce the problem (output is in
> the last) :
Thanks. I can try this program by myself later to see if I can
reproduce the issue.
> libusb_set_debu
Hi,
I use libusb1.0.14/WinUSB (v6.1.7600.16385)
This is a simple program which can reproduce the problem (output is in
the last) :
#include
#include "libusb.h"
struct device_descriptor {
uint16_t vid;
uint16_t pid;
};
static struct device_descriptor managed_devices[] = {
{ 0x0525, 0xA4A0 },
};
