Boot Images - Emerson MVME4100 Installation And Use Manual

MOTLoad Firmware
For further details on CR/CSR space, please refer to the VME64 Specification, listed in
B, Related Documentation.
The MVME4100 uses a TSi148 for its PCI/X-to-VME bus bridge. The offsets of the mailboxes in
the TSi148 are defined in the TSi148 VMEBus PCI/X-to-VME User Manual, listed in
Related Documentation, but are noted here for reference:
Mailbox 0 is at offset 7f610 in the CR/CSR space
Mailbox 1 is at offset 7f614 in the CR/CSR space
Mailbox 2 is at offset 7f618 in the CR/CSR space
Mailbox 3 is at offset 7f61C in the CR/CSR space
The selection of the mailbox used by remote start on an individual MVME4100 is determined
by the setting of a global environment variable (GEV). The default mailbox is zero. Another GEV
controls whether remote start is enabled (default) or disabled. Refer to the Remote Start
appendix in the MOTLoad Firmware Package User's Manual for remote start GEV definitions.
The MVME4100's IBCA needs to be mapped appropriately through the master's VMEbus
bridge. For example, to use remote start using mailbox 0 on an MVME4100 installed in slot 5,
the master would need a mapping to support reads and writes of address 0x002ff610 in VME
CR/CSR space (0x280000 + 0x7f610).
6.7

Boot Images

Valid boot images whether POST, USER, or Alternate MOTLoad, are located on 1 MB boundaries
within the upper 8 MB of flash. The image may exceed 1 MB in size. An image is determined
valid through the presence of two "valid image keys" and other sanity checks. A valid boot
image begins with a structure as defined in the following table:
Name
UserDefined
ImageKey 1
ImageKey 2
ImageChecksum
ImageSize
ImageName
120
Type Size
unsigned integer 8
unsigned integer 1
unsigned integer 1
unsigned integer 1
unsigned integer 1
unsigned character 20
MVME4100 Single Board Computer Installation and Use (6806800H18D)
Notes
User defined
0x414c5420
0x424f4f54
Image checksum
Must be a multiple of 4
User defined
Appendix
Appendix B,