Hardware SDKs

Definition

A hardware SDK is a collection of software components that exposes the capabilities of a physical device to software applications. These components include device drivers, libraries, documentation and tools for interacting with device functions. Depending on the device, a hardware SDK addresses application programmers working on a host computer, embedded developers writing firmware for the device itself, or both.

Kits of this kind appear under various names, including device SDKs, embedded SDKs, board support packages and toolkits. The term "development kit" is also used for the physical evaluation boards that manufacturers sell together with the software.

Historical development

Hardware SDKs originated with early computing devices, when manufacturers provided toolkits that enabled software development for specific hardware, including assemblers, monitors and reference documentation. Microcontroller vendors developed compilers, debuggers and peripheral libraries for their chips, and embedded operating systems added hardware abstraction layers that separate application code from a particular board.

As devices became more complex, SDKs evolved to cover advanced capabilities such as programming graphics processing units (GPUs) for general-purpose computation, sensor fusion and interaction in virtual reality. NVIDIA introduced the CUDA platform for general-purpose GPU computing in 2007; its development kit is distributed as the CUDA Toolkit. Virtual reality headsets were initially programmed through manufacturer-specific SDKs, such as the Oculus SDK, whose successors are distributed as the Meta XR SDKs. The Khronos Group published the OpenXR standard in 2019 as a vendor-neutral API for virtual and augmented reality devices, and many headset manufacturers now provide OpenXR runtimes alongside their own kits.

Components

Hardware SDKs typically include the following components.

1. Device drivers. Drivers enable communication between the operating system or application and the hardware.
2. Low-level libraries. Libraries provide access to hardware functions, such as peripheral registers, sensor data or accelerated computation, often behind a hardware abstraction layer.
3. Toolchains. Compilers, linkers and related tools translate source code for the target processor; embedded development commonly relies on cross-compilation from a host computer.
4. Development tools. Tools support debugging, profiling, flashing and testing, including debug probes, simulators and emulators.
5. Board support and configuration. Board support packages and configuration files, such as device trees, describe a specific board to the operating system.
6. Documentation. Documentation describes device capabilities, electrical and timing constraints and usage patterns.

Function and purpose

Hardware SDKs serve several functions.

• Device access. They provide programmatic access to hardware features.
• Performance optimization. They support efficient use of hardware resources, such as parallel processors, memory and power.
• Integration. They enable software to interact with sensors, actuators and embedded systems.
• Portability. Abstraction layers allow application code to run on different boards or devices with limited changes.

Access provided by a hardware SDK does not by itself establish any safety property of a machine or device. Protective functions of drives and controllers, such as overcurrent or thermal shutdown, protect the equipment; functional safety requires separate design, assessment and documentation.

Applications

Hardware SDKs are used in robotics, IoT, virtual and augmented reality, industrial automation, machine vision and high-performance computing. Examples include the CUDA Toolkit for NVIDIA GPUs, the Meta XR SDKs and OpenXR runtimes for headsets, the Android Native Development Kit (NDK), which allows parts of Android applications to be written in C and C++ with direct access to native libraries, and the device SDKs of IoT platforms that connect sensors and gateways to cloud services. In industrial automation, manufacturers of drives, cameras and controllers supply SDKs for integrating their devices into control and vision software.

Comparison with other SDK types

Hardware SDKs differ from developer SDKs in that their counterpart is a physical device rather than a remote service, and from platform SDKs in that they expose a device rather than extend a software platform. The boundaries overlap where devices are connected: an IoT device SDK combines device access on the device with a developer SDK for the cloud service to which the device reports. The context card Layers of a hardware SDK outlines the layers from application to silicon.

Conclusion

Hardware SDKs are essential for enabling software to interact with physical devices. They provide the tools necessary for accessing hardware capabilities and developing applications that rely on device functionality.