Freescale Semiconductor metrowerks CodeWarrior User manual

A
Freescale Semiconductor Company
CodeWarrior™
USB TAP Users Guide
Revised 10 March 2005

Metrowerks, and the Metrowerks logo are registered trademarks of Metrowerks Corporation in the United States and/
or other countries. CodeWarrior is a trademark or registered trademark of Metrowerks Corporation in the United States
and/or other countries. All other trade names and trademarks are the property of their respective owners.
Copyright © 2005 Metrowerks Corporation. ALL RIGHTS RESERVED.
No portion of this document may be reproduced or transmitted in any form or by any means, electronic or me-
chanical, without prior written permission from Metrowerks. Use of this document and related materials is gov-
erned 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 agree-
ment. If you do not have a copy of the license agreement, contact your Metrowerks representative or call 1-800-
377-5416 (if outside the U.S., call [phone]).
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 prod-
ucts 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 fail-
ure, 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 simi-
lar degree of potential hazard.
How to Contact Metrowerks
Corporate Headquarters Metrowerks Corporation
7700 West Parmer Lane
Austin, TX 78729
U.S.A.
World Wide Web http://www.metrowerks.com
Sales United States Voice: 800-377-5416
United States Fax: [phone]
International Voice: [phone]
Email: [email protected]
Technical Support United States Voice: 800-377-5416
International Voice: [phone]
Email: [email protected]

3 USB TAP Users Guide
Table of Contents
1 Introducing the CodeWarrior™ USB TAP Emulator 5
What is the USB TAP Emulator? . . . . . . . . . . . . . . . . . . . . . 5
Product Highlights . . . . . . . . . . . . . . . . . . . . . . . . . 6
The Debugging Environment . . . . . . . . . . . . . . . . . . . . . 7
USB TAP Emulator Benefits . . . . . . . . . . . . . . . . . . . . . 7
Target Connections . . . . . . . . . . . . . . . . . . . . . . . . . 7
Operating Requirements . . . . . . . . . . . . . . . . . . . . . . . . 8
Standard Electrostatic Precautions . . . . . . . . . . . . . . . . . . . 8
Electrical Requirements . . . . . . . . . . . . . . . . . . . . . . . 8
Operating Temperature. . . . . . . . . . . . . . . . . . . . . . . . 8
Target Requirements. . . . . . . . . . . . . . . . . . . . . . . . . 9
Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Setting up the USB TAP Emulator 11
Unpacking the USB TAP Emulator . . . . . . . . . . . . . . . . . . . 11
Identifying the Components . . . . . . . . . . . . . . . . . . . . . . 12
Installing the CodeWarrior USB TAP Device Drivers . . . . . . . . . . . . 12
Connecting to the Target and your Host Computer . . . . . . . . . . . . . 14
Debug Port Connector Information . . . . . . . . . . . . . . . . . . 14
Target Connection . . . . . . . . . . . . . . . . . . . . . . . . 15
Setting the Debug Port Clock Frequency. . . . . . . . . . . . . . . . 16
Connecting to your Host Computer . . . . . . . . . . . . . . . . . . 16
What To Do Next . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 Using the USB TAP 19
USB TAP System Startup . . . . . . . . . . . . . . . . . . . . . . . 19
Notes on Using the USB TAP . . . . . . . . . . . . . . . . . . . . 19
Run/Pause/Mixed Mode States . . . . . . . . . . . . . . . . . . . 20
Breakpoints in Exception/Interrupt Handlers . . . . . . . . . . . . . . 20

