Trace Analysis Considerations; Restriction Of The Analyzer - HP 7750 User Manual

Trace Analysis
Considerations
Restriction of the
Analyzer
Line addr,H M7750/51 Mnemonic,H
----- ------ ------------------------------------
0 00c00c LDA A,DT:0100H
1 00c00e
2 000100
3 00c00f CMP A,#00H
4 00c010
5 00c011 BEQ 00c00cH
6 00c012
7 00c014
8 00c00c
9 00c00c LDA A,DT:0100H
10 00c00e
11 000100
12 00c00f CMP A,#00H
13 00c010
14 00c011 BEQ 00c00cH
15 00c012
16 00c014
17 00c00c
18 00c00c LDA A,DT:0100H
19 00c00e
20 000100
There is a restriction on the function of the emulation analyzer. It
cannot trace the data which is read from internal RAM or SFR area.
Such data always appears ff hex in the trace listing. This is because the
emulator uses the internal RAM and SFR of emulation processor to
perform emulation. Data read from internal RAM or SFR doesn't
appear on the analyzer data bus.
As an example, trace the accesses to the INPUT_POINTER.
To initialize the analyzer, type:
U> tinit
Set up the trigger condition and perform the trace:
U> tg addr=0c00c and stat=exec
U> t
U> tl 0..20
c901H opcode fetch
xxffH data read
f000H opcode fetch
e2f9H opcode fetch
a210H opcode fetch
00adH opcode fetch
c901H opcode fetch
xxffH data read
f000H opcode fetch
e2f9H opcode fetch
a210H opcode fetch
00adH opcode fetch
c901H opcode fetch
xxffH data read
As you can see in line 2 of the listing above, data read from internal
RAM (which should be 00 hex) appears ff hex.
count,R seq
--------- ---
2.000 uS
mx 6.000 uS
mx 4.000 uS
2.000 uS
mx 6.000 uS
2.000 uS
6.000 uS
8.000 uS
8.000 uS
2.000 uS
mx 6.000 uS
mx 4.000 uS
2.000 uS
mx 6.000 uS
2.000 uS
6.000 uS
8.000 uS
8.000 uS
2.000 uS
mx 6.000 uS
mx 4.000 uS
+
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Getting Started 2-31