Table of Contents
Advertisement
Testing memory access with the foreground
monitor
Once the foreground monitor looks like it is running properly, you can use it to test
accesses to different ranges of memory in your target system. This may be an
easier way to diagnose problems than by running a program that accesses each
memory range. It is also easy to check accesses of different sizes using the monitor.
mo -ax -dl
m 0badad=12345678
When accesses to your target memory are not performed exactly right, the monitor
attempts to diagnose these problems and resolve them so the monitor program does
not malfunction. However, the monitor does not read back write cycles to check
the integrity of the data written. When testing memory accesses, check the data to
make sure it is correct.
M>m 0badad
0000badad
ffdf00ff
If your target memory does not respond to a bus cycle, the monitor will force
termination of the cycle and report this error message.
!STATUS 170! Emulator terminated hung bus cycle: 0000badad@sd word read
!ERROR
700! Target memory access failed
Or, if the target system responds with a bus error for this memory access, the
monitor will report that information.
!ERROR
170! Target bus error: 0000badad@sd
!ERROR
700! Target memory access failed
Chapter 4:Connecting the Emulator to a Target System
Installing Emulator Features
93
Advertisement
Table of Contents
