HP Integrity rx2800 rx2800 i2 User Service Guide - Page 94

Troubleshooting the firmware, Identifying and troubleshooting firmware problems, Updates

Page 94 highlights

5) Firmware code stack is initially in BBRAM in PDH, retrieved 4 byes at a time, through PDH and DMD buses. 5) PAL code configures all CPUs. 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 may use runtime PAL and SAL calls, and APCI features (these abstraction layers allow platform independence). Troubleshooting the firmware The system has three sets of firmware installed: • System firmware • iLO 3 firmware • I/O card firmware All firmware (SFW, iLO 3, etc.) 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 http://www.hp.com under "Support and Drivers". Identifying and troubleshooting firmware problems Erratic system operation, or the fact that the server may not boot successfully to the UEFI Boot Manager or to the UEFI Shell, are symptoms of possible firmware problems. It should be noted that problems due to firmware are relatively rare, and you should look for other problem causes first. If you are dealing with a firmware problem, the probable failure areas are as follows: • Unsupported firmware installation • Corrupt firmware installation To troubleshoot firmware problems: 1. Verify that all system and iLO firmware components are from the same release (use the iLO 3 sr command). 2. Reinstall all firmware. Updates System firmware updates are available from the HP Business Support Center at: http://www.hp.com/go/bizsupport. To update your firmware, follow these steps: 1. Start up the system and go to the UEFI command prompt. 2. To determine the current firmware version, run the UEFI info fw command at the UEFI Shell prompt. 94 Troubleshooting

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151

5) Firmware code stack is initially in BBRAM in PDH, retrieved 4 byes at a time, through PDH and
DMD buses.
5) PAL code configures all CPUs.
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 may use runtime PAL and SAL calls, and APCI features (these abstraction layers allow
platform independence).
Troubleshooting the firmware
The system has three sets of firmware installed:
System firmware
iLO 3 firmware
I/O card firmware
All firmware (SFW, iLO 3, etc.) 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
under “Support and Drivers”.
Identifying and troubleshooting firmware problems
Erratic system operation, or the fact that the server may not boot successfully to the UEFI Boot
Manager or to the UEFI Shell, are symptoms of possible firmware problems.
It should be noted that problems due to firmware are relatively rare, and you should look for other
problem causes first.
If you are dealing with a firmware problem, the probable failure areas are as follows:
Unsupported firmware installation
Corrupt firmware installation
To troubleshoot firmware problems:
1.
Verify that all system and iLO firmware components are from the same release (use the iLO 3
sr
command).
2.
Reinstall all firmware.
Updates
System firmware updates are available from the HP Business Support Center at:
.
To update your firmware, follow these steps:
1.
Start up the system and go to the UEFI command prompt.
2.
To determine the current firmware version, run the UEFI
info fw
command at the UEFI Shell
prompt.
94
Troubleshooting