• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 20 subscribers
  • Views 1496 views
  • Users 0 members are here
Options
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

USB HID example, size problems .. again and again

Ulrich Behrenbeck

Hi all

first of all thanks to Tsuneo Chinzei for contributing here that much. Very helpful. THANK YOU !! I am afraid my question finally will end up there top;)

So, here is the common problem, wanting to increase msg sizes. read around here a lot and obeyed all the hints, but still failing.

I am using the Std Keil XP Client, except that I converted it back to VC 6 and added minor overlapped support (works fine for 1 byte msgs)

First I used the simplified report desciptor TC provided , together with one byte msgs -> Still OK

const BYTE HID_ReportDescriptor[] = {
  HID_UsagePageVendor(0x00),
  HID_Usage(0x01),
  HID_Collection(HID_Application),
    HID_LogicalMin(0),             // value range: 0 - 0xFF
    HID_LogicalMaxS(0xFF),
    HID_ReportSize(8),             // 8 bits
    HID_ReportCount(1),            // one byte
    HID_Usage(0x01),
    HID_Input(HID_Data | HID_Variable | HID_Absolute),
    HID_Usage(0x01),
    HID_Output(HID_Data | HID_Variable | HID_Absolute),
  HID_EndCollection,
};

I modified the wMaxPacketSize to 0x40 , still OK

Then I set the Report Count to 60 Bytes. Inspection with HID Device Exerciser shows device now with 61 bytes, as expected. (in both directions)

Next step is to modify the VC program to reflect the report changes, so setting both i+o structres to 61 bytes. WriteFile is Ok, but ReadFile always hangs.

Looking ant the many threads here about this particular topic , it would really have been a good idea to provide such a sample? Hello ? KEIL ?!?!? someone reading here ?!?!

Even harder to understand is: How can they ship a broken product like they do with ULINK 2 . Using the inspector shows a completely broken string table, as is in all the samples here too. Again - thanks TC , that can be fixed, but why do they ship such broken stuff ?

0