Abstract:
A method of tracing a data processor upon reset of the data processor. A data processor reset signal resets the data processor, part of trace collection hardware and does not reset remaining parts of trace collection hardware. The data processor reset signal may be not owned, owned by an application program or owned by a debugger. The partial not reset of the trace collection hardware occurs only upon a data processor reset signal owned by the debugger. A trace logic reset signal resets both the data processor and the trace collection hardware when not owned. This trace logic reset signal resets the data processor only when owned by the debugger and resets the trace collection hardware when owned by an application program.

Description:
[0001]     This application is a divisional of U.S. patent application Ser. No. 10/302,082 filed Nov. 22, 2002. 
     
    
     TECHNICAL FIELD OF THE INVENTION  
       [0002]     The technical field of this invention is emulation hardware particularly for highly integrated digital signal processing systems.  
       BACKGROUND OF THE INVENTION  
       [0003]     Advanced wafer lithography and surface-mount packaging technology are integrating increasingly complex functions at both the silicon and printed circuit board level of electronic design. Diminished physical access to circuits for test and emulation is an unfortunate consequence of denser designs and shrinking interconnect pitch. Designed-in testability is needed so the finished product is both controllable and observable during test and debug. Any manufacturing defect is preferably detectable during final test before a product is shipped. This basic necessity is difficult to achieve for complex designs without taking testability into account in the logic design phase so automatic test equipment can test the product.  
         [0004]     In addition to testing for functionality and for manufacturing defects, application software development requires a similar level of simulation, observability and controllability in the system or sub-system design phase. The emulation phase of design should ensure that a system of one or more ICs (integrated circuits) functions correctly in the end equipment or application when linked with the system software. With the increasing use of ICs in the automotive industry, telecommunications, defense systems, and life support systems, thorough testing and extensive real-time debug becomes a critical need.  
         [0005]     Functional testing, where the designer generates test vectors to ensure conformance to specification, still remains a widely used test methodology. For very large systems this method proves inadequate in providing a high level of detectable fault coverage. Automatically generated test patterns are desirable for full testability, and controllability and observability. These are key goals that span the full hierarchy of test from the system level to the transistor level.  
         [0006]     Another problem in large designs is the long time and substantial expense involved in design for test. It would be desirable to have testability circuitry, system and methods that are consistent with a concept of design-for-reusability. In this way, subsequent devices and systems can have a low marginal design cost for testability, simulation and emulation by reusing the testability, simulation and emulation circuitry, systems and methods that are implemented in an initial device. Without a proactive testability, simulation and emulation plan, a large amount of subsequent design time would be expended on test pattern creation and upgrading.  
         [0007]     Even if a significant investment were made to design a module to be reusable and to fully create and grade its test patterns, subsequent use of a module may bury it in application specific logic. This would make its access difficult or impossible. Consequently, it is desirable to avoid this pitfall.  
         [0008]     The advances of IC design are accompanied by decreased internal visibility and control, reduced fault coverage and reduced ability to toggle states, more test development and verification problems, increased complexity of design simulation and continually increasing cost of CAD (computer aided design) tools. In the board design the side effects include decreased register visibility and control, complicated debug and simulation in design verification, loss of conventional emulation due to loss of physical access by packaging many circuits in one package, increased routing complexity on the board, increased costs of design tools, mixed-mode packaging, and design for produceability. In application development, some side effects are decreased visibility of states, high speed emulation difficulties, scaled time simulation, increased debugging complexity, and increased costs of emulators. Production side effects involve decreased visibility and control, complications in test vectors and models, increased test complexity, mixed-mode packaging, continually increasing costs of automatic test equipment and tighter tolerances.  
         [0009]     Emulation technology utilizing scan based emulation and multiprocessing debug was introduced more than 10 years ago. In 1988, the change from conventional in circuit emulation to scan based emulation was motivated by design cycle time pressures and newly available space for on-chip emulation. Design cycle time pressure was created by three factors. Higher integration levels, such as increased use of on-chip memory, demand more design time. Increasing clock rates mean that emulation support logic causes increased electrical intrusiveness. More sophisticated packaging causes emulator connectivity issues. Today these same factors, with new twists, are challenging the ability of a scan based emulator to deliver the system debug facilities needed by today&#39;s complex, higher clock rate, highly integrated designs. The resulting systems are smaller, faster, and cheaper. They have higher performance and footprints that are increasingly dense. Each of these positive system trends adversely affects the observation of system activity, the key enabler for rapid system development. The effect is called “vanishing visibility.” 
         [0010]      FIG. 1  illustrates the trend in visibility and control over time and greater system integration. Application developers prefer the optimum visibility level illustrated in  FIG. 1 . This optimum visibility level provides visibility and control of all relevant system activity. The steady progression of integration levels and increases in clock rates steadily decrease the actual visibility and control available over time. These forces create a visibility and control gap, the difference between the optimum visibility and control level and the actual level available. Over time, this gap will widen. Application development tool vendors are striving to minimize the gap growth rate. Development tools software and associated hardware components must do more with less resources and in different ways. Tackling this ease of use challenge is amplified by these forces.  
         [0011]     With today&#39;s highly integrated System-On-a-Chip (SOC) technology, the visibility and control gap has widened dramatically over time. Traditional debug options such as logic analyzers and partitioned prototype systems are unable to keep pace with the integration levels and ever increasing clock rates of today&#39;s systems. As integration levels increase, system buses connecting numerous subsystem components move on chip, denying traditional logic analyzers access to these buses. With limited or no significant bus visibility, tools like logic analyzers cannot be used to view system activity or provide the trigger mechanisms needed to control the system under development. A loss of control accompanies this loss in visibility, as it is difficult to control things that are not accessible.  
         [0012]     To combat this trend, system designers have worked to keep these buses exposed. Thus the system components were built in a way that enabled the construction of prototyping systems with exposed buses. This approach is also under siege from the ever-increasing march of system clock rates. As the central processing unit (CPU) clock rates increase, chip to chip interface speeds are not keeping pace. Developers find that a partitioned system&#39;s performance does not keep pace with its integrated counterpart, due to interface wait states added to compensate for lagging chip to chip communication rates. At some point, this performance degradation reaches intolerable levels and the partitioned prototype system is no longer a viable debug option. In the current era production devices must serve as the platform for application development.  
         [0013]     Increasing CPU clock rates are also limiting availability of other simple visibility mechanisms. Since the CPU clock rates can exceed the maximum I/O state rates, visibility ports exporting information in native form can no longer keep up with the CPU. On-chip subsystems are also operated at clock rates that are slower than the CPU clock rate. This approach may be used to simplify system design and reduce power consumption. These developments mean simple visibility ports can no longer be counted on to deliver a clear view of CPU activity. As visibility and control diminish, the development tools used to develop the application become less productive. The tools also appear harder to use due to the increasing tool complexity required to maintain visibility and control. The visibility, control, and ease of use issues created by systems-on-a-chip tend to lengthen product development cycles.  
         [0014]     Even as the integration trends present developers with a tough debug environment, they also present hope that new approaches to debug problems will emerge. The increased densities and clock rates that create development cycle time pressures also create opportunities to solve them. On-chip, debug facilities are more affordable than ever before. As high speed, high performance chips are increasingly dominated by very large memory structures, the system cost associated with the random logic accompanying the CPU and memory subsystems is dropping as a percentage of total system cost. The incremental cost of several thousand gates is at an all time low. Circuits of this size may in some cases be tucked into a corner of today&#39;s chip designs. The incremental cost per pin in today&#39;s high density packages has also dropped. This makes it easy to allocate more pins for debug. The combination of affordable gates and pins enables the deployment of new, on-chip emulation facilities needed to address the challenges created by systems-on-a-chip.  
         [0015]     When production devices also serve as the application debug platform, they must provide sufficient debug capabilities to support time to market objectives. Since the debugging requirements vary with different applications, it is highly desirable to be able to adjust the on-chip debug facilities to balance time to market and cost needs. Since these on-chip capabilities affect the chip&#39;s recurring cost, the scalability of any solution is of primary importance. “Pay only for what you need” should be the guiding principle for on-chip tools deployment. In this new paradigm, the system architect may also specify the on-chip debug facilities along with the remainder of functionality, balancing chip cost constraints and the debug needs of the product development team.  
         [0016]      FIG. 2  illustrates a prior art emulator system  100  including four emulator components. These four components are: a debugger application program  110 ; a host computer  120 ; an emulation controller  130 ; and on-chip debug facilities  140 .  FIG. 2  illustrates the connections of these components. Host computer  120  is connected to an emulation controller  130  external to host  120 . Emulation controller  130  is also connected to target system  140 . The user preferably controls the target application on target system  140  through debugger application program  110 .  
         [0017]     Host computer  120  is generally a personal computer. Host computer  120  provides access the debug capabilities through emulator controller  130 . Debugger application program  110  presents the debug capabilities in a user-friendly form via host computer  120 . The debug resources are allocated by debug application program  110  on an as needed basis, relieving the user of this burden. Source level debug utilizes the debug resources, hiding their complexity from the user. Debugger application program  110  together with the on-chip trace and triggering facilities provide a means to select, record, and display chip activity of interest. Trace displays are automatically correlated to the source code that generated the trace log. The emulator provides both the debug control and trace recording function.  
         [0018]     The debug facilities are preferably programmed using standard emulator debug accesses through a JTAG or similar serial debug interface. Since pins are at a premium, the preferred embodiment of the invention provides for the sharing of the debug pin pool by trace, trigger, and other debug functions with a small increment in silicon cost. Fixed pin formats may also be supported. When the pin sharing option is deployed, the debug pin utilization is determined at the beginning of each debug session before target system  140  is directed to run the application program. This maximizes the trace export bandwidth. Trace bandwidth is maximized by allocating the maximum number of pins to trace.  
         [0019]     The debug capability and building blocks within a system may vary. Debugger application program  100  therefore establishes the configuration at runtime. This approach requires the hardware blocks to meet a set of constraints dealing with configuration and register organization. Other components provide a hardware search capability designed to locate the blocks and other peripherals in the system memory map. Debugger application program  110  uses a search facility to locate the resources. The address where the modules are located and a type ID uniquely identifies each block found. Once the IDs are found, a design database may be used to ascertain the exact configuration and all system inputs and outputs.  
         [0020]     Host computer  120  generally includes at least 64 Mbytes of memory and is capable of running Windows 95, SR-2, Windows NT, or later versions of Windows. Host computer  120  must support one of the communications interfaces required by the emulator. These may include: Ethernet 10T and 100T, TCP/IP protocol; Universal Serial Bus (USB); Firewire IEEE 1394; and parallel port such as SPP, EPP and ECP.  
         [0021]     Host computer  120  plays a major role in determining the real-time data exchange bandwidth. First, the host to emulator communication plays a major role in defining the maximum sustained real-time data exchange bandwidth because emulator controller  130  must empty its receive real-time data exchange buffers as fast as they are filled. Secondly, host computer  120  originating or receiving the real-time data exchange data must have sufficient processing capacity or disc bandwidth to sustain the preparation and transmission or processing and storing of the received real-time data exchange data. A state of the art personal computer with a Firewire communication channel (IEEE 1394) is preferred to obtain the highest real-time data exchange bandwidth. This bandwidth can be as much as ten times greater performance than other communication options.  
         [0022]     Emulation controller  130  provides a bridge between host computer  120  and target system  140 . Emulation controller  130  handles all debug information passed between debugger application program  110  running on host computer  120  and a target application executing on target system  140 . A presently preferred minimum emulator configuration supports all of the following capabilities: real-time emulation; real-time data exchange; trace; and advanced analysis.  
         [0023]     Emulation controller  130  preferably accesses real-time emulation capabilities such as execution control, memory, and register access via a 3, 4, or 5 bit scan based interface. Real-time data exchange capabilities can be accessed by scan or by using three higher bandwidth real-time data exchange formats that use direct target to emulator connections other than scan. The input and output triggers allow other system components to signal the chip with debug events and vice-versa. Bit I/O allows the emulator to stimulate or monitor system inputs and outputs. Bit I/O can be used to support factory test and other low bandwidth, non-time-critical emulator/target operations. Extended operating modes are used to specify device test and emulation operating modes. Emulator controller  130  is partitioned into communication and emulation sections. The communication section supports host communication links while the emulation section interfaces to the target, managing target debug functions and the device debug port. Emulation controller  130  communicates with host computer  120  using one of industry standard communication links outlined earlier herein. The host to emulator connection is established with off the shelf cabling technology. Host to emulator separation is governed by the standards applied to the interface used.  
         [0024]     Emulation controller  130  communicates with the target system  140  through a target cable or cables. Debug, trace, triggers, and real-time data exchange capabilities share the target cable, and in some cases, the same device pins. More than one target cable may be required when the target system  140  deploys a trace width that cannot be accommodated in a single cable. All trace, real-time data exchange, and debug communication occurs over this link. Emulator controller  130  preferably allows for a target to emulator separation of at least two feet. This emulation technology is capable of test clock rates up to 50 MHZ and trace clock rates from 200 to 300 MHZ, or higher. Even though the emulator design uses techniques that should relax target system  140  constraints, signaling between emulator controller  130  and target system  140  at these rates requires design diligence. This emulation technology may impose restrictions on the placement of chip debug pins, board layout, and requires precise pin timings. On-chip pin macros are provided to assist in meeting timing constraints.  
         [0025]     The on-chip debug facilities offer the developer a rich set of development capability in a two tiered, scalable approach. The first tier delivers functionality utilizing the real-time emulation capability built into a CPU&#39;s mega-modules. This real-time emulation capability has fixed functionality and is permanently part of the CPU while the high performance real-time data exchange, advanced analysis, and trace functions are added outside of the core in most cases. The capabilities are individually selected for addition to a chip. The addition of emulation peripherals to the system design creates the second tier functionality. A cost-effective library of emulation peripherals contains the building blocks to create systems and permits the construction of advanced analysis, high performance real-time data exchange, and trace capabilities. In the preferred embodiment five standard debug configurations are offered, although custom configurations are also supported. The specific configurations are covered later herein.  
       SUMMARY OF THE INVENTION  
       [0026]     A user may wish to diagnose the reason for resetting a data processor. Since the trace in the emulation is not reset upon functional reset, the user can have full visibility in the processor using the trace capability. This invention proposes real time tracing of data processor activity. The trace data enables program debug and analysis. This invention enables full visibility of data processor activity via trace through functional reset. The user can then view the trace data to diagnose the instruction address, data or data address that caused the functional reset. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0027]     These and other aspects of this invention are illustrated in the drawings, in which:  
         [0028]      FIG. 1  illustrates the visibility and control of typical integrated circuits as a function of time due to increasing system integration;  
         [0029]      FIG. 2  illustrates an emulation system to which this invention is applicable (prior art);  
         [0030]      FIG. 3  illustrates in block diagram form a typical integrated circuit employing configurable emulation capability (prior art);  
         [0031]      FIG. 4  illustrates in block diagram form a detail of the trace collection hardware according to this invention;  
         [0032]      FIG. 5  illustrates in block diagram form the pipeline flattener of this invention;  
         [0033]      FIG. 6  illustrates in block diagram form one embodiment of the sliding alignment correction circuit of this invention; and  
         [0034]      FIG. 7  illustrates in block diagram form an alternative embodiment of the sliding alignment correction circuit of this invention. 
     
    
     DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS  
       [0035]     Even though the processor gets reset on a functional reset, the emulation hardware can give the user full diagnostic capability for the reason of the reset. The user can trace the timing stream to get an idea of when and how long the reset lasted. The user can use the program counter and data streams to diagnose the addresses/data values that could have lead to the reset.  
         [0036]      FIG. 3  illustrates an example of a prior art one on-chip debug architecture embodying target system  140 . The architecture uses several module classes to create the debug function. One of these classes is event detectors including bus event detectors  210 , auxiliary event detectors  211  and counters/state machines  213 . A second class of modules is trigger generators including trigger builders  220 . A third class of modules is data acquisition including trace collection  230  and formatting. A fourth class of modules is data export including trace export  240 , and real-time data exchange export  241 . Trace export  240  is controlled by clock signals from local oscillator  245 . Local oscillator  245  will be described in detail below. A final class of modules is scan adaptor  250 , which interfaces scan input/output to CPU core  201 . Final data formatting and pin selection occurs in pin manager and pin micros  260 .  
         [0037]     The size of the debug function and its associated capabilities for any particular embodiment of a system-on-chip may be adjusted by either deleting complete functions or limiting the number of event detectors and trigger builders deployed. Additionally, the trace function can be incrementally increased from program counter trace only to program counter and data trace along with ASIC and CPU generated data. The real-time data exchange function may also be optionally deployed. The ability to customize on-chip tools changes the application development paradigm. Historically, all chip designs with a given CPU core were limited to a fixed set of debug capability. Now, an optimized debug capability is available for each chip design. This paradigm change gives system architects the tools needed to manage product development risk at an affordable cost. Note that the same CPU core may be used with differing peripherals with differing pin outs to embody differing system-on-chip products. These differing embodiments may require differing debug and emulation resources. The modularity of this invention permits each such embodiment to include only the necessary debug and emulation resources for the particular system-on-chip application.  
         [0038]     The real-time emulation debug infrastructure component is used to tackle basic debug and instrumentation operations related to application development. It contains all execution control and register visibility capabilities and a minimal set of real-time data exchange and analysis such as breakpoint and watchpoint capabilities. These debug operations use on-chip hardware facilities to control the execution of the application and gain access to registers and memory. Some of the debug operations which may be supported by real-time emulation are: setting a software breakpoint and observing the machine state at that point; single step code advance to observe exact instruction by instruction decision making; detecting a spurious write to a known memory location; and viewing and changing memory and peripheral registers.  
         [0039]     Real-time emulation facilities are incorporated into a CPU mega-module and are woven into the fabric of CPU core  201 . This assures designs using CPU core  201  have sufficient debug facilities to support debugger application program  110  baseline debug, instrumentation, and data transfer capabilities. Each CPU core  201  incorporates a baseline set of emulation capabilities. These capabilities include but are not limited to: execution control such as run, single instruction step, halt and free run; displaying and modifying registers and memory; breakpoints including software and minimal hardware program breakpoints; and watchpoints including minimal hardware data breakpoints.  
         [0040]      FIG. 4  illustrates a detail of trace collection  230 . Trace collection  230  hardware gets new trace data from the CPU core  201  every cycle. This trace comes form different pipeline stages of CPU core  201 . Pipeline flattener  401  combines all data from different clock cycles within the instruction pipeline that correspond to the same instruction. The data for each instruction is complete at the output of pipeline flattener  401 . Alignment logic  402  aligns the data coming from other parts of the emulation logic with the output of pipeline flattener  401 . This data then goes to trace logic  403 .  
         [0041]      FIG. 5  illustrates the pipeline flattener  401  of this invention. Pipeline flattener  401  achieves alignment of program counter (pc), pipeline-flow control information (pctl), memory access control (mem_acc_ctl), memory access address (mem_addr), memory access write data (wr_data) and memory access read data (rd_data).  
         [0042]     Alignment is implemented in 2 steps. First, the data collected in early stages of the pipeline is aligned in a per case bases in order to account for the differences in the data collection behavior. This presents a simpler group of data to the second processing step. Heterogeneous stage aligner  510  performs this initial alignment step. Second, the data collected in the first step presents a single type of behavior. The 3-stage delay pipeline  530  aligns this data from the first stage as a group to the last arriving memory access read data (rd_data).  
         [0043]     The point of collection of the last arriving memory access read data (rd_data) is the target point of alignment. In this example this point of collection is stage  5  of the pipeline (e 5 ). As a first step towards the final alignment goal, the early arriving data is processed in various ways and aligned via heterogeneous stage aligner  510  to the second stage of the pipeline (e 2 ). In order to be considered fully aligned to e 2 , the data should not be updated at the beginning of the clock cycle if the pipeline did not advance in the previous cycle. This is indicated by cpu_stall=1 in previous cycle. For the example illustrated in  FIG. 5  there are 5 sources of early arriving data program counter (pc), pipeline-flow control information (pctl), memory access control (mem_acc_ctl), memory access address (mem_addr) and memory access write data (wr_data). These represent 3 independent data retention policies and require 3 different mechanisms in order to be aligned to pipeline state e 2  as a group.  
         [0044]     The pipeline-flow control information (pctl) data group is collected in pipeline stage e 1 . This data has a data retention policy similar to the policy of any stage in the architectural pipeline. Thus all that is required to align pipeline-flow control information (pctl) to pipeline stage e 2  is the single stage pipeline delay element  511 . Pipeline delay element  511  is implemented by a single register stage that updates when the pipeline advances (cpu_stall=0).  
         [0045]     A second set of early collected data is the program counter (pc). The program counter is generated in pipeline stage e 0 . The program counter is delayed 1 clock cycle via a single register stage (not shown) and then presented at the input of heterogeneous stage aligner  510  as the signal pc_e 0 +1 clock delay. Program counter (pc) data is aligned to pipeline stage e 2  via a single register stage in pipeline delay element  512 . Pipeline delay element  512  updates only when the pipeline advances (cpu_stall=0) and only if the current instruction in pipeline state e 1  is a new instruction (inst_exe=1). OR gate  513  advances receives the cpu_stall signal and the inst_exe signal and insures pipeline delay element  512  advances only under these conditions. Enforcing these 2 conditions ensures that the aligned program counter (pc) value in pipeline stage e 2  during multicycle instructions remains the same during all the cycles it takes to execute the instruction. This retention is in spite of the fact that the program counter (pc) retention policy will overwrite the program counter (pc) value presented after the first clock cycle of the instruction in pipeline stage e 1 .  
         [0046]     The three remaining sets of early collected data are related to memory accesses. These are memory access control (mem_acc_ctl), memory access address (mem_addr) and memory access write data (wr_data). For the particular implementation illustrated in  FIG. 5 , the three sources of data have a similar data retention policy and are collected in the same pipeline stages. Thus the same mechanism is used in order to align them to pipeline state e 2 . These 3 pieces of data are architecturally generated in pipeline stage e 2 . However, due to some special needs of this particular implementation there are a few exceptional cases where the memory access data is collected in pipeline stages e 1  and e 0  rather than pipeline stage e 2 .  
         [0047]     Memory access elastic buffer  520  copes with these alternatives. Received memory access control data (mem_acc_ctl) supplies the input to two stage pipeline delay element  521 , the input to multiplexer  522  and an input to elastic buffer control  523 . The memory access address (mem_addr) and memory access write data (w__data) supply the input to pipeline delay element  521  and multiplexer  522 . It should be understood that the memory access control data (mem_acc_ctl), the memory access address (mem_addr) and memory access write data (wr_data) are handled in parallel in pipeline delay element  521  and multiplexer  522 .  
         [0048]     The memory access control data (mem_acc_ctl) indicates the pipeline stage of collection of the memory access signals. Elastic buffer control  523  uses this indication to control pipeline delay element  521  and multiplexer  522 . If the memory access data was collected during pipeline stage e 2 , then elastic buffer control  523  sends a select signal to multiplexer  522  to select the directly received memory access signals. If the memory access data was collected during pipeline stage e 1 , then elastic buffer control  523  sends a select signal to multiplexer  522  to select memory access signals from pipeline delay element  521 . Elastic buffer control  523  also controls pipeline delay element  521  to insert one pipeline stage delay. If the memory access data was collected during pipeline stage e 0 , then elastic buffer control  523  sends a select signal to multiplexer  522  to select memory access signals from pipeline delay element  521 . Elastic buffer control  523  also controls pipeline delay element  521  to insert two pipeline stage delays. This behavior is summarized in Table 1.  
                               TABLE 1                                       Multiplexer   Pipeline delay           Data collected   522 select   element 521                           e0   delayed data   2 stage delay           e1   delayed data   1 stage delay           e2   direct data   —                      
 
         [0049]     The 3-stage delay pipeline  530  takes the homogeneously behaved data at its input already aligned to the second pipeline stage e 2 . Three-stage delay pipeline  530  includes pipeline delay element  531  for the memory access data, pipeline delay element  532  for the program counter data and pipeline delay element  533  for the pipeline-flow control information. Three-stage delay pipeline  530  outputs this data at pipeline stage e 5 . This is the same stage as the arrival of the read data (rd_data). Three-stage delay pipeline  530  sends every bit of input data through 3 serially connected registers that update its content every clock cycles that the pipeline is not stalled (cpu_stall=0). The clock signal clk 1  is supplied to pipeline delay elements  511  and  512  and to every register of pipeline delay elements  521 ,  531 ,  532  and  533 . The cpu_stall signal stalls pipeline delay elements  511 ,  512 ,  531 ,  532  and  533  when the central processing unit is stalled. Since the memory access data is not updated by heterogeneous stage aligner  510  during pipeline stall cycles, no data is lost during pipeline stalls. Pipeline flattener  401  effectively aligns the program counter (pc), pipeline-flow control information (pctl), memory access control (mem_acc_ctl), memory access address (mem_addr), memory access write data (wr_data) to the late received read data (rd_data) in pipeline stage e 5 .  
         [0050]      FIG. 6  illustrates alignment circuit  402  in one embodiment of this invention. The data presented at the input of this circuit is aligned to the cycle and pipeline stage where the last set of data, the memory access read data (rd_data), becomes available. In this example the data processor has a five stage pipeline. Thus the write data (wr_data_e 5 ), memory access control data (mem_acc_ctl_e 5 ), memory address (mem_addr_e 5 ), program counter (pc_e 5 ) and pipeline-flow control information (pctl_e 5 ) has been aligned with the late arriving read data (rd_data) in pipeline stage e 5 .  
         [0051]     In  FIG. 6  although all the data presented at the input of the circuit is be aligned to pipeline stage e5, there is an issue with 1 clock cycle sliding of read data (rd_data) that could cause it not to be correctly captured if the pipeline stalls. The 1 clock cycle sliding of read data (rd_data) happens when the read data (rd_data) presented at the input boundary of the circuit as it updates one more cycle once the pipeline stalls. As part of this behavior the same source of read data (rd_data) will not be updated like the rest of the aligned data at the beginning of the second pipeline advance cycle after the stall. In other words the 1 cycle sliding of the read data (rd_data) could be described as a 1 cycle delay in response to the stall or advance taking place in the pipeline.  
         [0052]     In order to prevent the potential lost of the read data, additional registering stage is inserted in the path of the data. This one pipeline stage delay is implemented via pipeline delay elements  601 ,  602 ,  603 ,  604  and  605 . The pipeline delay element  605  provides storage to capture the read data (rd_data) and eliminates the loss of read data associated with the instruction in pipeline state e 5  being overwritten when the read data in pipeline stage e 4  slides into pipeline stage e 5  during the first cycle of a CPU stall window. Pipeline delay elements  601 ,  602 ,  603  and  604  do not hold data and have been added as delay elements to compensate for the delay of pipeline delay register  605 , which captures and holds the read data. In order to remove the 1 clock slide in the read data, the hold signal supplied to pipeline delay register  605  is a 1 clock delayed version of the pipeline stall signal (cpu_stall) provided by delay element  606 .  
         [0053]      FIG. 6  illustrates two additional register stages in each data path: pipeline delay elements  611  and  621  in the write data path, pipeline delay elements  612  and  622  in the memory access control data and the memory address paths; pipeline delay elements  613  and  624  in the program counter path; pipeline delay elements  614  and  624  in the pipeline-flow control information path; and pipeline delay elements  615  and  625  in the read data path. These two additional stages add additional latency specific to this implementation of the preferred embodiment of the invention. The 3 additional register stages alignment circuit  602  do not represent additional pipeline stages, they only add clock latency to the implementation. The data at the output of alignment circuit  602  is the contents of pipeline stage e 5  in the pipeline delayed by 3 clock cycles.  
         [0054]     The correction to the N-bit sliding on the memory data is done via an N-bit slide operation in the opposite direction to the slide of the data. The data bus is assumed to be 2 words wide in this embodiment. The sliding of data at the input is limited to a swapping between the upper and lower words of the bus. Shift correction circuit  630  receives the memory access control signal and detects the sliding condition. Shift correction circuit  630  controls multiplexers  631 ,  632 ,  633 , and  634  to enable or disable a swap of the most significant and least significant bits. In order to restore the architectural view of the data it is necessary to align the least significant bits of the write data and the read data to the least significant bits of the data bus. On a normal state of the multiplexer control signal from shift control circuit  630  multiplexer  631  selects the most significant bits from pipeline delay element  601  to output to the most significant bits of pipeline delay element  611 , multiplexer  632  selects the least significant bits from pipeline delay element  601  output to the least significant bits of pipeline delay element  611 , multiplexer  633  selects the most significant bits from pipeline delay element  605  to output to the most significant bits of pipeline delay element  615 , multiplexer  634  selects the least significant bits from pipeline delay element  605  output to the least significant bits of pipeline delay element  611 . In the opposite swap state multiplexer  631  selects the least significant bits from pipeline delay element  601  to output to the most significant bits of pipeline delay element  611 , multiplexer  632  selects the most significant bits from pipeline delay element  601  output to the least significant bits of pipeline delay element  611 , multiplexer  633  selects the least significant bits from pipeline delay element  605  to output to the most significant bits of pipeline delay element  615 , multiplexer  634  selects the most significant bits from pipeline delay element  605  output to the least significant bits of pipeline delay element  611 . This swaps the most significant bits with the least significant bits of both the write data and the read data.  
         [0055]      FIG. 7  illustrates alignment circuit  700  in an alternative embodiment of this invention. In this alternative clock delay elements  601 ,  602 ,  603  and  604  are replaced with respective pipeline delays elements  701 ,  702 ,  703  and  705 . An additional pipeline delay has been added by holding the contents of pipeline delay elements  701 ,  702 ,  703 ,  704  and  615  by connecting their hold inputs to the cpu_stall signal. As a result the pipeline data aligned to pipeline stage e 5  presented as input of adjustment circuit  700  will require that the pipeline advances one more stage to pipeline stage e 6 , before it could be propagated via 2 stages of latency to the output.  
         [0056]     Reset for the trace logic and CPU core  201  is qualified as shown in Table 2. Table 2 gives some background knowledge about interaction of reset, CPU core  201  and trace.  
                                       TABLE 2                                       Functional   Trace Logic   Reset   Reset           Unit owned by   reset   reset   CPU   Trace                           Not owned   Y   —   Y   Y           Not owned   —   Y   Y   Y           Application   Y   N   Y   Y           Application   N   Y   N   N           Debugger   Y   N   Y   N           Debugger   N   Y   N   Y                      
 
         [0057]     Pipeline flattener  401  and alignment logic  402  are reset when CPU core  201  resets. However trace logic  403  is only reset as shown in Table 2. As shown in Table 2, trace logic  403  can only trace through reset when the debugger/emulator owns the reset and there is a functional reset.  
         [0058]     The reset request is initiated via emulation hardware. The reset information from CPU core  201  cannot be used for trace collection  230 . By the time such information is pipelined and sent to trace collection  230 , it misses the window in which the reset started. Therefore, the reset signal sent to trace collection  230  is a pipelined version of the reset sent to CPU core  201 .  
         [0059]     The user sees the following sequence:  
         [0060]     1. Normal information traced;  
         [0061]     2. Start of reset information;  
         [0062]     3. Timing cycles indicating no activity;  
         [0063]     4. Active timing bits indicating the activity of boot load code;  
         [0064]     5. Stalls indicating the loading of instruction memory;  
         [0065]     6. Exception to address 0, where the reset code resides.  
         [0066]     The user can use this sequence to diagnose the probable location of reset, the duration for reset and any other information that might interest him.