User`s guide

System Initialization and Acceptance Testing (Normal Operation)

4.1 Basic Initialization Flow

Following a successful diagnostic countdown (see Example 4–2), the console

may prompt you for a default boot device.

Example 4–2 Successful Diagnostic Countdown

KA52-A VX.X, VMB 2.14

Performing normal system tests.

72..71..70..69..68..67..66..65..64..63..62..61..60..59..58..57..

56..55..54..53..52..51..50..49..48..47..46..45..44..43..42..41..

40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..

24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..

08..07..06..05..04..03..

Tests completed.

>>>

4.2 Power-On Self-Tests (POST)

Power-on self-tests provide core testing of the system kernel comprised of the

CPU and memory. Certain registers are ﬂushed, and data structures are set

up to initialize and set the system to a known state for the operating system.

4.2.1 Power-Up Tests for Kernel

In a nonmanufacturing environment where the intended console device is the

serial line unit (SLU), the console program performs the following actions at

power-up:

1. Checks for POK.

2. Establishes SLU as console device.

3. Prints banner message.

The banner message contains the processor name, the version of the

ﬁrmware, and the version of VMB. The letter code in the ﬁrmware version

indicates if the ﬁrmware is pre-ﬁeld test, ﬁeld test, or ofﬁcial release.

The ﬁrst digit indicates the major release number and the trailing digit

indicates the minor release number (Figure 4–1).

System Initialization and Acceptance Testing (Normal Operation) 4–3