Debug interface including logic generating handshake signals between a processor, an input/output port, and a trace logic

[0002] This application relates to U.S. application Ser. No. 60/043,070, filed Apr. 8, 1997, which is hereby incorporated by reference.

[0003] 1. Field of the Invention

[0004] The present invention relates to computer systems such as microprocessors. More specifically, the present invention relates to a software debug support system and operating method in processors.

[0005] 2. Description of the Related Art

[0006] The growth in software complexity, in combination with increasing processor clock speeds, has placed an increasing burden on application software developers. The cost of developing and debugging new software products is now a significant factor in processor selection. A failure to include adequate software debug functionality in a processor results in longer customer development times and reduces attractiveness of the processor for use within industry. Software debug support is particularly useful in the embedded products industry, where specialized on-chip circuitry is often combined with a processor core.

[0007] The software debug tool configuration of a processor addresses the needs of several parties in addition to the software engineer who develops program code for execution on the processor. A “trace” algorithm developer searches through captured software trace data that reflects instruction execution flow in a processor. An in-circuit emulator developer deals with problems of signal synchronization, clock frequency and trace bandwidth. A processor manufacturer seeks a software debug tool solution that avoids an increased processor cost or design and development complexity.

[0008] In the desktop systems, complex multitasking operating systems are currently available to support software debugging. However, the initial task of getting the operating systems running reliably often calls for special development equipment. While not standard in the desktop environment, development equipment such as logic analyzers, read-only memory (ROM) emulators, and in-circuit emulators (ICE) are sometimes used in the embedded industry. In-circuit emulators have some advantages over other debug environments including complete control and visibility over memory and register contents, and supplying overlay and trace memory if system memory is insufficient.

[0009] Traditional in-circuit emulators are used by interfacing a custom emulator back-end with a processor socket to allow communication between emulation equipment and the target system. The custom design of emulator interfaces in increasingly unrealistic and expensive as product life cycles are reduced and nonstandard and exotic integrated circuit packages are predominant in present day processor design.

[0010] Few known processor manufacturing techniques are available that include a suitable full-function in-circuit emulation functionality. Most processors in personal computer (PC) systems implement emulation functionality using a multiplexed approach in which existing pins are multiplexed for alternative use in a software debug application. Multiplexing of pins is not desirable in embedded controllers, which inherently suffer from overload of pin functionality.

[0011] Some advanced processors multiplex debug pins in time, for example by using the address bus to report software trace information during a Branch Target Address (BTA) cycle. The BTA-cycle is stolen from regular bus operation cycles. However in debug environments with high branch activity and low cache hit rates, BTA-cycles are often fully occupied handling branches, resulting in a conflict over access to the address bus that necessitates processor “throttle back” to prevent a loss of instruction race information. For example, software in the communications industry is branch-intensive and suffers poor cache utilization often resulting in 20% or more throttle back, an unacceptable amount for embedded products which are subject to real-time constraints.

[0012] In another approach, a second “trace” or “slave” processor is combined with a main processor, with the two processors operating in-step. Only the main processor fetches instructions. The second, slave processor monitors fetched instructions on the data bus and maintains an internal state in synchronization with the main processor. The address bus of the slave processor supplies trace information. After power-up, via a JTAG (Joint Test Action Group) input, the second processor is switched into a slave mode of operation. The slave processor, freed from instruction fetch duties, uses the slave processor address bus and other pins to supply trace information.

[0013] Another existing debug strategy utilizes implementation of debug support into every processor in a system, but only bonding-out signal pins in a limited number of packages. The bond-out versions of the processor are used during debug and replaced with the smaller package for final production. The bond-out approach suffers from the need to support additional bond pad sites in all fabricated devices, a burden in small packages and pad limited designs, particularly if a substantial number of extra pins are required by the debug support variant. Furthermore, the debug capability of specially-packaged processors is unavailable in typical processor-based production systems.

[0014] In yet another approach, specifically the Background Debug Mode (BDM) implemented by Motorola, Inc., limited on-chip debug circuitry is implemented for basic run control. The BDM approach utilizes a dedicated serial link having additional pins and allows a debugger to start and stop the target system and apply basic code breakpoints by inserting special instructions in system memory. Once halted, special commands are used to inspect memory variables and register contents. The BDM system includes trace support, but not conveniently using the serial link. Instead the BDM system supplies trace support through additional dedicated pins and expensive external trace capture hardware that transfer instruction trace data.

[0015] Accordingly, present day techniques for software debugging suffer from a variety of limitations including increased packaging and development costs, circuit complexity, processor throttling, and bandwidth matching difficulties. Furthermore, no adequate low-cost procedure for providing trace information is currently available. The limitations of the existing solutions are likely to be exacerbated in the future as internal processor clock frequencies continue to increase.

[0016] What is needed is a software debug system and operating procedure that includes an improved trace capability.

[0017] A system for debugging a processor includes a debug interface including a handshake logic for communicating commands and data from a serial input/output port to a processor and to a trace control logic with a low delay. The handshake logic results in a low latency through the inclusion of a state machine that operates at the same speed as the processor. The state machine generates handshake signals to communicate among the serial input/output port, the processor, and the trace control logic.

[0018] In accordance with an embodiment of the present invention, a processor includes a debug interface for interfacing to an external debug device. The processor includes a processor core, a serial input/output port connected to the processor core and communicating information between the external debug device and the processor core, a trace logic accessing trace information indicating instruction execution flow in the processor core, and a debug interface. The debug interface is connected to the processor core, the serial input/output port, and the parallel input/output port. The debug interface includes a handshake logic generating handshake signals controlling communications between the serial input/output port and the processor core and between the trace logic and the processor core. The handshake logic includes a synchronization block synchronizing the handshake signals.

[0019] In accordance with another embodiment of the present invention, a debug interface for interfacing a processor to a debug device includes a serial input/output port, a trace logic connected to the serial input/output port, and an interface logic. The interface logic is connected to the serial input/output port and connected to the trace logic. The interface logic generates handshake signals to communicate data between the serial input/output port, the trace logic, and the processor. The interface logic includes a synchronization block for synchronizing the handshake signals.

[0020] The debug interface and handshake logic advantageously control debug functionality so that all state machines in the handshake logic that interact during command execution are interlocked and the serial/parallel port does not process any new commands until a command that is currently executed is completed. Several state machines advantageously operate at processor clock speeds, resulting in a reduced delay and latency.

[0021] The present invention may be better understood, and its numerous objects, features, and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

[0022] FIG. 1 is a schematic block diagram showing a software debug environment utilizing a software debug port according to an embodiment of the present invention.

[0023] FIG. 2 is a schematic block diagram illustrating details of an exemplary embedded processor product incorporating a software debug port according to the present invention.

[0024] FIG. 3 is a state diagram illustrating a JTAG TAP controller state machine that is included in a JTAG TAP controller of the embedded processor product shown in FIG. 2.

[0025] FIG. 4 is a state diagram illustrating states of a standard JTAG interface access operation.

[0026] FIG. 5 is a state diagram illustrating states of an enhanced JTAG interface access operation.

[0027] FIG. 6 is a timing diagram showing signal behavior for acquisition and release of a parallel debug bus.

[0028] FIG. 7 is a flow chart depicting a parallel debug port interface protocol followed by the host system during communications via the parallel port.

[0029] FIG. 8 is a schematic state diagram illustrating operating states of the pending/finished state machine shown in FIG. 2.

[0030] FIG. 9 is a schematic state diagram illustrating operating states of the debug port state machine shown in FIG. 2.

[0031] FIG. 10 is a schematic state diagram depicting operating states of the parallel port state machine shown in FIG. 2.

[0032] FIG. 11 is a schematic state diagram depicting operating states of the processor interface state machine shown in FIG. 2.

[0033] FIG. 12 is a schematic circuit diagram illustrating an embodiment of a synchronization circuit for communicating commands and data between a communication port which is operating at a specified lower frequency and a processor core and trace control circuit that are operating at multiple various frequencies that are higher than the specified lower frequency.

[0034] FIG. 13 is a schematic block diagram illustrating synchronization elements of the embedded processor device.

[0035] FIG. 14 is a schematic circuit diagram illustrating a data steering circuit in the software debug port.

[0036] FIG. 15 is a schematic block diagram illustrating the utilization of data steering signals in the software debug port.

[0037] FIG. 16 is a schematic block diagram illustrating a circuit for generating a TDO signal from a TCK signal and a TDI signal.

[0038] The use of the same reference symbols in different drawings indicates similar or identical items.

[0039] Referring to FIG. 1, a schematic block diagram illustrates a software debug environment utilizing a debug port 100. A target system 101 is shown containing an embedded processor device 102 coupled to system memory 106. The embedded processor device 102 is an integrated debug interface for flexible, high-performance in an embedded hardware/software debug system. The embedded processor device 102 includes a processor core 104 and the debug port 100. In some embodiments, the embedded processor device 102 may incorporate additional circuitry (not shown) for performing application specific functions, or may take the form of a stand-alone processor or digital signal processor. In the illustrative embodiment, the debug port 100 includes an IEEE-1149.1-1990 compliant JTAG interface or other similar standardized serial port interface.

[0040] A host system 111 is used to execute debug control software 112 for transferring high-level commands and controlling the extraction and analysis of debug information generated by the target system 101. The host system 111 and target system 101 of the disclosed embodiment of the invention communicate via a serial link 110. Most computers are equipped with a serial or parallel interface which can be inexpensively connected to the debug port 100 by means of a serial connector 108, allowing most computers to function as a host system 111. In some embodiments, the serial connector 108 is replaced with higher speed JTAG-to-network conversion equipment.

[0041] Referring to FIG. 2, a schematic block diagram illustrates the embedded processor device 102 in more detail, including the processor core 104 and various elements of the debug port 100 in an enhanced form. The embedded processor device 102 includes a plurality of state machines that communicate messages and data between a serial port of a JTAG TAP controller 204, a trace control circuit 218, and the processor core 104. In some embodiments, the embedded processor device 102 includes a parallel port 214 and the state machines similarly establish communication between the parallel port 214, the trace control circuit 218, and the processor core 104.

[0042] The state machines include a debug port state machine 206, a parallel port state machine 226, a processor interface state machine 202, and a pending/finished state machine 224. The state machines read the commands and data from the serial/parallel ports and direct decoding of the commands by a command decode and processing block 208 logic. Some commands, such as a command for reading data from memory, utilize processor core 104 intervention and are appropriately sent to the processor core 104. The state machines do not accept further commands until execution of a previous command is complete. Once the command is completed, a flag in a debug port state machine 206 block is asserted or an output pin is asserted to indicate command completion to the host system 111.

