Interpreting Address Pattern Test Results; If Problems Were Found By The Address Pattern Test - Agilent Technologies E5900B User Manual

? mtest ap.
For general instructions on using the command line interface see page 131.

Interpreting Address Pattern test results

This test does not ensure that the data lines or individual data locations are
without error. If a bit is stuck in a memory location, but is stuck in the written
value, the stuck bit will not be detected.
You can view the memory in an analyzer memory window of a 16700-series
logic analysis system by selecting Window <emulator> Memory.... Enter ? m at
the command line prompt for help viewing memory using a terminal interface.
You should see direct correlation between each address and the data stored at
that address.
Consistent errors typically indicate problems in the address lines. This is
especially likely if the results of the Basic Pattern test were without errors.
Errors in specific memory locations may indicate errors in the memory
hardware instead of the address lines.

If problems were found by the Address Pattern test

You may see no errors in the Basic Pattern test, but errors in the Address
Pattern test. For example, you might see the following result in the Address
Pattern test:
Example:
Error: 1 at address 00000000:
Read 0020
Expected 0000
Error: 2 at address 00000002:
Read 0022
Expected 0002
You would see that the data stored at locations 00 through 0f is the data that
should be at locations 20 through 2f. This indicates an address line problem.
Address bit 5 must be stuck low because the addresses that should have been
written to the range 20 through 2f were written instead to 00 through 0f.
Random errors typically do not indicate address line errors. Use the Walking
Ones (see page 98) and Walking Zeros (see page 99) tests to check the
locations of random errors.
Emulation for the Motorola M•CORE
(0000 0000 0010 0000)
(0000 0000 0000 0000)
(0000 0000 0010 0010)
(0000 0000 0000 0010)
Testing Target System Memory
Memory Test Patterns
95