Debug in Depth

B.8 Determining the core and system state

When the ARM7TDMI core is in debug state, you examine the core and system state by forcing the load and store multiples into the instruction pipeline.

Before you can examine the core and system state, the debugger must determine if the processor entered debug from Thumb state or ARM state, by examining bit 4 of the EmbeddedICE debug status register. When bit 4 is HIGH, the core has entered debug from Thumb state, when bit 4 is LOW, the core has entered debug entered from ARM state.

B.8.1 Determining the core state

When the processor has entered debug state from Thumb state, the simplest course of action is for the debugger to force the core back into ARM state. The debugger can then execute the same sequence of instructions to determine the processor state.

To force the processor into ARM state while in debug, execute the following sequence of Thumb instructions on the core:

Note

Because all Thumb instructions are only 16 bits long, the simplest course of action, when shifting scan chain 1, is to repeat the instruction. For example, the encoding for BX R0 is 0x4700, so when 0x47004700 shifts into scan chain 1, the debugger does not have to keep track of the half of the bus on which the processor expects to read the data.

You can use the sequences of ARM instructions in Example B-1 and Example B-2 on page B-25 to determine the state of the processor.

With the processor in the ARM state, the instruction to execute is shown in

Example B-1.

Example B-1 Instruction to determine core state

STM R0, {R0-R15}

Debug in Depth

The instruction in Example B-1 on page B-24 causes the contents of the registers to appear on the data bus. You can then sample and shift out these values.

Note

The use of r0 as the base register for the STM is only for illustration and you can use any register.

After you have determined the values in the current bank of registers, you might want to access the banked registers. To do this, you must change mode. Typically, a mode change can occur only if the core is already in a privileged mode. However, while in debug state, a mode change from one mode into any other mode can occur. The debugger must restore the original mode before exiting debug state.

For example, if the debugger has been requested to return the state of the User mode registers and FIQ mode registers and debug state was entered in Supervisor mode, the instruction sequence can be as listed in Example B-2.

Example B-2 Determining state of User and FIQ mode registers

All these instructions execute at debug speed. Debug speed is much slower than system speed. This is because between each core clock, 33 clocks occur in order to shift in an instruction, or shift out data. Executing instructions this slowly is acceptable for accessing the core state because the ARM7TDMI core is fully static. However, you cannot use this method for determining the state of the rest of the system.

While in debug state, only the following instructions can be scanned into the instruction pipeline for execution:

•all data processing operations

•all load, store, load multiple, and store multiple instructions

•MSR and MRS.

Debug in Depth

B.8.2 Determining system state

To meet the dynamic timing requirements of the memory system, any attempt to access system state must occur synchronously to it. The ARM7TDMI core must be forced to synchronize back to system speed. This is controlled by the 33rd bit of scan chain 1.

Any instruction can be placed in scan chain 1 with bit 33, the BREAKPT bit, clear. This instruction is then executed at debug speed. To execute an instruction at system speed, the instruction prior to it must be scanned into scan chain 1 with bit 33 set.

After the system speed instruction has been scanned into the data bus and clocked into the pipeline, the RESTART instruction must be loaded into the TAP controller. This causes the ARM7TDMI core to automatically synchronize back to MCLK, the system clock, execute the instruction at system speed, and then re-enter debug state and switch itself back to the internally generated DCLK. When the instruction has completed, DBGACK is HIGH and the core is switched back to DCLK. At this point, INTEST can be selected in the TAP controller and debugging can resume.

To determine that a system speed instruction has completed, the debugger must look at both DBGACK and nMREQ. To access memory, the ARM7TDMI core drives nMREQ LOW, after it has synchronized back to system speed. This transition is used by the memory controller to arbitrate if the ARM7TDMI core can have the bus in the next cycle. If the bus is not available, the core can have its clock stalled indefinitely. Therefore, the only way to tell that the memory access has completed, is to examine the state of both nMREQ and DBGACK. When both are HIGH, the access has completed. Usually, the debugger uses the EmbeddedICE macrocell to control debugging and by reading the EmbeddedICE macrocell status register, the state of nMREQ and DBGACK can be determined.

By using system speed load multiples and debug speed store multiples, the system memory state can be fed back to the debug host.

There are restrictions on which instructions can have the 33rd bit set. The only valid instructions on which to set this bit are loads, stores, load multiple, and store multiple. See also Exit from debug state. When the core returns to debug state after a system speed access, bit 33 of scan chain 1 is set HIGH. This gives the debugger information about why the core entered debug state the first time this scan chain is read.

B.8.3 Exit from debug state

Leaving debug state involves restoring the internal state of the ARM7TDMI core, causing a branch to the next instruction to be executed and synchronizing back to MCLK. After restoring internal state, a branch instruction must be loaded into the pipeline. See Behavior of the program counter during debug on page B-29 for a description of how to calculate the branch.

Debug in Depth

Bit 33 of scan chain 1 is used to force the ARM7TDMI core to resynchronize back to MCLK. The penultimate instruction of the debug sequence is scanned in with bit 33 set HIGH. The final instruction of the debug sequence is the branch and this is scanned in with bit 33 LOW. The core is then clocked to load the branch into the pipeline. Now, the RESTART instruction is selected in the TAP controller. When the state machine enters the RUN-TEST-IDLE state, the scan chain reverts back to system mode and clock resynchronization to MCLK occurs in the core. The ARM7TDMI core then resumes normal operation, fetching instructions from memory. The delay, until the state machine is in the RUN-TEST-IDLE state, enables conditions to be set up in other devices in a multiprocessor system without taking immediate effect. Then, when the RUN-TEST-IDLE state is entered, all processors resume operation simultaneously.

The function of DBGACK is to tell the rest of the system when the core is in debug state. This can be used to inhibit peripherals such as watchdog timers that have real time characteristics. Also, DBGACK can be used to mask out memory accesses which are caused by the debugging process. For example, when the core enters debug state after a breakpoint, the instruction pipeline contains the breakpointed instruction plus two other instructions that have been prefetched. On entry to debug state, the pipeline is flushed. Therefore, on exit from debug state, the pipeline must be refilled to its previous state. Because of the debugging process, more memory accesses occur than is normally expected. Any system peripheral that is sensitive to the number of memory accesses can be inhibited by using DBGACK.

For example, imagine a fictitious peripheral that simply counts the number of memory cycles. This device must return the same answer after a program has been run both with and without debugging. Figure B-6 on page B-28 shows the behavior of the core on exit from the debug state.