[0043] A minimal embodiment of the debug port 100 supports only conventional JTAG pins in a fast JTAG compliant interface that advantageously attains controllability and observability. The JTAG pins are a transportation mechanism that use existing pins to enter commands for performance by the processor core 104. Conventional JTAG pins carry conventional JTAG support signals that are well known in the art including a test clock signal TCK, a test mode select signal TMS, a test data input signal TDI, and a test data output signal TDO and JTAG reset pin TRST_L. The conventional JTAG pins are driven by a JTAG Test Access Port (TAP) controller 204.

[0044] The JTAG compliant serial interface is augmented for higher-speed access via supplemental sideband signals and a bond-out parallel interface with a 16-bit data path. Specifically, four pins are added to an embedded processor device 102 that supports JTAG functionality in a non-bondout package to fully support the enhanced 10-pin debug port 100 format. The enhanced embodiment of the debug port 100 supports the four additional pins carrying “sideband” signals including a command acknowledge signal CMDACK, a break request/trace capture signal BRTC, a stop/transmit signal STOPTX, and a trigger signal/trace-on signal TRIG/TRACE-ON to the standard JTAG interface. The additional sideband signals advantageously enhance performance and functionality of the debug port 100 by attaining highly precise external breakpoint assertion and monitoring, by triggering external devices in response to internal breakpoints, and by eliminating status polling of the JTAG serial interface. The TRIG pin is multiplexed to indicate the Trace-on/off status by setting a bit in the ITCR register. The sideband signals offer extra functionality and improve communications speeds for the debug port 100, but are optional and not utilized in the simplest embodiments of debug port 100 which uses conventional JTAG support signals. In the illustrative embodiment the sideband signals are used with an optional parallel port 214 provided on special bond-out versions of the embedded processor device 102.

[0045] Using conventional JTAG signals, the JTAG TAP controller 204 accepts standard JTAG serial data and control signals. When public JTAG DEBUG instruction is written to a JTAG instruction register (not shown) using a Capture IR-Update IR sequence in a JTAG TAP controller state machine that is shown in FIG. 3, the serial debug shifter 212 is connected to the JTAG TDI-TDO serial interface. A JTAG test data input signal TDI and a test data output signal TDO are received by the serial debug shifter 212 via the JTAG TAP controller 204 so that commands and data are loaded into debug registers 210 and read from the debug registers 210. In the disclosed embodiment, the debug registers 210 include two debug registers for transmitting (TX_DATA register) and receiving (RX_DATA register) data, an instruction trace configuration register (ITCR), and a debug control status register (DCSR), a soft address register for loading the serial/CPU register addresses. Data are typically read from the JTAG TAP controller 204 using a Capture DR-Update DR sequence in the JTAG TAP controller state machine.

[0046] The Instruction Trace Configuration Register (ITCR) is written to control enabling, disabling, and configuration of Instruction Trace debug functions. The ITCR is accessed through the serial/parallel debug register write/read commands or by using a reserved instruction MOV ITCR.

[0047] The Debug Control/Status Register (DCSR) indicates when the processor core 104 enters debug mode and allows the processor core 104 to be forced into debug mode using the enhanced JTAG interface. DCSR also includes miscellaneous control feature enable bits. DCSR is accessible only through the serial/parallel debug register write/read commands.

[0048] A debug port state machine 206 coordinates loading and reading of data between the serial debug shifter 212 and the debug registers 210. The debug port state machine 206 interfaces to the JTAG TAP controller 204 via a parallel port state machine 226. A command decode and processing block 208, and the processor interface state machine 202, in combination, decode commands and data and dispatch the commands and data to a data steering circuit 222 which, in turn, communicates with the processor core 104 and trace control circuit 218. The processor interface state machine 202 communicates directly with the processor core 104 and a trace control circuit 218. A parallel port 214 communicates with the debug port state machine 206 and the data steering circuit 222 to perform parallel data read and write operations in optional bond-out versions of the embedded processor device 102.

[0049] The trace control circuit 218 supplies trace information for reconstructing instruction execution flow in the processor core 104. The trace control circuitry 218 supports tracing either to a trace pad interface port 220, which is also called a DEBUG trace port 220, or to an internal trace buffer 200 and implements user control for selectively activating and deactivating trace functionality. The trace control circuitry 218 controls a trace pad interface port 220 which, in the illustrative embodiment, shares communication lines of the parallel port 214. When utilized, the trace pad interface port 220 supplies trace data while the processor 104 is executing instructions at the rate specified by the TCLK [2:0] bits in the ITCR register. On a CPU reset the TCLK[2:0] bits are loaded with a code signifying a CPU internal clock speed. A user subsequently may program the bits to select a clock speed. The trace control circuitry 218 enables other features including programmability of synchronization address generation and user specified trace records.

[0050] The trace buffer 200 improves bandwidth matching and reduces the need to incorporate throttle-back circuitry in the processor core 104. In one embodiment, the trace buffer 200 is a 256 entry first-in, first-out (FIFO) circular cache. Increasing the size of the trace buffer 200 increases the amount of software trace information that is captured.

[0051] The JTAG TAP controller 204 functions as an IEEE-1149.1-1990-compliant serial command port that serves as a primary mode of communication between a host processor 111 and target processor to a maximum TCK rate of 25 MHz. Before debug information is communicated via the debug port 100 using only conventional JTAG signals, the port 100 is enabled by writing the public JTAG instruction DEBUG into a JTAG instruction register contained within the JTAG TAP controller 204. After the DEBUG instruction is loaded into the JTAG TAP controller instruction register, a 38-bit dedicated data register that serves as a command/status/data interface with the SLE486 processor is connected between TDI and TDO pins. The serial command interface includes a 38-bit register including a 32-bit data field debut_data[31:0], a four-bit command field cmd[3:0] to point to various internal registers and functions provided by the debug port 100, a command pending flag (P), and a command finished flag (F). Some commands use bits of the debug_data field as a sub-field to extend the number of available commands. The pending and finished flags are controlled by a pending/finished state machine 224 that is connected to the serial port register shown below.

[0052] Referring to FIG. 16, a schematic block diagram illustrates a circuit for generating a transmit data output signal (TDO) from a clock signal (TCK) and a transmit data input signal (TDI). The transmit data output (TDO) pin supplies a signal that is based on the values of a select_IR signal, the JTAG_debug inst instruction, and an output signal from the debug registers 210. JTAG_debuo_inst is decoded from the DEBUG instruction in a TAP_IR register 1602.

[0053] The select IR signal is determined according to the following logical code implemented in a bypass register 1606 and a boundary scan register 1608:

[0054] select_IR=(tap_state=SEL_IR_SCAN)|tap-state=CAPTURE-IR |tap_state=SHIFT_IR|tap_state=EXIT1_IR|tap_state=PAUSE_IR|tap_state=EXIT2_IR|tap_state=UPDATE_IR).

[0055] The transmit data output (TDO) signal is determined, as follows:

[0056] TDO=!(select_IR & JTAG_debug inst & debug_shfout).

[0057] where debug_shfout is bit 0 shifted output of the 38-bit serial port register 1604.

[0058] Commands and data are loaded into and read from the 38-bit serial-port register/shifter using the capture DR—Update_DR sequence in the JTAG TAP controller state machine.

[0059] JTAG_debug_inst Register is enabled after DEBUG inst is written into the JTAG_TAP_IR Register.

[0060] A signal definition includes two sections, a standard section and a bond-out section. Standard signals are shown in TABLE I and are available for usage on all embedded processor device 102 integrated circuits. Bond-out signals are shown in TABLE II and are available only on specially-packaged parts, typically for usage by in-circuit emulation (ICE) vendors. A TBUS[18:0] is shared between the parallel port 214 and the trace pad interface 220. The remaining bond-out signals are dedicated to either the parallel port or the trace pad interface 220.

[0061] Referring to FIG. 4, a state diagram illustrates a high-level flowchart of the host/serial port interface of the JTAG TAP controller 204 when using standard JTAG communication. The host system 111 writes a DEBUG instruction to the Instruction Register in the JTAG TAP controller 204 in operation 402. After the DEBUG instruction has been written the 38-bit serial port register is connected between TDI and TDO pins. Now the host begins to shift a 38-bit serial value into the 38-bit serial port register using the capture DR—Update DR sequence in the JTAG TAP controller state machine with the Command Pending Flag (P) asserted and data (if applicable, otherwise zero) in the data field in operation 404. Upon completing the command, which typically involves transferring a value between the data field of the 38-bit serial register and a predetermined processor register or memory/IO location in the processor core 104, the debug-port state machine clears the Pending flag (P=0) and asserts the Finished flag (F=1), simultaneously storing a value in the data field, if applicable. The entire 38-bit register is scanned out to monitor the Finished (F) and Pending (P) flags. If the Pending flag P is reset to zero and the Finished flag F is set to one, the previous command is finished. The status of the flags is captured during the Capture-DR TAP controller state shown in FIG. 3. A slave copy of the flag status is saved internal to the JTAG TAP controller 204 and checked in operation 406 to determine in logic state 408 whether the next instruction is to be loaded in the Update-DR TAP controller state. If the Finished flag (F) is set, a new 38-bit command is scanned in operation 406, otherwise the previous data scan is repeated in operation 410. A slave copy is maintained due to the possibility of the status changing between the Capture-DR and Update-DR TAP controller states. The processor saves the slave copy to determine the status the user will detect at the time the status capture is performed to prevent the loading of the next instruction if the user sees that the previous instruction has not finished.

[0062] Referring again to FIG. 2, the processor interface state machine 202 performs asynchronous control operations for adding the signals CMDACK, BRTC, STOP/TX, and TRIG/TRACE-ON/OFF to the standard JTAG interface. The CMDACK, BRTC, STOP/TX, and TRIG/TRACE-ON/OFF signals are enabled when the DEBUG instruction is written to the JTAG instruction register in the JTAG TAP controller 204, but forced to a logic zero when disabled. The BRTC signal pin is supplied with an internal pull-down resistor (not shown).

[0063] Referring to FIG. 5, a flow diagram illustrates state operation of the enhanced JTAG interface. The host system 111 writes a DEBUG instruction to the JTAG TAP controller 204 in operation 502 then optionally monitors the output signal CMDACK to determine command completion status in a logic operation 504. The CMDACK signal is asserted high simultaneous with assertion of the Finished flag (F) and remains high until the next command is shifted. When using the CMDACK pin, the Finished flag (F) status is captured without shifting out the serial port register in the serial debug port shifter block 227 since the CMDACK pin transitions high on the next rising edge of TCK after the real-time status of the Finished flag (F) changes from 0 to 1. The CMDACK signal is not delayed from the state saved during the previous Capture-DR state entry of the TAP controller state machine. Accordingly, in the enhanced JTAG mode a new shift sequence is not started in operation 506 until the CMDACK pin is asserted high. The CMDACK pin asserts high when the serial port is ready to receive instructions after the DEBUG instruction is loaded into the JTAG instruction register. The CMDACK signal is synchronous with the TCK signal. TCK is generally not clocked at all times, but is clocked continuously when waiting for a CMDACK response.

