libusb

libusb-win32: Automated installation of a driver filter

狂风中的少年 提交于 2019-12-02 03:20:45
问题 I've faced a problem getting my libusb-w32 based program to detect devices. The program has to detect digital cameras, and I need to automatically install driver filter for any new camera to be detected without any manual work. I've used install-filter i --class={6BDD1FC6-810F-11D0-BEC7-08002BE2092F} , i. e. installing filter for MTP devices, and it seemed to work. But today I tried it on a clean machine and found out it actually only seemed that way. Tried install-filter with different

ld: symbol(s) not found for architecture x86_64 (libusb)

六月ゝ 毕业季﹏ 提交于 2019-12-02 02:23:52
问题 I'm trying to compile the following libusb snippet on my Mac: #include <stdio.h> #include <stdlib.h> #include <libusb.h> int main(void) { libusb_device **devices; ssize_t device_count = 0; device_count = libusb_get_device_list(NULL, &devices); printf("%d devices found\n", (int)device_count); return EXIT_SUCCESS; } I have libusb installed via Homebrew. I'm getting the following error during compilation: ld: symbol(s) not found for architecture x86_64 The full compiler output is as follows: 22

How can I comunicate with this device using pyusb?

 ̄綄美尐妖づ 提交于 2019-12-02 02:04:33
I have a Netware uniFlow device. When I plug it in it shows up in dmesg: [ 2962.369905] usb 2-1.4: new full-speed USB device number 11 using ehci-pci [ 2962.463867] usb 2-1.4: New USB device found, idVendor=171b, idProduct=2001 [ 2962.463871] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2962.463874] usb 2-1.4: Product: USB Keyboard [ 2962.463876] usb 2-1.4: Manufacturer: RFIDeas [ 2962.465361] input: RFIDeas USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/0003:171B:2001.0008/input/input17 [ 2962.465481] hid-generic 0003:171B:2001.0008: input

LibUsbDotNet No devices found when calling UsbDevice.AllDevices

自作多情 提交于 2019-12-01 23:45:05
I am executing the example code of LibUsbDotNet which will return me the information of all connected usb devices. You can find this code below. using System; using LibUsbDotNet; using LibUsbDotNet.Info; using LibUsbDotNet.Main; using System.Collections.ObjectModel; namespace Examples { internal class ShowInfo { public static UsbDevice MyUsbDevice; public static void Main(string[] args) { // Dump all devices and descriptor information to console output. UsbRegDeviceList allDevices = UsbDevice.AllDevices; foreach (UsbRegistry usbRegistry in allDevices) { if (usbRegistry.Open(out MyUsbDevice)) {

Rust program requires the libusb DLL to be present even though it was statically linked

感情迁移 提交于 2019-12-01 20:43:14
I'm trying to make a Rust program that statically links against libusb, using the MSVC toolchain, but it blows up at run-time from a missing DLL: error: process didn't exit successfully: `target\debug\test_libusb.exe` (exit code: 0xc0000135, STATUS_DLL_NOT_FOUND) I used Dependency Walker to find that the missing DLL is LIBUSB-1.0.DLL. Adding it to the project solves the problem and so does dynamically linking everything, but I would like to avoid this solution. My starting point was this libusb-sys crate , but since it didn't work I made a simpler similar crate. I got libusb from vcpkg. libusb

Set USB transfer type manually for a device

。_饼干妹妹 提交于 2019-12-01 12:45:54
I try to run the Asus xtion on a ARM Board (Pandaboard) and I already installed and used the samples (e.g NiSimpleRead) provided by openni. To get these samples running on this Platform it needed some tweaks, one of them is to set the UsbInterface manually to isochronous (in the GlobalDefaults.ini). But after that everything runs smoothly Now I want to use PCL (which is based on openni) to grab some frames but PCL doesn't work. I believe that pcl tries to set the USB-Interface on its own (it probably uses XnUSBLinux.cpp to be generic) and tries to bypass the GlobalDefaults.ini, respectively

Set USB transfer type manually for a device

雨燕双飞 提交于 2019-12-01 11:47:35
问题 I try to run the Asus xtion on a ARM Board (Pandaboard) and I already installed and used the samples (e.g NiSimpleRead) provided by openni. To get these samples running on this Platform it needed some tweaks, one of them is to set the UsbInterface manually to isochronous (in the GlobalDefaults.ini). But after that everything runs smoothly Now I want to use PCL (which is based on openni) to grab some frames but PCL doesn't work. I believe that pcl tries to set the USB-Interface on its own (it

How can I get Linux device with FTDI D2XX driver API

扶醉桌前 提交于 2019-11-30 14:25:19
问题 I am using FTDI D2XX driver API to communicate with a FTDI device. It gives me some information about the device like locid, serialnumber, description but it is not enough. How can I get the device number ( /dev/ttyUSBXX ) or bus or port with this API. thanks 回答1: As the D2XX Programmer's Guide tells in the Introduction: For Linux, Mac OS X (10.4 and later) and Windows CE (4.2 and later) the D2XX driver and VCP driver are mutually exclusive options as only one driver type may be installed at

How can I get Linux device with FTDI D2XX driver API

人盡茶涼 提交于 2019-11-30 10:37:19
I am using FTDI D2XX driver API to communicate with a FTDI device. It gives me some information about the device like locid, serialnumber, description but it is not enough. How can I get the device number ( /dev/ttyUSBXX ) or bus or port with this API. thanks As the D2XX Programmer's Guide tells in the Introduction: For Linux, Mac OS X (10.4 and later) and Windows CE (4.2 and later) the D2XX driver and VCP driver are mutually exclusive options as only one driver type may be installed at a given time for a given device ID. The problem is that your Linux may automatically loads the VCP driver (

Unable to claim USB interface with C + libusb on Mac OS X

生来就可爱ヽ(ⅴ<●) 提交于 2019-11-30 09:02:56
问题 I've got a compound USB + CDC device I built using a PIC32 microcontroller, and I'm trying to connect to the device and send some data to the CDC data interface endpoint from my Mac. I know the circuit works 100%, as the device registers as both a HID joystick, and I'm able to connect to the device using Zoc terminal, on /dev/tty.usbmodemfa132. I can send commands with Zoc, and see my MCU responding to these commands by blinking some LEDs on the circuit. I'm running this on Mac OS X Mavericks