MVME5100 Single Board Computer Programmer's Reference Guide

Introduction
CVMEbus Mapping Example
C
This appendix contains an application note on establishing addressability
on the VMEbus using the MVME5100 and MVME2700 boards as
examples. Future Motorola board level documents may contain additional
application notes aimed at clarifying configuration or implementation
issues that have been noted by several Motorola customers. If you are
unsure if this application will work on your particular product
configuration, contact your Motorola sales representative.
The following paragraphs describe the setup of Universe chip registers,
using the MVME5100 and MVME2700 in order to establish
communication across a VMEbus. The scenario is simplistic at best and
does not presuppose operational consistency involving multiple
representations of these and other MVME boards. In this description, all
64MB of both boards are mapped onto the VMEbus in A32/D32 space.
The specific slave image register set used was arbitrary, but based most
nearly on those setup correctly by PPCBug’s default settings. These are
displayed in the following table:.
Table C-1. MVME2700/MVME5100 Sample Slave Image Settings
PCI Slave 1
Original
PCI Slave 1
Modified
VME Slave 0
Original
VME Slave 0
Modified
2700: Control C082 0000 C082 0000 E0F2 0000 E0F2 0000
2700: Base 0100 0000 0100 0000 0000 0000 1000 0000
2700: Bound 2000 0000 2000 0000 0400 0000 13FF FFFF
2700: Translate 0000 0000 FF00 0000 8000 0000 7000 0000
5100: Control C082 0000 C082 0000 E0F2 0000 E0F2 0000
5100: Base 8100 0000 8100 0000 0000 0000 1400 0000
5100: Bound A000 0000 A000 0000 0400 0000 17FF FFFF
5100: Translate 8000 0000 7F00 0000 0000 0000 EC00 0000
C-1