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, if I can > toggle a LED, I'll be a happy man :)
I'm not sure you should use interrupt OUT to trigger measurements, probably a control transfer is more suitable, or simply no transfer at all if the micro can decide on it's own when to measure. > I installed a version of WinUSB supplied by the µC manufacturer. WinUSB is WinUSB, it's from Microsoft. I would suggest to use zadig.exe to check that WinUSB has been installed correctly for your device, if not then you can correct it using zadig very easily. > The device has 2 endpoints (TX+RX) of 64 bytes. IN and OUT is the USB terminology. You may not need the OUT one, interrupt transfers aren't a very good fit for sending commands. > On WinXP32, libusb_claim_interface() returns 0. Ok, that's good. > In Linux, my app works very well. Should I see those kernel warnings > in the console ? log files ? In dmesg. It would be helpful to see usbmon output from a run of your Linux application. Use these two links: http://people.redhat.com/zaitcev/linux/usbmon-6.tar.gz http://kernel.org/doc/Documentation/usb/usbmon.txt //Peter ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
