This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
Open Firmware is a standard defining the interfaces of a computer firmware system, formerly endorsed by the Institute of Electrical and Electronics Engineers (IEEE). It originated at Sun Microsystems, where it was known as OpenBoot, and has been used by vendors including Sun, Apple, IBM and ARM. Open Firmware allows the system to load platform-independent drivers directly from a PCI device, improving compatibility.
Open Firmware is described by IEEE standard IEEE 1275-1994, which was not reaffirmed by the Open Firmware Working Group (OFWG) since 1998 and has therefore been officially withdrawn by IEEE.
Several commercial implementations of Open Firmware have been released to the Open Source community in 2006, including Sun OpenBoot, Firmworks OpenFirmware and Codegen SmartFirmware. The source code is available from the OpenBIOS project. Sun's implementation is available under a BSD license.
Open Firmware defines a standard way to describe the hardware configuration of a system, called the device tree. This helps the operating system to better understand the configuration of the host computer, relying less on user configuration and hardware polling. For example, Open Firmware is essential for reliably identifying slave I²C devices like temperature sensors for hardware monitoring,: whereas the alternative solution of performing a blind probe of the I²C bus, as has to be done by software like lm_sensors on generic hardware, is known to result in serious hardware issues under certain circumstances.:
Open Firmware Forth Code may be compiled into FCode, a bytecode which is independent of computer architecture details such as the instruction set and memory hierarchy. A PCI card may include a program, compiled to FCode, which runs on any Open Firmware system. In this way, it can provide platform-independent boot-time diagnostics, configuration code, and device drivers. FCode is also very compact, so that a disk driver may require only one or two kilobytes. Therefore, many of the same I/O cards can be used on Sun systems and Macintoshes that used Open Firmware. FCode implements ANS Forth and a subset of the Open Firmware library.
Being based upon an interactive programming language, Open Firmware can be used to efficiently test and bring up new hardware. It allows drivers to be written and tested interactively. Operational video and mouse drivers are the only prerequisite for a graphical interface suitable for end-user diagnostics. Apple shipped such a diagnostic "operating system" in many Power Macintoshes. Sun also shipped an FCode-based diagnostic tool suite called OpenBoot Diagnostics (OBDiag) used by customer service support and hardware manufacturing teams
This section contains instructions, advice, or how-to content. (July 2011)
On Sun SPARC systems, the Open Firmware interface is displayed on the console terminal before the bootstrapping of the system software. If a keyboard is connected, the main video display will be used as the console terminal and Open Firmware can be re-entered at any time by pressing Stop+A (L1+A) on the keyboard. If no keyboard is connected, then the first serial line on the system is usually used as the console and Open Firmware is re-entered by sending a "Break" on the serial line. While the system software is running, various Open Firmware settings can be read or written using the
On a PowerPC-based Macintosh, the Open Firmware interface can be accessed by pressing the keys ⌘ Cmd+⌥ Option+O+F at startup (⊞ Win+Alt+O+F if using standard PC USB keyboard). Intel-based Macintoshes do not use Open Firmware; they use Extensible Firmware Interface. Also, early versions (before the PowerBook 3400) connect Open Firmware's input and output to the Modem port by default. This functionality is generally only used by developers or troubleshooting I.T. personnel; for common users, the Mac OS X operating system provides a high level graphical user interface to change commonly used Open Firmware settings. For instance, it is possible to specify the boot disk or partition without directly using the Open Firmware interface, but with some limitations (e.g. it is not possible to select boot from USB mass-storage devices, but Open Firmware allows iMac to boot using
boot ud:,\\:tbxi command). Other Open Firmware settings can be changed using the
nvram command while the system software is running.
On Pegasos, the interface is accessed by pressing Esc at startup.
On IBM Power Systems, Open Firmware ("ok" prompt) can be accessed through the SMS Boot Menu. SMS Boot Menu can be accessed by pressing 1 or F1 during the boot sequence, after hardware checking, and just before the OS boot.
On the OLPC XO-1 laptop, Open Firmware access requires a developer key, that can be obtained after registration with OLPC. After installing the key, upon each power-on, the boot countdown can be interrupted with Esc (the upper left key) to get to the Forth prompt.
- Building Open Firmware for ARM
- "OpenBIOS". Retrieved 10 May 2012.
- Mauro, Jim (2001). Solaris Internals: Core Kernel Components. Prentice-Hall Professional. p. 107. ISBN 9780130224965. Retrieved 16 May 2020.
- Constantine A. Murenin (21 May 2010). "5.1. Open Firmware and I²C". OpenBSD Hardware Sensors — Environmental Monitoring and Fan Control (MMath thesis). University of Waterloo: UWSpace. hdl:10012/5234. Document ID: ab71498b6b1a60ﬀ817b29d56997a418.
- Apple's Transition from Open Firmware to Extensible Firmware Interface, mactech, 2007.
- OPEN FIRMWARE HOME PAGE (via Internet Archive)
- Sun's SPARC OBP documentation
- The last IEEE 1275 text
- Firmworks OpenFirmware source code
- Codegen SmartFirmware source code
- Boot Process on IBM POWER (via Internet Archive)
- OFW FAQ on OLPC Wiki
- Aurora SPARC Linux OBP reference guide (via Internet Archive)
- Quick Reference
- TinyBoot aka Tiny Open Firmware: an embeddable OpenFirmware-like system for small CPUs (via Internet Archive)