[0064] The BRTC input signal functions either as a break request signal or a trace capture enable signal depending on the BRKMODE bit in the DCSR. The BRTC signal, when set to function as a break request signal, is pulsed to cause the target system 101 to enter debug mode. If the BRTC signal is set to function as a trace capture enable signal, asserting the signal high activates the trace capture. Deasserting the BRTC signal deactivates the trace capture. The BRTC signal takes effect on the next instruction boundary after detection and is internally synchronized with the internal processor clock. The BRTC signal can be asserted at any time.

[0065] The TRIG/TRACE-ON/OFF output signal is optionally enabled to pulse whenever an internal breakpoint in the processor core 104 is asserted and if the corresponding enable bit is set in the ITCR register. The TRIG signal event is typically used to trigger an external capturing device such as a logic analyzer. When the processor core 104 generates a breakpoint, the TRIG output signal event is pulsed for two CPUCLK periods. When bit-14 in the ITCR register is set the TRIG/TRACE-ON/OFF pin is used to indicate the internal status of TRACE-ON/OFF.

[0066] The STOPTX output signal is asserted high when the target system 101 enters debug mode and is ready for register interrogation and modification, or memory or I/O reads and writes through the serial/parallel command interface. In a normal (nondebug) mode, the STOPTX signal is asserted high when the target system 101 is ready to transmit data during Operating System (OS) or Application communication. The STOPTX signal reflects the state of bit 7 or bit 11 in the debug control/status register (DCSR). The STOPTX signal is synchronous with JTAG TCK clock. When external instruction tracing through the bond-out DEBUG trace port is enabled, assertion of STOPTX is delayed until all data in the instruction trace buffer 200 is transferred out.

[0067] Referring again to FIG. 2, the parallel port 214 is a high-performance interface that is typically available in the bond-out version of the target system 101. The parallel port 214 supplies a 16-bit data path is intended to perform fast downloads and uploads between the host system 111 and the target system memory. The parallel port 214 is optionally used for all debug communication with the target system 101 whenever the processor core 104 is stopped. The serial port interface, either standard or enhanced, is used for debug access to the target system 101 when the processor core 104 is executing instructions or when the processor core 104 is stopped.

[0068] The parallel port 214 includes a 16-bit wide bi-directional data bus PDATA[15:0], a 3-bit address bus PADR[2:0], a read/write strobe PRW, and a request-grant pair PBREQ—PBGNT. The interface uses TCK (see Table 1) for synchronization of all transactions. TCK is continually clocked while the parallel debug interface is enabled.

[0069] The parallel port 214 is enabled by setting DCSR:3 to logic 1 via the serial port of the JTAG TAP controller 204. The serial port interface is not disabled when the parallel port is enabled and has mandatory usage for access while the processor core 104 is executing instructions. Any transaction started on the parallel port 214 completes on the parallel parallel port 214. Similarly, any transaction begun on the serial port of the JTAG TAP controller 204 also completes on the serial port.

[0070] All input signals to the parallel port 214 are sampled on the rising edge of TCK. All output signals are changed on the falling edge of TCK.

[0071] Referring to FIG. 6, a timing diagram illustrates three complete bus cycles of signal behavior for acquisition and release of a parallel debug bus PDATA[15:0] and PADR[2:0]. Because pins are shared between the parallel port 214 and the DEBUG trace port 220, parallel port transmission commands are initiated only while the processor core 104 is stopped and the DEBUG trace port 220 is disconnected from the shared bus. A request-grant handshake pair of signals PB REQ/PB GNT are supplied to expedite turnaround of the shared bus signals between the DEBUG trace port 220 and the parallel port 214. When the host system 111 interface to the parallel port 214 determines that PBREQ is asserted high, the host system 111 is to begin driving the parallel port 214 signals and assert PBGNT. When PBREQ is deasserted, the host system 111 interface to the parallel port 214 responds by tri-stating host system 111 interface signals and deasserting PBGNT to indicate that the host system 111 interface is isolated from the bus. To prevent bus contention, devices driving the parallel port 214 are tri-stated whenever PBGNT is deasserted.

[0072] The PBREQ signal is asserted immediately after the debug mode entry when the parallel port is enabled and is deasserted after exiting the debug mode. When PBREQ is deasserted the CMDACK is not yet asserted until the PBGNT is deasserted. The parallel port 214 host interface responds to the PBREQ deassertion by tri-stating the parallel port 214 drivers and deasserting the PBGNT signal. The parallel port 214 controller then activates the DEBUG trace port pin drivers in the debug trace port 220, asserts the CMDACK signal, and returns control of the debug trace port 220 interface to the trace control circuit 218.

[0073] In FIG. 6, the abbreviations are as follows: WDATA=Write Data; READ=Read Data; WCMD=Write Command; RCMD=Read Command; and Trace=Instruction Trace Record. Host_lat_data is an illustrative signal showing when the host system latches read data. Tar_lat_data is an illustrative signal showing when the parallel port controller latches host data/commands and processor data. Host_sample_CMDACK is an illustrative signal showing when the host system samples CMDACK. Cycle_type is an illustrative signal showing the types of parallel bus cycles occurring in the diagram. PRW and PADR[1:0] must be driven stable on any rising TCK edge on which PBGNT is asserted. If PBGNT is asserted and PRW is low, PDATA[15:0] must also be driven stable on all rising edges of TCK.

[0074] For the Register Read command the register address is supplied in the debug data register. The command should be preceded by the register address. These cycles are not shown in the timing diagram. These cycles are similar to the WDATA cycles shown for low 16-bits and high 16-bits for the WCMD. For memory Read operation the command is preceded by only low 16-bit WATA cycles.

[0075] Referring to FIG. 7, a flow chart depicts a parallel debug port interface protocol followed by the host system 111 during communications via the parallel port 214. Address pins PADR[2:0] select the field of the 38-bit internal debug register that is mapped to the 16-bit data bus PDATA[15:0]. The field is selected from among a null selection, the right 16 bits of debug data, the left 16 bits of debug data, and a four-bit command register (PDATA[3:0]). The internal pending flag (P) is automatically set when performing a write operation to the 4-bit command register, and is cleared when the Finished flag (F) is asserted. The host system 111 typically monitors the CMDACK pin to determine when the Finished flag (F) is asserted. On read cycles, PADR is set to 000 for one clock cycle before and after reading data to allow for bus turn-around.

[0076] The soft-address register should be loaded with values using load soft address register command to point to the various internal registers in the DEBUG Registers 210. The 38-bit serial register is accessible only via the serial/parallel debug interface. Some of the commands use bits from the debug data field as a sub-field to extend the number of available commands. Table 3 is a map of available functions.

[0077] The Load Soft Address register command places a new 32-bit value for the soft address pointer in the debug data[31:0] field in combination with the command code and the pending bit (P). Debug logic transfers the data to the Soft Address register and asserts the Finished flag (F) and the CMDACK signal.

[0078] The Memory or I/O read or write command is issued following a command that sets an address and port designation in the Soft Address register. For a read command, data is transferred directly to the debug data register when the Finished flag (F) and CNDACK pin is set. For a write command, data is supplied in the debug data register in combination with the command in the Debug Command register. The address is postincremented by the appropriate size for any read/write transfer to allow block transfers without continually setting up the Soft Address. On memory accesses of a microcontroller with multiple physical memory spaces, the appropriate chipset mapping registers are set prior to issue of the access command. Memory accesses occur as data accesses. A memory access is directed either to normal memory space or SMM space based on the setting of the SMMSP bit in the DCSR register.

[0079] Issue of a General or Serial/parallel Debug Register Read command includes designation of a register address in the debug data register in combination with identification of the command in the Debug Command register. The address is transferred to the Soft Address register as a side effect to simplify read/modify/write setting of individual bits, and the register contents are transferred directly to the debug data register when the Finished flag/CMDACK pin is set.

[0080] For a General or Serial/parallel Debug Register Write command, the Soft Address is used to hold the register address. The soft address is set up with a previous Read Register or Load Soft Address command. The data to be written is supplied in the debug data register in combination with the command in the Command register.

[0081] The Read Trace Record command implements read access to the 256-record internal trace buffer 200 when the internal instruction trace configuration is selected. The read trace record command is not applicable to an external trace configuration since all trace record data is output to the bond-out DEBUG trace port upon generation. The read trace record command is invoked by setting bit 0 of the Instruction Trace Configuration Register (ITCR) to logic 1 to enable the instruction trace buffer 200, then the internal trace configuration is selected by setting bit 3 of the ITCR register to 0.

[0082] The Read Trace Record command reads the 21-bit trace record at the displacement given in the soft address register, places the record in bits 20:0 of the debug data register and asserts the finished flag and CMDACK pin. The soft address register is post-incremented so that a subsequent read retrieves the next location in the buffer in reverse order of history. A read operation from displacement 0 retrieves the most recent trace record. A read operation from displacement 255 retrieves the oldest trace record in the buffer. When the instruction trace buffer 200 is read, the valid bit on each record is to be checked. If the valid bit of a record is zero, an event that occurs only when one or more of the 256 locations of the buffer is not loaded with trace record data since last initialized, the record should be discarded. The trace buffer 200 wraps around and continually overwrites the oldest data when full. Once the buffer has wrapped around, all valid bits are set, and are cleared only when the TINIT bit (bit 2) in the Instruction Trace Configuration Register is set.

[0083] The Peripheral reset command sends a reset signal to all system logic except the processor core 104 to be pulsed active and released. The peripheral reset command allows peripheral logic to be reinitialized without resetting the processor core 104.

[0084] A command to enter or exit Debug mode enables and disables debug functionality. Debug functions are enabled by writing the DEBUG instruction to the JTAG TAP controller. When a DEBUG instruction is received, the debug serial port register is enabled to receive commands. While the processor is executing instructions only the Debug Control/Status register, Instruction trace configuration register, SOFT_ADDR register, RX_DATA, and TX_DATA registers are accessed through the serial interface. All serial debug registers become accessible when the processor has stopped. The processor may be stopped (forced into debug mode) by one of the following methods:

[0085] Setting bit 1 of the Debug ControlStatus register (DCSR)

[0086] Pulsing the BRTC pin (low-to-high transition)

[0087] Via legacy processor core 104 debug registers DRO-DR3 after setting bit 4 of the Debug Control/Status register (DCSR). Single stepping with the TF bit set causes entry to debug mode when DCSR bit 4 is set. Moving to and from debug registers with the bit 12 of DR7 set causes entry to debug mode when DCSR bit 4 is set.