Table of Contents
4
USB TAP Users Guide
4 Hardware Specifications 21
Connectors and LEDs . . . . . . . . . . . . . . . . . . . . . . . . 21
Run/Pause Indicator . . . . . . . . . . . . . . . . . . . . . . . . 22
Transmit/Receive Indicator . . . . . . . . . . . . . . . . . . . . . 22
USB Connector . . . . . . . . . . . . . . . . . . . . . . . . . 23
Debug Port Connector . . . . . . . . . . . . . . . . . . . . . . . 23
USB TAP Specifications . . . . . . . . . . . . . . . . . . . . . . . 24
Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . 24
Physical Considerations . . . . . . . . . . . . . . . . . . . . . . 25
A JTAG/COP Connector Information 27
B DPI Connector Information 33
C BDM Connector Information 37
D OnCE Connector Information 43
E ARM JTAG Connector Information 47
F USB TAP Firmware (Loader) 53
The USB TAP Internal Software Overview . . . . . . . . . . . . . . . . 53
Loader Software . . . . . . . . . . . . . . . . . . . . . . . . . 53
Dispatcher Software . . . . . . . . . . . . . . . . . . . . . . . . 53
Reprogramming the USB TAP Firmware Image . . . . . . . . . . . . . . 54
What To Do Next . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Index 57

5 USB TAP Users Guide
1
Introducing the
CodeWarrior™ USB TAP
Emulator
The CodeWarrior USB TAP emulator is a cost-effective tool that helps you develop
and debug a number of processors and microcontrollers.
This chapter introduces you to the USB TAP emulator.
The sections are:
•What is the USB TAP Emulator?
•Operating Requirements
•Related Documentation
What is the USB TAP Emulator?
The USB TAP emulator uses advanced emulation technology to provide control of
and visibility into your target system. Combined with the CodeWarrior IDE, the USB
TAP emulator (Figure 1.1) speeds the debugging process by letting you interactively
control and examine the state of your target system.

Introducing the CodeWarrior™ USB TAP Emulator
What is the USB TAP Emulator?
6 USB TAP Users Guide
Figure 1.1 USB TAP for ARM®JTAG with USB 2.0 Cable
Product Highlights
The USB TAP emulator has these features:
• Supports the following systems: PowerPC™ processors, ARM®processors,
ColdFire™ processors, StarCore™ processors, 56800 Hybrid Controllers
(processors and microcontrollers), and RCF base-band controllers.
• Supports all CPU core speeds.
• Lets you control and debug software running in-target, with minimal intrusion
into target operation.
• Lets you debug code in cache, ROM, RAM, and flash memory.
• Provides high performance:
– Split-second single-step execution.
– Capable of download speeds greater than 12 MB per minute from host to
target.
NOTE The actual download speed depends on the target processor, the
debug port’s clock frequency, the network speed, and the debugger.
• Supports one USB 2.0 connection.
• Supports both big and little endian byte-order.
• Automatically supports target signal levels from 1.8V to 3.3V.

Introducing the CodeWarrior™ USB TAP Emulator
What is the USB TAP Emulator?
7 USB TAP Users Guide
• Software debug capabilities including:
– Controlling instruction execution.
– Display and modify target memory.
– Examine and modify any processor registers.
– Run to breakpoints in ROM, RAM, or flash memory.
– Single-step through source and assembly language code views.
– Single-step into, over, or out of functions.
The Debugging Environment
The USB TAP emulator works with the CodeWarrior™ debugger. The debugger has
been integrated with the USB TAP emulator to give you control over the emulation
functions and your target.
USB TAP Emulator Benefits
The USB TAP emulator provides these key benefits:
•Visibility: The USB TAP emulator makes it possible for you to observe 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.
•Control: You can conveniently control the state of the target system by
downloading code, manually modifying processor registers and memory, single-
stepping through the code, or setting breakpoints.
Target Connections
The USB TAP connects to your target through the standard debug port for the
processor family. Each USB TAP supports a single target connection. The USB TAPs
are available in the following versions:
• JTAG/COP, for PowerPC™ targets
• DPI, for PowerPC™ 5xx and 8xx targets
• BDM, for ColdFire™ targets
• OnCE, for StarCore™, 56800 Hybrid Controllers, RCF base-band, and
PowerPC™ 5500 targets
•ARM®JTAG, for i.MX and MAC7100 targets
For more details see “Connecting to the Target and your Host Computer” on page 13.

