Table of Contents
Advertisement
MOTLoad Firmware
CR/CSR space for a board in the 5th slot will start at 0x0028.0000
CR/CSR space for a board in the 6th slot will start at 0x0030.0000
CR/CSR space for a board in the 7th slot will start at 0x0038.0000
CR/CSR space for a board in the 8th slot will start at 0x0040.0000
CR/CSR space for a board in the 9th slot will start at 0x0048.0000
CR/CSR space for a board in the ath slot will start at 0x0050.0000
CR/CSR space for a board in the bth slot will start at 0x0058.0000
CR/CSR space for a board in the cth slot will start at 0x0060.0000
For further details on CR/CSR space, please refer to the VME64 Specification, listed in
Appendix
C, Related
Documentation.
The MVME5500 uses a Tundra Universe II for its VME bridge. The offsets of the mailboxes in the
Universe II are defined in the Universe II User Manual, listed in
Appendix C, Related
Documentation, but are noted here for reference:
Mailbox 0 is at offset 7f348 in the CR/CSR space
Mailbox 1 is at offset 7f34C in the CR/CSR space
Mailbox 2 is at offset 7f350 in the CR/CSR space
Mailbox 3 is at offset 7f354 in the CR/CSR space
The selection of the mailbox used by remote start on an individual MVME5500 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
chapter in the MOTLoad Firmware Package User's Manual for remote start GEV definitions.
The MVME5500's IBCA needs to be mapped appropriately through the master's VMEbus
bridge. For example, to use remote start using mailbox 0 on an MVME5500 installed in slot 5,
the master would need a mapping to support reads and writes of address 0x002ff348 in VME
CR/CSR space (0x280000 + 0x7f348).
80
MVME55006E Single Board Computer Installation and Use (6806800A37H)
Advertisement
Table of Contents
