WireTAP Run Control Tool for PowerPC Processors Installation Guide

Transcription

1 WireTAP Run Control Tool for PowerPC Processors Installation Guide Rev A Revised 2003/06/11

2 Metrowerks, the Metrowerks logo, CodeWarrior, CodeTEST, PowerTAP, CodeTAP, and WireTAP are trademarks or registered trademarks of Metrowerks Corporation in the United States and/or other countries. All other tradenames and trademarks are the property of their respective owners. Copyright 2003 Metrowerks Corporation. ALL RIGHTS RESERVED. No portion of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, without prior written permission from Metrowerks. Use of this document and related materials is governed by the license agreement that accompanied the product to which this manual pertains. This document may be printed for non-commercial personal use only in accordance with the aforementioned license agreement. If you do not have a copy of the license agreement, contact your Metrowerks representative or call (if outside the U.S., call ). Metrowerks reserves the right to make changes to any product described or referred to in this document without further notice. Metrowerks makes no warranty, representation or guarantee regarding the merchantability or fitness of its products for any particular purpose, nor does Metrowerks assume any liability arising out of the application or use of any product described herein and specifically disclaims any and all liability. Metrowerks software is not authorized for and has not been designed, tested, manufactured, or intended for use in developing applications where the failure, malfunction, or any inaccuracy of the application carries a risk of death, serious bodily injury, or damage to tangible property, including, but not limited to, use in factory control systems, medical devices or facilities, nuclear facilities, aircraft navigation or communication, emergency systems, or other applications with a similar degree of potential hazard. How to Contact Metrowerks Corporate Headquarters World Wide Web Metrowerks Corporation 7700 West Parmer Lane Austin, TX U.S.A. Sales United States Voice: United States Fax: International Voice: sales@metrowerks.com Technical Support United States Voice: International Voice: support@metrowerks.com

3 Table of Contents 1 About Your WireTAP Run-Control Tool 7 What is the WireTAP Run-Control Tool? Product Highlights System Installation Installing the IDE and Debugger Connecting System Hardware What to Do Next Debugging With the WireTAP Tool 15 System Startup Installation Confidence Test Create a Project Configure the Debugger Run the Project Congratulations! Notes on Using the WireTAP tool Run/Pause States Setting the Interface Clock Frequency Detecting Target Power Loss Connecting to Running Targets Applying and cycling the WireTAP tool power Sharing the Parallel Port with Other Devices Instruction Execution Breakpoints Additional 6xx/7xx/82xx Notes Additional 8xx Notes Generating a JTAG File Troubleshooting 31 Resolving System Startup Problems Is the problem on the host or target side? Can the Host Configure/Communicate with the WireTAP tool? WireTAP Run-Control Tool Installation Guide 3

4 Table of Contents Freescale Semiconductor, Inc. Can the WireTAP tool Communicate with/control the Target? Error Messages Getting Help Did you receive the WireTAP tool as part of a Motorola board kit? Did you purchase the WireTAP tool separately? Do you need CodeWarrior support? Specifications and Operating Requirements 43 WireTAP Specifications Connectors and LEDs DC electrical characteristics AC electrical characteristics Physical Characteristics Standard Precautions Power precautions Electrostatic Precautions Radio Interference Warning Target Requirements for WireTAP 6xx/7xx/82xx 51 Target requirements Evaluation boards Custom target requirements Target Connections Target power Need More Information? Target Requirements for WireTAP 8xx 57 Target Requirements Evaluation boards Target Connections Target power Need More Information? WireTAP Run-Control Tool Installation Guide

5 Table of Contents 7 Parallel Port Driver Reference 61 Overview of WireTAP Driver Software Driver Installation Verifying driver startup (Windows NT/2000 only) Sharing the parallel port with another device Registry Creation (Win9x only) Resolving Win9x Port and Addressing Problems Index 67 WireTAP Run-Control Tool Installation Guide 5

6 Table of Contents Freescale Semiconductor, Inc. 6 WireTAP Run-Control Tool Installation Guide

7 1 About Your WireTAP Run-Control Tool The Metrowerks WireTAP TM Run-Control Tool provides a cost-effective approach to developing and debugging systems that use the PowerPC microprocessor. This chapter provides an introduction to the product features as well as procedures for host configuration and WireTAP hardware installation. System startup, debugger setup, and an installation confidence test are covered in Debugging With the WireTAP Tool on page 15. This chapter has the following sections: What is the WireTAP Run-Control Tool? on page 7 System Installation on page 10 What to Do Next on page 14 What is the WireTAP Run-Control Tool? The WireTAP run-control tool uses advanced emulation technology to provide control of and visibility into your PowerPC target system. Combined with an integrated host debugger, using the WireTAP tool speeds the debugging process by providing the ability to control and examine the state of your target system interactively. WireTAP Run-Control Tool Installation Guide 7

8 About Your WireTAP Run-Control Tool What is the WireTAP Run-Control Tool? Freescale Semiconductor, Inc. Product Highlights The following bullets summarize key benefits of the WireTAP run-control tool if used with a CodeWarrior product. Gain optimal performance: Split-second single-step execution. Up to 15 MB/minute code download to target, depending on processor and target design: 6xx/7xx/82xx/5200: 1.5 MB/minute 8xx: 15 MB/minute Control and debug your software running in-target, with minimal intrusion into target operation. Use software or hardware breakpoints: 6xx/7xx/82xx: Up to 1024 software execution breakpoints, or one on-chip hardware breakpoint. 8xx: Up to 32 software breakpoints or 4 on-chip hardware breakpoints. Get crash-proof control of the PowerPC processor. Obtain and modify register contents. 8 WireTAP Run-Control Tool Installation Guide

