I had hoped that I could make some progress by investigating this
further myself, but wasn't able to figure much out...  It seems to me
in the log file that I posted, the log entry of most interest is this
one:
  libusbx: debug [darwin_handle_callback] handling isoc completion
with kernel status -536854513
That message is shown for most [darwin_handle_callback] entries,
alternating sometimes with:
  libusbx: debug [darwin_handle_callback] handling isoc completion
with kernel status 0

-536854513 presumably means kIOUSBNotSent2Err.  Perhaps a helpful
discussion about this error can be found in this thread:
  http://lists.apple.com/archives/usb/2007/Apr/msg00003.html
But it's too technical for my current knowledge of mac and USB.  In
particular, maybe this comment is relevant?

"if you take a look at AppleUSBOHCI.cpp, you'll find that kIOUSBNotSent2Err
corresponds to OHCI status 15. You can look that up in the OHCI spec. A not
sent error occurs because your request is never put onto the bus. This
usually happens if the request is for a frame number in the past, or too far
in the future. I think that all your requests are for a time in the past, so
they never get put onto the bus by the controller."
  http://lists.apple.com/archives/usb/2007/Apr/msg00008.html

Anyone have any suggestions?

Here is the output from lsusb -vvv for my device which isn't working
on mac (but, as described previously, works fine on linux):

Bus 002 Device 006: ID 088d:0006
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x088d
  idProduct          0x0006
  bcdDevice            0.02
  iManufacturer           1 Syntech NL
  iProduct                2 IDAC 4
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               32mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         0 (Defined at Interface level)
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0258  1x 600 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            1
          Transfer Type            Isochronous
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0005  1x 5 bytes
        bInterval               1


On Mon, Jun 18, 2012 at 12:20 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> On Sun, Jun 17, 2012 at 10:33 PM, Ellis Whitehead
> <ellis.whiteh...@gmail.com> wrote:
>>>> You can produce detailed debug log if you set the environmental
>>>> variable LIBUSB_DEBUG to 4. That debug log may help to identify
>>>> the potential problem.
>>
>> Ok, I've uploaded it here:
>> http://gcead.sourceforge.net/libusbx-debug-20120617.log
>> I issued the command to start recording at timestamp [12.054910].  Due
>> to the large number of debug lines, I stopped recording at
>> [12.528804].  Shutdown was at [18.014753].
>>
>
> Indeed this looks like a potential problem in the Mac OS X backend.
>
> What is the Mac OS X version you are using? Could you post
> the details about your device (eg: USB Prober output about
> your device, or "lsusb -vvv" under Linux or the USBView
> output under Windows)?
>
> I do not know much about the details of the OS X backend but hopefully
> others can help you here.
>
>
> --
> Xiaofan
>
> ------------------------------------------------------------------------------
> 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

------------------------------------------------------------------------------
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

Reply via email to