Freescale Semiconductor NXP CodeWarrior USB TAP User manual

CodeWarrior™
USB TAP Users Guide
Revised: 11 November 2005
USB_TAP.book Page 1 T hursd a y , November10,2005 2:27 PM

Freescale™ and the Freescale logo are trademarks of Freescale Semiconductor, Inc. CodeWarrior is a trademark or reg-
istered trademark of Freescale Semiconductor, Inc. in the United States and/or other countries. All other product or ser-
vice names are the property of their respective owners.
Copyright © 2005 by Freescale Semiconductor, Inc. All rights reserved.
Information in this document is provided solely to enable system and software implementers to use Freescale Semicon-
ductor products. There are no express or implied copyright licenses granted hereunder to design or fabricate any inte-
grated circuits or integrated circuits based on the information in this document.
Freescale Semiconductor reserves the right to make changes without further notice to any products herein. Freescale
Semiconductor makes no warranty, representation or guarantee regarding the suitability of its products for any partic-
ular purpose, nor does Freescale Semiconductor assume any liability arising out of the application or use of any product
or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental dam-
ages. “Typical” parameters that may be provided in Freescale Semiconductor data sheets and/or specifications can and
do vary in different applications and actual performance may vary over time. All operating parameters, including “Typ-
icals”, must be validated for each customer application by customer's technical experts. Freescale Semiconductor does
not convey any license under its patent rights nor the rights of others. Freescale Semiconductor products are not de-
signed, intended, or authorized for use as components in systems intended for surgical implant into the body, or other
applications intended to support or sustain life, or for any other application in which the failure of the Freescale Semi-
conductor product could create a situation where personal injury or death may occur. Should Buyer purchase or use
Freescale Semiconductor products for any such unintended or unauthorized application, Buyer shall indemnify and hold
Freescale Semiconductor and its officers, employees, subsidiaries, affiliates, and distributors harmless against all
claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of
personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Freescale
Semiconductor was negligent regarding the design or manufacture of the part.
How to Contact Us
Corporate Headquarters Freescale Semiconductor, Inc.
7700 West Parmer Lane
Austin, TX 78729
U.S.A.
World Wide Web http://www.freescale.com/codewarrior
Technical Support http://www.freescale.com/support
USB_TAP.book Page 2 T hursd a y , November10,2005 2:27 PM

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 Connecting to the Target and your Host Computer 11
Debug Port Connector Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Target Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Setting the Debug Port Clock Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Connecting to your Host Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What To Do Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3 Using the USB TAP 15
USB TAP System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Notes on Using the USB TAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Run/Pause/Mixed Mode States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Breakpoints in Exception/Interrupt Handlers . . . . . . . . . . . . . . . . . . . . . . . . 16
4 Hardware Specifications 17
Connectors and LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Run/Pause Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Transmit/Receive Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
USB Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Debug Port Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
USB_TAP.book Page 3 T hursd a y , November10,2005 2:27 PM

Table of Contents
4 USB TAP Users Guide
USB TAP Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Physical Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
A JTAG/COP Connector Information 21
B DPI Connector Information 27
C BDM Connector Information 31
D OnCE Connector Information 37
E ARM® JTAG Connector Information 41
F USB TAP Firmware (Loader) 47
The USB TAP Internal Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Loader Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Dispatcher Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Reprogramming the USB TAP Firmware Image . . . . . . . . . . . . . . . . . . . . . . . .48
What To Do Next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
G Troubleshooting 51
Index 53
USB_TAP.book Page 4 T hursd a y , November10,2005 2:27 PM

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.
USB_TAP.book Page 5 T hursd a y , November10,2005 2:27 PM

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 Windows®NT/2000/XP and the following Linux operating systems: Red
Hat® Linux®version 8.0 or 9.0, Fedora™ Core 3 or Core 4, and
Mandrake®Linux®10.0.
• 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.
USB_TAP.book Page 6 T hursd a y , November10,2005 2:27 PM

Introducing the CodeWarrior™ USB TAP Emulator
What is the USB TAP Emulator?
7 USB TAP Users Guide
• Automatically supports target signal levels from 1.8V to 3.3V.
• 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™ 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.
USB_TAP.book Page 7 T hursd a y , November10,2005 2:27 PM

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).
USB_TAP.book Page 8 T hursd a y , November10,2005 2:27 PM

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.
USB_TAP.book Page 9 T hursd a y , November10,2005 2:27 PM

Introducing the CodeWarrior™ USB TAP Emulator
Related Documentation
10 USB TAP Users Guide
USB_TAP.book Page 10 T hursd a y , N ovem ber 10,2005 2:27 PM

11 USB TAP Users Guide
2
Connecting to the Target
and your Host Computer
To test your software using the USB TAP emulator, you must have working target
hardware.
This chapter explains how to connect the USB TAP emulator to such hardware and to your
host computer.
The sections are:
•Debug Port Connector Information
•Setting the Debug Port Clock Frequency
•Connecting to your Host Computer
•What To Do Next
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 21.
•“DPI Connector Information” on page 27.
•“BDM Connector Information” on page 31.
•“OnCE Connector Information” on page 37.
•“ARM® JTAG Connector Information” on page 41.
USB_TAP.book Page 11 T hursd a y , N ovem ber 10,2005 2:27 PM