9 About Your WireTAP Run-Control Tool What is the WireTAP Run-Control Tool? Display and modify memory. Control instruction execution. Run/stop/step/reset. The WireTAP tool for 6xx/7xx/82xx supports: 603, 603e, 603ev, 603ei, 603r, 7400, 7410, 750, 740, 745, and 755 variants, and the PowerQUICC II 8240 and The WireTAP 8xx provides support for all speed grades and variants of the MPC860, MPC821, MPC855, MPC850, MPC801, MPC823, and MPC5200. Expect rapid deployment of COP drivers for new processors or mask revisions. Combine powerful C/<cee>C<cpp>++ symbolic debugger with integrated interface to all features of WireTAP. Debug code in ROM, RAM, and flash. WireTAP 6xx/7xx/82xx, Quiescent Acknowledge, QACK, tied low for simple target connection for 603e and EC603e processors. Eliminates tying QACK low on target. Low-voltage processor compatible. Optional CodeTEST Software Test and Analysis Tools. Trace software execution flow in cache. Trace triggering on code execution in cache. Use detailed source-level trace to validate complex code execution despite cache and pre-fetch operations. The debugging environment The WireTAP works with debuggers which have been integrated with the WireTAP to give you control over the emulation functions and your target. The WireTAP offers debugging capabilities without requiring you to modify any target code or provide any special target I/O port (other than JTAG or DPI port) for communications with a monitor. WireTAP benefits The WireTAP provides these key benefits: Visibility: The WireTAP makes it possible for the debugger to display registers and the current state of target memory. You can halt program execution at predefined states, and examine the data for a particular program state. WireTAP Run-Control Tool Installation Guide 9

10 About Your WireTAP Run-Control Tool System Installation Freescale Semiconductor, Inc. Control: You can conveniently control the state of the target system by downloading code, manually modifying processor registers and memory, singlestepping through the code, or setting breakpoints. Transparency: When you use the WireTAP, it is virtually indistinguishable from non-debug target execution. System Installation CAUTION The WireTAP Run-Control Tool is easy to install and use. The WireTAP contains components that are subject to damage from electrostatic discharge. Whenever you are using, handling, or transporting the WireTAP, or connecting to or disconnecting from a target system, always use proper anti-static protection measures, including using static-free bench pads and grounded wrist straps. Refer to the Quick Start Guide for an illustrated guide to hardware connection and setup. It is included in PDF format with all systems, and supplied in printed form with most. If you have any problems, see the chapters following this one for detailed requirements and troubleshooting. NOTE Windows NT, Windows 2000: If you will be using the CodeWarrior IDE/debugger on a PC running Windows NT/2000/XP, you will need administrator privileges to perform installation. The installation program creates new system registries so that WireTAP s parallel port driver is automatically loaded when you boot up the computer. Installing the IDE and Debugger You should install the software and request a license before proceeding with WireTAP installation. WireTAP relies on a driver and registry keys that are part of software installation. In addition, the CodeWarrior debugger is license controlled, and obtaining a license key can take several hours. 10 WireTAP Run-Control Tool Installation Guide

11 About Your WireTAP Run-Control Tool System Installation To install the debugger 1. Locate the CodeWarrior IDE/debugger CD-ROM and installation instructions. 2. Follow the debugger instructions to complete installation. 3. When prompted, register and request a license. 4. When installation is complete, reboot your PC to activate the new registries. NOTE Windows NT/2000 loads the port driver on boot up. If you encounter driver conflicts during reboot, see Sharing the parallel port with another device on page 63 for a discussion of the issues and possible solutions. Connecting System Hardware Your host PC must meet these minimum requirements. Component Processor OS RAM Disk storage space Parallel port Port address Supported minimums Pentium-class or higher Windows NT 4.0 SP4 or higher Windows 95 Windows 98 Windows 2000 Windows XP 32 MB (64 MB recommended) See debugger documentation LPT port with ECP mode enabled Default port address (Win9x only): LPT1: 378 LPT2: 378 LPT3: 278 LPT4: Not set WireTAP Run-Control Tool Installation Guide 11

12 About Your WireTAP Run-Control Tool System Installation Freescale Semiconductor, Inc. NOTE WireTAP performance is dependent on the speed of the PC and the host system resources used by other applications during debugging. ECP (Extended Capabilities Port) is a parallel port standard for PCs that supports bidirectional communication between the PC and the attached device Win9x users must adjust registry settings if non-default port addresses or LPT4 are used. See Resolving Win9x Port and Addressing Problems on page 65 before attempting to connect to WireTAP. NOTE Checking the CMOS setup to ensure that the parallel port meets requirements is optional. Most PCs manufactured in the last five years use the required settings. However, most initial connection failures result from improper port configuration. To confirm that the parallel port meets requirements NOTE The procedure summarizes how to check your current parallel port settings and modify them if necessary. Because each BIOS provides a slightly different setup utility and uses different settings for port configuration, someone familiar with BIOS configuration should perform these steps. 1. Reboot your PC. 2. Watch the boot messages for one that lets you start the BIOS/CMOS setup utility. For example, PRESS [DEL] TO ENTER SETUP 3. Use the BIOS setup controls to page to the port configuration settings. They are usually in an I/O device configuration section. 4. Locate the parallel port to which the WireTAP will connect. 5. Confirm that ECP mode is enabled. 6. (Win9x only) If the port address for the port does not match the defaults shown in the foregoing table, note the port address. You will need it in Step WireTAP Run-Control Tool Installation Guide