[0088] Executing a EDEBUG instruction. Inserting a EDEBUG instruction into the code stream enters debug mode at a specific, arbitrary point in source code. The processor core 104 is set in debug mode (DEBUG instruction is automatically written to the TAP controller). The EDEBUG instruction causes an invalid opcode execution if bit 12 of DR7 is not set.

[0089] The external pin STOPTX or bit 7 of the Debug Control/Status register (DSCR) is optionally monitored to determine when the processor enters debug mode. The flushing of cache on entry to debug mode is controlled by the DISFLUSH bit of DCSR. If the bit is reset the cache is flushed (using the SLE486 FLUSH pin) upon entry to debug mode. If the bit is set the cache is not flushed on entry to debug mode. On receipt of the STOPTX signal, either by sampling debug of the STOPTX pin or by polling DCSR bit 7, the host system 111 starts writing commands.

[0090] Debug mode is exited through command 0111. The exit options include:

[0091] Exit and begin execution at current value of EIP. In one example, the processor jumps to a section of patch code. A breakpoint is set at the end of the patch code to enable reentry to debug mode. In another example, the processor state is restored to the original debug entry state, using the general register write commands, before exiting.

[0092] Exit and perform a single instruction step. The processor executes a single instruction, takes a trap, and reenters debug mode.

[0093] Exit via a hard reset. A hard CPU reset is asserted immediately.

[0094] Exit via a soft reset.

[0095] The X86 Enhanced Software debug mode supplies a trace and breakpoint interrupt debug functionality on the processor core 104 without inclusion of external debug hardware. The mode is enabled by setting DR7 bit 12. The serial interface does not need to be enabled. When the X86 Enhanced Software debug mode is enabled, access and control of the instruction trace buffer 200 and the ITCR (Instruction Trace Control Register) are supplied through a set of reserved instructions. The instructions cause an illegal opcode exception if executed when DR7 bit 12 is not set.

[0096] Debug control and status is configured by setting the Debug Control/Status Register (DCSR) through the Serial/Parallel debug interface, using the serial/parallel debug registers read/write command, address 00. DCSR control and status bits are described, as follows:

[0097] Bit 0 (FRESET) is a reset bit allowing the host system 111 to completely reset all devices on the target system 101 other than the Serial/Parallel controller. FRESET is useful in the event of a total target system crash.

[0098] Bit 1 (FBRK) is a register version of the BRTC pin. The host system 111 writes a 1 followed by a 0 to FBRK to force a break into debug mode at the next instruction boundary following synchronization of the received command with the internal processor clock.

[0099] Bit 2 (DSPC) is a processor clock disable bit for disabling the stopping of internal processor clocks that normally occurs when entering Halt and Stop Grant states. DSPC allows the processor to continue to respond to break requests while halted or in the Stop Grant state.

[0100] Bit 3 (PARENB) is a parallel port enable bit that enables the auxiliary parallel data port. PARENB is not set on non bond-out versions of the target system 101.

[0101] Bit 4 (DBTEN) is a debug trap enable bit that causes entry into a hardware debug mode for all debug traps/faults of the processor core 104 that otherwise cause a software INT1. The trace mode on/off toggling control in the ITCR has priority over DBTEN in that breakpoints mapped for trace mode on/off toggling are not affected by setting of DBTEN.

[0102] Bit 5 (BRKMODE) is a bit for controlling entry into debug mode. BRKMODE allows a developer to change the functionality of the BRTC pin to become an external control for enabling and disabling the trace capture operation. When the JTAG TAP controller 204 Instruction Register is programmed with a DEBUG instruction, the BRTC pin causes the processor core 104 to stop executing an instruction sequence and enter debug mode. Setting of the BRKMODE pin causes the BRTC pin to control activation of the trace capture operation. The trace capture status is designated by the TRON bit of the ITCR.

[0103] Bit 6 (FRCRDY) is a bit that controls forcing the RDY signal to the processor that is active to enable the processor to move on to the next bus cycle in cases where a bus operation to an undefined memory or I/O space has occurred in the absence of a subtractive decode agent. Use of FRCRDY is to be coordinated with chipset logic.

[0104] Bit 7 (STOP) is a stop bit that supports a software technique for checking, the state of the STOPTX pin. When STOP reads back high, the processor is in debug mode and all debug commands are enabled.

[0105] Bit 8 (SMMSP) is an SM control bit that allows memory accesses initiated through the debug port 100 to take place in the SMM space. When SMMSP is reset, memory accesses initiated through the debug port 100 apply to the normal memory address space. Setting Of SMMSP causes memory accesses initiated through the debug, port 100 to apply to the SLIM address space.

[0106] Bit 9 (DISFLUSH) is a control bit for controlling flushing, of a cache on entry to debug, mode. With DISFLUSH reset the cache is flushed on entry to debug mode. Setting DISFLUSH prevents the cache from flushing on entry to debug mode.

[0107] Bit 10 (RX) is a data received bit that indicates whether data has been received from the host system 111 so that the processor core 104 can read the data from the RX_DATA register.

[0108] Bit 11 (TX) is a data transmit bit that indicates the processor core 104 is ready to transmit data so that the host system 111 can read the data from the TX_DATA register.

[0109] Communication between an operating system (OS) and Applications via the JTAG Debug port 100 is initiated by the host system 111 writing the DEBUG instruction to the JTAG instruction register in the JTAG TAP controller 204. Writing of the DEBUG instruction causes the Serial Debug Shifter 212 to connect to the JTAG TDI-TD0 serial interface of the JTAG TAP controller 204. The serial debug port 100, includes two debug registers for transmitting (TX_DATA register) and receiving (RX_DATA register) data. TX_DATA and RX_DATA are accessed using the soft address and serial/parallel debug register commands.

[0110] The processor core 104 initiates a data transmission by first testing the read-only TX bit in the ITCR register. If the TX bit is set to 0 then the processor core 104 executes an X86 instruction to transfer the data to the TX_DATA register. The serial port 100 sets the TX bit in the DCSR and ITCR registers indicating to the host system 111 data is ready for transmission. The serial port 100 also sets the STOPTX pin to high. After the host system 111 completes reading the transmit data from the TX_DATA register, the TX bit is set to 0. A TXINTEN bit in the ITCR register, when set, generates a signal to interrupt the processor core 104. The interrupt is generated only when TX bit in the ITCR register makes a transition to 0.

[0111] The communication is accomplished by the host system 111 writing the DEBUG instruction to the JTAG instruction register in the JTAG TAP controller 204, causing the Serial Debug Shifter 212 to connect to the JTAG TDI-TDO serial interface. Two of the debug registers 210 are available in the serial debug port 100 for the processor core 104 to transmit (TX_DATA register) data and receive (RX_DATA register) data from the host system 111. The receive and transmit data registers are accessed using the soft address and serial/parallel debug register commands.

[0112] When the processor core 104 attempts to transmit the data, the processor core 104 first tests the TX bit in the ITCR register. If the TX bit is set to 0, the processor core 104 executes an X86 instruction to transfer the data to the TX_DATA register. The serial port 100 sets the TX bit in the DCSR and ITCR registers indicating to the host system 111 a readiness to transmit data, and asserts the STOPTX pin active high. After the host system 111 completes reading the transmit data from the TX_DATA register the TX bit is set to 0. A TXINTEN bit in the ITCR register, when set, generates a signal to interrupt the processor core 104. An output pin RXTX_INTR is used to assert the interrupt. The interrupt is generated only when TX bit in ITCR makes a transition to 0. The TXINTRSTATUS bit in the ITCR register is set to 1. The interrupt output pin RXTX_INTR is active high and remains active until the processor core 104 services the interrupt by reading the ITCR register. The processor core 104 detects that the TXINTRSTATUS bit set to 1 in the ITCR register and services the TX interrupt. At the end of the TX interrupt service the processor core 104 sets the TXINTRSTATUS bit to 0, acknowledging completion of service of the TX interrupt.

[0113] When the processor core 104 writes a 0 to the TXINTRSTATUS bit , logic of the serial port 100 updates the bit in the ITCR only if the processor core 104 has previously read a 1 value at the beginning of the service routine. The interrupt pin RXTX_INTR is deasserted after the processor core 104 sets the TXINTRSTATUS bit set to 0 in the ITCR register. When the TXINTEN bit is not set, the processor core 104 polls the ITCR register and monitors the TX bit to further transmit the data.

[0114] When the host system 111 at tempts to send data, the host system 111 first tests the RX biting the DCSR register. If RX bit is set to, then the host system 111 writes the data to the receive data (RX_DATA) register and the serial port 100 sets the RX bit to 1 in t he DCSR and ITCR registers. A RXINTEN bit in the ITCR register, when set, generates a signal to interrupt the processor core 104. An output pin RXTX_INTR is used to assert the interrupt. The interrupt is only generated when RX bit in the DCSR makes a transition to 1. The RXINTRSTATUS bit in the ITCR register is set to 1. The interrupt output pin RXTX_INTR is active high and remains active until the processor core 104 services the interrupt by reading the ITCR register. The processor core 104 detects that the RXINTRSTATUS bit set to 1 in the ITCR register and services the RX interrupt. At the end of the RX interrupt service, the processor core 104 sets the RXINTRSTATUS bit to 0, acknowledging completion of service for the RX interrupt.

[0115] When the processor core 104 writes a 0 to the RXINTRSTATUS bit, logic in the serial port 100 updates the bit in the ITCR only if the processor core 104 has previously read a 1 at the beginning of the service routine. The interrupt pin RXTX_INTR is deasserted only after the processor core 104 sets the RXINTRSTATUS bit set to 0 in the ITCR register. When RXINTEN bit is not set, the processor core 104 polls the ITCR register, monitors the RX bit, and if the RX bit is set to 1 the processor core 104 executes an X86 instruction to read the data from the receive data (RX_DATA) register. After the data is read by the processor core 104 from the RX_DATA register, the RX bit is set to 0 by the serial port 100. The host system 111 continuously reads the DCSR register and monitors the RX bit to further send the data.

[0116] Both the RX and TX bits can be set concurrently. If so, the RXTX_INTR interrupt output is asserted. The host system 111 might complete reading the TX_DATA register when the processor core 104 is servicing the RX interrupt. For interrupt controllers that are edge sensitive, a problem occurs because the RXTX_INTR output signal is not asserted for the pending TX interrupt after the RX interrupt is serviced. To overcome the problem, a FRCDISINTR bit is defined in the ITCR register. If the interrupt controller logic is level sensitive, the FRCDISINTR bit need not be used. The FRCDISINTR bit is utilized because of the sharing of the RX and TX interrupts on one output RXTX_INTR pin. When the processor core 104 begins servicing of the interrupt because of the RXTX_INTR pin going active, the processor core 104 sets FRCDISINTR bit to 1 at the beginning of the service routine. At the end of the service routine, the processor core 104 sets the FRCDISINTR bit to 0. If an interrupt is pending during the service routine, the interrupt is disabled and then immediately activated when the FRCDISINTR bit is set 0, in turn causing the RXTX_INTR output signal to go active. The processor core 104 then services the pending interrupt. The RXTX_INTR output signal is asynchronous and remains active until the processor core 104 services the interrupt and sets the TXINTRSTATUS or RXFNTRSTATUS bit to 0.

