CCS/TM4C1294NCPDT: Creating Custom HID Device using TivaWare USB library

Hello Erik,

I would add in the call for MAP_IntMasterEnable(); as well, I don't see that being called and there are a few interrupts setup.

Do you get the message on UART for "Host Connected..."? That would indicate if the device is connecting to Windows and just isn't enumerating or if the code is not even communicating with Windows.

Depending what is going on, you may need a USB analyzer to understand where in the process this is breaking.

The program never receives the host connected event and therefore always hangs in the while loop before that UART message.  I am not sure where MAP_IntMasterEnable(); would be used and I have looked through the keyboard example and I don't see this function ever called, should it just be called near the start of the main loop?

Hello Erik,

I would add it after:

    //
    // Set the system tick to fire 100 times per second.
    //
    MAP_SysTickPeriodSet(ui32SysClock / SYSTICKS_PER_SECOND);
    MAP_SysTickIntEnable();
    MAP_SysTickEnable();

Alright, I added that line but it still doesn't receive a connect event from the host.

Hello Erik,

In that event, you would need to get a USB analyzer in order to check what information is being exchanged and where in the enumeration process the Custom HID device is failing to meet what Windows is expecting from the USB device. Unfortunately as I am just a device expert, I don't have in-depth knowledge on the USB enumeration requirements for interfaces like Custom HID so I don't really have much guidance I can offer. Maybe another community member will be able to assist though...

Erik Kinstler said:

Alright, I added that line but it still doesn't receive a connect event from the host.

Erik,

The only difference between a "keyboard HID" and a "Generic HID" is the report descriptors. The "Usage Page" tells the host that the report  conforms to either a standard device, like a keyboard or mouse, or a custom/vendor-specific device. The host uses this to know which driver to load.

Given how you describe your problem, I suspect that your report descriptor is screwed up in some way, or that the size of the descriptor is being reported incorrectly. A bus analyzer, or perhaps even Wireshark (which has USB analysis) will tell you that you have malformed descriptors.

Getting descriptors right is part of the pain of developing a USB product!