13 About Your WireTAP Run-Control Tool System Installation 7. Exit the setup program, saving any changes, and allow the PC to complete bootup. 8. (Win9x only) If your port address does not match defaults, turn to Resolving Win9x Port and Addressing Problems on page 65, complete that procedure, then return. To connect the WireTAP tool to host and power 1. Connect the IEEE 1284 cable (P/N ) between the host parallel port and the 25-pin parallel port on the WireTAP. 2. Connect the pin plug of the power supply ( ) to the pin jack on the side of the WireTAP. To connect the WireTAP tool to the target 1. If you are connecting to a custom target, rather than a supported evaluation board, see one of the following to confirm that the signal interface connections meet requirements: 6xx/7xx/82xx: Target requirements on page 51. 8xx: Target Requirements on page Connect the WireTAP s flexible ribbon cable to the JTAG or DPI connector on the target board. The red lead indicates pin 1. See the following for connector pinouts: 6xx/7xx/82xx: Figure 5.1 on page 54 8xx: Figure 6.1 on page If you are using an evaluation board, see: MPC*** Kit Installation Guide for additional host/target connections, including board power setup and optional target serial connection. Tested Jumper and Dipswitch Settings in CodeWarrior: Targeting Embedded PowerPC for required settings of board switches and jumpers. 4. Turn to Debugging With the WireTAP Tool on page 15 to complete installation. WireTAP Run-Control Tool Installation Guide 13

14 About Your WireTAP Run-Control Tool What to Do Next Freescale Semiconductor, Inc. What to Do Next In the next chapter, you complete installation by: Starting the system Configuring the debugger Running a project Reviewing general operation and special operational notes 14 WireTAP Run-Control Tool Installation Guide

15 2 Debugging With the WireTAP Tool This chapter describes system startup procedures and debugger configuration, confirms successful installation, and provides important information about using the system. This chapter has the following sections: System Startup on page 15 Installation Confidence Test on page 16 Notes on Using the WireTAP tool on page 22 System Startup The following sections take you step-by-step through powering up the system and starting the debugger. These instructions assume that you have already done the following: Connected the WireTAP tool to your host computer. Connected the WireTAP tool to the target system. Configured the BIOS for ECP mode parallel communications on the port that will be used. Installed the debugger software and requested a license. To power up the system 1. Apply power to the target system. If you are using a Motorola evaluation target, follow the power-up instructions provided in the board documentation. WireTAP Run-Control Tool Installation Guide 15

16 Debugging With the WireTAP Tool Installation Confidence Test Freescale Semiconductor, Inc. 2. Plug the WireTAP tool power supply cable into a power source or a switchable power strip, and apply power. LEDs are provided to indicate the status of the WireTAP tool. LED Activity Description Power Red - solid the WireTAP tool power is on. Orange - solid Unlit the WireTAP tool and target power are on. the WireTAP tool power is off. TX/RX Green - flashing the WireTAP tool receiving from host. Red - flashing Orange - flashing the WireTAP tool transmitting to host. Transmitting and receiving. Run/Pause Green - solid Target is running. Red - solid Target is paused. Installation Confidence Test The following procedures use sample projects to verify successful installation. Create a Project Debuggers that support the WireTAP tool must be configured to use the required communications and debug settings. Preference panels are provided to simplify this procedure. NOTE The CodeWarrior Remote Connections panel provides templates for all connection devices, such as the PowerTAP, WireTAP, and CodeTAP tools. This section provides brief the WireTAP tool specific startup procedures. If you need more detailed information about CodeWarrior startup, see the CodeWarrior: Targeting Embedded PowerPC manual. 16 WireTAP Run-Control Tool Installation Guide

17 Debugging With the WireTAP Tool Installation Confidence Test To create a project and connection 1. Install the license string that you received from license@metrowerks.com. In CodeWarrior, see install_dir\metrowerks\codewarrior\ Licensing\License_install.txt. NOTE You cannot build or debug code until you have installed the license string. 2. From Start Programs Metrowerks CodeWarrior, start CodeWarrior for EPPC. 3. From the Edit menu, select Preferences, click Remote Connections, and click Add. 4. Give your connections file a name, and ensure that WireTAP JTAG or WireTAP 8xx is selected in the Debugger field. Ensure the Interface Clock Frequency (for the JTAG or DPI interface) is at or below the maximum clock rate for your processor. NOTE Differences in target design can affect the maximum reliable JTAG or DPI serial rate. If you encounter problems, reduce the clock rate. See also Setting the Interface Clock Frequency on page 22 for a discussion of issues. 5. See Table 2.1 for the remaining settings. Recommended settings are bold italic. 6. Click File New, and select EPPC Stationery Wizard. 7. Give your project a name, and click OK. NOTE To be able to edit debugger preferences, you must open a project. 8. In the Target Dialog, select the target type and processor, and enable Present Detailed Wizard. NOTE If you are using a custom target, select a type that approximates your target. After this confidence test, see Appendix B and C in WireTAP Run-Control Tool Installation Guide 17

