Table 35, Methodology for data input to memory – Dell R510 User Manual
Page 78
Dell
78
PowerEdge R510 Technical Guide
Table 35. Methodology for Data Input to Memory
How is data input to this memory?
Planar
System BIOS SPI Flash Loading flash memory requires a vendor-provided firmware file and loader program which is
executed by booting up the system from a floppy or OS-based executable containing the
firmware file and the loader. System loaded with arbitrary data in firmware memory will not
operate.
LOM Configuration
Data
Loading flash memory requires a vendor-provided firmware file and loader program which is
executed by booting the system from a floppy or OS-based executable containing the
firmware file and the loader. LOMs loaded with arbitrary data in firmware memory will not
operate.
iDRAC6 Controller
ROM
N/A
iDRAC6 controller
RAM
iDRAC embedded system
System CPLD
Loading flash memory requires a vendor-provided firmware file and loader program which is
executed by booting the system from a floppy or OS-based executable (currently only DRMK
utility support) containing the firmware file and the loader. A system loaded with arbitrary
data in CPLD memory will not operate.
System CPLD
Not used
iDRAC6 Express
Internal Flash
iDRAC OS: Loading flash memory requires a vendor-provided firmware file and loader program
which is executed by booting the system from a floppy or OS-based executable containing the
firmware file and the loader. System loaded without a good iDRAC firmware image yields a
non-functional iDRAC.
Managed Services Repository: Various partitions are loaded via vendor-provided firmware file
and loader program just like iDRAC OS.
System RAM
System OS
TPM ID EEPROM (Plug
in module only)
Factory load only
TPM Binding EEPROM
(on China planar
only)
BIOS only
iDRAC6 SDRAM
Embedded iDRAC OS for 108MB and 8MB for VGA frame buffer
iDRAC6 FRU
Factory and iDRAC embedded OS
iDRAC6 Boot Block
Flash
Loading flash memory requires a vendor-provided firmware file and loader program which is
executed by booting the system from a floppy or OS-based executable or out-of-band
firmware updates across the management network. Bad content makes the iDRAC inoperable
and is unrecoverable in the customer environment. The lifecycle log is automatically updated
by the iDRAC as various system component firmware, hardware, and software versions are
changed.
Trusted Platform
Module
Using TPM-enabled operating systems