[0117] The RX and TX bits in the DCSR and ITCR are read-only bits. The serial port 100 sets and resets the bits. The RXINTRSTATUS, TXINTRSTATUS, and FRCDISINTR bits in the ITCR are read-only bits for the host system 111. The processor core 104 and serial port 100 write the RXINTRSTATUS, TXINTRSTATUS, and FRCDISINTR bits.

[0118] The ITCR register controls enabling/disabling and configuration of Instruction Trace debug functions. The ITCR register is accessed through the serial/parallel debug register write/read commands, at location 01, or via the reserved instruction MOV ITCR.

[0119] The host system 111 sends data to the processor core 104 by first testing the read-only RX bit in the DCSR register. If the RX bit is set to 0, then the host system 111 writes the data to the receive data (RX_DATA) register and the serial port 100 sets the RX bit to 1 in the DCSR and ITCR registers. The RXINTEN bit in the ITCR register, when set, generates a signal to interrupt the processor core 104. The interrupt is only generated when RX bit in the DCSR makes a transition to 1. When the RXINTEN bit is not set, the processor core 104 polls the RX bit of the ITCR register. If the RX bit is set to 1, the processor core 104 executes an X86 instruction to read the data from the receive data (RX_DATA) register. After data is read by the processor core 104 from the RX_DATA register, the RX bit is set to 0 by the serial port 100. The host system 111 continuously reads the DCSR register and monitors the RX bit to continue sending data.

[0120] Referring to FIG. 8, a schematic state diagram illustrates operating states of the pending/finished state machine 224. The 38-bit serial register in the serial debug port shifter 227 operates as a serial command interface including the 32-bit data field, the 4-bit command, the command pending flag (P), and the command finished flag (F). The 32-bit data, 4-bit command, and the pending flag are shifted serially into the 38-bit serial shift register using the shift-DR state in the JTAG TAP controller. When the TAP controller enters the Update-DR state the 38-bit data is loaded into the internal data and command registers. The command pending flag is set. For commands that do not include a data transfer, bits in the data field are set to 0. The pending/finished state machine 224 enters and Idle state (state=0) 800 immediately after the TRST_L JTAG input signal is asserted (See the JTAG standard signals designated in TABLE I). After shifting the 38-bit data, when the JTAG TAP controller 204 is in the Update-DR state and the pending flag is set (P=1), the state machine enters Cycle Pending state (state=1) 801.

[0121] The pending/finished state machine 224 transitions to a Cycle Finished state (state=2) 802 when the JTAG TAP controller 204 is in the Capture-DR state and an indication occurs that the previous command is completed. The 38-bit serial debug shifter 227 is loaded with the 32-bit output data, the finished flag is set to 1 (F=1), and the command field cmd[3:0] (4′b0000) and the pending flag are set to 0.

[0122] When the pending/finished state machine 224 is in the Cycle Finished state 802, the JTAG TAP controller 204 is in the Update-DR state, and the Pending Flag is set to 1 (P=1), then the pending/finished state machine 224 transitions to the Cycle Pending State(state=1) 801. Signals that set the finished flag (F) and pending flag (P) in the 38-bit shifter are set to 0 and 1, respectively. If the JTAG TAP controller 204 is in the Update-DR state and the Pending Flag is set to 0 (P=0), then the pending/finished state machine 224 transitions to the Idle State (state=0) 800. Signals that set the finished flag (F) and pending flag (P) are set to 0. Otherwise, the pending/finished state machine 224 in the Cycle Finished state 802. Signals that set the finished flag (F) and pending flag (P) are set to 1 and 0, respectively.

[0123] Referring to FIG. 9, a schematic state diagram depicts operating states of the debug port state machine 206. The debug port state machine 206 interfaces with the pending/finished state machine 224, the parallel port state machine 226, the processor interface state machine 202, and the command decode and processing block 208. The debug port state machine 206 generates output signals for command decoding and generates debug register clock signals for register write operations. The debug port state machine 206 issues a signal to the parallel port state machine 226 and the pending/finished state machine 224 when the command is completed.

[0124] A JTAG reset, a reset of the JTAG TAP controller 204, is generated by a TRST_L signal of the standard JTAG signals. Upon a JTAG reset, the debug port state machine 206 enters a Not JTAG Debug State (state=0) 900. When the host system 111 writes a DEBUG private instruction to the JTAG instruction register using the Capture-IR—Update IR sequence shown in the JTAG TAP controller state machine shown in FIG. 3, a JTAG debug instruction state variable is set to 1 and the debug port state machine 206 transitions to a JTAG Debug Mode state (state=1) 901.

[0125] In the JTAG Debug Mode state 901, if the Pending flag is set (P=1), the TAP controller state in the previous cycle was Update-DR, and the JTAG debug instruction state variable is equal to 1, then the debug port state machine 206 transitions to a Decode 1 state (state=3) 903. and sets a JTAG decode output signal to 1. If the processor core 104 is in a debug mode so that a Debug Mode TCK signal is asserted and the JTAG debug instruction state variable is asserted, then the debug port state machine 206 transitions to a Debu g Active state (state=2) 902 and sets a debug acknowledge TCK output signal to 1 with the finished flag (F) holding, to the same value as in the previous state. If the JTAG debug instruction state variable is equal to 0, then the debug port state machine 206 transitions back to the Not JTAG Debug State (state=0) 900.

[0126] When the debug port state machine 206 is in the Debug Active state 902, several state transitions are possible. If a command is written either through the JTAG TAP controller 204 or the parallel port 214, and the processor core 104 is in the debug mode so that the Debug Mode TCK signal is asserted, the debug port state machine 206 transitions to a Decode 2 state (state=4) 904. Upon entering, the Decode 2 state 904, the e JTAG decode output signal is set to 1 and the debug acknowledge TCK signal is set to 1, acknowledging entry to the debug mode to the parallel port state machine 226. If the processor core 104 leaves the debug mode which is indicated by the Debug Mode TCK signal being deasserted to 0, then the debug port state machine 206 transitions back to the JTAG Debug Mode state 901 and the output Finished flan (F) is set to the previous value. If the debug port state machine 206 transitions to the Debug Active state 902 from a CPU Trace Command Wait state (state=5) 905, then a parallel port acknowledge signal is asserted to 1 and the finished flag is asserted (F=1). The parallel port acknowledge signal is an acknowledgment to the parallel port state machine 226 indicating that t the previous CPU/TRACE command has completed execution.

[0127] In the Decode1 state 903, the debug port state machine 206 transitions to a Register Write state (state=6) 906 in the next clock cycle and sets a JTAG decode output signal to 1 indicating for the command decode and processing block 208 to decode the received command. Also in the transition to the Register Write state 906, the parallel port acknowledge signal is asserted to 1, the debug acknowledgment TCK signal retains the value of the previous cycle, a serial debug port (SDP) register write TCK clock signal is asserted to 1, and the finished flag is asserted (F=1).

[0128] In the Decode2 state (state=4) 904, if the command decoded by the command decode and processing block 208 is a CPU command or a serial trace read command, the debug port state machine 206 transitions to the CPU Trace Command Wait state (state=5) 905, the JTAP decode output signal is asserted to 1, and the debug acknowledgment TCK signal retains the value of the previous cycle. If the decoded command is not a CPU command or a serial trace read command, the debug port state machine 206 transitions to the Register Write state 906 and the JTAG decode output signal is asserted to 1, the parallel port acknowledge signal is asserted to 1, the debug acknowledgment TCK signal retains the value of the previous cycle, the serial debug port (SDP) register write TCK clock signal is asserted to 1, and the finished flag is asserted (F=1).

[0129] When the debug port state machine 206 is in the CPU Trace Command Wait state (state=5) 905 waiting for the CPU command or the serial trace command to complete and if a CPU command done TCK signal is asserted to 1, then the debug port state machine 206 transitions to the Debug Active state 902. In the transition to the Debug Active state 902, the debug acknowledgment TCK signal is asserted to 1, the finished flag is asserted (F=1), and the parallel port acknowledge signal is asserted to 1.

[0130] In the Register Write state 906, if the serial debug port register write feedback signal is asserted to 1 and the processor core 104 is in the debug mode so that the Debug Mode TCK signal is asserted, then the debug port state machine 206 transitions to the Debug Active state 902. The asserted serial debug port register write feedback signal indicates that the clock signal for the register writes was generated. If the serial debug port register write feedback signal is asserted to 1 and the processor core 104 is not in the debug mode (the Debug Mode TCK signal is deasserted to 0), then the debug port state machine 206 transitions to the JTAG Debug mode state 901 and the finished flag (F) retains the previous value.

[0131] Referring to FIG. 10, a schematic state diagram depicts operating states of the parallel port state machine 226. The parallel port state machine 226 reads data and commands from the parallel port 214 and establishes a request-grant handshake between the host system 111 and the target system 101. The parallel port state machine 226 communicates with the debug port state machine 206 when the command is read from the parallel port 214, as is indicated by a Parallel update signal that is asserted to 1. The debug port state machine 206 asserts the parallel port acknowledge signal to 1 when the CPU command or serial trace read command is completed. The parallel port state machine 226 also generates pad control signals from the parallel port lines CI_PDATA[15:0] and CI_PADR[2:0]. The parallel port state machine 226 generates a command acknowledge CO_CMDACK signal.

[0132] The parallel port state machine 226 enables pads CI_PDATA[15:0], CI_PADR[2:0], and CI_PRW for generating output signals when a breakpoint request CO_PBREQ signal is deasserted to 0 and the command acknowledge CO_CMDACK signal is asserted to 1. Trace data[19:0] is transmitted on the 20-bit bus formed by the CI_PDATA[15:0] and CI_PADR[2:0], and CI_PRW signals. When the parallel port 214 is enabled the CI_PDATA[15:0] is used for sending output signals when CI_PRW=1. When CI_PRW=0, the 20-bit bus it is used as an input bus.