18 Debugging With the WireTAP Tool Installation Confidence Test Freescale Semiconductor, Inc. 9. Click Next, and select C++. CodeWarrior: Targeting PowerPC for procedures to create initialization files for your target. 10. Click Next and select the connection that you created in Step Click Finish to generate the project. Table 2.1 CodeWarrior preference settings for the WireTAP tool IDE Preferences, Debugger: Remote Connections Option Selection Comments Name User specified Creates a named file which contains connection and the WireTAP tool startup settings. Debugger AMCWireTAP JTAG AMCWIRETAP8xx Selects the WireTAP 6xx/7xx/82xx. Selects the WireTAP 8xx. Connection Type Parallel Required. Parallel Port LPT1~4 LPT4 is not automatically supported. See To add entries for unsupported ports on page -66. Interface Clock Frequency 32, 24, 16, 8, 4 See Setting the Interface Clock Frequency on page -22 for considerations. Mem Read Delay Mem Write Delay Number of additional processor cycles inserted as a delay for completion of memory reads. Number of additional processor cycles inserted as a delay for memory writes. Reset on Launch Enable/Disable Issues a hard reset to the target board before executing any debug initialization file. 32-Bit Mode Enable/Disable When enabled, indicates the CPU is set to use only half of the 64-bit data bus. 18 WireTAP Run-Control Tool Installation Guide

19 Debugging With the WireTAP Tool Installation Confidence Test Table 2.1 CodeWarrior preference settings for the WireTAP tool (continued) IDE Preferences, Debugger: Remote Connections Option Selection Comments Show Inst Cycles (the WireTAP tool 8xx only) Serialize Instruction Execution (the WireTAP tool 8xx only) None Indirect Flow All Enable Disable No show cycles are performed. All indirect change of flow. All change of flow (direct and indirect). All fetch cycles. This option sets or clears bits 30 and 31 of the ICTRL register. For more on show cycles and the ICTRL register, see the Motorola MPC8XX User's Manual. Forces the core to serialize. Normal mode. Core is not serialized. Enable Logging Enable/Disable At connection, opens Protocol logging window and echoes all debug transactions. If the AMCTAP_LOG_FILE environment variable is set, logging is routed to the specified file, and the log window does not open. Configure the Debugger Several preference panels control how the debugger handles your program. For this demonstration, most default settings will work. To configure the debugger 1. Click Debug Version Settings in the project toolbar. 2. Select Debugger: Remote Debugging, and use the dropdown list to select the connection file you created. 3. Select Debugger: Debugger Settings preference panel, and ensure that Stop on application launch is enabled. WireTAP Run-Control Tool Installation Guide 19

20 Debugging With the WireTAP Tool Installation Confidence Test Freescale Semiconductor, Inc. 4. Select the Debugger: EPPC Debugger Settings preference panel and ensure that the correct processor is selected, and that the target OS is set to BareBoard. In most cases, a target initialization file will have been selected when you used the wizard to create the project. 5. Use Table 2.2 to examine the remaining settings that can apply. Table 2.2 CodeWarrior preference settings for the WireTAP tool Target Preferences, Code Generation: EPPC Processor Options Selections Comment Struct Alignment PowerPC Must be set to PowerPC. Function Alignment Specifies alignment from 4 to 128 bytes. Processor Specifies the processor to the compiler. Target Preferences, Debugger: Debugger Settings Options Selections Comment Stop on Launch Program entry Breaks at default entry, typically main. User specified Breaks at any specified program location. Default entry Breaks before any instructions are executed. Target Preferences, Debugger: Remote Debugging Options Selections Comment Connection Varies Select the connection file that you created in IDE Preferences, Debugger: Remote Connections. Remote Download NA Does not apply. Launch Remote Host NA Does not apply. Target Preferences, Debugger: EPPC Debugger Settings Options Selections Comment Target Processor Variants of MPC 6xx,7xx, 82xx, 8xx These selections control debugger settings, such as register display. Choose the one closest to your variant. Some 745/755 control registers are not available in the Registers windows. 20 WireTAP Run-Control Tool Installation Guide

21 Debugging With the WireTAP Tool Installation Confidence Test Table 2.2 CodeWarrior preference settings for the WireTAP tool (continued) Target OS Bareboard Select BareBoard. Use Target Initialization File Use Memory Configuration File Verify memory Writes Enable/Disable Enable/Disable Enable/Disable Prebuilt files are autoselected for supported boards. To clone one look in..\powerpc_eabi_support\ Initialization_Files\JTAG or BDM. Optional file that specifies the legally accessible memory regions of your target. For samples, see...\powerpc_eabi_support\initialization_files\mem ory. Performs read-after-write verification. Debugger Menu, EPPC cascading menu Options Selections Comment Breakpoint Type Watchpoint Type Auto Software Hardware Read Write Read/Write WireTAP selects. Uses software breakpoints. Uses on-chip breakpoint register(s). Triggers on read access. Triggers on write access. Triggers on read or write access. Run the Project Once you have configured the debugger, you are ready to run the project. To run the project 1. If necessary, apply power to the WireTAP tool and the target board. 2. In the Project toolbar, click the Debug button. If everything is working properly, you should see: A progress dialog showing the project being built. A connection dialog showing connection to the WireTAP tool and image download. The debugger window should come up, and program execution should stop at main(). WireTAP Run-Control Tool Installation Guide 21

