Firmware Checkpoints
Firmware uses progress codes (checkpoints) in the range of E1xx to EFFF. These
checkpoints occur during system startup and can be useful in diagnosing certain
problems. Service processor checkpoints are listed in “Service Processor Checkpoints”
on page 86.
If you replace FRUs or perform an action, and the problem is still unresolved, go to
“MAP 1540: Minimum Configuration” on page 63 unless otherwise indicated in the
tables.
If you replace FRUs or perform an action, and the problem is corrected, go to ″MAP
0410: Repair Checkout″ in the
RS/6000
Eserver
pSeries Diagnostic Information for
Multiple Bus Systems
.
Table 2. Firmware Checkpoints.
Checkpoint Description Action/ Possible Failing FRU
E100 Reserved/Unused See “Unresolved Checkpoint Problems”
on page 85.
E101 Video enabled, extended memory test See “Unresolved Checkpoint Problems”
on page 85.
E102 Firmware restart See “Unresolved Checkpoint Problems”
on page 85.
E103 Set memory refresh (composite image) See “Unresolved Checkpoint Problems”
on page 85.
E104 Set memory refresh (recovery block) See “Unresolved Checkpoint Problems”
on page 85.
E105 Transfer control to operating system
(normal boot).
See “Boot Problems/Concerns” on
page 110.
E108 Run recovery block base memory (test
2K), set stack
See “Unresolved Checkpoint Problems”
on page 85.
E109 Copy CRC verification code to RAM See “Unresolved Checkpoint Problems”
on page 85.
E10A Turn on cache See “Unresolved Checkpoint Problems”
on page 85.
E10B Flush cache See “Unresolved Checkpoint Problems”
on page 85.
E10C Jump to CRC verification code in RAM See “Unresolved Checkpoint Problems”
on page 85.
E10D Compute composite image CRC See “Unresolved Checkpoint Problems”
on page 85.
E10E Jump back to ROM See “Unresolved Checkpoint Problems”
on page 85.
E10F Transfer control to open firmware See “Unresolved Checkpoint Problems”
on page 85.
E110 Turn off cache, check if composite
image CRC is valid
See “Unresolved Checkpoint Problems”
on page 85.
92 Service Guide
To Next Page
Loading...
