Oracle Vacuum Cleaner CPU-56T User Manual

The OpenBoot firmware consists of the Common Operations and Reset Environment
(CORE), the power−on selftest (POST), the OpenBoot Diagnostics (OBDIAG), and the
OpenBoot itself as well as support for the VxWorks real−time operating system (RTOS).

The OpenBoot firmware is subject to changes. For the newest version and how to
upgrade, refer to the SMART service accessible via the Force Computers World Wide Web
site (www.forcecomputers.com).

Note:

a

The appearance of the on−screen output shown in the examples can differ from

the appearance of the output on your monitor according to your device tree (CPU
architecture).

For more information on the OpenBoot firmware, see the

a

OpenBoot 4.x Manual Set.

CORE is responsible for setting up proper environments for booting purposes. It first
initializes the system to a status where different firmware can be loaded from.

a

CORE automatically transfers control to its clients (such as OpenBoot, VxWorks, Chorus
Booter...) during power up.

a

Furthermore, it provides a unified interface for using public CORE functions. Thus, the
CORE unifies system initialization and minimizes modifications within the upper level
firmware.

a

The following figure gives a system overview of which systems are initialized by CORE.

Basic System Initialization

CORE with bPOST

FVM

Basic

Loader

BSP

cPOST

Solaris

Basic OS

VxWorks

RTOS

Running from

PROM

Running from

Memory

Operating

System

Figure 24:

 OpenBoot CORE Overview