HP MC68040 User Manual page 687

Chapter 18: Connecting the Emulator to a Target System
Line addr,H 68040 Mnemonic
----- -------- ------------------------------------------
-4 000010f0 $00------ log sdata byte read
-3 00001e74 $4E714E71 log sprog long read
-2 0000f0ec $000a007C log sdata long read
-1 0000f0e8 $27000000 log sdata long read
0 00000008 $000060FE log sprog long read
1 0000000c $000BADAD log sprog long read
If the monitor detects problems with the stack pointer (the stack pointer must be
even), or if the monitor has a problem accessing the stack memory, an error
message is issued. Additionally, the monitor checks to make sure that the stack has
been written correctly before exiting. Problems are indicated by the following error
messages:
!ERROR 151! Interrupt stack pointer is odd or uninitialized
!ERROR 610! Unable to run
This message indicates that the stack pointer is invalid. Only word aligned stack
pointers are allowed with the emulator. The run is not attempted.
!ERROR 170! Target bus error: 00000f0e8@sd
!ERROR 610! Unable to run
This message indicates a bus error occurred during the stack write. This behavior
can be caused if the stack is in a memory range that responds with bus error for all
accesses or for write accesses. Or, this behavior can be caused by putting the stack
where the target system fails to respond immediately; the bus error is the result of a
timeout. Keep in mind that the stack grows down from the initial stack pointer.
!STATUS 170! Emulator terminated hung bus cycle: 00000f0e8@sd long write
!ERROR 610! Unable to run
This indicates that the stack is in an address range that did not respond with a
memory strobe. Make sure that the stack is placed in valid memory.
!ERROR 151! Interrupt stack is not located in RAM: 00000f0e8@sd
!ERROR 610! Unable to run
This indicates that the stack memory was not writeable. Check to make sure that
the stack is placed in RAM.
If the target program appears to start at the wrong address, or if there is some other
problem, the stack can be decoded to see if the correct information is present. The
stack above is interpreted as follows: The initial stack pointer is defined to point to
Installing Emulator Features
<-unstack
<-unstack
<-target program
657