Freescale Semiconductor CodeWarrior TAP User Manual
CodeWarrior TAP Probe
User Guide
Revised: 3 October 2012
Freescale, Freescale logo, and CodeWarrior are trademarks of Freescale Semiconductor, Inc. All other product or service names are the property of their respective owners.
© 2012 Freescale Semiconductor, Inc. All rights reserved.
Information in this document is provided solely to enable system and software implementers to use Freescale Semiconductor products. There are no express or implied copyright licenses granted hereunder to design or fabricate any integrated 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 particular 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 damages. “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 “Typicals”, 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 designed, 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 Semiconductor 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 Freescale
Corporate Headquarters Freescale Semiconductor, Inc.
6501 William Cannon Drive West
Austin, Texas 78735
U.S.A.
World Wide Web http://www.freescale.com/codewarrior
Technical Support http://www.freescale.com/support
Table of Contents
1 Introducing the CodeWarrior TAP Probe 5
1.1 What is CodeWarrior TAP Probe? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1.1 Product Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1.2 The Debugging Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.3 CodeWarrior TAP Probe Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.4 Target Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Operating Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.1 Standard Electrostatic Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.2 Operating Temperature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.3 Electrical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2 Connecting to a Network 11
2.1 Connecting the CodeWarrior TAP Probe to the Network . . . . . . . . . . . . . . . 11
2.2 Customizing the CodeWarrior TAP Probe . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Testing Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3 Connecting to the Target System 17
3.1 Debug Port Connector Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Connecting to the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.1 Connecting Probe Tip to the Target . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3 Connecting to the Target System Serial Port . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3.1 Connecting the CodeWarrior TAP Probe to the Target System . . . . . . 20
3.3.2 Configuring the Target Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.3.3 Accessing the Target Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4 Using the CodeWarrior TAP Probe 23
4.1 Debugging with the CodeWarrior TAP System . . . . . . . . . . . . . . . . . . . . . . 23
4.1.1 Run/Pause/Mixed Mode States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.1.2 Connecting to Multiple TAP Probes . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2 Accessing a Ethernet TAP Probe Remotely . . . . . . . . . . . . . . . . . . . . . . . . . 25
iCodeWarrior TAP Probe User Guide
Table of Contents
5 Hardware Specifications 27
5.1 LEDs on CodeWarrior TAP Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
5.1.1 Transmit/Receive Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
5.1.2 Run/Pause Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
5.1.3 RJ45 Ethernet Connector with Link and Activity Indicators . . . . . . . .29
5.2 Host Connectors on CodeWarrior TAP Probe. . . . . . . . . . . . . . . . . . . . . . . .29
5.2.1 RJ45 Ethernet Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
5.2.2 USB Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
5.3 Target Connectors on CodeWarrior TAP Probe . . . . . . . . . . . . . . . . . . . . . .30
5.3.1 RJ25 Target Serial Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
5.3.2 Probe Tip Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
5.3.3 Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
5.3.4 Physical Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
A Ethernet TAP Probe Setup Utility Commands 35
A.1 Connecting to the CodeWarrior TAP Probe Setup Utility . . . . . . . . . . . . . .35
A.2 Ethernet TAP Probe Setup Utility Commands and Variables . . . . . . . . . . .36
A.2.1 Commands to Configure Communications . . . . . . . . . . . . . . . . . . . . .36
A.2.2 Commands to Troubleshoot Communication . . . . . . . . . . . . . . . . . . .40
B Network Administration 43
B.1 CodeWarrior TAP Probe Network Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . .43
B.2 Configuring the Ethernet TAP Probe Using netparam . . . . . . . . . . . . . . . . .44
B.2.1 Configuring a Dynamic IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . 44
B.2.2 Configuring a Static IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
B.2.3 Static Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
B.2.4 Changing an Existing Route Entry . . . . . . . . . . . . . . . . . . . . . . . . . . .46
B.2.5 Entering Static Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
B.3 Using CCS to Search for CodeWarrior TAP Probes. . . . . . . . . . . . . . . . . . .48
C Ethernet TAP Probe Firmware (Core) 51
C.1 CodeWarrior TAP Probe Internal Software Overview . . . . . . . . . . . . . . . . .51
C.1.1 Boot Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
C.1.2 Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
ii CodeWarrior TAP Probe User Guide
Table of Contents
C.1.3 Shell Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
C.2 Reprogramming the Ethernet TAP Probe Firmware Images . . . . . . . . . . . . 52
C.2.1 Reprogramming the Firmware through the Ethernet Port . . . . . . . . . . 52
D JTAG/COP Connector Information 55
E OnCE Connector Information 61
F ColdFire BDM Connector Information 65
G Troubleshooting 71
G.1 Troubleshooting Communications Problems. . . . . . . . . . . . . . . . . . . . . . . . 71
G.1.1 Verify Network Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
G.1.2 View Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
G.2 Troubleshooting Power Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Index 75
iiiCodeWarrior TAP Probe User Guide
Table of Contents
iv CodeWarrior TAP Probe User Guide
1
Introducing the CodeWarrior TAP Probe
The CodeWarrior TAP probe allows your personal computer workstation to communicate with Freescale
Power Architecture, StarCore, and ColdFire processors using a privileged debug connection, such as
COP, OnCE, or BDM.
This chapter explains:
• What is CodeWarrior TAP Probe?
• Operating Requirements
• Related Documentation
CAUTION The CodeWarrior TAP probe contains components that are subject to damage from
electrostatic discharge. Whenever you are using, handling, or transporting the
CodeWarrior TAP probe, or connecting to or disconnecting from a target system, always
use proper anti-static protection measures, including static-free bench pads and grounded
wrist straps.
1.1 What is CodeWarrior TAP Probe?
The CodeWarrior TAP probe uses advanced emulation technology to provide control and visibility into
your target embedded system. Combined with a host debugger, the CodeWarrior TAP probe speeds the
debugging process by letting you interactively control and examine the state of your target system.
The basic CodeWarrior TAP probe system is composed of two parts:
• The CodeWarrior TAP probe (Figure 1.1
system using a JTAG or BDM interface, and connects to your host computer through a USB 2.0,
10BaseT, or 100BaseT link.
• JTAG/COP, StarCore, or ColdFire/BDM probe tip, which is designed to provide a physical and
electrical interface to the target system processor that you want to gain visibility into.
), which provides visibility into and control of your target
5CodeWarrior TAP Probe User Guide
Introducing the CodeWarrior TAP Probe
What is CodeWarrior TAP Probe?
Figure 1.1 CodeWarrior TAP Probe
1.1.1 Product Highlights
The CodeWarrior TAP probe has these features:
• Supports the Power Architecture, StarCore, and ColdFire™ processors. Go to the http://
freescale.com/CWTAP for the latest supported Freescale processors
• Supports all CPU core speeds
• Allows you to control and debug software running in-target, with minimal intrusion into the target
system operation
• Allows you to debug code in cache, ROM, RAM, and flash memory
• Supports 10/100 Ethernet network connection
• Supports telnet access to your target systems serial port, allowing you to interact with your target
system’s serial port over the network
• Supports USB 2.0 high-speed connection
• USB powered
• Supports both big and little endian byte-order
6
CodeWarrior TAP Probe User Guide
Introducing the CodeWarrior TAP Probe
What is CodeWarrior TAP Probe?
• Software debug capabilities, usually part of host software like CodeWarrior, include:
– Control instruction execution
– Display and modify target system 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
– Step into, over, or out of functions
– Collect and analyze real-time data
– Perform boundary scan testing with support from correct host-level software
– Program all onboard memories with support from correct host-level software
1.1.2 The Debugging Environment
The CodeWarrior TAP probe works with the CodeWarrior debugger to give you control over the
emulation functions and your target system.
1.1.3 CodeWarrior TAP Probe Benefits
The CodeWarrior TAP probe provides these key benefits:
• Visibility: Allows you to observe registers and the current state of target system memory. You can
halt program execution at predefined states and examine the data for a particular program state.
• Control: Enables you to control the state of the target system by downloading code, manually
modifying processor registers and memory, single-stepping through the code, or setting breakpoints.
1.1.4 Target Connections
The TAP probe connects to your target through the standard debug port for the processor family, and
supports a single target connection, based on the connected probe tip. For details on processor list, go to
http://freescale.com/CWTAP.
The TAP probes are available in the following Freescale versions:
• JTAG/COP for Power Architecture™, QorIQ, PQII, PQIII, AMP, Qonverge, but not PQI
• BDM for ColdFire® targets (not ColdFire v1)
• OnCE for StarCore
For information on connecting to a target, refer to the Connecting to the Target System
chapter.
7CodeWarrior TAP Probe User Guide
Introducing the CodeWarrior TAP Probe
Ω
Ω
Operating Requirements
1.2 Operating Requirements
Before setting up the system, ensure that the operating environment is prepared.
1.2.1 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.
It is recommended 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.
1.2.2 Operating Temperature
For operating temperature of TAP probe, refer to the Physical Considerations topic.
1.2.3 Electrical Requirements
The TAP probe can be powered through a USB cable and does not require an external power supply. It is
designed to be plugged directly into a host computer, but can also work with self-powered hubs. For
details on Bus-powered hubs, refer to the Electrical Characteristics
provide sufficient power, connect the TAP probe directly to your host PC, or purchase a self-powered
USB hub.
If you only plan to use Ethernet communications, the CodeWarrior TAP probe can be powered from the
external power supply provided with your unit. It can use line voltages of 100-240 VAC (50/60 Hz).
NOTE It is recommended to use a surge protector between the power supply and AC power.
8
topic. If your hub is not able to
CodeWarrior TAP Probe User Guide
Introducing the CodeWarrior TAP Probe
Operating Requirements
1.2.3.1 Connecting the Power Supply Cable
Connect the power supply USB cable connector to the USB connector on the CodeWarrior TAP probe as
shown below.
CAUTION Connect only the provided power supply to the CodeWarrior TAP probe. Other power
supplies may look similar, but can damage the probe if the supply specifications differ
from the required specifications.
Figure 1.2 CodeWarrior TAP Probe with USB Connector
1.2.3.2 Cycling Power to the System
When you need to apply or cycle power to the CodeWarrior TAP probe, connect or disconnect the power
cable from the power source or from the probe. After you have connected the probe to your target system,
use the following sequence for applying or removing the power.
To turn the power on
1. Turn on the CodeWarrior TAP probe power.
2. Turn on the target system power.
9CodeWarrior TAP Probe User Guide
Introducing the CodeWarrior TAP Probe
Related Documentation
To turn the power off
1. Turn off the target system power.
2. Turn off the CodeWarrior TAP probe power.
NOTE In the case of PowerPC targets with a QACK signal, for the CodeWarrior TAP probe to
properly stop and restart the target, the QACK signal must be pulled low. The CodeWarrior
TAP probe pulls this signal low through the probe tip.
1.3 Related Documentation
The CodeWarrior documentation explains how to install and configure the CodeWarrior IDE and
debugger and use the CodeWarrior TAP.
10
CodeWarrior TAP Probe User Guide
2
Connecting to a Network
This chapter explains how to connect the CodeWarrior TAP probe to an existing TCP/IP network.
The CodeWarrior TAP probe is an Ethernet device that may be configured for TCP/IP either using DHCP
to acquire its IP configuration (the default method) or through a static IP configuration.
This chapter explains:
• Connecting the CodeWarrior TAP Probe to the Network
• Customizing the CodeWarrior TAP Probe
• Testing Network Communication
2.1 Connecting the CodeWarrior TAP Probe to the Network
The CodeWarrior TAP probe’s default operation is to acquire its network configuration automatically
using DHCP, and attempt to register its hostname with a name server. The factory assigned host name is
FSLXXYYZZ where XXYYZZ is the last three octets of the Ethernet MAC address, provided on a label on
the bottom side of the probe. For example, if the probe’s Ethernet MAC address is 00:04:9f:00:77:31, the
host name will be FSL007731. Figure 4.1
The CodeWarrior TAP probe can connect directly to a network using Ethernet (10/100BaseT) cables.
shows TAP serial number.
11CodeWarrior TAP Probe User Guide
Connecting to a Network
Connecting the CodeWarrior TAP Probe to the Network
To connect to the Ethernet interface
1. Plug one end of the supplied RJ45 cable (p/n 600-75499) into the RJ45 connector of the CodeWarrior
TAP probe.
Figure 2.1 CodeWarrior TAP Probe with Ethernet Connector
2. Connect the other end of the RJ45 cable into the RJ45 connector of the Ethernet network or host
computer.
Figure 2.2 CodeWarrior TAP Probe with an RJ45 Cable Attached
12
CodeWarrior TAP Probe User Guide
Connecting to a Network
Customizing the CodeWarrior TAP Probe
NOTE When you configure the debugger for the hardware connection, you will need to specify the
CodeWarrior TAP probe IP address or hostname. The CCS findcc utility is used to search
any probe on the local subnet. For more information, refer to the Using CCS to Search for
CodeWarrior TAP Probes topic.
NOTE Depending on the type and complexity of your network, your network administrator may need
to update network server tables so that the network accesses the CodeWarrior TAP probe
correctly. Updating network server tables requires both a detailed knowledge of Ethernet
address resolution and network routing with write access permission to the server tables. For
more information on network administration, refer to the Network Administration topic.
2.2 Customizing the CodeWarrior TAP Probe
As shipped, the CodeWarrior TAP probe acquires its network configuration automatically using DHCP.
If you cannot use DHCP, you must configure the probe for your network using static IP address
resolution.
To manually configure the network settings of the CodeWarrior TAP probe for your network, access the
probe configuration console as described below and use the probe on-board setup utility netparam to
change the probe network settings. The probe netparam utility lets you select and modify network
parameters that are saved in probe memory. Use netparam to configure the probe to match the network
address resolution and routing protocols.
If the probe needs to communicate with hosts on other subnets, you will need to configure the probe for
one of the following routing options:
• Default gateways
• Static routing tables
13CodeWarrior TAP Probe User Guide
Connecting to a Network
Customizing the CodeWarrior TAP Probe
To Access the CodeWarrior TAP Configuration Console
1. Connect the other end of the USB cable to the USB connector of the CodeWarrior TAP probe (Figure
2.3).
Figure 2.3 CodeWarrior TAP Probe with USB Cable Attached
2. Wait for the TX/RX LED to start flashing green.
3. Identify the serial port device assigned to the CodeWarrior TAP. On Windows, click Start > Control
Panel >Adminstrative Tools > Computer Management > Device Manager > Ports and then select
USB serial port from the ports list. On Linux, the device file is located at: /dev/ttyACM0.
4. When prompted, press Enter. The login banner should be displayed and the core> command-line
prompt appears.
To customize the CodeWarrior TAP probe network settings
1. Change the CodeWarrior TAP probe network settings.
a. At the core> prompt, enter the netparam command to view the current settings.
b. For network setup, see the netparam
installing the CodeWarrior TAP probe on a network, see the Network Administration section.
c. At the core> prompt, enter the netparam commands and required parameters.
14
section for syntax and options. For more information on
CodeWarrior TAP Probe User Guide
Connecting to a Network
Testing Network Communication
2. At the core> prompt, enter reset to reboot the CodeWarrior TAP probe to activate the new
network settings.
NOTE If you connect to the CodeWarrior TAP using telnet rather than the USB configuration
console, you may lose access when you change network settings, and will need to reconnect
after the settings have changed.
Example: Assign a static IP address and hostname to the CodeWarrior TAP probe
If the CodeWarrior TAP probe has a static IP address of 195.121.1.2 and a hostname of lab01, enter the
following commands:
core> netparam static_ip_address 195.121.1.2
core> netparam bootconfig static:lab01
core> reset
The netparam utility copies its settings into non-volatile memory on the probe. Follow these rules
while using the netparam utility:
• Each time you enter a netparam command, wait for the core> prompt to re-appear before
entering the next command. The prompt indicates that the parameter change is logged.
• When you have finished entering all settings, type reset at the core> prompt. When the probe
restarts, it will use the new netparam parameters.
2.3 Testing Network Communication
You can use the ping command to ensure that the CodeWarrior TAP probe can communicate with the
host.
To verify communication
At a host command prompt, type the following:
ping hostname | ip_address
where hostname is the name and ip_address is the IP address assigned to the CodeWarrior TAP
probe.
If no output is displayed on the screen, check the following:
• The physical connections are tight.
• The CodeWarrior TAP probe address and netmask in the hosts file match those in CodeWarrior
TAP probe flash.
• The netmask used for the CodeWarrior TAP probe and for the Ethernet Network Interface Card
(NIC) are appropriate to the class of the IP address.
15CodeWarrior TAP Probe User Guide
Connecting to a Network
Testing Network Communication
16
CodeWarrior TAP Probe User Guide
3
Connecting to the Target System
To use your CodeWarrior TAP probe, you must have a prototype hardware or an evaluation board.
This chapter explains how to connect a CodeWarrior TAP probe to the target system.
This chapter explains:
• Debug Port Connector Information
• Connecting to the Target System
• Connecting to the Target System Serial Port
3.1 Debug Port Connector Information
The CodeWarrior TAP probe offers debugging capabilities without modifying any target system code or
any special I/O port in the target system for communication with a monitor program running on the target
system. Target system connections can be made using the debug ports (JTAG/COP, StarCore, or
ColdFire BDM).
The CodeWarrior TAP probe connects to the target system's JTAG header using a probe tip adapter and
ribbon cable. The TAP probe is a powerful development tool for use with a wide variety of processors
that use either JTAG/COP, ColdFire BDM, or StarCore debug interfaces.
The following appendices describe the debug port connector specifications:
• “JTAG/COP Connector Information”
• “ColdFire BDM Connector Information”
17CodeWarrior TAP Probe User Guide
Connecting to the Target System
Connecting to the Target System
3.2 Connecting to the Target System
CAUTION Failure to properly connect the TAP probe to the target may damage the probe or target.
Verify all connections before applying power.
The target system must have a debug port header that you can connect to the CW TAP probe. Make sure
that you properly align the TAP multi-pin socket connector with the multi-pin header on your target
system.
Figure 3.1 CW TAP Probe — Connecting Probe Tip to the Probe
NOTE Pin 1 is clearly marked on the gray ribbon cable by a red line down one side of the cable and a
small triangle in the plastic socket.
3.2.1 Connecting Probe Tip to the Target
To connect the CW TAP cable to the target debug port header:
1. Turn off the power to the target system.
2. Make sure that the USB cable from the TAP probe is not connected to the host computer.
3. Connect the probe tip to the CodeWarrior TAP probe.
4. Make sure that pin 1 of the gray ribbon cable connector aligns with pin 1 on the target’s debug port
header.
18
CodeWarrior TAP Probe User Guide
Connecting to the Target System
Connecting to the Target System Serial Port
Figure 3.2 CW TAP Probe — Connecting to the Target
5. Gently (but firmly) press the connector onto the target system debug port header.
3.3 Connecting to the Target System Serial Port
Many target system boards have a built-in serial port. A console interface connection to the serial port of
the target system lets you query and configure the state of your target system.
Figure 3.3 CW TAP Probe — Target Serial Connector
The CodeWarrior TAP probe provides a serial port which can be configured to access the serial port of
the target system. This is useful if you need to access the serial port of a remotely located target system
over Ethernet from the host system.
19CodeWarrior TAP Probe User Guide
Connecting to the Target System
Connecting to the Target System Serial Port
The following sections explain how to access the serial port of the target system:
• Connecting the CodeWarrior TAP Probe to the Target System
• Configuring the Target Serial Port
• Accessing the Target Serial Port
3.3.1 Connecting the CodeWarrior TAP Probe to the
Target System
A RJ25 cable (P/N 600-76822) is provided with the CodeWarrior TAP probe to connect to the serial port
of your target system.
To connect the serial cable between the CodeWarrior TAP probe
and the serial port of the target system
1. Connect one end of the RJ25 cable and the appropriate adapter to the serial port on your target system
board.
2. Connect the other end of the RJ25 cable to the CodeWarrior TAP probe RJ25 serial connector.
3.3.2 Configuring the Target Serial Port
This table shows the default settings of the CodeWarrior TAP Target Serial port.
Table 3.1 CodeWarrior TAP Probe Target Serial Port Default Settings
For this option... Select...
Baud rate 9600
Data bits data8
Stop bits stop1
Parity noparity
Hardware flow control nortscts
XON/XOFF flow control noxon
Target echo feature echo
20
CodeWarrior TAP Probe User Guide
Connecting to the Target System
Connecting to the Target System Serial Port
If the CodeWarrior TAP probe Target Serial port settings do not match the serial port settings of your
target system, use the following steps:
To configure the CodeWarrior TAP probe serial port
1. Make sure network communications are configured correctly. For more information, refer to the
Connecting to a Network
2. Connect to the CodeWarrior TAP probe internal setup utility. For more information, refer to the
Connecting to the CodeWarrior TAP Probe Setup Utility
3. When the core> prompt appears on the terminal, enter the tgtty command to configure the
CodeWarrior TAP probe Target Serial port. The syntax is:
tgtty
[9600|19200|38400|57600|115200]
[data8|data5|data6|data7]
[stop1|stop2]
[noparity|oddparity|evenparity|lowparity|highparity]
[rtscts|nortscts]
[xon|noxon]
[echo|noecho]
For example:
tgtty 19200 data8 stop2 noparity nortscts noxon echo
4. Verify the Target Serial port configuration at the core> prompt by entering the tgtty command by
itself:
tgtty
chapter or Setting Up a Standalone PC Ethernet appendix.
topic.
To restore the target serial port to the default settings
1. Make sure network communications are configured correctly. For more information, refer to the
Connecting to a Network chapter or Setting Up a Standalone PC Ethernet appendix.
2. Connect to the DCU probe internal setup utility. For more information, refer to the Connecting to the
CodeWarrior TAP Probe Setup Utility topic.
3. When the core> prompt appears on the terminal, use the tgtty command to reset the Target Serial
port to the default settings:
tgtty default
21CodeWarrior TAP Probe User Guide
Connecting to the Target System
Connecting to the Target System Serial Port
3.3.3 Accessing the Target Serial Port
You can use telnet to connect to the CodeWarrior TAP probe Target Serial port and access the serial port
of your target system remotely over Ethernet.
To telnet to the Target Serial port
1. Make sure that you have physically connected the DCU probe RJ25 cable to your target system (for
more information, refer to the Connecting the CodeWarrior TAP Probe to the Target System topic).
2. Verify the serial port settings (refer to the Configuring the Target Serial Port
3. Start a telnet session and connect to the DCU probe Target Serial port:
telnet {hostname | ip_address} 1082
Use the host name or IP address of the probe. For static IP, the host name must be the same one you
entered into the hosts database file; refer to the Connecting to a Network
Standalone PC Ethernet appendix. To identify the IP address of any probe on the subnet, refer to the
Using CCS to Search for CodeWarrior TAP Probes topic. The Target Serial port number of the
CodeWarrior TAP probe is 1082.
4. You should now have access to the serial port of your target system. You can use this connection in
the same manner as if your host computer were connected directly to the serial port of your target
system.
topic).
chapter or Setting Up a
22
CodeWarrior TAP Probe User Guide
Loading...