Trace List
Label:
Address
Base:
symbols
after
:cmd_rds.s:+0014
+001
:cmd_rds.s:+0016
+002
cmd_rds.sr:Cmd_A
+003
:cmd_rds.s:+001E
+004
:cmd_rds.s:+0020
+005
:cmd_rds.s:+0022
+006
cmd_rds.sr:Cmd_B
+007
cmd_rd:Write_Msg
+008
:cmd_rds.s:+0034
+009
cmd_rd:Clear_Old
+010
cmd_r:Clear_Loop
+011
:cmd_rds.s:+003A
+012
:Msg_Dest
+013
:cmd_rds.s:+003C
+014
:cmd_rds.s:+003E
STATUS:
H8/338--Running user program
modify memory Cmd_Input byte to 41h
run
trace
Store Condition and
Trace
2-28 Getting Started
trace after cmd_rds.src:Exe_Cmd+2
<RETURN>
(Since the instruction at Exe_Cmd label is two bytes instruction, the
next instruction starts from Exe_Cmd+2.)
modify memory Cmd_Input bytes to 41h
<RETURN>
Offset=0
Data
hex
mnemonic w/symbols
4706
BEQ cmd_rds.sr:Cmd_A
AA42
AA42
FB11
MOV.B #11,R3L
7904
MOV.W #2000,R4
2000
2000
400E
BRA cmd_rd:Write_Msg
FB11
FB11
7905
MOV.W #FE82,R5
FC02
FC02
FE20
MOV.B #20,R6L
68D8
MOV.B R0L,@R5
0B05
ADDS #1,R5
0000
00
1A0E
DEC R6L
46F8
BNE cmd_r:Clear_Loop
step
display
If you need to see the execution of the instruction at Exe_Cmd label,
use trace about command instead of trace after command. When you
use the trace about command, the state which triggered the analyzer
will appear in the center of the trace list.
When you specify store condition with trace only command,
disassembling of program execution is unreliable.
trace <RETURN>
Opcode or Status
fetch mem
fetch mem
fetch mem
fetch mem
write mem byte
Emulation trace complete______........
modify
break
end
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
---ETC--