Well, as I said, the USB device is a Microchip µC. So, I picked a demo
board and used the WinUSB demo firmware provided by Microchip. After a
few changes, I could mimic their VC++ example program with my classes
ported from Linux, and Qt4.
So, the firmware was the cause, not Libusbx ! Also, I t
On 2012.09.17 09:52, Peter Stuge wrote:
> The Linux backend has been worked on quite a lot and by different
> people while the Windows backend is much younger and is principally
> the work of one person - so there are several differences, and the
> odd new one is discovered now and then. :\
Congra
On Mon, Sep 17, 2012 at 3:27 PM, Bob Lapique wrote:
> Hi all,
>
> I can see a lot of very technical posts out there. So, I wonder if it Is
> the right place to seek help on basic Libusbx usage...
>
> If not, I'd be very pleased if someone could redirect me to some place
> where the difference betw
Bob Lapique wrote:
> What I want to do is to communicate with a home made board, based on a
> Microchip PIC microcontroller (PIC18 or PIC32), with interrupt
> transfers. I don't want anything special, just send and receive packets
> to trigger measurements and get the results. But at the moment,
OK, I am really glad to find some help here.
What I want to do is to communicate with a home made board, based on a
Microchip PIC microcontroller (PIC18 or PIC32), with interrupt
transfers. I don't want anything special, just send and receive packets
to trigger measurements and get the results.
Hi Bob,
Bob Lapique wrote:
> the right place to seek help on basic Libusbx usage...
Sure, if you find no other resource to explain what you want to know.
> If not, I'd be very pleased if someone could redirect me to some place
> where the difference between the Linux and Windows implementation
