SMT32 usb two HIDs

I got the encoder working; In the device manager, I can see another keyboard HID interface.

Everything seems to be fine, but if I change the vendor ID and / or the product ID -> the USB HID device will be unknown. No keyboard device will be available in the device manager. Both report descriptors won't be read by the host.

Is it correct, that there are some information stored in the registry (which driver has to be loaded for this USB connection and so on)?

Jan

3) Four options are proposed for the second HID top-level collection for touchscreen

a) Generic Desktop - Mouse
b) Generic Desktop - Joystick (or GamePad)
c) Digitizer page - Pen (or Touchscreen)
d) Vendor specific device

I will try to use the version a) - writing my own calibration method.

It's a little bit strange. If I start the host with the connected usb device, the device won't be shown as keyboard in the device manager.

If I try to search for new connected hardware (in the device manager), then the device will be found and shown. Therefore I'm not able to find the existing error using USBlyzer, because this software always search for new connected devices at startup.

I've some volatile global variables for the encoder part; if I delete them (6 volatile char variables) the device will be recognized by the host after booting.

The stack-size is big enough.

If I start the host with the device connected to the usb port (with new vendor and product ID), the device will be shown as unknown in the device manager. After a while, windows tries to talk to the device a second time, and after that both HID interrfaces from the device will be shown in the device manager (without any kind of error)....

ok I deleted the whole code for the encoder - getting the same problem; the device is always listened in the device manager as "other devices".

summary:

a) booten -> device manager shows usb device -> "other devices" -> after a while -> some usb resets occur -> usb device is shown as keyboard and mouse HID device

b) host is already running -> connect usb device -> device manager shows device as keyboard and mouse device (as expected)

In both ways, I use a new vendor and product ID.

Is your device bus-powered (supplied by USB line), or self-powered (has stand alone power supply) ?

KEIL examples are made for bus-powered devices.
For self-powered, you have to add several process to your code.
- VBUS detection - USB physical connection detection and additional initialization

Tsuneo

That's a point. My device is self-powered.

> VBUS detection - USB physical connection detection and additional initialization

I'm using an external pullup on data+ line for the correct detection of the usb device (full-speed). I can enable / disable the usb detection by the device controller, because the pullup 1k5 is directly connected to an GPIO.

By the way, is my report descriptor for the touch (configurated as mouse device) ok?

const BYTE HID_ReportDescriptor2[] = {
0x05, 0x01, // USAGE_PAGE (Generic Desktop)
0x09, 0x02, // USAGE (Mouse)
0xa1, 0x01, // COLLECTION (Application)
0x09, 0x01, // USAGE (Pointer)
0xa1, 0x00, // COLLECTION (Physical)

0x05, 0x01, // USAGE PAGE (Generic Desktop)
0x09, 0x30, // USAGE (X)
0x09, 0x31, // USAGE (Y)
0x15, 0x81, // LOGICAL_MINIMUM (-127)
0x25, 0x7F, // LOGICAL_MAXIMUM (127)
0x75, 0x08, // REPORT_SIZE (8)
0x95, 0x02, // REPORT_COUNT (2)
0x81, 0x06, // INPUT (Data,Var,Relative)
0xc0, // END_COLLECTION
0xc0, // END_COLLECTION
};

In the device manager, I can see a second HID usb mouse device.

unsigned short coordinate[2];

GetValue(&coordinate[0]);

USB_WriteEP(0x82, (BYTE *) &coordinate[0], 2 * sizeof(unsigned int));

I'm not sure if this USB_WriteEP() will work. Moreover is it better to use LOGICAL_MINIMUM, LOGICAL_MAXIMUM (-127, 127) or (0, 255)?

const WORD HID_ReportDescSize = sizeof(HID_ReportDescriptor);

//report descriptor touchscreen
const BYTE HID_ReportDescriptor2[] = {
0x05, 0x01, // USAGE_PAGE (Generic Desktop)
0x09, 0x02, // USAGE (Mouse)
0xa1, 0x01, // COLLECTION (Application)
0x09, 0x01, // USAGE (Pointer)
0xa1, 0x00, // COLLECTION (Physical)

0x05, 0x01, // USAGE PAGE (Generic Desktop)
0x09, 0x30, // USAGE (X)
0x09, 0x31, // USAGE (Y)
HID_LogicalMin   ( 0x000                        ),
HID_LogicalMaxS   ( 0x320                               ),  // max value 800px
HID_ReportSize   ( 16                           ),
HID_ReportCount  ( 2   ),
HID_Input                ( HID_Data | HID_Variable | HID_Absolute),
//0x81, 0x06, // INPUT (Data,Var,Relative)
0xc0, // END_COLLECTION
0xc0, // END_COLLECTION
};

I can't uss the relative values in the original descriptor therefore I will use absolute values. The maximum size of the display is 800px -> therefore one 16bit value for each length (height and width) will be enough.

Therefore I changed the usb report descriptor to this one. In USBlyzer I can see the values transmitted, but the mouse is always at the left top corner...

Here's my endpoint descriptor - I only changed the size to 32bit.

/* Endpoint, HID Interrupt In */
  USB_ENDPOINT_DESC_SIZE,            /* bLength */
  USB_ENDPOINT_DESCRIPTOR_TYPE,      /* bDescriptorType */
  USB_ENDPOINT_IN(2),                /* bEndpointAddress */
  USB_ENDPOINT_TYPE_INTERRUPT,       /* bmAttributes */
  WBVAL(0x0020),                      /* wMaxPacketSize */
  0x0A,          /* 8ms */          /* bInterval */

One small additional question: is it possible to add a feature report to the report descriptor of a mouse? If I only read, that it is not possible to add a output report to a mouse...

const WORD HID_ReportDescSize = sizeof(HID_ReportDescriptor);

//report descriptor touchscreen
const BYTE HID_ReportDescriptor2[] = {
0x05, 0x01, // USAGE_PAGE (Generic Desktop)
0x09, 0x02, // USAGE (Mouse)
0xa1, 0x01, // COLLECTION (Application)
0x09, 0x01, // USAGE (Pointer)
0xa1, 0x00, // COLLECTION (Physical)

0x05, 0x01, // USAGE PAGE (Generic Desktop)
0x09, 0x30, // USAGE (X)
0x09, 0x31, // USAGE (Y)
HID_LogicalMin   ( 0x000                        ),
HID_LogicalMaxS   ( 0x320                               ),  // max value 800px
HID_ReportSize   ( 16                           ),
HID_ReportCount  ( 2   ),
HID_Input                ( HID_Data | HID_Variable | HID_Absolute),
//0x81, 0x06, // INPUT (Data,Var,Relative)
0xc0, // END_COLLECTION

HID_ReportCount ( HID_FEATURE_REPORT_BYTES ),
HID_Usage ( 0x01 ),
HID_Feature ( HID_Data | HID_Variable | HID_Absolute ),

0xc0, // END_COLLECTION
};