On 2012.05.26 11:05, Xiaofan Chen wrote: > I am not so sure why there is the last warning about pipe stall. > > Claiming interface 0... > > Reading string descriptors: > String (0x01): "SEGGER" > String (0x02): "J-Link" > String (0x03): "xxxxxxxx" > libusbx: warning [darwin_transfer_status] transfer error: pipe is stalled
I've seen that one too, and it occurs when trying to read a string descriptor that doesn't exist. Basically, xusb will try to access string descriptor 0xEE to find out if the device is WCID and display the WCID data if that is the case (which can be done on any platform, not just Windows). It looks like trying to access 0xEE on Mac produces a pipe stall. Regards, /Pete ------------------------------------------------------------------------------ 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