Connecting to the Target and your Host Computer
Target Connection
12 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.1 shows the USB TAP for ARM® JTAG connector.
Figure 2.1 USB TAP for ARM® JTAG
4. Gently (but firmly) press the USB TAP connector onto the target debug port header.
5. Reconnect the USB cable to the USB TAP emulator.
6. Apply power to your target.
ARM ® JT A G C on n ector
Top
Pin 1
USB_TAP.book Page 12 T hursd a y , N ovem ber 10,2005 2:27 PM

Connecting to the Target and your Host Computer
Setting the Debug Port Clock Frequency
13 USB TAP Users Guide
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 port on your host computer. Connect
the other end of the cable to your CodeWarrior USB TAP emulator.
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 15.
USB_TAP.book Page 13 T hursd a y , N ovem ber 10,2005 2:27 PM

Connecting to the Target and your Host Computer
What To Do Next
14 USB TAP Users Guide
USB_TAP.book Page 14 T hursd a y , N ovem ber 10,2005 2:27 PM

15 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 11)
• 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.
These topics provide information specific to USB TAP operation:
•Run/Pause/Mixed Mode States
•Breakpoints in Exception/Interrupt Handlers
USB_TAP.book Page 15 T hursd a y , N ovem ber 10,2005 2:27 PM

Using the USB TAP
USB TAP System Startup
16 USB TAP Users Guide
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.”
USB_TAP.book Page 16 T hursd a y , N ovem ber 10,2005 2:27 PM

17 USB TAP Users Guide
4
Hardware Specifications
This chapter provides hardware specifications for the USB TAP emulator.
The sections are:
•Connectors and LEDs
•USB TAP Specifications
Connectors and LEDs
Figure 4.1 and Figure 4.2 show the various LEDs and connectors of the USB TAP device.
Figure 4.1 USB TAP Device—Top View
Figure 4.2 USB TAP Device Connector—End View
Debug port connector
Transmit/Receive LED
Run/Pause LED
USB Connector
USB_TAP.book Page 17 T hursd a y , N ovem ber 10,2005 2:27 PM

Hardware Specifications
Connectors and LEDs
18 USB TAP Users Guide
These topics explain the various LEDs and connectors on the USB TAP device:
•Run/Pause Indicator
•Transmit/Receive Indicator
•USB Connector
•Debug Port Connector
Run/Pause Indicator
The USB TAP hardware has a status LED labeled Run/Pause. It indicates the state of
execution on the target device as follows:
• The LED is green when the target is running.
• The LED is red when the target is paused.
• The LED is orange when the target is in mixed mode.
• The LED is initially unlit and remains so until the debugger is connected to the USB
TAP.
Transmit/Receive Indicator
The transmit/receive (labeled TX/RX) LED indicates the state of the USB interface as
follows:
• The LED flashes red when the USB TAP is powered but has not been configured.
• The LED flashes green when the USB TAP is properly configured.
• The LED flashes orange when data is being transferred.
• The LED is off if the USB TAP is disabled or disconnected.
NOTE When the USB TAP is powered on, it performs a brief self-test that displays a
test pattern on both LEDs. After the self-test completes, it reverts to the
behavior described above.
USB Connector
The USB interface consists of an USB type B connector that connects directly to the
provided USB cable.
USB_TAP.book Page 18 T hursd a y , N ovem ber 10,2005 2:27 PM

Hardware Specifications
USB TAP Specifications
19 USB TAP Users Guide
Debug Port Connector
The debug connector consists of a 5.5 inch ribbon cable with the appropriate debug
connector attached. The ribbon cable has a red stripe down one side to indicate the
location of pin 1.
NOTE The OnCE connector is equipped with a removable plug in pin 8. This follows
the keying convention for the OnCE header (pin 8 should be removed). This
plug is removable, in case the target being connected to it does not come with
pin 8 removed.
USB TAP Specifications
Figure 4.3 shows the dimensions of the USB TAP device.
Figure 4.3 USB TAP Dimensions
Electrical Characteristics
The USB TAP was designed to affect the target processor and target electrical
characteristics as little as possible. Care, however, should be taken in designing the target
to accommodate the small signal delays associated with any in-circuit emulator or other
test equipment.
The USB TAP automatically supports target signal levels from 1.8V to 3.3V.
5.875'' (14.92 cm) 5.500'' (13.97 cm)
5.875'' (14.92 cm)
3.000'' (7.620 cm)
1.250''
(3.175 cm)
USB_TAP.book Page 19 T hursd a y , N ovem ber 10,2005 2:27 PM

Hardware Specifications
USB TAP Specifications
20 USB TAP Users Guide
Physical Considerations
The USB TAP was carefully designed to be as small as possible. Even so, it may not
physically fit in all target systems.
Contact Freescale if you have any special considerations that need review.
Table 4.1 shows the physical characteristics of the USB TAP.
Table 4.1 USB TAP—Physical Characteristics
Current consumption
• USB TAP current consumption
from USB cable
< 200 mA
• USB TAP current consumption
from target
< 50 µA
Physical dimensions
• USB TAP dimensions 5.875" x 3.000" x 1.250"
(14.92 cm x 7.620 cm x 3.175 cm)
• Target connector ribbon length 5.50” (13.97 cm)
• Target connector dimensions
Height
Depth
JTAG/COP width
DPI width
ARM®JTAG width
OnCE width
BDM width
0.38" (0.97 cm)
0.20" (0.51 cm
0.98" (2.49 cm)
0.68" (1.72 cm)
1.18" (3.00 cm)
0.88" (2.24 cm)
1.48” (3.76 cm)
USB_TAP.book Page 20 T hursd a y , N ovem ber 10,2005 2:27 PM