Introducing the CodeWarrior™ USB TAP Emulator
Operating Requirements
8 USB TAP Users Guide
Operating Requirements
Before setting up your system, you should make sure that the operating environment is
prepared.
Standard Electrostatic Precautions
This instrument contains static-sensitive components that are subject to damage from
electrostatic discharge. Use standard ESD precautions when transporting, handling, or
using the instrument and the target, when connecting/disconnecting the instrument and
the target, and when removing the cover of the instrument.
We recommend that you use the following precautions:
• Use wrist straps or heel bands with a 1 MΩresistor connected to ground.
• On the work surface and floor, use static conductive mats with a 1 MΩresistor
connected to ground.
• Keep high static-producing items, such as non-ESD-approved plastics, tape and
packaging foam, away from the instrument and the target.
The above precautions should be considered as minimum requirements for a static-
controlled environment.
Electrical Requirements
The USB TAP emulator is powered through the USB cable and does not use an
external power supply. The USB TAP emulator is designed to be plugged directly into
a host computer, but also can work with self-powered hubs. Bus powered hubs may be
unable to provide sufficient power for the USB TAP, which requires 200 mA. If
insufficient power is available, your host operating system will indicate this failure
and the USB TAP emulator will go into a low power suspend mode. If your hub is not
able to provide sufficient power, connect the USB TAP directly to your host PC, or
purchase a self-powered USB hub.
Operating Temperature
The USB TAP emulator can operate in a temperature range of 0 to 40 °C (32 to 104
°F).

Introducing the CodeWarrior™ USB TAP Emulator
Related Documentation
9 USB TAP Users Guide
Target Requirements
The USB TAP emulator automatically supports target signal levels from 1.8V to 3.3V.
NOTE In the case of the PowerPC, for the USB TAP emulator to properly
stop and restart a JTAG/COP target processor, the QACK signal
must be pulled low. The USB TAP emulator pulls this signal low
through the JTAG/COP connector.
Related Documentation
This manual describes the procedures for unpacking the USB TAP emulator, setting
up USB communications, and connecting the USB TAP emulator to your target
system.
The CodeWarrior documentation explains how to install and configure the
CodeWarrior IDE and debugger.

Introducing the CodeWarrior™ USB TAP Emulator
Related Documentation
10 USB TAP Users Guide

11 USB TAP Users Guide
2
Setting up the USB TAP
Emulator
This chapter explains how to set up the USB TAP emulator.
The sections are:
•Unpacking the USB TAP Emulator
•Identifying the Components
•Installing the CodeWarrior USB TAP Device Drivers
•Connecting to the Target and your Host Computer
•What To Do Next
CAUTION The USB TAP emulator is subject to damage from electrostatic
discharge. When you use, handle, or transport the USB TAP
emulator, or connect or disconnect the USB TAP emulator from a
target system, always use proper anti-static protection measures,
including using static-free bench pads and grounded wrist straps.
Unpacking the USB TAP Emulator
Your USB TAP emulator has been inspected and tested for electrical and mechanical
defects before shipping. Although the hardware was carefully packed, examine all
components for external damage.
When you unpack the USB TAP emulator, be sure to save the protective packaging in
case you have to ship or transport the USB TAP emulator.
If you find any damage, file a claim with the carrier and notify Metrowerks.

