REGISTER

Firmware development information is available from major OS and RTOS vendors:

Linux Distributions:

Check out the article: Embedded Development - QNX* or Linux*? from Intel® Software Network

1. Check with the operating system vendor for Intel architecture platform drivers.
2. If third party drivers are required, check with the vendor for Intel architecture driver support.
3. For users of embedded Windows and Linux operating systems, driver binaries for drivers implemented by Intel are available for Intel embedded platforms at the time of launch.
4. The Intel Software Installation Utility (INF) is available for Intel chipsets. The Intel® Chipset Software Installation Utility files inform the operating system how to properly configure the chipset for specific functionality such as AGP, USB, Core PCI, and ISA PnP services. In order to be able to install any chipset-related drivers (e.g. graphics, IDE, etc.), your operating system must first be able to recognize your chipset. Note: The Intel® Chipset Software Installation Utility only informs the operating system how to identify components by installing INF files. It does not install any drivers for your system.
5. If in-house development is required, check with the OS vendor to determine the availability of development tools for Intel architecture. Check the Intel® Software Products for information about Intel tools.

You can choose from third-party firmware such as BIOS or the Extensible Firmware Interface (EFI). Alternatively, you may choose to use a boot loader for fast system initialization and small footprint to meet the needs of many embedded solutions.

Choose BIOS if your design will support multiple standard interfaces and expansion slots or host mainstream operating systems with a broad set of pre-OS features, which are ready to run multiple applications.

Choose EFI for a C language based firmware alternative to traditional BIOS that emphasizes ease of use and ubiquity across platforms. EFI defines a software interface layer between the operating system and the platform firmware.

Choose a boot loader for minimal or specialized firmware stacks where requirements include optimizations for speed, size, or specific system requirements, with minimal upgrade or expansion capabilities.

A basic input/output system (BIOS) initializes the hardware and boots it to a point where the operating system can load, and it also abstracts the operating system from the hardware. Access to the hardware is made through specific BIOS commands.

A fully featured BIOS solution is engineered to perform complete discovery and initialization algorithms. The BIOS is used in designs that will support multiple use cases for the platform, customizable services, multiple boot paths, multiple operating systems, or rich feature sets. For some embedded designs, a traditional BIOS or a fully featured UEFI firmware stack used by typical notebook designs may be appropriate.

Often, the design goals for embedded systems include faster boot times, smaller footprints, specialized functionality and lower cost. For these reasons, many embedded system designs would be encumbered by adopting the full-featured BIOS and therefore designers seek a more optimized solution.

Intel promotes Extensible Firmware Interface (EFI) as a C language based modular firmware alternative to traditional BIOS.

The EFI specification defines a model for the interface between operating systems and platform firmware. The interface consists of data tables that contain platform-related information, plus boot and runtime service calls that are available to the operating system and its loader. Together, these provide a standard environment for booting an operating system and running pre-boot applications.

Figure 1 shows the location of the EFI layer in the platform architecture.

Figure 1. EFI Layer Location

In 2005 a new industry organization, known as the Unified EFI Forum (UEFI), was formed to manage and promote the EFI specification, and EFI was renamed to UEFI. Visit the UEFI Web site for more information.

Embedded devices have unique requirements which challenge “one size fits all” PC BIOS solutions. The UEFI frameworks can provide flexible solutions that can be differentiated for embedded production solutions.

Details about the EFI specification, writing EFI drivers, and how to use the EFI Sample Implementation and EFI Application Toolkit are available on Intel’s EFI Web page.

The Framework is Intel's recommended implementation of the EFI Specification for platforms based on all members of the Intel® architecture family. The Framework is a set of architectural interfaces, implemented in C, that has been designed to enable the BIOS industry and Intel customers to accelerate the evolution of platform designs.

Participating vendors offer products and services based on the Framework, for both Intel and non-Intel silicon. Information on the Framework and specification is available here.

Download this Intel Developer Forum presentation to learn the benefits of EFI and its application to embedded computing: Intel Framework Customization for Optimized Platform Boot Initialization.

Participating Framework vendors:

Tiancore provides an UEFI Development Kit.

A boot loader is a good choice for situations where there is no user customization anticipated, and where the platform only requires basic initialization support. In cases where the “do it yourself” model is preferred, royalty payment for initialization code is not acceptable, and fast booting or small footprint is required, a custom boot loader may be the optimum choice.

Get the Intel® Boot Loader Development Kit (Intel® BLDK) for your boot loader development needs.