PIPELINE INFORMATION AND GLOBAL DATA BUS REGISTER
MOTOROLA
ON-CHIP EMULATION (OnCE)
10 - 17
10.6.5
Software Request During Normal Activity
Upon executing the DEBUG or DEBUGcc instruction when the specified condition is true,
the chip enters the debug mode after the instruction following the DEBUG instruction has
entered the instruction latch.
10.6.6
Enabling Trace Mode
When the trace mode mechanism is enabled and the trace counter is greater than zero,
the trace counter is decremented after each instruction execution. The completed execu-
tion of an instruction when the trace counter is zero will cause the chip to enter the debug
mode.
Note: Only instructions actually executed cause the trace counter to decrement, i.e. an
aborted instruction will not decrement the trace counter and will not cause the chip to enter
the debug mode.
10.6.7
Enabling Memory Breakpoints
When the memory breakpoint mechanism is enabled with a breakpoint counter value of
zero, the chip enters the debug mode after completing the execution of the instruction that
caused the memory breakpoint to occur. In case of breakpoints on executed program
memory fetches, the breakpoint will be acknowledged immediately after the execution of
the fetched instruction. In case of breakpoints on data memory addresses (accesses to
X, Y or P memory spaces by MOVE instructions), the breakpoint will be acknowledged
after the completion of the instruction following the instruction that accessed the specified
address.
10.7
PIPELINE INFORMATION AND GLOBAL DATA BUS REGISTER
A number of on-chip registers store the chip pipeline status to restore the pipeline and re-
sume normal chip activity upon return from the debug mode. Figure 10-8 shows the block
diagram of the pipeline information registers with the exception of the program address
bus (PAB) registers, which are shown in Figure 10-9.
10.7.1
Program Data Bus Register (OPDBR)
The OPDBR is a 24-bit latch that stores the value of the program data bus which was gen-
erated by the last program memory access before the chip entered the debug mode.
OPDBR can be read or written through the OnCE serial interface. It is affected by the op-
erations performed during the debug mode and must be restored by the external com-
mand controller when the chip returns to normal mode.
Summary of Contents for DSP56K
Page 12: ...xii LIST of TABLES MOTOROLA List of Tables Continued Table Page Number Title Number ...
Page 13: ...MOTOROLA DSP56K FAMILY INTRODUCTION 1 1 SECTION 1 DSP56K FAMILY INTRODUCTION ...
Page 31: ...MOTOROLA DATA ARITHMETIC LOGIC UNIT 3 1 SECTION 3 DATA ARITHMETIC LOGIC UNIT ...
Page 50: ...DATA ALU SUMMARY 3 20 DATA ARITHMETIC LOGIC UNIT MOTOROLA ...
Page 51: ...MOTOROLA ADDRESS GENERATION UNIT 4 1 SECTION 4 ADDRESS GENERATION UNIT ...
Page 77: ...MOTOROLA PROGRAM CONTROL UNIT 5 1 SECTION 5 PROGRAM CONTROL UNIT ...
Page 124: ...INSTRUCTION GROUPS 6 30 INSTRUCTION SET INTRODUCTION MOTOROLA ...
Page 125: ...MOTOROLA PROCESSING STATES 7 1 SECTION 7 PROCESSING STATES STOP WAIT EXCEPTION NORMAL RESET ...
Page 167: ...STOP PROCESSING STATE MOTOROLA PROCESSING STATES 7 43 ...
Page 168: ...STOP PROCESSING STATE 7 44 PROCESSING STATES MOTOROLA ...
Page 169: ...MOTOROLA PORT A 8 1 SECTION 8 PORT A ...
Page 176: ...PORT A INTERFACE 8 8 PORT A MOTOROLA ...
Page 177: ...MOTOROLA PLL CLOCK OSCILLATOR 9 1 SECTION 9 PLL CLOCK OSCILLATOR x x d Φ VCO ...
Page 191: ...10 2 ON CHIP EMULATION OnCE MOTOROLA SECTION 10 ON CHIP EMULATION OnCE ...
Page 218: ...USING THE OnCE MOTOROLA ON CHIP EMULATION OnCE 10 29 ...
Page 604: ...INSTRUCTION ENCODING A 338 INSTRUCTION SET DETAILS MOTOROLA ...
Page 605: ...MOTOROLA BENCHMARK PROGRAMS B 1 APPENDIX B BENCHMARK PROGRAMS T T T T T P1 P3 P2 P4 T T T ...
Page 609: ...BENCHMARK PROGRAMS MOTOROLA BENCHMARK PROGRAMS B 5 ...
Page 611: ...BENCHMARK PROGRAMS MOTOROLA BENCHMARK PROGRAMS B 7 ...
Page 613: ...BENCHMARK PROGRAMS MOTOROLA BENCHMARK PROGRAMS B 9 ...
Page 615: ...BENCHMARK PROGRAMS MOTOROLA BENCHMARK PROGRAMS B 11 ...