Technical data

VME3- Universe VME to PCI Bridge Tests

http://www.motorola.com/computer/literature 3-145

Entering VME3 without parameters causes all VME3 tests to run in the

order shown in the table below, except as noted.

To run an individual test, add that test name to the VME3 command. The

individual tests are described in alphabetical order on the following pages.

The PPCBUG Diagnostics engine includes a test init function, which is run

prior to each of the tests in the test group. For the Universe diagnostics,

several things will be tested during test init.

The init phase testing verifies that there is agreement between the board’s

Base Module Feature Register (BMFR) and the actual installation of the

board’s Universe chip. If the VME Present bit in the BMFR indicates the

Universe is not installed, all post-init phase Universe testing will be

bypassed. Whether this is an error condition or not depends on the

following sets of conditions. In order to establish whether the Universe is

actually installed, the Universe’s PCI Configuration Space Vendor ID

value (at offset 2) is read. If the Vendor ID indicates that the Universe is

installed, but the VME Present bit indicates it should not be, an error will

be logged and the currently-running test will exit. If the Vendor ID cannot

be read and the VME Present bit indicates the device should be installed,

an error will be logged and the currently-running test will exit.

There are currently no active CF parameters for the Universe Tests.

Table 3-25. VME3 Test Group

Name Description

REGR Register Read

REGW Register walking bits (write/read)