[0133] The parallel port state machine 226 transitions to an Idle state (state=0) 1000 under several conditions. The parallel port state machine 226 enters the Idle state 1000 when a JTAG Test Reset signal is asserted to 1, when the parallel port enable (PARENB) signal is 0 in the Debug Registers 210, or when the JTAG debug instruction state variable is 0. In the Idle state 1000, an output signal tri_pdata that is used for pad control of the parallel lines CI_PDATA[15:0] is deasserted to 0 so that the port CI_PDATA[15:0] is enabled as input to the parallel port 214. The parallel port state machine 226 operates using several state variables. For example, an output signal sel_d t_leo is used as a multiplexer select between usage of the parallel port 214 as the data bus and as the trace bus. A command acknowledge signal cmdack_out indicates that a parallel port command is complete. A CO_CMDACK signal designates a logical-OR condition of the command acknowledge output signal cmdack_out and the finished flag (F). A signal low_data_up is used for latching the lower sixteen bits of data on the parallel port 214. A signal up_data_up is used for latching the upper sixteen bits of data on the parallel port 214. A parallel port read select signal par_read_sel is used to select an upper or lower word when the processor core 104 reads data using the parallel port 214. In the Idle state 1000, the output signal sel_d_t_leo is deasserted to 0, the CO_PBREQ is deasserted to 0, the low_data_up signal and the up data up signal are deasserted to 0, and the par_read_sel signal is deasserted to 0.

[0134] In the Idle state 1000, if the parallel port enable (PARENB) signal is asserted to 1 and the debug acknowledgment TCK signal is asserted to 1, then the parallel port state machine 226 transitions to a parallel port mode state (state=1) 1001. Command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ are asserted to 1. Parallel bus read select, upper order data select, and lower order data select output signals, respectively, par_read_sel, up_data_up, and low_data_up are deasserted to 0. Up_data_up and low_data_up signals from the previous cycle are latched and used to generate a pulse that is used to latch the upper or lower 16-bits of parallel port data into 1 data in[15:0] and udata_in[15:0] registers.