22 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Freescale Semiconductor, Inc. If there is a problem, consult Chapter Troubleshooting. Congratulations! If the debugger connects to the WireTAP tool, loads the program, and runs, you have successfully completed installation. You are now ready to begin actual debugging. For important operational notes, see the remainder of this chapter. Using CodeWarrior For details on creating projects and using the debugger, refer to the CodeWarrior: Targeting Embedded PowerPC manual. Notes on Using the WireTAP tool Please familiarize yourself with the WireTAP tool operation. Run/Pause States When powered on and connected to the target, the WireTAP tool is always in one of two states, or modes: run or pause. The LED labeled Run/Pause indicates the current state. Run mode When the WireTAP tool is in run mode, the target s processor is running your target code. (LED: green) Pause mode When the WireTAP tool is in pause mode, the target s processor has stopped running target code. (LED: red) Setting the Interface Clock Frequency The WireTAP tool uses an asynchronous clock to drive the JTAG or DPI interface. The WireTAP tool can generate the clock signal at the following speeds: 32 MHz, 24 MHz, 16 MHz, 8 MHz, 4 MHz. Current processor clock maximums are as follows (as specified by the manufacturer): 22 WireTAP Run-Control Tool Installation Guide

23 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Processor Max rate (MHz) Processor Max rate (MHz) ei xx Debug clock = Bus speed/ NOTE Variations in the design of target systems make it impossible to guarantee that all systems can be operated at the maximum clock rates. Such variations include circuit impedances, trace lengths, and signal terminations. You may need to select a lower clock rate for reliable operation. Setting the clock rate in CodeWarrior CodeWarrior supports adjustments of the JTAG or DPI interface clock rate: In CodeWarrior, use the Interface Clock Frequency pull-down in the connections file created in the IDE Preferences: Debugger: Remote Connections preference panel. The rate can also be set in an initialization file using the AMCTargetInterfaceClockFreq command. Detecting Target Power Loss the WireTAP tool monitors target power through the JTAG or DPI cable. If target power is lost during normal operation, the Power LED turns from orange to red. If power is lost while in pause mode, a warning message is displayed the next time you attempt to enter run mode. Connecting to Running Targets At target power up, the WireTAP tool detects the presence of target power and asserts the HRESET pin to reset the target when the connection is first made. For this reason, you cannot connect to a running target and debug the currently running image. Successful connection requires that the target be stopped or reset. WireTAP Run-Control Tool Installation Guide 23

24 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Freescale Semiconductor, Inc. Applying and cycling the WireTAP tool power There is no required power-on power sequence. The WireTAP tool has circuitry to protect both the WireTAP tool and the target system regardless of which is powered on first. Cycling power is the simplest way to reset the WireTAP tool in the event that it no longer responds. To cycle power Remove and re-insert the power supply pin plug. Sharing the Parallel Port with Other Devices the WireTAP tool does not require dedicated access to the parallel port. Even so, Applied Microsystems encourages dedicating a port to the WireTAP tool use whenever possible. If you must share the parallel port, see Sharing the parallel port with another device on page -63 for a discussion of the issues. Instruction Execution Breakpoints the WireTAP tool provides two types of instruction (also referred to as execution) breakpoints: hardware and software. To maximize resources, it is best to leave the breakpoint type selector in its default setting (Auto). In the CodeWarrior IDE, you access this setting from the Debug EPPC menu. When Auto is selected: Software breakpoints are used unless the instruction resides in read-only memory. They can be placed only in writable memory. On 6/7xx, 82xx, and 74x0 processors, the hardware resource is used for software breaks. It is used only when the instruction resides in read-only memory. For both types of breakpoints, please note the following: If you specify an address, the address must be on a four-byte boundary. Program execution stops before execution of the target instruction. 24 WireTAP Run-Control Tool Installation Guide

25 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Software instruction breakpoints When a software breakpoint is requested, the target instruction is replaced with a special opcode. WireTAP 6xx/7xx/82xx uses a TRAP (0x7fe00008) instruction. the WireTAP 8xx uses an illegal (0x ) instruction. When the breakpoint occurs, execution is halted, and the original instruction is placed back into memory. When you view memory, you see your program code, not the breakpoint instruction. Using software breakpoints requires that any breakpoint location reside in RAM so that the special opcode can be written to target memory. Note that, if the breakpoint memory location is overwritten while your target is running, the breakpoint will not trigger, even though the breakpoint continues to be listed in the Breakpoints window. This could happen due to a problem in your software, such as an errant pointer, or even in normal operation, such as when code sections are copied from ROM to RAM. The WireTAP 6xx/7xx/82xx provides 1024 software instruction breakpoints. The WireTAP 8xx provides 32 software instruction breakpoints. Hardware breakpoints The PowerPC 8xx processors provide four hardware breakpoints. The 6xx/7xx, 82xx, and 7400 processors provide one hardware execution breakpoint. Unlike software breakpoints, a hardware breakpoint works in ROM and in flash memory. WireTAP 6xx/7xx/82xx only: While the hardware breakpoint is set, no software breakpoints can be set. Single-stepping Anytime that the debugger is unable to allocate a breakpoint resource to perform a source-level step operation, it uses assembly-level stepping in order to accomplish the source step. Typically this occurs when all hardware resources are in use, or when stepping through ROM. You will see a step warning, but the debugger will attempt to perform assembly-level steps until it reaches the address where it would normally set the source-level breakpoint. If the step operation is a stepover a branch, the operation can be extremely slow. WireTAP Run-Control Tool Installation Guide 25

