Table of Contents
Advertisement
Line
addr,H
data,A
-----
------
------
0
0ff804
..
1
0ff805
..
2
0ff806
..
3
0ff807
..
4
0ff808
..
5
0ff809
..
6
0ff80a
..
7
0ff80b
..
8
0ff80c
..
9
0ff80d
..
10
0ff80e
..
11
0ff80f
..
12
0ff810
..
13
0ff811
..
14
0ff812
..
15
0ff813
..
16
0ff814
..
17
0ff815
..
18
0ff804
TT
19
0ff805
HH
20
0ff806
II
21
0ff807
SS
22
0ff808
..
23
0ff809
II
24
0ff80a
SS
25
0ff80b
..
26
0ff80c
MM
27
0ff80d
EE
28
0ff80e
SS
29
0ff80f
SS
30
0ff810
AA
31
0ff811
GG
32
0ff812
EE
33
0ff813
..
34
Emulation trace halted
count,R
seq
---------
---
---
+
0.760 uS
.
0.720 uS
.
0.760 uS
.
0.760 uS
.
0.760 uS
.
0.720 uS
.
0.760 uS
.
0.760 uS
.
0.760 uS
.
0.720 uS
.
0.760 uS
.
0.760 uS
.
0.760 uS
.
0.720 uS
.
0.760 uS
.
0.760 uS
.
0.760 uS
.
12.00 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.160 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
1.120 uS
.
If you look at the last lines of the trace listing, you will notice that the
analyzer seems to have stored only part of the output message, even
though you specified more than the full range needed to store all of the
message. The reason for this is that the analyzer has a storage pipeline,
which holds states that have been acquired but not yet written to trace
memory. To see all of the states, halt the analyzer by typing:
U> th
You will see:
Now display the trace list:
U> tl 0..34
You will see:
Getting Started 2-25
Advertisement
Table of Contents
