Open Firmware

Short description: Standard for computer bootstrap code

Not to be confused with open-source firmware.

Open FirmwareStatus| Withdrawn

|

First published| 28 October 1994
Domain| Boot firmware
OpenBoot screenshot

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,[1] IBM and ARM.[citation needed]

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.

## Contents

* 1 History
* 2 Features
* 3 Implementations and licensing
* 4 See also
* 5 References
* 6 External links

## 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.[2]

## Features

Open Firmware defines a standard way to describe the hardware configuration of a system, called the device tree.[3] 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 I2C devices like temperature sensors for hardware monitoring,[4]: §5.1 whereas the alternative solution of performing a blind probe of the I2C 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.[4]: §5.2

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[5]

## 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.[citation needed]

## See also

* Software:Coreboot
* Power-on self-test - Process performed by firmware or software routines

## References

1. ↑ "Apple Wiki - Open Firmware". https://apple.fandom.com/wiki/Open_Firmware.
2. ↑ IEEE Standard for Boot (Initialization Configuration) Firmware: Core Requirements and Practices. October 28, 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. https://books.google.com/books?id=r_cecYD4AKkC&pg=PA107.
4. ↑ 4.0 4.1 Constantine A. Murenin (2010-05-21). "5.1. Open Firmware and I2C". 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)". https://docs.oracle.com/cd/E19088-01/250.srvr/805-3389-11/6j37qsqsj/index.html.

## External links

*   * 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

IEEE standards

Current|

* 488
* 730
* 754
* Revision
* 854
* 828
* 829
* 896
* 1003
* 1014
* 1016
* 1076
* 1149.1
* 1154
* 1164
* 1275
* 1278
* 1284
* 1355
* 1394
* 1451
* 1497
* 1516
* 1541
* 1547
* 1584
* 1588
* 1596
* 1603
* 1613
* 1666
* 1667
* 1675
* 1685
* 1722
* 1733
* 1800
* 1801
* 1815
* 1850
* 1900
* 1901
* 1902
* 1904
* 1905
* 2030
* 2050
* 11073
* 12207
* 14764
* 16085
* 16326
* 29148
* 42010

802 series|

| 802.1|

* D
* p
* Q
* Qat
* Qay
* w
* X
* ab
* ad
* AE
* ag
* ah
* ak
* aq
* AS
* ax
* az
* BA

|

802.3|

* -1983
* a
* b
* d
* e
* i
* j
* u
* x
* y
* z
* ab
* ac
* ad
* ae
* af
* ah
* ak
* an
* aq
* at
* av
* az
* ba
* bt
* by

802.11|

* legacy mode
* a
* b
* c
* d
* e
* f
* g
* h
* i
* j
* k
* n
* p
* r
* s
* u
* v
* w
* y
* ac
* ad
* af
* ah
* ai
* ax
* ay

* .2
* .4
* .5
* .6
* .7
* .8
* .9
* .10
* .12
* .14
* .15
* .1
* .4
* .4a
* .6
* .16
* Original · d · e
* .17
* .18
* .20
* .21
* .22

Proposed|

* P1363
* P1619
* P1699
* P1823
* P1906.1

Superseded|

* 754-1985
* 830
* 1219
* 1233
* 1362
* 1364
* 1471

See also
IEEE Standards Association
Category:IEEE standards

Template:Firmware and booting

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Open Firmware. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Open_Firmware&oldid=3977074"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template