26 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Freescale Semiconductor, Inc. Breakpoints on exceptions: Interrupts and the machine status save/restore registers Care must be taken when setting breakpoints in exception handler code. A typical PPC exception consists of a prologue that saves processor context, the actual exception handler, and then an epilogue that restores processor context. The rule is you can use software breakpoints in the actual exception handler code, but not in the code where processor context is being saved. Placing the CPU into debug mode is just another interrupt. For example: your code is in an interrupt epilogue and has just placed the return address into SRR0 when a breakpoint occurs. The breakpoint causes the IP for the address of the breakpoint to be written to SRR0, destroying your original return address. Stepping through code which accesses SRR0 and SRR1 exhibits the same problem. To avoid this problem, always set your breakpoints before or after code which accesses SRR0 and SRR1, and never single-step through such code. For example, you can set your breakpoint anywhere after the interrupt prologue, but before the epilogue. Instructions that involve the SRR0 and SRR1 registers are MTSPR SRR0/1,RX, MFSPR RX,SRR0/1, SC, and RFI. Additional 6xx/7xx/82xx Notes Modifying the IABR or trace bits of the MSR When using the WireTAP tool, do not modify the IABR or trace bits in the MSR. Whenever the WireTAP tool enters run, it places the processor in soft-stop mode. This means instead of taking a trace exception, the processor will simply stop. Depending on the processor, it stops on an illegal instruction (60x, 82xx), or takes a program exception (7xx, 7400). Access (load/store) breakpoints (740/750/8xx processors only) The WireTAP tool uses the load/store breakpoints provided on the PowerPC processor. With these breakpoints, program execution halts immediately after the access. 26 WireTAP Run-Control Tool Installation Guide

27 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Polling memory access status The UseRUNNDATCheck environment variable enables the WireTAP tool to poll memory status to determine whether each memory access has completed. In rare situations, you may need to enable this switch to prevent and debug memory access errors in very slow memory regions. When enabled, UseRUNNDATCheck performs an additional JTAG polling operation after each memory operation. The variable defaults to OFF because such polling can double the time necessary for downloads and single-steps. If you detect memory access problems perhaps by enabling Memory Write Verify in the EPPC Target Settings preference panel then try enabling UseRUNNDATCheck to see if it fixes the problem. For instructions, see Is data being corrupted? on page bit data mode The 6xx, 82xx, and some 7xx(x) processors can be put in 32-bit data mode. When the processor is in this mode, data is read and written using just half of the bus. When using this mode, you must preconfigure the WireTAP tool. In CodeWarrior, enable the 32-Bit Mode checkbox in the Remote Connections preference panel. Software watchdog timer The MPC8260 s software watchdog timer (SWT) is enabled after a reset. The SWT times out periodically and resets the processor. To successfully emulate, you must disable the software watchdog enable bit (SWE) in the system protection control register (SYPCR). This is done with a target initialization file. See Table 2.2 on page 20. Additional 8xx Notes Breakpoints in ISRs: enabling recoverable interrupts The recoverable interrupt bit (MSR RI ) of the machine state register (MSR) indicates whether the interrupt is restartable. If this bit is not set, the target CPU may not respond to breakpoints. To the processor, a normal, maskable break looks just like any other interrupt/exception. WireTAP Run-Control Tool Installation Guide 27

28 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Freescale Semiconductor, Inc. For example, if you want to set a breakpoint at the beginning of an interrupt service routine, you need to ensure that the recoverable interrupts are enabled, and that the machine status save/restore registers (SSR0/SSR1) are correctly written. To handle exceptions, your interrupt service routine must do the following: 1. Save the SSR0 and SSR1 registers to memory. 2. Set the MSR RI bit. 3. Execute any exception processing. 4. Clear the MSR RI bit. 5. Restore the SSR0 and SSR1 registers. 6. Execute the RFI system call. For more information on recoverable interrupts, see the Motorola MPC8XX User s Manual. Access (load/store) breakpoints (740/750/8xx processors only) The WireTAP tool uses the load/store breakpoints provided on the PowerPC processor. With these breakpoints, program execution halts immediately after the access. Software watchdog timer The MPC8xx software watchdog timer (SWT) is enabled after a reset. The SWT times out every four seconds and resets the processor. If you don t plan to use the SWT, you must clear the software watchdog enable bit (SWE) in the system protection control register (SYPCR) to disable the timer. This is done with a target initialization file. See Table 2.2 on page 20. Serialize instruction execution The MPC8xx core has multiple execution units; these allow instructions to be executed concurrently. By setting the MPC8xx Instruction Support Control Register (ICTRL) register bit (29), you can force the CPU core to serialize. The Serialize Instruction Execution option clears bit 29 of the ICTRL register. 28 WireTAP Run-Control Tool Installation Guide

