Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Wind River Trace for Wind River Workbench ® HARDWARE REFERENCE 3.
Copyright © 2007 Wind River Systems, Inc. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means without the prior written permission of Wind River Systems, Inc. Wind River, the Wind River logo, Tornado, and VxWorks are registered trademarks of Wind River Systems, Inc. Any third-party trademarks referenced are the property of their respective owners. For further information regarding Wind River trademarks, please see: http://www.windriver.
Contents 1 Overview ............................................................................................... 1 1.1 Introduction ............................................................................................................. 1 Other Resources ........................................................................................ 3 Wind River Trace Features .................................................................................... 3 1.2.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 2.3.3 2.4 3 Signal Requirements for ColdFire Processors ...................................... 9 Wind River Trace with Wind River ICE SX ....................................................... 10 2.4.1 13 Applying Power to Wind River Trace and Wind River ICE SX ......... Using Wind River Trace ....................................................................... 15 3.1 Getting Started .............................................
Contents Address ...................................................................................................... Address Mask ........................................................................................... Before Trace Counter ............................................................................... After Trace Counter .................................................................................. Post Trigger Counter .............................................................
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 ColdFire Processor Performance ............................................................ A B 38-pin Mictor Connector (AMCC 405 and 440 Processors) ............. 75 A.1 38-Pin Mictor Connector Specifications ............................................................. 75 A.2 AMCC 405 and 440 Timing Specifications ........................................................ 78 AMCC 405 Processor .......................................
1 Overview 1.1 Introduction 1 1.2 Wind River Trace Features 3 1.3 Wind River ICE Features 4 1.4 Safety Information 5 1.1 Introduction This document describes the Wind River Trace tool. The Wind River Trace tool is used in conjunction with the Wind River ICE SX emulator, providing a real-time code execution trace.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Figure 1-1 Wind River Trace The Wind River Trace captures a snapshot of your executing code to a memory array, at full speed. It saves up to hundreds of thousands of machine cycles, displaying addresses, instructions, and transferred data. The Wind River ICE SX emulator translates raw machine cycles to assembly code or C/C++ statements, and displays them in the Trace view in Wind River Workbench.
1 Overview 1.2 Wind River Trace Features Other Resources 1 For information on Wind River Workbench, see the Wind River Workbench User’s Guide. For information on Workbench low-level commands, see the Wind River Workbench for On-Chip Debugging Command Reference. For information on configuring Wind River emulators, see the Wind River Workbench for On-Chip Debugging Configuration Options Reference. For information on on-chip debugging, see the Wind River Workbench for On-Chip Debugging User Tutorials.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 ■ Real-time trace with the AMCC 405 or 440 trace clock running at up to 200 MHz (since the trace clock runs at half the core clock frequency for 405, and one quarter the core clock frequency for 440, the AMCC 405 core clock can run at up to 400 MHz, and the AMCC 440 core clock can run at up to 800 MHz.) The capture frequency may increase with future development. Contact http://www.windriver.com/support for information on all updates.
1 Overview 1.4 Safety Information The Wind River ICE SX utilizes On-Chip Debugging (OCD) services embedded in the target microprocessor (BDM/JTAG/EJTAG). These OCD services are a set of debugging services that reside in the chip’s micro-code. When accessed, they provide complete control of the target microprocessor. There is no hardware or software intrusion into the system, and these debug services do not require any target interrupts, RAM, ROM, or RS-232 communications.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Precautions to Avoid Property Damage ! CAUTION: Take precautions against electrostatic discharge as it may damage some components. Use care in handling, as delicate components can be easily damaged. Provide proper ventilation to prevent the product from overheating.
2 Hardware Setup 2.1 Introduction 7 2.2 Connection Schemes 7 2.3 Trace Signal Requirements 8 2.4 Wind River Trace with Wind River ICE SX 10 2.1 Introduction This chapter includes information related to hardware connections with Wind River Trace. 2.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 type. The preferred connection scheme is specified when purchased. The following two sections describe the connection schemes in detail. 2.2.1 AMCC 405 and 440 Processors The connection to the AMCC 405 or 440 target board is through a 38-pin Mictor connector, which contains all the run control and trace functionality in a single connector.
2 Hardware Setup 2.3 Trace Signal Requirements will automatically configure these pins to be trace signal pins when the configuration option Acquire Trace on GO (TRCAQU) is set to ON. The AMCC 405 trace signals are enabled only when the AMCC 405 is actually executing code. NOTE: These pins must not be re-configured as GPIO pins by the application code. 2.3.
Wind River Trace for Wind River Workbench Hardware Reference, 3.
2 Hardware Setup 2.4 Wind River Trace with Wind River ICE SX Figure 2-1 Wind River Trace with Wind River ICE SX 2 Wind River ICE SX connects to Wind River Trace via a 51-pin extension cable. If you order the Wind River Trace as a separate product, it will have to be attached to your Wind River ICE SX before use. ! CAUTION: Wind River recommends that you return your Wind River ICE SX to a Wind River service representative to have the Wind River Trace unit attached to it.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Figure 2-2 Removing the Personality Module 3. To attach the Wind River Trace, align the rear edge of the connector with the rear edge of the target end of the 51-pin cable. The fan on the Wind River Trace should be facing away from you. When the rear edges are aligned, as shown in Figure 2-3, the grooves on both the connector and the 51-pin cable are also aligned.
2 Hardware Setup 2.4 Wind River Trace with Wind River ICE SX 4. Press both thumbs on each side of the connector, and snap the Wind River Trace into place. When inserting, press down on both sides of the connector with equal force. When the Trace unit is properly inserted, it snaps into place and is solidly attached to the cable. A 4xx/44x or ColdFire filtered trace cable is shipped already attached to the Wind River Trace unit. 2.4.
Wind River Trace for Wind River Workbench Hardware Reference, 3.
3 Using Wind River Trace 3.1 Getting Started 15 3.2 Establishing Communications 17 3.3 Configuration Settings 34 3.4 Setting Up a Project 40 3.5 Using the Trace View 46 3.6 Tracing Execution 55 3.1 Getting Started This chapter explains how to configure Wind River Workbench to read trace information from the Wind River Trace unit. For information on Workbench, please refer to the Wind River Workbench User’s Guide.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Before you can use the Wind River Trace, you must set a new environment variable called DFW_OPCODE_READER on your host system to 1. To set this variable, use the following procedure: Windows Hosts: You must have administrator privileges to set environment variables. 1. Select Start > Control Panel > System. 2. In the dialog that appears, click on the Advanced tab. 3.
3 Using Wind River Trace 3.2 Establishing Communications 3.2 Establishing Communications The Wind River Trace operates only in conjunction with a Wind River ICE SX. To establish communications with your Wind River ICE SX, use the following steps. First, open Workbench according to the method for your host computer. Linux/Solaris Hosts From your installation directory, issue the command $ ./startWorkbench.sh Windows Hosts Select Start > All Programs > Wind River > Wind River Workbench version.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 2. 18 Choose Wind River OCD ICE Connection from the list of options and click Next.
3 Using Wind River Trace 3.2 Establishing Communications The Communication Settings dialog appears. 3 To configure communication settings manually, see Configuring Communication Settings Manually, p.19. To configure communication settings through a serial port, see Configuring Communication Settings Manually, p.19. Configuring Communication Settings Manually NOTE: If you choose this option you will need to know either the network name of the emulator or its IP address.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 The Emulator Settings dialog appears. 4. In the Designators area, enter your target processor type in the Processor field, or click Select to choose from a list of available processor types. If you are using multiple processors, or if you have other devices besides your processor on your JTAG scan chain, you must specify a board file in the Board File field. Check the Board File radio button and click Browse to navigate to your board file.
3 Using Wind River Trace 3.2 Establishing Communications 3 6. When you have entered the correct processor or board file and IP address, click Next. The Target Operating System Settings dialog appears. Proceed to Step 7. Configuring Communication Settings Through a Serial Port If you choose to make your connection using the serial port, make sure that a serial cable is connected between Wind River ICE SX and your host computer. NOTE: A direct serial cable is required to create your connection this way.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 22 a. Select Query the communication settings from the ICE through a serial port and click Next. The serial settings fields become active. b. Use these fields to select the serial port you want to connect to, and set a timeout value in seconds. Communication settings, such as the emulator’s dynamically assigned IP address and other settings, are retrieved and displayed automatically.
3 Using Wind River Trace 3.2 Establishing Communications 3 The retrieved settings can also be modified (select the Modify Communication Settings checkbox); that is, you can reconfigure the emulator’s communication settings using a serial connection. c. Click Next. The Target Operating System Settings dialog appears. Proceed to Step 7.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 7. In the Booted Target OS on selected CPU field, select the operating system that is running on your target processor. The default is None. 8. Next to the Kernel Image field, click Browse to navigate to the kernel image you wish to specify. If you selected None in the previous step, you do not need to specify a kernel image. 9.
3 Using Wind River Trace 3.2 Establishing Communications 10. ■ notasklist=1: Never fetch process list. ■ noautomodules=1: Do not plant internal breakpoints to do automatic kernel module load/unload detection. When this option is specified, you must manually refresh to see an updated module list. ■ noloadcheck=1: Do not issue gophers until the hardware breakpoint is used to detect kernel load triggers.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Use the Memory Options dialog to specify how memory on the target is partitioned, and what the attributes of the particular memory regions are. NOTE: The Memory Options dialog is only necessary for Linux or other non-VxWorks target operating systems. To specify an area of memory, click Add. The Set Memory Map dialog appears.
3 Using Wind River Trace 3.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Use the Set Memory Map dialog to specify which memory areas are read-only, read-write, or write-only, and to specify the access width Workbench should use to read the data from those regions. 11. Click Next. The Object Path Mappings dialog appears. Use the Object Path Mappings dialog to specify how files in the target file system are visible in the host file system.
3 Using Wind River Trace 3.2 Establishing Communications Workbench uses object path mappings in two ways: ■ ■ They allow the debugger to find symbol files for processes created on the target by creating a correspondence between a path on the target and the appropriate path on the host. Workbench also uses object path mappings to calculate target paths for processes that you want to launch by browsing to them with a host file system browser.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Since retrieving status information from the target leads to considerable target traffic, this page allows you to configure how often and under what conditions the information displayed in the Remote Systems view is refreshed. You can change these settings later by right-clicking the target connection and selecting Refresh Properties. In the Available CPU(s) on target board field, Workbench identifies the target CPU.
3 Using Wind River Trace 3.2 Establishing Communications Use the Initial target state query settings checkboxes to specify whether Workbench should query the target on connect, on stopped events, and/or on running events. You can select any or all of these options. Use the Target state refresh settings to specify whether Workbench should auto-refresh the target state, or if it should only refresh when you refresh manually. You can also specify the auto-refresh interval.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Use this dialog to set default breakpoint options for newly created breakpoints. 14. ■ Select Stop all if you want the breakpoint to stop all threads. ■ Select Stop triggering thread if you want the breakpoint to stop only the thread that triggered it. Click Next. The Connection Summary dialog appears. Inspect the displayed values to make sure they are correct.
3 Using Wind River Trace 3.2 Establishing Communications 3 15. Check the displayed values to make sure they are correct. To connect to your target now, select Immediately connect to target if possible. 16. If you want to share your target connection, select Shared. This option serves a dual purpose: ■ When you define a target connection configuration, this connection is normally only visible for your user-id.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 ■ 17. Normally, when you disconnect a target connection, the target server (and simulator) are killed because they are no longer needed. In a connection that is flagged as Shared, however, they are left running so that other users can connect to them. In other words, you can flag a connection as shared if you want to keep the target server (and simulator) running after you disconnect or exit Workbench. Click Finish.
3 Using Wind River Trace 3.3 Configuration Settings ■ NO — When GO command is issued, the trace data will be stored in trace memory starting at the next trace memory location. All previously stored trace data will not be overwritten. All newly captured trace data will be stored starting at the next trace memory location. Acquire Trace on GO (TRCAQU) Use the TRCAQU parameter to control the acquiring of trace data to the trace memory on a GO command.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Code Range (CR) Use the CR parameter to set the code range. The code range must be set accurately when the CF TRCREPORT parameter is set to YES. The code range settings BASE and RANGE set the base address and the range that the code runs in. BASE -- Any valid address from 0 to FFFFFFFE that is word aligned. Enter the value as a hex address. (Do not enter a leading 0x before the address.
3 Using Wind River Trace 3.3 Configuration Settings Setting CF Options With the Configure Trace Button Clicking on the Configure Trace button in the Trace view opens the Configure Trace dialog (see Figure 3-6). This dialog contains fields for all trace-specific CF options for your target architecture. Trace-specific CF options vary between architectures. The Configure Trace dialog shows only those options for your target architecture. For descriptions of all trace-specific CF options, see 3.3.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 If you set the Emit Operands on DDATA Pins option to NO, skip this step. If you set the Emit Operands on DDATA Pins option to YES: In the list of available CF options, select Code Range. Select the Current Setting field and enter the code range base address and the size of the code range in bytes. For example, entering 400 1000 will set the code range base address to 0x00000400 with a range of 0x1000 bytes. d.
3 Using Wind River Trace 3.3 Configuration Settings ColdFire processors only: a. Configure the Set Workspace option. A 1K workspace in RAM is required to load a debug exception handler for filtered trace with ColdFire. Set the workspace in the OCD Command Shell using the syntax CF WSPACE base_addr size base_addr is the base address of the workspace. size is the size of the workspace in bytes.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 cf set_vbr value value is the exception table base address, which needs to be configured in RAM so that the debug exception handler address, which is defined in the Set Work Space option in Step a, can be entered in the exception table. For example, entering the command >BKM>cf set_vbr 20000000 will set the Vector Base Register to 20000000 whenever an IN command is issued. 4. Reset the target to make your changes take effect: >BKM>in 3.
3 Using Wind River Trace 3.4 Setting Up a Project 3 2. Expand the Examples folder and select Standalone Sample Project. 3. Click Next. A sample project template appears.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 4. Select C Demonstration Program and click Finish. Workbench creates the sample project in the default workspace folder and displays the project c_demo_sa in the Project Explorer view.
3 Using Wind River Trace 3.4 Setting Up a Project 3 5. To build the sample project for use with your target processor, right-click on the c_demo_sa top-level folder and select Build Options > Set Active Build Spec. The Set Active Build Spec and Debug Mode dialog appears.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 6. Select the build spec for your target processor. For AMCC 40x and 44x processors, use the PowerPC build spec (the prefix is PPC.) For ColdFire processors, use a ColdFire build spec (the prefix is MCF.) 7. Make sure the Debug mode (use debug mode flags) checkbox is selected (so Workbench will generate symbolic debug information) and click OK. 8. Right-click on the project name and select Build Project.
3 Using Wind River Trace 3.4 Setting Up a Project 3 9. In the Project Explorer, expand Build Targets. Right-click on the cdemo.elf file for your target and select Reset and Download. The Reset and Download view appears. 10. Leave the settings at their defaults and click Debug. The OCD Console view opens and shows the status of the download operation, as Workbench downloads the sample code to the target.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 You are now ready to run and trace code. 3.5 Using the Trace View To open the Trace view, select Window > Show View > Trace View. The Trace view appears, unpopulated, as shown in Figure 3-1.
3 Using Wind River Trace 3.5 Using the Trace View Figure 3-1 Trace View 3 The Trace view has two fields: the Events field and the Trace field. The Events field shows the trace buffer. When code runs, the Events field shows the start of trace and the end of trace. It also displays the type of trace event. The Trace field has five columns, from left to right: Event Occurrences (unlabeled), Address, Abs Time, DEL Time, and Instruction (unlabeled.) The Event Occurrences column shows the type of trace event.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 3.5.1 Trace View Buttons Table 3-1 shows all the buttons in the Trace view toolbar. More detailed descriptions follow the table.
3 Using Wind River Trace 3.5 Using the Trace View Figure 3-2 Trace Toggle Buttons 3 Toggle Delta Timestamp Bar Toggle Absolute Timestamp Bar Toggle Address Bar Toggle Event Bar To collapse any column, click on the toggle button for that field. To re-expand it, click on the toggle button again. The Instruction column cannot be collapsed.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Refresh Trace View Click this button to refresh the entire Trace view, including the Events field. Refresh the Trace view to display the newest good information. Open Trace Rules Dialog Click this button to open the Trace Rules dialog, as shown in Figure 3-3.
3 Using Wind River Trace 3.5 Using the Trace View Use the Trace Rules dialog to create a trace rules file, for cases where the code is not running in the address range of the download file specified in the Reset and Download view, such as an interrupt service routine in flash. To create a trace rules file, use the following steps: 3 1. Click Add Rule. 2. In the Memory Type field, select CODE (for executable code) or DATA. 3.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 3. Click OK to close the Trace Rules dialog. 4. In the Remote Systems view, right-click on your target connection name and select OCD Reset and Download. 5. The Reset and Download view appears. 6. Select the Files tab. 7. Click Add Files. 8. In the browser window that appears, navigate to the trace.elf file you have just created and click Open. 9. The trace.elf file appears in the file list. 10. Uncheck the Load Symbols box.
3 Using Wind River Trace 3.5 Using the Trace View Figure 3-4 Filtered Trace Options for AMCC440GP 3 Figure 3-5 Filtered Trace Options for ColdFire MCF5239 For descriptions of all filtered trace options, see 4. Filtering Trace.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Configure Trace Click this button to open the Configure Trace dialog. Use this dialog to configure trace-specific configuration options for the Wind River ICE SX. Configuration options vary by processor family, so the Configure Trace dialog will appear differently depending on your target processor. Figure 3-6 shows the Configure Trace dialog for ColdFire processors.
3 Using Wind River Trace 3.6 Tracing Execution 3.6 Tracing Execution Once you have set up your project as described in 3.4 Setting Up a Project, p.40, you can begin to trace code. First, decide what trace events you want to be visible in the Events field. In the Trace view toolbar, click Filter Visible Trace Events. Available trace events vary by processor family. Examples of available trace events are shown in Figure 3-4 and Figure 3-5. For a description of all trace events, see 4. Filtering Trace.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Figure 3-7 Line Tracepoint Dialog Click on the Tracepoint tab. Use the Tracepoint tab to specify the properties of your tracepoint. The Tracepoint tab contains the following options: Address Set a tracepoint at a specified address. Address Mask Not currently implemented. Before Trace Counter Not currently implemented.
3 Using Wind River Trace 3.6 Tracing Execution After Trace Counter This counter can be used with either the Trace Off or Trace Around options to capture more trace data after the matched address. To use this counter, select After Trace Counter and enter a value in the After Trace Counter field. The value you enter is the number of trace records that will be captured after the trace event is detected. The limit is FFFF.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Syntax: Get PT Set PT value value = limit is FFFF.
3 Using Wind River Trace 3.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Trace Options Use this field to specify what kind of tracepoint you are setting. Enable the tracepoint by selecting the Trace Options checkbox, and choose the type of tracepoint you want from the drop-down list. The available types of tracepoints vary by processor family. For a description of all trace events, see 4. Filtering Trace. TWrap This option sets the Stop Trace When Buffer is Full flag.
3 Using Wind River Trace 3.6 Tracing Execution Figure 3-8 Trace View 3 (In Figure 3-8, the Event Occurrences column is collapsed to make it easier to read the information in the Instruction field.
Wind River Trace for Wind River Workbench Hardware Reference, 3.
4 Filtering Trace 4.1 Overview 63 4.2 Filtered Trace Options 64 4.3 Filtered Trace Limitations 67 4.1 Overview The filtered trace capabilities of the Wind River Trace use internal hardware breakpoints to trigger trace capture. You can select an Internal Hardware Code/Data breakpoint and choose the Filtered Trace options to control the trace capture.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 NOTE: Filtered trace uses the high speed Personality Module with Auto Voltage Sense. The Auto Voltage Sense features in the Personality Module assume that the customer provides the voltage reference signal. For the AMCC 405 and 440 processors, this is pin 12 of the 38-pin Mictor connector. For ColdFire processors, this is pin 9 of the 26-pin BDM connector.
4 Filtering Trace 4.2 Filtered Trace Options PID Changes Display a marker in the Events field whenever the Process ID (PID) of the running process changes. 4 Report Only This option will tell the processor to output a special trigger pattern, which will be captured, stored in the trace buffer, and reported as a matched “of” address. This option is only valid with the instruction code breakpoint. This option can also be set using low-level commands.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 Trace On Starts capturing trace when the matched address is hit. The trace capture will be disabled until there is an address match. You can stop trace capturing to preserve the starting matched address by enabling the Trace Until Buffer Is Full flag.
4 Filtering Trace 4.3 Filtered Trace Limitations Trace Sync Broadcast This is an internal Wind River option. Trace Trigger 4 This option is similar to Trace Off. The only difference is that once it hits the trigger and stops tracing, the trace will remain stopped until the next GO command is issued. Use the Post Trigger Counter to control the amount of trace captured after the address match. This option can also be set using low-level commands.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 ■ One Trace Around (TC) ■ One To Four Trace Trigger (TR) NOTE: When using both a Trace On (TE) and Trace Off (TD), the processor must execute the instruction at the Trace On address before the instruction at the Trace Off address. This is because the Wind River Trace module will treat the first trace event it encounters as the Trace On event.
4 Filtering Trace 4.3 Filtered Trace Limitations unique trigger event on the PST[0:3]/DDATA[0:3] lines. The debug exception is written to the address defined by the CF WSPACE option. The size of the WSPACE must be at least 1K bytes long and should be located in a free area of RAM. Also, the exception vector table entries at the offset addresses 0x30 and 0x31 are written with the address of the debug exception. The Vector Base Register (VBR) value must also be set to a location in RAM prior to running code.
Wind River Trace for Wind River Workbench Hardware Reference, 3.
4 Filtering Trace 4.3 Filtered Trace Limitations A debug exception can be used for filtered trace with the V3 Core with a Revision B+ Debug Module. The V3 Core, with a Revision B+ Debug Module, has four internal hardware code breakpoints.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 A debug exception can be used for filtered trace with the V4 Core with a Revision D Debug Module, since it does not have the debug exception problem of the V2 Core. The V4 core has four internal hardware code breakpoints.
5 Wind River Trace Performance 5.1 Introduction The number of trace instructions in Wind River Trace memory depends on the target processor’s operational mode. When the caches are enabled, the number of instructions executed in a given time frame is considerably greater than when the caches are disabled. Wind River Trace stores the trace information on every trace clock cycle.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 AMCC 440 is for four core clock cycles. When the caches are enabled, the trace information can show that up to 16 instructions were executed for any trace clock cycle. This means that with both the instruction cache and data cache enabled it is possible to see as many as 900,000 instructions stored in the trace memory.
A 38-pin Mictor Connector (AMCC 405 and 440 Processors) A.1 38-Pin Mictor Connector Specifications 75 A.2 AMCC 405 and 440 Timing Specifications 78 A.1 38-Pin Mictor Connector Specifications The recommended manufacturer’s part number for this 38-pin Mictor connector is part number AMP 2-767004-2. This connector’s pin-out information for the AMCC 405 processor is shown in Figure A-1. The pin-out information for the AMCC 440 processor is shown in Figure A-2.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 NOTE: These are the termination values for the Wind River reference design. It is important that you verify that the pull-up and pull-down values you use are appropriate for the board that you are working with.
A 38-pin Mictor Connector (AMCC 405 and 440 Processors) A.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 A.
B 26-pin BDM Connector (ColdFire Processors) B.1 Connector Signal Specifications 79 B.2 ColdFire Timing Specifications 85 B.1 Connector Signal Specifications The signal pin-out of the ColdFire BDM connector varies by ColdFire processor type. This appendix describes the signal pin-outs for each of the four standard 26 pin ColdFire BDM connectors based on the ColdFire processor type. Table B-1 breaks down the connector options by processor type.
Wind River Trace for Wind River Workbench Hardware Reference, 3.
B 26-pin BDM Connector (ColdFire Processors) B.1 Connector Signal Specifications B.1.1 Option One: 26-Pin BDM Connector ■ 26 (2 by 13) 0.025" square posts ■ 0.10" between centers of adjacent posts ■ A sample connector is Samtec part number TSW-113-07-S-D The pin-outs for the 2 by 13, 0.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 B.1.2 Option Two: 26-Pin BDM Connector ■ 26 (2 by 13) 0.025" square posts ■ 0.10" between centers of adjacent posts ■ A sample connector is Samtec part number TSW-113-07-S-D The pin-outs for the 2 by 13, 0.
B 26-pin BDM Connector (ColdFire Processors) B.1 Connector Signal Specifications B.1.3 Option Three: 26-Pin BDM Connector ■ 26 (2 by 13) 0.025" square posts ■ 0.10" between centers of adjacent posts ■ A sample connector is Samtec part number TSW-113-07-S-D The pin-outs for the 2 by 13, 0.
Wind River Trace for Wind River Workbench Hardware Reference, 3.0 B.1.4 Option Four: 26-Pin BDM Connector ■ 26 (2 by 13) 0.025" square posts ■ 0.10" between centers of adjacent posts ■ A sample connector is Samtec part number TSW-113-07-S-D The pin-outs for the 2 by 13, 0.
B 26-pin BDM Connector (ColdFire Processors) B.2 ColdFire Timing Specifications B.
Wind River Trace for Wind River Workbench Hardware Reference, 3.
C Volatility C.1 Introduction The Wind River Trace hardware consists of both volatile synchronous static RAM (SSRAM) and an electronically programmable logic device (EPLD). Table C-1 lists the manufacture and description of the Wind River Trace hardware.
Wind River Trace for Wind River Workbench Hardware Reference, 3.
Index Numerics B 26-pin BDM Connector (ColdFire Processors) 79 38-Pin Mictor Connector 78 38-pin Mictor Connector (AMCC 405 and 440 Processors) 75 38-Pin Mictor Connector Specifications 75 Before Trace Counter A Acquire Trace on GO (TRCAQU) 35 Address 56 Address Mask 56 After Trace Counter 57 AMCC 405 and 440 Processors 8 AMCC 405 and 440 Processors (Formerly IBM 405 and 440) 3 AMCC 405 and 440 Timing Specifications 78 AMCC 405 Processor 78 AMCC 405 Processor Performance 73 AMCC 405, 440, and Freescale
Wind River Trace for Wind River Workbench Hardware Reference, 3.
Index 71 Revision D Debug Modules 71 U Using the Trace View 46 Using Wind River Trace 15 S Safety Information 5 Save Output to File 54 Set Vector Base Register on IN Command (SET_ VBR) 36 Set Work Space (WSPACE) 36 Setting a Tracepoint 55 Setting CF Options With Low-level Commands 38 Setting CF Options With the CF Options View 37 Setting CF Options With the Configure Trace Button 37 Setting Configuration Options 36 Setting Up a Project 40 Signal Requirements for ColdFire Processors 9 Signal requirements
