Table of Contents
Advertisement
Trace Analysis
Considerations
How to Specify
Trigger Condition
Trace List
Label:
Address
Base:
symbols
after
cmd_rds.:Exe_Cmd
+001
cmd_rds.src:Scan
+002
:cmd_rds.s:+000C
+003
:cmd_rds.s:+000E
+004
:Cmd_Input
+005
:cmd_rds.s:+0010
+006
cmd_rds.:Exe_Cmd
+007
cmd_rds.src:Scan
+008
:cmd_rds.s:+000C
+009
:cmd_rds.s:+000E
+010
:Cmd_Input
+011
:cmd_rds.s:+0010
+012
cmd_rds.:Exe_Cmd
+013
cmd_rds.src:Scan
+014
:cmd_rds.s:+000C
STATUS:
H8/338--Running user program
trace after Exe_Cmd
run
trace
There are some points to be noticed when you use the emulation
analyzer.
You need to be careful to specify the condition on which the emulation
analyzer should start the trace. Suppose that you would like to start the
trace when the program begins executing Exe_Cmd routine:
trace after cmd_rds.src:Exe_Cmd
<RETURN>
modify memory Cmd_Input bytes to 41h
<RETURN>
You will see:
Offset=0
Data
hex
AA41
AA41
6A0A
MOV.B @:Cmd_Input,R2L
FE80
FE80
AA00
CMP.B #00,R2L
00FF
00
47F8
BEQ cmd_rds.src:Scan
AA41
AA41
6A0A
MOV.B @:Cmd_Input,R2L
FE80
FE80
AA00
CMP.B #00,R2L
00FF
00
47F8
BEQ cmd_rds.src:Scan
AA41
AA41
6A0A
MOV.B @:Cmd_Input,R2L
FE80
FE80
step
display
This is not what we were expecting to see. As you can see at the first
line of the trace list, the address of Exe_Cmd routine appears on the
address bus during the program executing Scan loop. This made the
emulation analyzer start trace. To avoid mis-trigger by this cause, set
the trigger condition to the second instruction of the routine you want
to trace:
Opcode or Status
mnemonic w/symbols
fetch mem
fetch mem
read
mem byte
fetch mem
fetch mem
read
mem byte
fetch mem
fetch mem
Emulation trace complete______........
modify
break
time count
absolute
------------
+ 200
nS
+ 400
nS
+ 600
nS
+ 800
nS
+
1.0
uS
+
1.2
uS
+
1.4
uS
+
1.6
uS
+
1.8
uS
+
2.0
uS
+
2.2
uS
+
2.4
uS
+
2.6
uS
+
2.8
uS
end
---ETC--
Getting Started 2-27
Advertisement
Table of Contents