29 Debugging With the WireTAP Tool Notes on Using the WireTAP tool For information about serialization of the MPC8x core, see the Motorola MPC860 User's Manual. You can't have Serialize Instruction Execution disabled and have Show Instruction Cycles set to ALL at the same time. According to the Motorola MPC860 User's Manual, this is an illegal combination for the ICTRL bits (29:31). Generating a JTAG File the WireTAP tool support software includes JTAG configuration files for most of the MPC6xx, 7xx, 74xx, and 82xx variants. When you launch a debug session, the WireTAP tool reads the PVR register of the target processor, determines the variant, and automatically loads the correct JTAG configuration file. Occasionally, Motorola or IBM issues a new PowerPC variant with a new PVR value. When it encounters an unknown value, the WireTAP tool aborts the connection and signals an unknown PVR value. To correct this problem before Applied issues an updated set of JTAG files, you can sometimes clone a new JTAG file from the existing ones. To clone a file 1. Locate the current set of JTAG files in the CodeWarrior installation directories...\metrowerks\codewarrior\bin\plugins\ support\amctap\powertap 2. Determine which existing JTAG configuration file to use as a basis for your new file. Frequently, you can use heuristics to determine the correct base file. For example, if the PVR reported at startup is 0x , you should look for another file that attaches a three-digit prefix to IBM versioning uses a prefix to the original Motorola number (here 70201); whereas Motorola increments the final digit. Select the file that supports a processor that is architecturally closest to the one on your target. 3. Copy the base file to the new name. the WireTAP tool expects the filename to be in the following format: pvr_string.jtag For example, a PVR of 0x becomes jtag WireTAP Run-Control Tool Installation Guide 29

30 Debugging With the WireTAP Tool Notes on Using the WireTAP tool Freescale Semiconductor, Inc. 4. Attempt to start the debug session again. If you selected the correct base file and applied the correct name, the WireTAP tool should connect successfully. If not, try using another related JTAG file as a base. Customer Support can assist you is you are unable to generate a JTAG file that works. For more information, see Getting Help on page 40. For a list of all current PVR numbers for all versions of Motorola PowerPC processors, see the following URL: allelse/allelse.html 30 WireTAP Run-Control Tool Installation Guide

31 3 Troubleshooting WireTAP setup and use is designed to be straightforward. However, some problems may occur. If the solutions presented in this chapter fail to resolve your problem, see the Getting help section for customer support contact procedures. This chapter has the following sections: Resolving System Startup Problems on page 31 Error Messages on page 38 Getting Help on page 40 Resolving System Startup Problems During initial system startup (and anytime that basic system requirements are not met), you may experience the problems described in the following sections. If, on the other hand, you have been able to connect, download, and run, step, and break, you may have a problem beyond the scope of the solutions presented here. For system startup problems, try to determine whether the problem lies on the host or target side. Then use the questions, in the order presented, to isolate the point of failure. That will help identify what works and what doesn t if you must contact customer support. If you have experienced a sudden failure in a previously working system, scan the questions for the symptom closest to what you are seeing. Is the problem on the host or target side? To begin debugging a startup problem, use the following procedure to help identify the source of the problem. 1. Disconnect the JTAG or DPI ribbon cable from the target. 2. In the CodeWarrior Debug menu, select Connect. WireTAP Run-Control Tool Installation Guide 31

32 Troubleshooting Resolving System Startup Problems Freescale Semiconductor, Inc. If you see the following message, the host is able to communicate with the WireTAP tool. The problem resides on the target side. No target power or the JTAG cable has been disconnected. Almost any other message indicates that the problem resides in the host configuration or hardware, or the parallel connection. See the appropriate section below for possible solutions. NOTE Although the following sections touch on debugger configuration issues, you should also consult the CodeWarrior: Targeting Embedded PowerPC manual for debugger troubleshooting. Can the Host Configure/Communicate with the WireTAP tool? Unless you receive an error that is specific enough to identify the source of the problem, perform the following checks in order until the problem is identified and resolved. Is AMC WireTAP or AMC WireTAP 8xx the selected device in the connection preferences? 1. Select Edit Preferences, and open the Debugger: Remote Connections preference panel. 2. Confirm that, in the selected connection, Debugger is set to EPPC AMC WireTAP Protocol Plugin WireTAP for the 6xx/7xx/82xx, or to EPPC AMC WireTAP8xx Protocol Plugin for the 8xx. Is the correct parallel port selected in the debugger preferences? 1. Select Edit Preferences, and open the Debugger: Remote Connections preference panel. 2. Confirm that, in the selected connection, Parallel Port is set to the correct LPT port. 32 WireTAP Run-Control Tool Installation Guide

