5. Firmware code stack is initially in BBRAM in PDH, retrieved 4 bytes at a time, through PDH and
DMD buses.
5. PAL code configures all processors.
5. SAL code configures all platform ICH10 chips, including shared memory and all responding
I/O devices.
5. Firmware code and stack are relocated to shared memory, after all x4 DIMM ranks in shared
memory are configured and tested.
5. UEFI Shell is launched from shared memory, and cache lines are retrieved 128 bytes at a time
by MEMC in ICH10.
6. OS loader is launched using the UEFI device driver.
6. OS boots and starts its own device drivers.
6. OS can use runtime PAL and SAL calls, and ACPI features (these abstraction layers enable
platform independence).
Troubleshooting the firmware
The server has the following sets of firmware installed:
•
System firmware
•
iLO 3 firmware
•
I/O card firmware
Fibre Channel cards
◦
◦
SAS HBA cards
◦
LAN cards
•
SAS controller firmware
•
SAS HDD firmware
•
LOM firmware
System firmware and iLO 3 firmware must be from the same release. Independent updates are not
supported. Details about a specific release are available in the associated Release Notes.
Firmware updates are available from the HP website at
under "Support and
Drivers".
Identifying and troubleshooting firmware issues
Erratic system operation, or the fact that the server might not boot successfully to the UEFI Boot
Manager or to the UEFI Shell, are symptoms of possible firmware issues.
Firmware issues are relatively rare, and, therefore, look for other causes first.
If you are attempting to resolve a firmware issue, the possible failure areas are as follows:
•
Unsupported firmware installation
•
Corrupt firmware installation
To troubleshoot firmware issues:
1.
Verify that all system and iLO firmware components are from the same release (use the iLO 3
sr
command).
2.
Reinstall all firmware.
IMPORTANT:
If firmware reinstallation does not resolve the issue, processor or system board
replacement might be required.
HP Confidential
Troubleshooting the firmware
89