Setting up the USB TAP Emulator
Identifying the Components
12 USB TAP Users Guide
Identifying the Components
Before you begin, check that these components are present:
• USB TAP emulator.
• One USB 2.0 cable for connecting the USB TAP to your host computer.
Installing the CodeWarrior USB TAP
Device Drivers
NOTE If you are using the USB TAP emulator with a PC running
Windows®NT/2000/XP, the USB TAP device driver must initially
be installed before you can make a connection to the USB port.
The CodeWarrior Development software should automatically install the USB TAP
device driver.
However, if you wish to install the USB TAP device driver manually, a copy of the
driver and instructions can be downloaded at:
http://www.metrowerks.com/MW/Develop/Embedded/USBTAP/
default.htm
After either automatic or manual installation of the USB TAP driver, plug the USB
TAP emulator into your computer, as described in “Connecting to your Host
Computer” on page 16. The first time this is performed, the following Windows pop-
up dialog appears in the system tray: Found New Hardware: CodeWarrior USB
TAP. Then shortly after this message is displayed, the Found New Hardware
Wizard dialog box in Figure 2.1 appears.

Setting up the USB TAP Emulator
Installing the CodeWarrior USB TAP Device Drivers
13 USB TAP Users Guide
Figure 2.1 Found New Hardware Wizard
NOTE If you receive the message “unknown device,” this means that either
the USB TAP device driver was not installed properly or that there is
a problem with either the USB port or the USB TAP device. Please
reinstall the USB TAP device driver manually as described above.
With the New Hardware Wizard, you will need to select the usbtap.inf file,
which is located on either the CodeWarrior CD-ROM under the \drivers directory
or at the Metrowerks website mentioned above. To do this:
1. Chose Install from a list or specific location (Advanced)
2. Click the Next button to continue
3. With the Browse button, navigate to the location of the usbtap.inf file.

Setting up the USB TAP Emulator
Connecting to the Target and your Host Computer
14 USB TAP Users Guide
Connecting to the Target and your Host
Computer
To test your software using the USB TAP emulator, you must have working target
hardware.
This section explains how to connect the USB TAP emulator to such hardware and to
your host computer.
The topics in this sections are:
•Debug Port Connector Information
•Setting the Debug Port Clock Frequency
•Connecting to your Host Computer
CAUTION The USB TAP emulator contains components that are subject to
damage from electrostatic discharge. Whenever you are using,
handling, or transporting the USB TAP emulator, 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.
Debug Port Connector Information
The USB TAP emulator is a powerful development tool for use with a wide variety of
processors that use either JTAG/COP, DPI, BDM, OnCE or ARM®JTAG debug
interfaces
The appendices describe the debug port connector informations for:
•“JTAG/COP Connector Information” on page 27.
•“DPI Connector Information” on page 33.
•“BDM Connector Information” on page 37.
•“OnCE Connector Information” on page 43.
•“ARM JTAG Connector Information” on page 47.

Setting up the USB TAP Emulator
Connecting to the Target and your Host Computer
15 USB TAP Users Guide
Target Connection
CAUTION Failure to properly connect the USB TAP emulator to the target may
damage the USB TAP emulator or target. Verify all connections
before applying power.
If your target system has a debug port header, you can directly connect the USB TAP
emulator to the target debug port header. Make sure that pin 1 of the USB TAP’s gray
ribbon cable connector lines up with pin 1 on the target’s debug port header.
NOTE Pin 1 is clearly marked on the USB TAP’s gray ribbon cable by a red
line down one side of the cable and a small triangle in the plastic
socket.
To connect the USB TAP connector to the target debug port header:
1. Remove power from your target.
2. Unplug the USB cable from the USB TAP emulator.
3. Make sure that pin 1 of the USB TAP’s gray ribbon cable connector lines up with
pin 1 on the target’s debug port header.
As an example, Figure 2.2 shows the USB TAP for ARM® JTAG connector.
Figure 2.2 USB TAP for ARM® JTAG
4. Gently (but firmly) press the USB TAP connector onto the target debug port
header.
ARM®JTAG Connector
Top
Pin 1