33 Troubleshooting Resolving System Startup Problems Is the WireTAP tool receiving power? The Power LED should be orange (target and the WireTAP tool receiving power) or red (the WireTAP tool receiving power; target power off). Is the IEEE 1284 parallel cable the one that was shipped with the WireTAP tool? Look for a label showing AMC P/N The AMC part is an off-the-shelf IEEE 1284 cable. If you aren t using the original part, make sure that the cable you are using is a true IEEE 1284 cable. Is the parallel cable securely connected to the correct port? Disconnect and reconnect the cable at both ends. If you have more than one parallel port, ensure that the WireTAP tool connects to the one selected in the IDE Preferences: Remote Connections file. Is the parallel port provided by an expansion card? 1. If the parallel port is provided by an expansion card, reconnect the WireTAP tool to a parallel port supplied by the motherboard. 2. In IDE Preferences: Remote Connections, select the new port. 3. In the Debug menu, click Connect. Is the Zeecube parallel port driver running? See Verifying driver startup (Windows NT/2000 only) on page 62 for procedures. Is the parallel port configured for ECP mode? See To confirm that the parallel port meets requirements on page 12. (Win9x only) Is the parallel port address other than 378 (LPT1/ 2) or 278 (LPT3)? See To confirm that the parallel port meets requirements on page 12 for procedures for viewing your port setup. If the port address is non-default, use To resolve port address assignments on page 66 to modify the registry entries. WireTAP Run-Control Tool Installation Guide 33

34 Troubleshooting Resolving System Startup Problems Freescale Semiconductor, Inc. Can the WireTAP tool Communicate with/ Control the Target? Target-side problems can be more troublesome to isolate. In general, if the simple test above indicates a target-side problem, it is most likely not a WireTAP malfunction. The following suggestions are intended to help narrow the source of your problem to debugger configuration or the target hardware. Are you able to connect to the target? NO: Go on to the next question. YES: If you can connect, but downloads fail, skip to Are you able to download to target? on page 35. Is your processor supported? WireTAP 6xx/7xx/82xx currently supports 603, 603e, 603ev, 603ei, 603r, 7400, 7410, 750, 740, 745, and 755 variants, MPC5200, and the PowerQUICC II 8240 and WireTAP 8xx supports all speed grades and variants of the MPC860, MPC821, MPC855, MPC850, MPC801 and MPC823. If the processor isn t listed here (or in the release notes), the WireTAP tool might be unable to identify the processor and apply the correct configuration file. Contact Customer Support. 6xx/7xx/82xx: Until support is added for your variant, you may be able to clone a JTAG configuration file that will work. See Generating a JTAG File on page 29. Is the JTAG or DPI cable correctly and securely connected? 1. See the connector pinout and connection illustration: 6xx/7xx/82xx: Figure 5.2 on page 54 8xx: Figure 6.1 on page Ensure that the cable header and the target s Pin 1 are properly aligned. The red lead should be oriented to the Pin 1 side of the target connector. 3. Ensure that the header is firmly seated in the target s connector. 34 WireTAP Run-Control Tool Installation Guide

35 Troubleshooting Resolving System Startup Problems Is the JTAG or DPI clock rate too high? 1. See the table on page 22 for the maximum clock rate for your processor variant. 2. Use the Interface Clock Frequency setting in the IDE Preferences, Debugger: Remote Connections preference panel to reduce the interface clock rate, and attempt to connect. If this corrects the problem, consider the discussion of possible causes in Setting the Interface Clock Frequency on page 22. Does CodeWarrior report a JTAG or DPI protocol error? This error can have several causes. If the parallel cable is defective (broken lead, bent pin, etc.), not all signals will be detected. Try substituting a known good IEEE 1284 parallel cable. 6xx/7xx/82xx: The JTAG configuration file may be corrupted. The JTAG or DPI connector on your target may not meet requirements. If you have a custom target, see Custom target requirements on page 52. Is your target malfunctioning? 1. If possible, substitute a known good target board preferably a Motorola evaluation board. 2. Ensure that the jumpers and switches are configured in their default settings. See Tested Jumper and Dipswitch Settings in CodeWarrior: Targeting Embedded PowerPC for required settings of board switches and jumpers. If these procedures correct the problem, and if yours is a custom target, see Custom target requirements on page 52 to confirm that your target interface meets WireTAP requirements. Are you able to download to target? NO: Continue to the next question. YES: Skip to Is data being corrupted? on page 36. WireTAP Run-Control Tool Installation Guide 35

36 Troubleshooting Resolving System Startup Problems Freescale Semiconductor, Inc. Are you able to read and write registers? 1. In the target settings preferences (ALT-F7), open the Code Generation: EPPC Processor preference panel, and ensure that the correct processor and code settings are selected. 2. In the View Registers Windows menu, select GPR. The current register values should be displayed. 3. Select any register, write a new value, and enter it. The display should reflect the updated value. If you are able to read and write selected registers, basic connection to the target is confirmed. Your problem is probably one of target configuration or target software. Are you able to read and write to RAM? 1. If necessary, configure memory using the CPU s configuration registers or an initialization file. 2. In the Data menu, select View Memory. 3. In the Display box, enter a valid RAM address. 4. Verify that memory data can be modified. If you cannot modify memory, it is likely that the memory control registers are not correctly configured, that memory access parameters need to be revised, or that target memory is faulty. Is data being corrupted? If you are using an evaluation board with CodeWarrior, refer to Tested Switch and Jumper Settings in the CodeWarrior: Targeting Embedded PowerPC. See also CodeWarrior Troubleshooting. If you have a custom target, confirm that the signal interface meets requirements. See Target Requirements for WireTAP 6xx/7xx/82xx on page 51 or Target Requirements for WireTAP 8xx on page 57. WireTAP 6xx/7xx/82xx: If you have slow memory regions or an exceptionally fast PC, see the discussion in Polling memory access status on page 27; then try the following. 1. Enable Verify Memory Write in the Debugger: EPPC Target Settings panel. 36 WireTAP Run-Control Tool Installation Guide