Device Drivers are essential for any IoT device. This section outlines how to write device drivers, how to driver signing works in Windows IoT Enterprise (this is different than traditional client signing), and how to add device drivers to images.
How to Write Device Drivers
Windows contains built-in drivers for many device types. If there is a built-in driver for your device type, you do not need to write your own driver. Your device can use the built-in driver. However if you need to write a device driver for your device, please leverage the programming reference for Windows Driver Kit (WDK).
Traditional Client Signing
For typical traditional client signing, if you are unfamiliar with the device and driver installation process, we recommend that you start by reviewing Roadmap for Device and Driver Installation. You may also want to read Overview of Device and Driver Installation for a high-level overview of this process and its components.
Follow this article to learn how attestation signing works for a kernel driver for public release.
When a driver receives attestation signing, it is not Windows Certified. An attestation signature from Microsoft indicates that the driver can be trusted by Windows, but because the driver has not been tested in HLK Studio, there are no assurances made around compatibility, functionality, etc.
How to Add Device Drivers to Images
With Windows IoT Enterprise, you can add device drivers to a Windows image before, during, or after you deploy the image. When planning how to add drivers to your Windows deployment, it's important to understand how driver folders are added to the image, how driver ranking affects deployment, and the digital signature requirements for drivers. To understand more about how to add drivers, check out the following article, Device Drivers.