Misplaced Pages

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Open Firmware" – news · newspapers · books · scholar · JSTOR (July 2011) (Learn how and when to remove this 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 multiple vendors including Sun, Apple, IBM and ARM.

Open Firmware allows a system to load platform-independent drivers directly from a PCI device, improving compatibility.

Open Firmware may be accessed through its command line interface, which uses the Forth programming language.

History

Open Firmware was described by IEEE standard as IEEE 1275-1994. This standard was not reaffirmed by the Open Firmware Working Group (OFWG) since 1998, and was therefore officially withdrawn by IEEE in May 2005.

Features

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 IC devices like temperature sensors for hardware monitoring, whereas the alternative solution of performing a blind probe of the IC 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 instruction set architecture. A PCI card may include a program, compiled to FCode, which runs on any Open Firmware system. In this way, it can provide 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

Implementations and licensing

Several commercial implementations of Open Firmware have been released to the Open Source community since 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.

See also

• Coreboot – Open-source computer firmware
• Power-on self-test – Process performed by firmware or software routines
• PowerPC Reference Platform – Computer system architecture
• UEFI – Technical specification for firmware architecture

References

1. "Apple Wiki - Open Firmware".
2. IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices. 28 October 1994. pp. 1–262. doi:10.1109/IEEESTD.1994.89427. ISBN 978-0-7381-1194-0.
3. Mauro, Jim (2001). Solaris Internals: Core Kernel Components. Prentice-Hall Professional. p. 107. ISBN 9780130224965.
4. ^ Constantine A. Murenin (21 May 2010). "5.1. Open Firmware and IC". OpenBSD Hardware Sensors – Environmental Monitoring and Fan Control (MMath thesis). University of Waterloo: UWSpace. hdl:10012/5234. Document ID: ab71498b6b1a60ff817b29d56997a418.
5. "Sun Enterprise 250 Server Owner's Guide > Chapter 12 Diagnostics and Troubleshooting > About OpenBoot Diagnostics (OBDiag)". Archived from the original on 7 March 2021.

External links

• Official website at the Wayback Machine (archived 2007-06-30)
• Sun's OpenBoot 2.x command reference manual (Revision A, November 1995)
• Sun's SPARC OpenBoot 4.x command reference manual
• The last IEEE 1275 text
• Boot Process on IBM POWER (via Internet Archive)
• OFW FAQ on OLPC Wiki
• Aurora SPARC Linux OBP reference guide (via Internet Archive)
• Quick Reference

v t e Firmware and booting
Processes	Windows 9x NT Linux Android
Booting firmware	Types Proprietary firmware Open-source firmware Custom firmware Interfaces UEFI BIOS Video BIOS Open Firmware ACPI MultiProcessor Specification APM Legacy Plug and Play AlphaBIOS SRM SFI Implementations SeaBIOS Award BIOS American Megatrends AMIBIOS AMI Aptio InsydeH2O Phoenix SecureCore UEFI TianoCore EDK II OpenBIOS Coreboot Libreboot LinuxBoot Kickstart Run-Time Abstraction Services
Hybrid firmware bootloader	Common Firmware Environment Das U-Boot ARCS
Bootloaders	Bootloader unlocking Comparison of bootloaders Implementations Acronis OS Selector Barebox BootManager BootX (Apple) BootX (Linux) GNU GRUB iBoot systemd-boot loadlin NTLDR OpeniBoot RedBoot rEFInd rEFIt SYSLINUX Windows Boot Manager xOSL Yaboot Plop Boot Manager MILO
Partition layouts	GUID Partition Table Master boot record Apple Partition Map
Partitions	EFI system partition BIOS boot partition /boot/
Utilities	Software flashrom fwupd UEFITool Odin Heimdall Hardware Bus Pirate Raspberry Pi ft2232
Network boot	Preboot Execution Environment gPXE iPXE NetBoot Remote Initial Program Load Wake-on-LAN Wake-on-ring
ROM variants	ROM PROM EPROM EEPROM
Related	Boot ROM ROM hacking ROM image Execute in place Devicetree Fastboot Instant-on Power-on self-test EDL mode

• Firmware
• Sun Microsystems software
• IEEE standards
• Macintosh firmware
• BIOS
• Open-source hardware
• MacOS
• Forth programming language family