[libhid-discuss] simple output

Charles Lepple clepple at ghz.cc
Mon Feb 16 02:49:05 UTC 2009


[Please keep the list CC'd.]

The last debug line that you posted was this:

  NOTICE: hid_prepare_parser(): successfully set up the HID parser  
for USB
device 004/003[0].

There should have been other lines after that, referring to looking  
up the path, and attempting to send the message to the device.

Also, the firmware may be expecting a message on an interrupt  
endpoint, but you did not include that part of the 'lsusb' output.

-- 

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

On Feb 15, 2009, at 11:28 AM, Ael Gain wrote:

> Ok thanks, I tried to send 1 byte instead of 2 at the path  
> { 0xffa00001, 0xffa00004 } via the hid_set_output_report function  
> but i've steel no reactions at the pic level... I don't know what  
> to do, have you any idea ?
> thank you,
>
> ----- Original Message ----- From: "Charles Lepple" <clepple at ghz.cc>
> To: "Ael Gain" <ael.gain at free.fr>
> Cc: "libhid-discuss List" <libhid-discuss at lists.alioth.debian.org>
> Sent: Saturday, February 14, 2009 7:46 PM
> Subject: Re: [libhid-discuss] simple output
>
>
>> On Feb 13, 2009, at 1:27 PM, Ael Gain wrote:
>>
>>> I'm not sure about what is the debug output but I'll paste this:
>>
>> That's what I am referring to.
>>
>>>  parse tree of HIDInterface 004/004[0]:
>>>   path: 0xffa00001.0xffa00003; type: 0x80
>>
>> This means you have one byte at path { 0xffa00001, 0xffa00003 }  
>> (input)...
>>
>>>   path: 0xffa00001.0xffa00004; type: 0x90
>>
>> ... one byte of output at { 0xffa00001, 0xffa00004 } ...
>>
>>>   path: 0xffa00001.0xffa00005; type: 0xb0
>>>   path: 0xffa00001.0x00000000; type: 0xb0
>>
>> and two feature bytes at { 0xffa00001, 0xffa00005 } (which can be   
>> either input or output).
>>
>> It sounds like you were trying to send two bytes to an output  
>> that  only expects one byte.
>>
>>> and this, when i try my program:
>>>
>>> TRACE: hid_prepare_parser(): setting up the HID parser for USB  
>>> device
>>> 004/003[0]...
>>>   TRACE: hid_reset_parser(): resetting the HID parser for USB device
>>> 004/003[0]...
>>>   TRACE: hid_prepare_parser(): dumping the raw report descriptor
>>>   TRACE: hid_prepare_parser(): 0x000: 0x06 0xa0 0xff 0x09 0x01  
>>> 0xa1  0x01
>>> 0x09
>>>   TRACE: hid_prepare_parser(): 0x008: 0x03 0x15 0x00 0x26 0x00  
>>> 0xff  0x75
>>> 0x08
>>>   TRACE: hid_prepare_parser(): 0x010: 0x95 0x01 0x81 0x02 0x09  
>>> 0x04  0x15
>>> 0x00
>>>   TRACE: hid_prepare_parser(): 0x018: 0x26 0x00 0xff 0x75 0x08  
>>> 0x95  0x01
>>> 0x91
>>>   TRACE: hid_prepare_parser(): 0x020: 0x02 0x09 0x05 0x15 0x00  
>>> 0x26  0x00
>>> 0xff
>>>   TRACE: hid_prepare_parser(): 0x028: 0x75 0x08 0x95 0x02 0xb1  
>>> 0x02  0xc0
>>>   TRACE: hid_prepare_parser(): parsing the HID tree of USB device
>>> 004/003[0]...
>>>  NOTICE: hid_prepare_parser(): successfully set up the HID  
>>> parser  for USB
>>> device 004/003[0].
>>>
>>> Thank you for your help,
>>> cloud
>>>
>>> ----- Original Message -----
>>> From: "Charles Lepple" <clepple at ghz.cc>
>>> To: "Ael Gain" <ael.gain at free.fr>
>>> Cc: "libhid-discuss List" <libhid-discuss at lists.alioth.debian.org>
>>> Sent: Thursday, February 12, 2009 4:23 AM
>>> Subject: Re: [libhid-discuss] simple output
>>>
>>>
>>>> On Feb 11, 2009, at 1:02 PM, Ael Gain wrote:
>>>>
>>>>> Is my path allright ? Do you see any (many? :-) ) things wrong   
>>>>> in  my
>>>>> code ? I'm a bit lost in HID programming...
>>>>
>>>> The easiest way to tell is from the debug output.
>>>>
>>>> -- 
>>>> Charles Lepple
>>>>
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> libhid-discuss mailing list
>>> libhid-discuss at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
>>> http://libhid.alioth.debian.org/
>>
>




More information about the libhid-discuss mailing list