Setting up the USB TAP Emulator
Connecting to the Target and your Host Computer
16 USB TAP Users Guide
5. Reconnect the USB cable to the USB TAP emulator.
6. Apply power to your target.
NOTE If you are using the USB TAP emulator with a PC running
Windows®NT/2000/XP, the first time that you connect the USB
TAP to the USB port, the following Windows pop-up dialog appears
in the system tray: Found New Hardware: CodeWarrior USB
TAP. Then shortly after this message is displayed, a Found New
Hardware Wizard dialog box appears. See “Installing the
CodeWarrior USB TAP Device Drivers” on page 12, for details on
how to navigate through this dialog box.
Setting the Debug Port Clock Frequency
The debug port on your target is a synchronous interface clocked by the TCK or
DSCK signal. The base frequency is set by the debugger and can be adjusted with
preferences in the debugger.
NOTE For directions on how to set the debug port clock frequency, please
see the CodeWarrior documentation.
Some slow targets might not be able to operate at the initial default rate. Therefore,
you may have to adjust the debug port clock rate.
NOTE Because of variations in the design of target systems, it is not
possible to guarantee that all systems can be operated at the
maximum debug port clock rates. These variations include circuit
impedances, trace lengths, and signal terminations. You may need to
select a lower clock rate to get reliable operation.
Connecting to your Host Computer
Connect one end of your USB 2.0 Cable to a USB 2.0 port on your host computer or a
powered USB 2.0 hub. Connect the other end of the cable to your CodeWarrior USB
TAP emulator.

Setting up the USB TAP Emulator
What To Do Next
17 USB TAP Users Guide
NOTE If you plug the USB 2.0 Cable into an USB 1.1 port, you will get a
warning in a Windows pop-up dialog box and the performance of the
USB TAP will be slower. Please disregard this warning if you only
have an USB 1.1 port.
What To Do Next
You can now install your software. See the IDE Users Guide or your targeting manual
about how to configure the debugger and run a confidence test.
For additional information about using the USB TAP with your target system, refer to
“Using the USB TAP” on page 19.

Setting up the USB TAP Emulator
What To Do Next
18 USB TAP Users Guide

19 USB TAP Users Guide
3
Using the USB TAP
This chapter provides system startup procedures, explains how the USB TAP works
and provides important information about using the system.
The sections are:
•USB TAP System Startup
•Notes on Using the USB TAP
USB TAP System Startup
This section explains how to start using the USB TAP and the debugger.
Before starting up the USB TAP, make sure you have:
• Connected the USB TAP to your Host Computer with your USB 2.0 Cable
• Connected the USB TAP to the target system (see “Connecting to the Target and
your Host Computer” on page 13)
• Installed the USB TAP drivers
• Installed the debugger software and properly configured it to communicate with
the USB TAP.
To start up the USB TAP:
1. Apply power to your target system.
2. Start the debugger.
You are now ready to begin your debug session. For information on using the
debugger, refer to the IDE User Guide and the targeting manual.
Notes on Using the USB TAP
This section provides information specific to the USB TAP. This section is useful for
users who are not familiar with USB TAP operation. Also refer to the debugger
documentation for becoming familiar with the system operation.

Using the USB TAP
USB TAP System Startup
20 USB TAP Users Guide
These topics provide information specific to USB TAP operation:
•Run/Pause/Mixed Mode States
•Breakpoints in Exception/Interrupt Handlers
Run/Pause/Mixed Mode States
When the host debugger is connected to the target via the USB TAP, the USB TAP is
always in one of these states (modes): run, pause or mixed mode.
• Run mode — in this mode, all target system processor cores execute the target
code
• Pause mode — in this mode, all target system processor cores have stopped
executing the target code
• Mixed mode — in this mode, some target system processor cores are in run mode
and others are in pause mode
The Run/Pause light on the USB TAP will be green in run mode, red in pause mode,
and orange in mixed mode.
Breakpoints in Exception/Interrupt
Handlers
Care must be taken when setting breakpoints in exception handler code. A typical
exception consists of a preamble that saves processor context, the actual exception
handler, and then a postamble 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.
For PPC processors, 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 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,” and “RFI.”