g...@novadsp.com wrote: > I've got a custom USB bulk device (Blackfin based with my own firmware > for what it's worth).
Fun! Did you already verify the USB part of the firmware, or is this part of what you are doing right now? > I run xdev face:feed (our VID/PID) and all device info gets reported > correctly. Most of this comes from Windows APIs rather than from communication with the device itself. > When libusb_open_device is called the console displays this error message: > > [ 4.425253] [000025f0] libusbx: error [cache_config_descriptors] could > not access > configuration descriptor (dummy) for > '\\.\USB#VID_05E3&PID_0608#8&85A6673&0&4' > : [31] A device attached to the system is not functioning. > > Can anyone tell me why? Is this caused during device > inspection/inquiry or what? In my experience Windows isn't so helpful about error messages when something doesn't work the way it wants. If you are indeed in the process of firmware bringup then I'd recommend testing also with other environments, in particular Linux or FreeBSD can provide many helpful error messages if something is slightly off in the firmware. //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
