return STATUS_SUCCESS; }
A hardware engineer, Alex, had designed a new touch I2C device that was compact, efficient, and highly responsive. However, when it came to integrating the device with Windows, Alex encountered a significant challenge. The device used the I2C protocol to communicate with the computer, but Windows didn't have a built-in driver to support this device.
// HID report handling NTSTATUS TouchI2C_ProcessHidReport(WDFDEVICE device, PVOID reportBuffer, ULONG reportLength) { // Implement HID report processing } kmdf hid minidriver for touch i2c device download
// HID descriptor VOID TouchI2C_GetHidDescriptor(WDFDEVICE device, PVOID buffer, ULONG bufferLength) { // Define the HID descriptor UCHAR hidDescriptor[] = { // Report descriptor 0x06, 0x00, 0x00, // Usage Page (Generic Desktop) 0x15, 0x00, 0x00, // Logical Minimum 0x26, 0xFF, 0x00, // Logical Maximum 0x35, 0x00, 0x00, // Physical Minimum 0x45, 0x00, 0x00, // Physical Maximum 0x75, 0x08, // Report Size 0x95, 0x01, // Report Count 0x85, 0x01, // Report ID 0x05, 0x08, // Usage (Multi-touch) 0x19, 0x01, // Usage Minimum 0x29, 0x01, // Usage Maximum 0x25, 0x01, // Logical Minimum 0x35, 0x01, // Physical Minimum 0x45, 0x01, // Physical Maximum 0x75, 0x08, // Report Size 0x95, 0x01, // Report Count 0xB1, 0x02, // Feature };
#include <wdf.h>
Alex began by setting up the development environment, installing the Windows Driver Kit (WDK) and the Windows SDK. They then created a new KMDF driver project using the WDF (Windows Driver Framework) template.
The driver was then submitted to Microsoft for certification, and after a thorough review, it was approved and added to the Windows Update catalog. return STATUS_SUCCESS; } A hardware engineer, Alex, had
The story of the KMDF HID minidriver serves as an example of how custom drivers can be developed to enable innovative hardware devices to work with Windows operating systems.