[0135] In the parallel port mode state 1001, the parallel port state machine 226 waits for the host system 111 to write data and commands, or read data from the target system 101. If the host system 111 asserts a parallel bus grant signal (CI_PBGNT=1) and the parallel address bits are deasserted (CI_PADR=2'b00), the parallel port state machine 226 transitions to a Grant Mode state (state=2) 1002 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1.

[0136] Also in the parallel port mode state 1001, if the host system 111 asserts the parallel bus grant signal (CI_PBGNT=1) but deasserts the parallel read/write signal (CI_PRW=0), and the parallel address bits are set to CI_PADR=2'b01, then the parallel port state machine 226 transitions to a Wait State (state=5) 1005 and asserts the parallel bus request (CO_PBREQ=1) indicating that the host system 111 has completed writing the command.

[0137] Also in the parallel port mode state 1001, if the host system 111 asserts the parallel bus grant signal (CI_PBGNT=1) but deasserts the parallel read/write signal (CI_PRW=₀), and the parallel address bits CI_PADR are set to either 2'b10 or 2'b11, then the parallel port state machine 226 transitions to a parallel read mode state (state=3) 1003 and asserts the command acknowledge and the parallel bus request (CO_CMDACK=1 and CO_PBREQ=1). In the transition to the parallel read mode state 1003, if the parallel address bits CI_PADR are 2'b10, the parallel port state machine 226 asserts the upper order 16-bit data transfer signal (up data up=1). If the parallel address bits CI_PADR are 2'b11, the parallel port state machine 226 asserts the lower order 16-bit data transfer signal (low data up=1).

[0138] Also in the parallel port mode state 1001, if the host system 111 asserts the parallel bus grant signal and the parallel read/write signal (CI_PBGNT=1 and CI_PRW=1), and the parallel address bits CI_PADR are set to either 2'b10 or 2'b11, then the parallel port state machine 226 transitions to a parallel write mode state (state=4) 1004 and asserts the command acknowledge and the parallel bus request (CO_CMDACK=1 and CO_PBREQ=1). In the transition to the parallel write mode state 1004, if the parallel address bits CI_PADR are 2'b10, the parallel port state machine 226 asserts the parallel read select (par_read_sel=1) indicating to multiplex the high-order 16-bits of data to the host system 111 on PDATA[15:0] bus. If the parallel address bits CI_PADR are 2'b11, the parallel port state machine 226 deasserts the parallel read select (par_read_sel=0) indicating to multiplex the low-order 16-bits of data to the host system 111 on PDATA[15:0] bus.

[0139] Also in the parallel port mode state 1001, if the debug acknowledgment TCK signal is deasserted to 0 indicating that the CPU is not in the debug mode, the parallel port state machine 226 transitions to the Idle state 1000, deasserting the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 0, and deasserting the parallel read select, upper order data, and lower order data signals par_read_sel=0, up_data up=0, and low_data_up=0, respectively.

[0140] In the Grant Mode state 1002, if the host system 111 deasserts the parallel bus grant signal CI_PBGNT=0, then the parallel port state machine 226 transitions to the parallel port mode state 1001 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. Also in the Grant Mode state 1002, if the debug acknowledgment TCK signal is deasserted to 0, the parallel port state machine 226 transitions to a DONE state (state=7) 1007 and deasserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 0, as well as deasserting the parallel read select, upper order data, and lower order data signals, respectively, par read sel, up data up, low_data_up, to 0.

[0141] Also in Grant_mode state 1002, if the parallel port read/write select signal CI_PRW is deasserted to 0 and the parallel port address CI_PADR selects 2'b01, then the parallel port state machine 226 transitions to a Wait state (state=5) 1005 and the parallel bus request CO_PBREQ is asserted to 1 and CO_CMDACK is set to 0. Otherwise in the Grant Mode state 1002, if the parallel port read/write select signal CI_PRW is deasserted to 0 and the parallel port address CI_PADR selects either 2'b10 or 2'b11, then the parallel port state machine 226 transitions to the parallel read mode state (state=3) 1003. In the transition to the parallel read mode state (state=3) 1003, the parallel port state machine 226 asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. If the parallel address bits CI_PADR are 2'b10, the parallel port state machine 226 asserts the upper order 16-bit data transfer signal (up_data_up=1). If the parallel address bits CI_PADR are 2'b11, the parallel port state machine 226 asserts the lower order 16-bit data transfer signal (low_data_up=1).

[0142] Also in Grant Mode state 1002, if the parallel read write select CI_PRW is asserted to 1 and the parallel port address CI_PADR is not equal to 2'b00, then the parallel port state machine 226 transitions to the parallel write mode state 1004 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. In the transition to the parallel write mode state 1004, if the parallel address bits CI_PADR are 2'b10, the parallel port state machine 226 asserts the parallel read select (par_read sel=1) indicating to multiplex the high-order 16-bits of data to the host system 111 on PDATA[15:0] bus. If the parallel address bits CI_PADR are 2'b11, the parallel port state machine 226 deasserts the parallel read select (par_read sel=0) indicating to multiplex the low-order 16-bits of data to the host system 111 on PDATA[15:0] bus.

[0143] In the parallel read mode state 1003, if the host system 111 deasserts the parallel bus grant signal CI_PBGNT to 0, then the parallel port state machine 226 transitions to the parallel port mode state 1001 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. Otherwise in the parallel read mode state 1003, if the host system 111 sets the parallel port address to 2'b00, then the parallel port state machine 226 transitions to the Grant Mode state 1002 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. Otherwise in the parallel read mode state 1003, if the host system 111 sets the parallel port address to 2'b01, then the parallel port state machine 226 transitions to the Wait state 1005 and asserts the parallel bus request output signal CO_PBREQ to 1.

[0144] In the parallel write mode state 1004, if the host system 111 deasserts the parallel bus grant signal CI_PBGNT to 0, then the parallel port state machine 226 transitions to the parallel port mode state 1001 and asserts the command acknowledge and parallel bus request output signals CO_CMNDACK and CO_PBREQ to 1. Otherwise in the parallel write mode state 1004, if the host system 111 sets the parallel port address to 2'b00, then the parallel port state machine 226 transitions to the Grant Mode state 1002 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. Otherwise in the parallel write mode state 1004, if the host system 111 deasserts the parallel read write select CI_PRW to 0 and sets the parallel port address to either 2'b10 or 2'b11, then the parallel port state machine 226 transitions to the parallel read mode state 1003 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. If the parallel address bits CI_PADR are 2'b10, the parallel port state machine 226 asserts the upper order 16-bit data transfer signal (up_data_up=1). If the parallel address bits CI_PADR are 2'b11, the parallel port state machine 226 asserts the lower order 16-bit data transfer signal (low_data_up=1).

[0145] In the Wait state 1005, if the host system 111 deasserts the parallel bus grant signal CI_PBGNT to 0, then the parallel port state machine 226 transitions to the parallel port mode state 1001 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO PBREQ to 1. Otherwise in the Wait state 1005, if the host system 111 sets the parallel port address CI_PADR to 2'b00, then the parallel port state machine 226 transitions to the Grant Mode state 1002 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. Otherwise in the Wait state 1005, if the parallel port acknowledge signal is 1, then the parallel port state machine 226 transitions to an Exit state (state=6) 1006 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_BREQ to 1.

[0146] In the Exit state 1006, if the debug acknowledgment TCK signal is equal to 0, then the parallel port state machine 226 transitions to the Idle state 1000 and deasserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 0. Also in the transition to the Idle state 1000, the parallel port state machine 226 deasserts the parallel read select, upper order data, and lower order data signals, respectively par read_sel, up data up, and low data up, to 0. Also in the Exit state 1006, if the host system 111 deasserts the parallel bus grant signal CI_PBGNT to 0, then the parallel port state machine 226 transitions to the parallel port mode state 1001 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1. Otherwise in the Exit state 1006, if the host system 111 asserts the parallel bus grant signal CI_PBGNT to 1 and if debug acknowledgment TCK signal is asserted to 1, the parallel port state machine 226 transitions to the Grant Mode state 1002 and asserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_PBREQ to 1.

[0147] In the Done state 1007, the parallel port state machine 226 waits for a deasserted parallel bus grant signal CI_PBGNT from the host system 111. When the host system 111 deasserts the parallel bus grant signal CI_PBGNT to 0, the parallel port state machine 226 transitions to the Idle state 1000 and deasserts the command acknowledge and parallel bus request output signals CO_CMDACK and CO_BREQ to 0, as well as deasserting the parallel read select, upper order data, and lower order data signals, respectively par_read_sel, up_data_up, and low_data_up, to 0.

[0148] Referring to FIG. 11, a schematic state diagram depicts operating states of the processor interface state machine 202. The processor interface state machine 202 interfaces to the processor core 104 and operates at the same frequency as the processor core 104. The processor interface state machine 202 also interfaces to the trace control circuit 218 and performs several functions. For example, the processor interface state machine 202 take appropriate actions for commands that are decoded by the command decode and processing block 208. The processor interface state machine 202 generates multiplexer control signals for multiplexing data for read operations of the processor core 104 including selection of read operations directed to the RX_DATA[31:0] register, the trace record[20:0], the ITCR[31:0] register, the soft_address[31:0] register, the command[3:0] including upper-order data udata_in[15:0] and lower-order data Idata_in[15:0].

[0149] The processor interface state machine 202 generates write strobe signals for writing the data from the processor core 104 to the ITCR[31:0] register, the TX_DATA[31:0] register, and the read_data[31:0] register. Data from the read_data register is read by the host system 111. For example, if the host system 111 requests a read operation from an EAX register in the processor core 104, data from the processor core 104 is placed in the read_data register that is eventually read by the host system 111. If the host system 111 reads the data using the JTAG TAP controller 204 and the JTAG TAP controller state machine is in capture-DR state (see FIG. 3), data from the read_data register is transferred to a shifter[37:6] register in the serial debug shifter 227. If the host system 111 uses the parallel port 214, data from the read_data register is placed onto the PDATA[15:0] bus.

[0150] The processor interface state machine 202 indicates to the trace control circuit 218 information regarding a serial trace read from a designated address in the soft address register. When the trace control circuit 218 completes reading of the trace data, the processor interface state machine 202 generates a command finished signal (cmd_done) to the debug port state machine 206 and generates a write strobe signal for read_data register.

[0151] The processor interface state machine 202 enters an Idle State (state=0) 1100 following a CPU_reset signal from the processor core 104. The command decode and processing block 208 decodes CPU commands and sends appropriate signals to the processor interface state machine 202. In the Idle State 1100, if the processor core 104 writes a DEBUG ACTIVATE command the processor interface state machine 202 remains in the Idle State 1100 and asserts the Debug Mode TCK output signal to 1, indicating that the processor core 104 is in debug mode. The Debug Mode TCK signal is used by the debug port state machine 206 to generate an acknowledgment signal.

[0152] In the Idle State 1100, if the processor core 104 writes a DEBUG INACTIVATE command the processor interface state machine 202 remains in the Idle State 1100 and deasserts the Debug Mode TCK output signal to 0, indicating that the processor core 104 has exited debug, mode.

[0153] In the Idle State 1100, if the processor core 104 writes the READ ITCR REGISTER command the processor interface state machine 202 transitions to a Data Read Processor State (state 1) 1101 and sets a processor output select cpu_out_sel[2:0] output signal to 3'b010. The processor output select control the multiplexer for sending data to the processor core 104.

[0154] In the Idle State 1100, if the processor core 104 sends the WRITE ITCR REGISTER command the processor interface state machine 202 transitions to a Write Processor TX ITCR Register state (state=5) 1105 and asserts an ICTR register write signal itcr_wr_str to 1 and asserts a multiplexer control signal data_in_mux cntl to 1. The ITCR register write signal itcr_wr_str is used to write the CPU data to the ITCR register. The multiplexer control signal data_in_mux_cntl is used to control a 2:1 multiplexer 1534 which is used for multiplexing processor data and serial port data.

[0155] In the Idle State 1100, if the processor core 104 writes a READ DEBUG DATA command the processor interface state machine 202 transitions to the Data Read Processor State 1101 and sets the processor output select cpu_out_sel[2:0] signal to 3'b01. The processor output select cpu out_sel value of 3'b011 multiplexes upper order and low order data, respectively udata_in[15:0] and ldata_in[15:0], to the processor core 104.

[0156] In the Idle State 1100, if the processor core 104 writes the READ DEBUG COMMAND the processor interface state machine 202 transitions to the Data Read Processor State 1101 and sets the processor output select cpu_out_sel[2:0] signal to 3'b100. The processor output select cpu_out_sel value of3'b100 multiplexes command cmd[3:0] register data to the processor core 104.

[0157] In the Idle State 1100, if the processor core 104 writes a WRITE DEBUG DATA command the processor interface state machine 202 transitions to the Data Write Processor State (state=3) 1103 and asserts a multiplexer select udb_data_reg_wr_enb signal to 1, controlling a multiplexer 1530 to select the processor data for writing to the read reg[31:0] register.

[0158] When the processor interface state machine 202 is in the Idle State 1100 and the processor core 104 writes a READ SOFT ADDRESS REGISTER command, the processor interface state machine 202 transitions to the Data Read Processor State 1101 and sets the processor output select cpu_out_sel[2:0] signal to 3'b101, multiplexing the soft_addr[31:0] register data to the processor core 104.

[0159] When the processor interface state machine 202 is in the Idle State 1100 and the processor core 104 writes a WRITE ITBUF N command or a POST ITBUF N command, the processor interface state machine 202 remains in the Idle State 1100. The trace control circuit 218 logic also reads the commands from the processor core 104 and appropriately decodes the commands and performs the requested operations.

[0160] In the Idle State 1100, if the processor core 104 writes a READ ITBUF N command the processor interface state machine 202 transitions to a the Read Processor Trace State (state=4) 1104. The processor output select signal cpu_out_sel signal is set to 3'b001 to select trace record data.

[0161] When the processor interface state machine 202 is in the Idle State 1100 and the processor core 104 writes a command to read the receive data, the processor interface state machine 202 transitions to the Data Read Processor State 1101 and sets the processor output select cpu_out_sel[2:0] to 3'b000, thereby selecting the receive data register data.

[0162] When the processor interface state machine 202 is in the Idle State 1100 and the processor core 104 writes a command to write data to the transmit data register, the processor interface state machine 202 transitions to the Write Processor TX ITCR Register state 1105 and asserts a write transmit register transmit reg_wr_str signal and a multiplex data data_in mux_cntl signal to 1. The write transmit register signal transmit reg_wr_str is used to write to the transmit register and also to set the TX bit in the ITCR register. The multiplex data signal data_in_mux_cntl is used to multiplex 1534 the data from the processor core 104.

[0163] When the processor interface state machine 202 is in the Idle State 1100 and the processor core 104 writes a command indicating that the serial/parallel port command is completed, the processor interface state machine 202 transitions to a Command Complete State 1106 and asserting the JTAG command done signal jtag_cmd_done to 1. The JTAG command done signal is used by the debug port state machine 206 to acknowledge command completion to the Host and accept new commands.

[0164] When the processor interface state machine 202 is in the Idle State 1100 and if a processor reset signal cpu reset or a processor soft reset signal cpu sreset occur, or the freset bit in the DCSR register is asserted, then the processor interface state machine 202 remains in the Idle State 1100, retaining the Debug Mode TCK output signal at a value of 0 to indicate that the processor core 104 is not in the debug mode.

[0165] When the processor interface state machine 202 is in the Idle State 1100 and the host system 111 writes a SERIAL TRACE READ command, the processor interface state machine 202 transitions to a Read Trace State 1102 and asserts a serial trace write enable serial_trace_wr_enb signal and a serial trace read serial_trace_read signal to 1. The serial trace write enable signal serial_trace_wr_enb is used to select, using multiplexer control, 1530 the trace record for writing to the read_data register. The host system 111 reads the trace data from the read_data register. The serial trace read signal serial_trace_read is sent to the trace control circuit 218 logic indicating for the trace control circuit 218 to read the trace data from the address in the soft_address register.

[0166] In the Data Write Processor State 1103, the processor interface state machine 202 waits for a write debug wr_udb_data signal from the processor core 104 which indicates that the processor core 104 writes the data. When the processor core 104 asserts the write debug wr_udb_data signal to 1, the processor interface state machine 202 transitions to the Idle State 1100. A write data signal udb_data_reg_wr_str is asserted to 1 and a multiplexer 1530 select signal udb_data_reg_wr_enb is set to remain at the previous latched value. The write data signal udb_data_regcwr str is used to write data to the read_data register. The multiplexer select signal udb_data_reg_wr_enb is used to multiplex 1530 select data from the processor core 104.

[0167] In the Data Read Processor State 1101, the processor interface state machine 202 waits for a read data signal rd_udb_data from the processor core 104. The read data signal rd_udb_data indicates that the processor core 104 is reading the data. When the processor core 104 asserts the read data signal rd_udb_data to 1, the processor interface state machine 202 transitions to the Idle State 1100, setting the processor output select signal cpu_out_sel to 3'b011. If the previous latched value of the processor output select signal cpu_out_sel is equal to 3'b000, indicating that the processor core 104 requests a data read from the receive data register, then an RX bit clear output signal rx_bit_wr is asserted to 1, clearing the RX bit in the ITCR/DCSR registers.

[0168] In Read Trace State 1102, the processor interface state machine 202 waits for a trace_data_done indication from the trace control circuit 218. When trace control circuit 218 asserts trace_data_done indication to 1, the processor interface state machine 202 transitions to the Command Complete State 1106. In the transition to the Command Complete State 1106 asserts serial trace write and enable read signals, respectively serial_trace_wr_str and serial_trace_wr_enb to 1, deasserts a serial trace read signal serial_trace_read to 0, and asserts the JTAG command complete jtag_cmd_done signal to 1. The serial trace write signal serial_trace_wr_str is used to write the trace data to the read_data register. The serial trace enable signal serial_trace_wr_enb is used to multiplex 1530 select the trace data. The serial trace read signal serial_trace_read deasserted to 0 is used to indicate to the trace control circuit 218 that the serial trace is complete. The JTAG command complete signal jtag_cmd_done indicates to the debug port state machine 206 that the command is complete.

[0169] In the Read Processor Trace State 1104, the processor interface state machine 202 waits for the trace_data_done indication from the trace control circuit 218, indicating that the data requested by the processor core 104 has been read from the trace buffer 200. When trace_data_done is set, the processor interface state machine 202 transitions to the Data Read Processor State 1101 and the processor output select signal cpu_out_sel[2:0] is set to 3'b001, multiplex selecting the trace data for processor core data read.

[0170] In the Write Processor TX ITCR Register state 1105, the processor interface state machine 202 transitions to the Idle State 1100 in the next clock cycle with a data multiplex select output signal data_in_mux_cntl asserted to 1, indicating for a multiplexer 1534 to select the processor core data for debug register write operations.

[0171] In the Command Complete State 1106, the processor interface state machine 202 waits for a JTAG decode signal jtag_decode_ph2 to be asserted to 0, an indication from the debug port state machine 206 that the CPU command has been completed and the processor core 104 is ready to accept new commands from the host system 111. When the JTAG decode signal jtag_decode_ph2 is equal to 0, the processor interface state machine 202 transitions to the Idle State 1100 and deasserts the JTAG command output signal jtag_cmd_done to 0.

[0172] Referring again to FIG. 2, the host system 111 writes data to the Debug Registers 210, including ITCR, DCSR, RX_DATA, TX_DATA, and soft_address registers, through the serial/parallel port 214. After the target system 101 reads the data and command for a write operation of a Debug Register 210, the debug port state machine 206 generates a serial debug port write TCK output signal (sdp_reg_write_tck). The debug port state machine 206 operates at a frequency of 25 MHz.

[0173] Referring to FIG. 12, a schematic circuit diagram illustrates an embodiment of a synchronization circuit 1200 for communicating commands and data between a communication port 214 which is operating at a specified lower frequency and a processor core 104 and trace control circuit 218 that are operating at multiple various frequencies that are higher than the specified lower frequency. The serial debug port register write TCK signal (sdp_reg_write_tck) is synchronized through the usage of one or more flip-flops which are clocked by the processor clock operating at frequencies such as 33 Mhz, 66 Mhz, 99 Mhz, or 133 Mhz. In the illustrative embodiment, three flip-flops 1210, 1212, and 1214 are included in the synchronization circuit 1200.

[0174] The rising edge of the serial debug port register write TCK signal (sdp_reg_write_tck) is detected by a first flip-flop 1210 and is synchronized through a second flip-flop 1212 and a third flip-flop 1214 that are clocked by the processor clock (clk_ph2). The output of the third flip-flop 1214 is qualified with a register enable signal generated by the command decode and processing block 208. The register enable signal is a gated signal used to clock the data to the registers of the Debug Registers 210. A reg_write_sync2 generated by the flip-flop 1216 is synchronized using a flip-flop 1218 clocked by a clock JTAG signal (clk_jtag) and the output clocked signal is sent to the debug port state machine 206. The serial debug port feedback signal (sdp_reg_write_fbak) indicates to the debug port state machine 206 that the data has been written to the Debug Registers 210. The debug port state machine 206 in response indicates to the host system 111 the debug register write command completion status.

[0175] Referring to FIG. 13 in combination with FIG. 12, a schematic block diagram illustrates synchronization elements of the embedded processor device 102 shown in FIGS. 1 and 2. Commands from the serial/parallel port 214 are decoded by the command decode and processing block 208. ARer the command is read from the host system 111, the debug port state machine 206 generates the JTAG decode (jtag_decode) output signal that is used by the command decode and processing block 208 to decode the command in the command register. If the decoded command from the host system 111 employs intervention of the processor core 104, the command decode and processing block 208 generates a processor command TCK clock signal (sle486_cpu_cmd_tck signal). The processor command TCK clock signal (sle486_cpu_cmd_tck signal) is synchronized through multiple back to back flip-flops 1210, 1212, and 1214, clocked by the processor clock, and the output processor command phase signal (sle486_cpu_pcmd_ph2) is sent to the processor interface state machine 202. The processor interface state machine 202 responds by sending notification of the command to the processor core 104. The processor core 104 reads the command and responds with suitable and appropriate actions. After recognizing the CPU command, the debug port state machine 206 enters a wait state and waits for the processor core 104 to complete execution of the command. After the processor core 104 completes command execution, the processor core 104 writes a command indicating that the CPU command is completed. The command indicating completion is decoded by the command decode and processing block 208, which issues a processor command done (cpu_cmd_done) signal to the processor interface state machine 202 and to the debug port state machine 206. The processor command complete signal (cpu_cmd_done) is synchronized by multiple back-to-back flip-flops, for example flip-flops 1210, 1212, and 1214, clocked by the clock tag (clk_tag) and sent to the debug port state machine 206. The debug port state machine 206 indicates to the host system 111 that the command is completed and deasserts the JTAG decode signal (jtag_decode) to 0. The JTAG decode (jtag_decode) signal is synchronized by the multiple back-to-back flip-flops clocked by the processor clock. The processor interface state machine 202 waits for the JTAG DECODE (jtag_decode) signal from the debug port state machine 206 to go low (0) and transitions to an Idle state (the Not JTAG Debug State (state=0) 900 shown in FIG. 9).

[0176] A similar synchronization technique and apparatus is used to communicate with the trace control circuit 218.

[0177] When the host system 111 completes writing a command, the debug port state machine 206 generates a JTAG DECODE (jtag_decode) signal output to the command decode and processing block 208. If the command is a CPU command the command decode and processing block 208 logic generates the processor command TCK clock signal (sle486_cpu_cmd_tck signal) which is synchronized in a synchronization logic block 232. The synchronized output processor command phase signal (sle486_cpu_cmd_ph2) is sent to the processor interface state machine 202 state machine. The debug port state machine 206 is in the wait state till the processor core 104 completes the execution of the command. A jump command pending (jmp_cmd_pending) signal and a jump command done (jmp_cmd_done) signal are generated by the processor core 104. An asserted jump command pending (jmp_cmd_pending) signal indicates that the processor core 104 is ready to accept new serial port/parallel port commands. An asserted jump command done (jmp_cmd_done) signal indicates that the processor core 104 has written a command to the serial port/parallel port 214 and is waiting, for command completion. The processor interface state machine 202 generates and sends an output signal processor debug jump (sle486_debu_jmps) to the processor core 104. Processor debug jump (sle486_debu_jmps) indicates either that the command sent by the processor core 104 is complete or a new serial port command is available for the processor core 104. The processor core 104 interprets the signal based on the jump command done (jmp_cmd_done) or jump command pending (jmp_cmd_pending) signals.

[0178] When the synchronization logic block 232 generates the processor command phase signal (sle486_cpu_cmd_ph2), and when the CPU asserts the jmp_cmd_pending signal the processor interface state machine 202 asserts sle486_debug_jmps. The processor core 104 reads the command and completes execution of an appropriate task in one or a plurality of processor core 104 commands. When the command is completed, the processor core 104 writes a CMD_DONE command on a debug data bus (udb_data) and asserts a write command (wr_udb_cmd) signal. The processor core 104 also periodically asserts the jump command done (jmp_cmd_done) signal and samples sle-486_debug_jmps until the processor debug jump (sle486_debug_jmps) signal is asserted. The command decode and processing block 208 logic decodes the command and generates a processor command finished (cpu_cmd_finished) output signal to the processor interface state machine 202. The processor interface state machine 202 transitions to a wait state and asserts the processor command finished (cpu_cmd_done) signal which is synchronized to a clock jtag (clk_jtag) signal in the synchronization logic block 232 and sent to the debug port state machine 206. The processor interface state machine 202 also asserts the processor debug jump (sle486_debug_jmps) signal. When CPU asserts the jmp_cmd_done indicating to the processor core 104 that the CMD_DONE command is completed. The debug port state machine 206 transitions to a state that accepts further commands from the host system 111 and generates a command completion status flag to the host system 111. The debug port state machine 206 deasserts the JTAG DECODE (jtag_decode) signal output. When the JTAG DECODE (jtag_decode) signal is equal to zero, the processor interface state machine 202 transitions to the Idle State 1100.

[0179] To read data from the serial port/parallel port 214, the processor core 104 asserts read data (rd_udb_data) signals and reads data from the processor data output (cpu_data_out) bus. The processor interface state machine 202 multiplexes the data requested by the processor core 104 by generating processor output select (cpu_out_sel[3:0]) multiplex controls.

[0180] To read trace data from the trace control circuit 218, the host system 111 writes a command through serial port/parallel port 214. The debug port state machine 206 asserts the JTAG DECODE (jtag_decode) signal and the command decode and processing block 208 logic decodes the command and generates a serial trace read (serial_trace_read) signal. The debug port state machine 206 waits until the trace control circuit 218 completes reading the trace data. The serial trace read (serial_trace_read) signal is synchronized to the processor core 104 clock in the synchronization logic block 232 and a serial trace read phase two (ser_trace_read_h2) signal is sent to the processor interface state machine 202. The processor interface state machine 202 generates the serial trace read (serial_trace_read) signal to the trace control circuit 218 and transitions to a wait state for the trace control circuit 218 to complete reading the data. When the serial trace read (serial_trace_read) signal is asserted the trace control circuit 218 reads the data from the trace buffer 200 from an address designated by an instruction buffer address (ITBUF_ADDR) bus. The trace control circuit 218 completes reading the data, asserts a trace data finished (trace_data_done) output signal, and sends the trace information via a trace record (trace_record) bus. The processor interface state machine 202 transitions to another state and asserts the processor command finished (cpu_cmd_done) signal for the debug port state machine 206. The processor command finished (cpu_cmd_done) signal is synchronized to the clock jtag (clk_jtag) signal in the synchronization logic block 232 and the debug port state machine 206 deasserts JTAG DECODE (jtag_decode) signal and transitions to a state that accepts new commands from the host system 111. The debug port state machine 206 also sets command completion status flag for the host system 111.

[0181] When the parallel port 214 is enabled, PDATA[15:0], PADR[2:0], and PRW are used as bidirectional pins. Controls for the pins are generated in the parallel port state machine 226 based on the PARENB bit in the DCSR register and the CO_PBREQ output signal. When external tracing is enabled the bidirectional pins are used to generate output trace record signals.

[0182] The data and commands from the JTAG TAP controller 204 port, and the parallel port 214 are latched into the ldata_in[15:0], udata_in[15:0], and cmd_in[3:0] registers in the Debug Registers 210 block, shown in FIG. 2. The data and commands are multiplexed from the serial/parallel port 214 to the registers by a 2:1 multiplexer. Data and commands that originate from the JTAG TAP controller 204 port are written to the Debug Registers 210 when the JTAG TAP controller 204 is in the update-DR state. When the data originates from the parallel port 214, the parallel port state machine 226 generates write strobe signals to the registers.

[0183] After the command is written to a command input (cmd_in[3:0]) register the debug port state machine 206 transitions to the DECODE1 or DECODE2 state and generates the JTAG DECODE (jtag_decode) output signal. The command decode and processing block 208 uses the JTAG DECODE (jtag_decode) signal to decode the command in the command input (cmd_in) register. The command decode and processing block 208 also decodes processor commands and the processor interface state machine 202 generates a multiplex control signal (data_in_mux_cntl) to select data from either the serial/parallel port 214 or from the processor core 104. The multiplexed output data in[31:0] is used to write to the debug registers (ITCR, DCSR, RX_DATA, TX_DATA, SOFT_ADDR) 210. The debug port state machine 206 generates a serial debug port write (sdp_reg_write) strobe for serial/parallel port data that is synchronized with the processor clock and qualified with the decoded signal to write to the registers. The processor interface state machine 202 generates the write strobe signals for writing the processor data to the Debug Registers 210 block.

[0184] The processor interface state machine 202 generates the multiplex select signals when the processor core 104 attempts to read the data from the serial port of the JTAG TAP controller 204.

[0185] While the invention has been described with reference to various embodiments, it will be understood that these embodiments are illustrative and that the scope of the invention is not limited to them. Many variations, modifications, additions and improvements of the embodiments described are possible. For example, those skilled in the art will readily implement the steps necessary to provide the structures and methods disclosed herein, and will understand that the process parameters, materials, and dimensions are given by way of example only and can be varied to achieve the desired structure as well as modifications which are within the scope of the invention. Variations and modifications of the embodiments disclosed herein may be made based on the description set forth herein, without departing from the scope and spirit of the invention as set forth in the following claims.