Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

How to debug when not working ?

2006-11-06
2013-04-22
  • Hello,

    I have a connectland-branded, prolific-based adapter.
    I do not manage to make it work, where my Keyspan adapter is working fine ( the iSmartTrain application )

    How can I pinpoint my problem ?

    I have noticed calls to a logging function in the code. How can I enable them ?
    ( the USB Logger crashes my iMac G5 when I try to start it...)

    thanks in advance,
    --Philippe

    please find below
    1- extract extract of system.log
    2- the output of the USB prober, regarding my device

    -------------------------------------------------
    ===== lundi 6 novembre 2006 21 h 12 Europe/Paris =====
    Nov  6 21:13:30 iMac-des-Barthelemy kernel[0]: USBF:    74579. 83    IOUSBCompositeDriver[0x3478b80] Could not open device (USB-Serial Controller)
    Nov  6 21:13:31 iMac-des-Barthelemy kernel[0]: USBF:    74580.116    ControlTransaction: control packet 1 error 0xe0004057
    Nov  6 21:13:31 iMac-des-Barthelemy kernel[0]: USBF:    74580.514    ControlTransaction: control packet 1 error 0xe0004057
    Nov  6 21:13:31 iMac-des-Barthelemy kernel[0]: USBF:    74580.527    ControlTransaction: control packet 1 error 0xe0004057
    Nov  6 21:15:01 iMac-des-Barthelemy kernel[0]: nl_bjaelectronics_driver_PL2303(0x32b8c00)::dequeueDataGated - INTERRUPTED

    -------------------------------------------------------
    Full Speed device @ 5 (0x0B200000): .............................................   Composite device: "USB-Serial Controller"
        Device Descriptor  
            Descriptor Version Number:   0x0110
            Device Class:   0   (Composite)
            Device Subclass:   0
            Device Protocol:   0
            Device MaxPacketSize:   64
            Device VendorID/ProductID:   0x067B/0x2303   (Prolific Technology, Inc.)
            Device Version Number:   0x0300
            Number of Configurations:   1
            Manufacturer String:   1 "Prolific Technology Inc."
            Product String:   2 "USB-Serial Controller"
            Serial Number String:   0 (none)
        Configuration Descriptor  
            Length (and contents):   39
                Raw Descriptor (hex)    0000: 09 02 00 27 01 01 00 A0  32 09 04 00 00 03 FF 00 
                Raw Descriptor (hex)    0010: 00 00 07 05 81 03 0A 00  01 07 05 02 02 40 00 00 
                Raw Descriptor (hex)    0020: 07 05 83 02 40 00 00
            Number of Interfaces:   1
            Configuration Value:   1
            Attributes:   0xA0 (bus-powered, remote wakeup)
            MaxPower:   100 ma
            Interface #0 - Vendor-specific  
                Alternate Setting   0
                Number of Endpoints   3
                Interface Class:   255   (Vendor-specific)
                Interface Subclass;   0   (Vendor-specific)
                Interface Protocol:   0
                Endpoint 0x81 - Interrupt Input  
                    Address:   0x81  (IN)
                    Attributes:   0x03  (Interrupt no synchronization data endpoint)
                    Max Packet Size:   10
                    Polling Interval:   1 ms
                Endpoint 0x02 - Bulk Output  
                    Address:   0x02  (OUT)
                    Attributes:   0x02  (Bulk no synchronization data endpoint)
                    Max Packet Size:   64
                    Polling Interval:   0 ms
                Endpoint 0x83 - Bulk Input  
                    Address:   0x83  (IN)
                    Attributes:   0x02  (Bulk no synchronization data endpoint)
                    Max Packet Size:   64
                    Polling Interval:   0 ms

     
    • B.J. Arnoldus
      B.J. Arnoldus
      2007-08-10

      The USB Prober with Logging is the way to debug the driver. You should recompile the driver with logging enabled.
      I know the problem that the USB prober driver can cause crashes, probably it is a wrong version for your kernel.

      I will publish in a few weeks a new version and maybe this solves your problem. In the current version are some
      problems with mass data transmission (buffer in the device will be overwritten, although data is not transmitted)