Ethernet TAP Probe - Users Guide - Freescale Semiconductor

Ethernet TAP Probe User Guide

Document Number: ETAPUGRev. 10.x, 11/2015

Ethernet TAP Probe User Guide, Rev. 10.x, 11/2015

2 Freescale Semiconductor, Inc.

Contents

Section number Title Page

Chapter 1Introducing CodeWarrior Ethernet TAP probe

1.1 What is Ethernet TAP probe?......................................................................................................................................... 13

1.1.1 Product highlights.............................................................................................................................................. 14

1.1.2 Debugging environment.....................................................................................................................................15

1.1.3 Ethernet TAP probe components....................................................................................................................... 15

1.1.4 Ethernet TAP probe benefits..............................................................................................................................15

1.1.5 Target system connections................................................................................................................................. 15

1.2 Operating requirements...................................................................................................................................................16

1.2.1 Target power requirements................................................................................................................................ 16

1.2.2 Standard electrostatic precautions......................................................................................................................17

1.2.3 Electrical requirements...................................................................................................................................... 18

1.2.4 Operating temperature........................................................................................................................................18

1.2.5 Target system requirements............................................................................................................................... 18

1.3 Related documentation....................................................................................................................................................19

Chapter 2Setting up Ethernet TAP probe

2.1 Unpacking Ethernet TAP probe .....................................................................................................................................21

2.2 Identifying components.................................................................................................................................................. 21

2.3 Connecting probe tip to Ethernet TAP probe................................................................................................................. 22

2.4 Connecting external power supply..................................................................................................................................22

2.4.1 Connecting power supply cable......................................................................................................................... 23

2.4.2 Cycling power to system....................................................................................................................................23

2.4.2.1 To turn power on................................................................................................................................24

2.4.2.2 To turn power off............................................................................................................................... 24

2.5 What to do next...............................................................................................................................................................24

Chapter 3Connecting to network


Freescale Semiconductor, Inc. 3


3.1 Setup overview................................................................................................................................................................25

3.2 Connecting Ethernet TAP probe to network...................................................................................................................26

3.2.1 To connect to twisted pair interface...................................................................................................................27

3.3 Customizing Ethernet TAP probe...................................................................................................................................27

3.3.1 To establish serial communication with Ethernet TAP probe........................................................................... 28

3.3.2 To customize Ethernet TAP probe network settings......................................................................................... 29

3.3.3 Guidelines for using netparam........................................................................................................................... 29

3.4 Testing network communications...................................................................................................................................30

3.4.1 To verify communication...................................................................................................................................30

3.5 What to do next...............................................................................................................................................................30

Chapter 4Setting up standalone PC Ethernet

4.1 System requirements.......................................................................................................................................................31

4.2 Tutorial: standalone network for the Ethernet setup.......................................................................................................32

4.2.1 Installing and configuring TCP/IP software...................................................................................................... 32

4.2.1.1 To add TCP/IP protocol to the host PC..............................................................................................33

4.2.2 Creating Windows hosts file.............................................................................................................................. 35

4.2.2.1 To create hosts database.....................................................................................................................35

4.2.3 Connecting Ethernet TAP probe to host computer............................................................................................ 36

4.2.3.1 To connect to standalone PC network................................................................................................37

4.3 Configuring Ethernet TAP probe....................................................................................................................................37

4.3.1 Starting setup utility........................................................................................................................................... 37

4.3.1.1 To connect terminal to serial port...................................................................................................... 38

4.3.2 Storing IP address and netmask in flash EPROM..............................................................................................38

4.3.2.1 To store IP address and netmask in flash EPROM............................................................................ 38

4.4 What to do next...............................................................................................................................................................39

Chapter 5Connecting to target system

5.1 Debug port connector information..................................................................................................................................41




5.2 Target system connection options...................................................................................................................................42

5.2.1 Connecting probe tip directly to debug port header...........................................................................................42

5.2.1.1 To connect probe tip to target system debug port header.................................................................. 42

5.2.2 Connecting probe tip to debug port header using extension cable.................................................................... 43

5.2.2.1 To connect flexible probe tip extension cable for debug port header................................................43

5.3 Setting debug port clock frequency................................................................................................................................ 44

5.4 Connecting to target system serial port...........................................................................................................................44

5.4.1 Connecting Ethernet TAP probe to target system..............................................................................................44

5.4.1.1 To connect serial cable between Ethernet TAP probe and serial port of target system.....................45

5.4.2 Configuring target serial port.............................................................................................................................45

5.4.2.1 To configure Ethernet TAP probe serial port.....................................................................................45

5.4.2.2 To restore target serial port to default settings...................................................................................46

5.4.3 Accessing target serial port................................................................................................................................ 46

5.4.3.1 To telnet to target serial port.............................................................................................................. 46

5.5 What to do next...............................................................................................................................................................47

Chapter 6Using Ethernet TAP probe

6.1 Ethernet TAP system startup.......................................................................................................................................... 49

6.1.1 To start Ethernet TAP probe ............................................................................................................................. 49

6.2 Notes on using Ethernet TAP probe............................................................................................................................... 50

6.2.1 Run/Pause/Mixed Mode States.......................................................................................................................... 50

6.2.2 Breakpoints in exception/interrupt handlers...................................................................................................... 50

6.2.3 Ethernet TAP probe power source..................................................................................................................... 51

6.3 Accessing Ethernet TAP probe remotely........................................................................................................................51

6.3.1 To remotely connect to setup utility.................................................................................................................. 51

6.3.2 To connect to your target's serial port remotely.................................................................................................52

Chapter 7Hardware specifications

7.1 Connectors and LEDs..................................................................................................................................................... 53




7.1.1 Run/Pause indicator........................................................................................................................................... 54

7.1.2 Target power indicator....................................................................................................................................... 55

7.1.3 Heartbeat indicator.............................................................................................................................................55

7.1.4 Trigger input/output/ground block.....................................................................................................................55

7.1.5 External power connector.................................................................................................................................. 55

7.1.6 RJ-45 Ethernet connector with RX and TX indicators...................................................................................... 55

7.1.7 RJ-11 config serial connector............................................................................................................................ 56

7.1.8 RJ-11 target serial connector..............................................................................................................................56

7.1.9 Probe tip cable connector...................................................................................................................................57

7.1.10 Debug port connector.........................................................................................................................................57

7.2 Ethernet TAP probe specifications................................................................................................................................. 57

7.2.1 Electrical characteristics.................................................................................................................................... 57

7.2.2 Physical characteristics...................................................................................................................................... 58

Chapter 8JTAG/COP connector information

8.1 Notes specific to MPC8240, MPC8241, and MPC8245................................................................................................ 64

8.1.1 Signal width example.........................................................................................................................................65

Chapter 9DPI connector information

Chapter 10ColdFire BDM connector information

Chapter 11OnCE connector information

Chapter 12ARM JTAG connector information

Chapter 13Ethernet TAP probe setup utility commands

13.1 Connecting to Ethernet TAP probe setup utility.............................................................................................................85

13.1.1 To connect to setup utility using serial port.......................................................................................................86

13.1.2 To connect to setup utility using port.................................................................................................................86




13.2 Ethernet TAP probe setup utility commands and variables............................................................................................87

13.3 Commands to configure communications...................................................................................................................... 88

13.3.1 netparam.............................................................................................................................................................88

13.3.1.1 Syntax.................................................................................................................................................88

13.3.2 tgtty.................................................................................................................................................................... 90

13.3.2.1 Syntax.................................................................................................................................................90

13.3.2.2 Options............................................................................................................................................... 90

13.4 Operational commands................................................................................................................................................... 91

13.4.1 floader................................................................................................................................................................ 91

13.4.1.1 Syntax.................................................................................................................................................91

13.4.2 logout................................................................................................................................................................. 91

13.4.2.1 Syntax.................................................................................................................................................92

13.4.3 reset.................................................................................................................................................................... 92

13.4.3.1 Syntax.................................................................................................................................................92

13.4.4 who.....................................................................................................................................................................92

13.4.4.1 Syntax.................................................................................................................................................92

13.5 Commands to troubleshoot communications..................................................................................................................92

13.5.1 arp.......................................................................................................................................................................92

13.5.1.1 Syntax.................................................................................................................................................93

13.5.1.2 Options............................................................................................................................................... 93

13.5.2 host..................................................................................................................................................................... 93

13.5.2.1 Syntax.................................................................................................................................................93

13.5.2.2 Options............................................................................................................................................... 93

13.5.3 netstat................................................................................................................................................................. 93

13.5.3.1 Syntax.................................................................................................................................................94

13.5.3.2 Options............................................................................................................................................... 94

13.5.4 ping.....................................................................................................................................................................94

13.5.4.1 Syntax.................................................................................................................................................94

13.5.4.2 Options............................................................................................................................................... 94




13.5.5 route................................................................................................................................................................... 95

13.5.5.1 Syntax.................................................................................................................................................95

13.5.5.2 Options............................................................................................................................................... 95

13.6 Utility commands............................................................................................................................................................95

13.6.1 alias.................................................................................................................................................................... 95

13.6.1.1 Syntax.................................................................................................................................................96

13.6.1.2 Options............................................................................................................................................... 96

13.6.2 batch................................................................................................................................................................... 96

13.6.2.1 Syntax.................................................................................................................................................96

13.6.2.2 Options............................................................................................................................................... 96

13.6.2.3 Examples............................................................................................................................................97

13.6.3 history.................................................................................................................................................................97

13.6.3.1 Syntax.................................................................................................................................................97

13.7 Commands for advanced troubleshooting...................................................................................................................... 98

13.7.1 di.........................................................................................................................................................................98

13.7.1.1 Syntax.................................................................................................................................................98

13.7.2 lsas......................................................................................................................................................................98

13.7.2.1 Syntax.................................................................................................................................................98

13.7.3 set....................................................................................................................................................................... 98

13.7.3.1 Syntax.................................................................................................................................................99

13.7.3.2 Options............................................................................................................................................... 99

13.7.4 unset................................................................................................................................................................... 99

13.7.4.1 Syntax.................................................................................................................................................99

13.7.4.2 Options............................................................................................................................................... 99

13.8 Built-in environment variables....................................................................................................................................... 99

13.8.1 batchfile..............................................................................................................................................................100

13.8.1.1 Syntax.................................................................................................................................................100

13.8.1.2 Examples............................................................................................................................................100

13.8.2 batchpath............................................................................................................................................................ 100




13.8.2.1 Syntax.................................................................................................................................................101

13.8.2.2 Examples............................................................................................................................................101

13.8.3 env_protect.........................................................................................................................................................101

13.8.3.1 Syntax.................................................................................................................................................101

13.8.4 username............................................................................................................................................................ 101

13.8.4.1 Syntax.................................................................................................................................................101

Chapter 14Network administration

14.1 TCP/IP networks.............................................................................................................................................................103

14.1.1 TCP/IP addressing and protocols.......................................................................................................................103

14.1.1.1 To install Ethernet TAP probe on TCP/IP network........................................................................... 103

14.1.1.2 Addressing Ethernet TAP probe ....................................................................................................... 104

14.1.1.3 IP configuration..................................................................................................................................104

14.1.1.4 Name servers......................................................................................................................................104

14.1.2 Windows name servers...................................................................................................................................... 105

14.1.2.1 To update Windows hosts file............................................................................................................105

14.1.3 Routing without RIP or RIP2.............................................................................................................................106

14.2 Ethernet TAP probe network ports................................................................................................................................. 106

14.3 Configuring Ethernet TAP probe using netparam.......................................................................................................... 106

14.3.1 Configuring dynamic IP address........................................................................................................................107

14.3.1.1 To configure dynamic IP address.......................................................................................................107

14.3.2 Configuring static IP address............................................................................................................................. 107

14.3.2.1 To enter IP and optional netmask in flash..........................................................................................108

14.3.3 Selecting dynamic or static routing....................................................................................................................109

14.3.3.1 To enable dynamic or static routing...................................................................................................109

14.3.3.2 Specify default gateway or static route table (optional).................................................................... 109

14.3.3.2.1 To specify default gateway............................................................................................. 110

14.3.4 Changing existing route entry............................................................................................................................ 110

14.3.4.1 To change existing routing entry....................................................................................................... 110




14.3.5 Entering static routes..........................................................................................................................................111

14.3.5.1 To enter static route or default gateway.............................................................................................111

14.3.5.2 Static route example...........................................................................................................................111

14.4 Using efind to discover Ethernet TAP probes................................................................................................................ 112

14.4.1 Sample output.................................................................................................................................................... 113

Chapter 15Ethernet TAP probe firmware (core)

15.1 Ethernet TAP probe internal software overview............................................................................................................ 115

15.1.1 Core software..................................................................................................................................................... 115

15.1.2 Shell software.....................................................................................................................................................115

15.1.3 Determine current core version (optional)......................................................................................................... 116

15.1.3.1 To check core version........................................................................................................................ 116

15.2 Reprogramming Ethernet TAP probe firmware image...................................................................................................116

15.2.1 Reprogramming firmware through Ethernet port.............................................................................................. 117

15.2.1.1 To reprogram the firmware image .................................................................................................... 117

15.2.2 Reprogramming firmware through serial port................................................................................................... 118

15.2.2.1 To configure Ethernet TAP probe for FLOADER.............................................................................118

15.2.2.2 To reprogram core firmware image................................................................................................... 118

15.3 What to do next...............................................................................................................................................................119

Chapter 16Troubleshooting

16.1 Troubleshooting communications problems...................................................................................................................121

16.2 Basic troubleshooting......................................................................................................................................................122

16.2.1 Using ping command......................................................................................................................................... 122

16.2.1.1 To verify network communications................................................................................................... 122

16.2.2 Using netstat command......................................................................................................................................123

16.2.2.1 To run netstat command.....................................................................................................................123

16.3 Dynamic troubleshooting................................................................................................................................................124

16.3.1 Using host command..........................................................................................................................................124




16.3.1.1 To add a hostname to the host table...................................................................................................124

16.3.1.2 To remove hostname from host table.................................................................................................124

16.3.2 Using route command........................................................................................................................................ 125

16.3.2.1 To add route to route table................................................................................................................. 125

16.3.2.2 To remove route from route table...................................................................................................... 125

16.3.3 Using arp command........................................................................................................................................... 125

16.3.3.1 To add hostname to arp table............................................................................................................. 126

16.3.3.2 To remove hostname from arp table.................................................................................................. 126

16.4 Advanced troubleshooting.............................................................................................................................................. 126

16.4.1 Ethernet TAP probe status indicators.................................................................................................................126

16.5 Troubleshooting power problems................................................................................................................................... 127



Chapter 1Introducing CodeWarrior Ethernet TAP probeThe CodeWarrior Ethernet TAP probe is a tool that helps you develop and debug anumber of processors and microcontrollers.

CAUTIONThe Ethernet TAP probe contains components that are subjectto damage from electrostatic discharge. Whenever you areusing, handling, or transporting the Ethernet TAP probe, orconnecting to or disconnecting from a target system, always useproper anti-static protection measures, including static-freebench pads and grounded wrist straps.

This chapter contains the following sections:

• What is Ethernet TAP probe?• Operating requirements• Related documentation

1.1 What is Ethernet TAP probe?The Ethernet TAP probe uses advanced emulation technology to provide control of andvisibility into your target system. Combined with a host debugger, the Ethernet TAPprobe speeds the debugging process by letting you interactively control and examine thestate of your target system.



Figure 1-1. Ethernet TAP probe with JTAG/CO probe tip

1.1.1 Product highlights

The Ethernet TAP probe has these features:

• Supports the following systems: PowerPC™ processors, StarCore processors,ColdFire® processors, 56800 Hybrid Controllers (processors and microcontrollers),ARM® processors, and RCF base-band controllers.

• Supports all CPU core speeds.• Lets you control and debug software running in-target, with minimal intrusion into

target system 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

system.

NOTEThe actual download speed depends on the targetsystem processor, the debug port's clock frequency, thenetwork speed, and the debugger.

• Supports 10/100BaseT Ethernet network connection.• Supports telnet access to your target system's serial port, allowing you to interact

with your target system's serial port over the network.• Supports both big and little endian byte-order.

What is Ethernet TAP probe?



• Automatically supports target system signal levels from 1.8V to 3.3V.• Software debug capabilities including:

• 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.

1.1.2 Debugging environment

The Ethernet TAP probe works with the CodeWarrior debugger to give you control overthe emulation functions and your target system.

1.1.3 Ethernet TAP probe components

The Ethernet TAP probe system is composed of two parts:

• The Ethernet TAP probe hardware, which provides visibility into and control of yourtarget system and connects to your host computer through a 10BaseT or 100BaseTEthernet link.

• A target system probe tip, which is designed to provide a physical and electricalinterface to the target system processor that you want to gain visibility into.

1.1.4 Ethernet TAP probe benefits

The Ethernet TAP probe provides these key benefits:

• Visibility: The Ethernet TAP probe makes it possible for you to observe registers andthe current state of target system memory. You can halt program execution atpredefined states and examine the data for a particular program state.

• Control: You can conveniently control the state of the target system by downloadingcode, manually modifying processor registers and memory, single-stepping throughthe code, or setting breakpoints.

Chapter 1 Introducing CodeWarrior Ethernet TAP probe



1.1.5 Target system connections

Target system connections can be made using any one of the debug ports (JTAG/COP,DPI, ColdFire BDM, OnCE, or ARM® JTAG).

The Ethernet TAP probe connects to the target system in any of the following three ways:

• Connect to the debug port header on the target system directly with the probe tip.• Connect to the debug port header on the target system using a flexible extension

cable. Use it when more clearance is required.

The extension cable is provided with your Ethernet TAP probe.

See Target system connection option for an illustration of the debug port interface.

The Ethernet TAP probe offers debugging capabilities without requiring you to modifyany target system code or provide any special I/O port in the target system forcommunications with a monitor.

1.2 Operating requirementsBefore setting up the system, you should make sure that the operating environment isprepared.

1.2.1 Target power requirements

Several configurations are possible for providing power to the system. The preferredconfiguration is for all target DC power supplies to use a 3-wire AC input with an earth(safety) ground and with the earth ground isolated from the DC return. Table belowshows various AC/DC configurations and the results of using each.

Table 1-1. Target system device power supply configurations

AC Input Isolation Result

Preferred configuration 3-wire system with earth(safety) wire

AC earth is isolated from DCreturn.Target system DC isfully isolated and is floating.

Normal operation

Acceptable configuration 2-wire system with no earth(safety) wire

AC return is isolated from DCreturn. Target system DC isfully isolated and is floating.

Normal operation

Acceptable configuration 3-wire system with earth(safety) wire

AC earth is tied to DC return.Target system DC is notisolated and is floating.

Configuration may result inunstable operation of DCsignals.

Table continues on the next page...

Operating requirements



Table 1-1. Target system device power supply configurations (continued)

AC Input Isolation Result

Prohibited configuration 2-wire system with no earth(safety) wire

AC return is tied to DC return.Target system DC is notisolated and is not floating.

Configuration may result inunstable operation of DCsignals and AC hum.A safetyhazard may result from powersupply or target system failurewhere DC voltage isconnected to AC return.

CAUTIONDo not use 2-wire AC input with the AC neutral tied to the DCreturn on any power supply in the system. A failure in a powersupply or target system where DC voltage becomes connectedto AC neutral may result in personal injury and damage to theequipment.

Figure 1-2. Prohibited target power supply connection

CAUTIONGood grounding practices should be observed when connectingdigital grounds to earth ground, since ground loops may inducesufficient currents to cause irregular operation of the combinedsystem.Under no circumstances should the third wire prong onany power cord be removed or disconnected.




1.2.2 Standard electrostatic precautions

This instrument contains static-sensitive components that are subject to damage fromelectrostatic discharge (ESD). Use standard ESD precautions when transporting,handling, or using the Ethernet TAP probe and the target system, when connecting/disconnecting the probe and the target system, and when removing the cover of theinstrument.

It is recommended to follow the following precautions:

• Use wrist straps or heel bands with a 1 MW resistor connected to ground.• On the work surface and floor, use static conductive mats with a 1 MW resistor

connected to ground.• Keep high static-producing items, such as non-ESD-approved plastics, tape and

packaging foam, away from the probe and the target system.

The above precautions should be considered as minimum requirements for a static-controlled environment.

1.2.3 Electrical requirements

The Ethernet TAP probe is powered from the external power supply provided with yourunit. It can use line voltages of 90-130 VAC (47-63 Hz) or 180-270 VAC (47-63 Hz).The Ethernet TAP probe probe tip draws less than 50 mA from the target system.

See Connecting the external power supply for information about connecting the EthernetTAP probe power supply.

1.2.4 Operating temperature

The Ethernet TAP probe can operate in a temperature range of 0 to 40 °C (32 to 104 °F).

1.2.5 Target system requirements

The Ethernet TAP probe automatically supports target system signal levels from 1.8V to3.3V.

NOTEIn the case of PowerPC, for the Ethernet TAP probe to properlystop and restart a JTAG/COP target system processor, the

Operating requirements



QACK signal must be pulled low. The Ethernet TAP probepulls this signal low through the probe tip.

1.3 Related documentationThis manual describes the procedures for unpacking the Ethernet TAP probe, connectingthe external power supply, setting up Ethernet communications, and connecting theEthernet TAP probe to your target system.

The CodeWarrior documentation explains how to install and configure the CodeWarriorIDE and debugger.




Related documentation



Chapter 2Setting up Ethernet TAP probeThis chapter explains how to set up the Ethernet TAP probe.


• Unpacking Ethernet TAP probe• Identifying components• Connecting probe tip to Ethernet TAP probe• Connecting external power supply• What to do next


2.1 Unpacking Ethernet TAP probeYour Ethernet TAP probe has been inspected and tested for electrical and mechanicaldefects before shipping. Although the hardware was carefully packed, examine allcomponents for external damage.

When you unpack the Ethernet TAP probe, be sure to save the protective packaging incase you have to ship or transport the Ethernet TAP probe.

2.2 Identifying componentsBefore you begin, check that these components are present:



• Ethernet TAP probe• External power supply with four interchangeable plugs• CodeWarrior™ Ethernet TAP Probe Users Guide (this manual)

These cables and adapters should also be present:

• One standard debug port (JTAG/COP, DPI, ColdFire BDM, OnCE, or ARM JTAG)probe tip cable assembly

• One flexible probe tip extension cable• One RJ-45 cable• One RJ-45 crossover cable• Two RJ-11 cables• Two 9-pin and two 25-pin cable adapters

2.3 Connecting probe tip to Ethernet TAP probeTo connect the probe tip:

1. Verify that the Ethernet TAP probe is not connected to power.2. Connect the probe tip 50-pin D-style connector to the TARGET PROBE connector

on the Ethernet TAP probe.

Figure 2-1. Ethernet TAP probe with probe tip attached

Instructions for connecting the Ethernet TAP probe to the target hardware are inConnecting to target system.

2.4 Connecting external power supplyThe Ethernet TAP probe requires the use of the auto-sensing (120V or 200V) externalpower supply supplied. It is suggested to use a surge protector between the power supplyand AC power.

Connecting probe tip to Ethernet TAP probe



2.4.1 Connecting power supply cable

To connect the power supply cable:

1. Install the plug for your environment onto the power supply.a. Depress the tab labeled `Push' on the back of the power supply.b. Slide the required connector into the slot.

Figure 2-2. Install plug onto power supply2. Connect the power supply DC cable connector to the POWER connector on the

Ethernet TAP probe.

Connect only the provided power supply to the Ethernet TAP probe.

CAUTIONOther power supplies may look similar, but can damage theprobe if the supply specifications differ from the requiredspecifications.

Figure 2-3. Ethernet TAP probe with a power cable attached

Chapter 2 Setting up Ethernet TAP probe



2.4.2 Cycling power to system

When you need to apply or cycle power to the Ethernet TAP probe, connect or disconnectthe power cable from the power source or from the probe. After you have connected theprobe to your target system, using the following sequence for applying or removingpower.

2.4.2.1 To turn power on1. Turn on Ethernet TAP probe power.2. Turn on target system power.

This is how you can turn on the power.

2.4.2.2 To turn power off1. Turn off target system power.2. Turn off Ethernet TAP probe power.

This is how you can turn off the power.

2.5 What to do nextSet up communications between the Ethernet TAP probe and the host by following theinstructions in the Connecting to a network or Setting up a standalone PC Ethernet, asappropriate.

What to do next



Chapter 3Connecting to networkThis chapter explains how to connect the Ethernet TAP probe to an existing TCP/IPnetwork.

To set up a new network between a PC and an Ethernet TAP probe, see Setting upstandalone PC Ethernet topic.

The Ethernet TAP probe is an Ethernet host device that may be configured for TCP/IPusing DHCP to acquire its IP configuration (the default method) or through a static IPconfiguration.


• Setup overview• Connecting Ethernet TAP probe to network• Customizing Ethernet TAP probe• Testing network communications• What to do next

CAUTIONThe probe contains electronic components that are sensitive toelectrostatic discharge. Always use accepted anti-staticprocedures when handling the probe components.

3.1 Setup overviewThe Ethernet TAP probe's default operation is to acquire its network configurationautomatically through DHCP, and optionally, attempt to register its hostname with aname server. The factory assigned host name is FSLXXYYZZ where XXYYZZ is thelast three octets of the Ethernet MAC address, provided on a label on the bottom side ofthe probe. For example, if the probe's Ethernet MAC address is 00:00:f6:00:77:31, thehost name will be FSL007731.



If you choose to configure the Ethernet TAP probe with a static network configuration,your network administrator typically will allocate the Ethernet TAP probe IP address andhost name, and update the network servers so that the probe is accessible to users on thenetwork.

You will need to follow the instructions here to set up communications:

1. Physically connect the Ethernet TAP probe to an available port on your network. Formore information, see Connecting Ethernet TAP probe to network topic.

2. If you are using a static address, use the Ethernet TAP probe on-board setup utility(see netparam.) to customize probe settings to meet site-specific networkrequirements. You may need to ask your network administrator to allocate anInternet Protocol (IP) address and hostname to your Ethernet TAP probe.

For more information, see Customizing Ethernet TAP probe topic.

NOTEWhen you change any network settings for the Ethernet TAPprobe, you must reboot the probe to activate the new networksettings. At the core> prompt, enter reset.

NOTEWhen you configure the debugger for the hardware connection,you will need to specify the Ethernet TAP probe IP address orhostname. The efind utility can be used to discover any probeon the local subnet. See Using efind to discover Ethernet TAPprobes topic.

NOTEDepending on the type and complexity of your network, yournetwork administrator may need to update network servertables so that the network accesses the Ethernet TAP probecorrectly. Updating network server tables requires both adetailed knowledge of Ethernet address resolution and networkrouting with write access permission to the server tables. SeeNetwork administration topic for more information on networkadministration.

3.2 Connecting Ethernet TAP probe to networkThe Ethernet TAP probe can connect directly to a network using twisted pair(10/100BaseT) cables.

Connecting Ethernet TAP probe to network



3.2.1 To connect to twisted pair interface1. Plug one end of the supplied RJ-45 cable (p/n 600-11112) into the RJ-45 connector

of the Ethernet TAP probe.2. Connect the other end of the RJ-45 cable into the RJ-45 connector of your twisted

pair network.

To connect to a thinwire or thickwire network, use a converter hub that accepts thetwisted pair (10/100BaseT) cable from the Ethernet TAP probe and converts to thethinwire (10Base2) or thickwire (10Base5) cable from your network.

Figure 3-1. Ethernet TAP probe with an RJ-45 cable attached

3.3 Customizing Ethernet TAP probeAs shipped, the Ethernet TAP probe acquires its network configuration automaticallyusing DHCP. If necessary, you can manually enter a network configuration. If you cannotuse DHCP, you must configure the probe for your network's address resolution protocolusing static IP address resolution.

To manually configure the network settings of the Ethernet TAP probe for your networkrequirements, connect a terminal to the probe configuration port (Config Serial) and usethe probe on-board setup utility (netparam) to change probe network settings. The probenetparam utility lets you select and modify network parameters that are saved in probememory. Use netparam to configure the probe to match your network address resolutionand routing protocols.

If the probe must be able to communicate with hosts on other subnets, you will need toconfigure the probe for one of the following routing options:

• Static routing

Chapter 3 Connecting to network



• Default gateways• Static routing tables

For more information, see Commands to configure communications and Networkadministration topics.

3.3.1 To establish serial communication with Ethernet TAP probe1. Connect to the setup utility using the serial port.

a. Connect one end of the RJ-11 cable (P/N 600-12500), and appropriate adapter, toa dumb terminal or to a serial port on your host computer.

b. Connect the other end of the RJ-11 cable to the Ethernet TAP probe RJ-11 serialconnector, labeled Config Serial.


Figure 3-3. Serial connectionc. Set your terminal or terminal communications software (e.g., Windows

HyperTerminal) as follows:• 9600 baud• 8 data bits• 1 stop bit

Customizing Ethernet TAP probe



• no parity• hardware handshaking disabled• XON/XOFF flow control disabled

d. Turn on power to the Ethernet TAP probe. If the power is already on, then cyclepower to the probe.

e. After the login banner is displayed, press Enter.

The core> command-line prompt appears.

3.3.2 To customize Ethernet TAP probe network settings

To complete the steps presented in this section you need write permissions to the networkdatabase or the assistance of your network system administrator.

1. Change the Ethernet TAP probe network settings.a. At the core> prompt, enter the netparam command to see the current settings.b. See netparam for syntax and options you need for network setup. See Network

administration for extended information about installing the Ethernet TAP probeon a network.

c. At the core> prompt, enter the netparam commands and required parameters.2. At the return of the core> prompt, activate the new network settings by rebooting the

Ethernet TAP probe. At the core> prompt, enter reset.

Example: Assign a static IP address and hostname to the Ethernet TAP Probe

If the Ethernet TAP probe has a static IP address of 195.121.1.2 and a hostname of lab01,enter the following commands:

core> netparam bootconfig static:lab01

core> netparam static_ip_address 195.121.1.2

core> reset

3.3.3 Guidelines for using netparam

The netparam utility writes its settings into non-volatile memory on the probe. Followthese rules when using netparam:

• Each time you enter a netparam command, wait for the core> prompt to re-appearbefore entering the next command. The prompt indicates that the parameter changehas been logged.

• When you have finished entering all settings, type reset at the core> prompt. Whenthe probe restarts, it will use the new netparam parameters.

Chapter 3 Connecting to network



3.4 Testing network communicationsYou can use the Windows ping command to ensure that the Ethernet TAP probe cancommunicate with the host.

3.4.1 To verify communication

At the Windows command prompt, type the following:

ping hostname | ip_address

where hostname is the name and ip_address is the IP address assigned to the EthernetTAP probe.

You should see screen output that indicates a reply from hostname that includes the IPaddress. If not, check the following:

• The physical connections are tight.• The Ethernet TAP probe address and netmask in the hosts file match those in

Ethernet TAP probe flash.• The netmask used for the Ethernet TAP probe and for the Ethernet Network Interface

Card (NIC) are appropriate to the class of the IP address.

3.5 What to do nextAfter you have set up the communication channel between your host and the EthernetTAP probe, connect the Ethernet TAP probe to your target system, see Connecting totarget system topic.

For additional information about using the Ethernet TAP probe with your target system,see Using Ethernet TAP probe topic.

If you need to reconnect to the Ethernet TAP probe internal setup utility aftercommunication has been established, see Accessing Ethernet TAP probe remotely topic.

If you have problems communicating with the Ethernet TAP probe after installing thedebugger, see Troubleshooting topic for troubleshooting methods.

Testing network communications



Chapter 4Setting up standalone PC EthernetThis chapter covers installation of a direct TCP/IP Ethernet standalone connectionbetween a PC host and the Ethernet TAP probe. Use it only if you do not want to connectyour probe to an existing multi-user network.

You may decide to have a standalone network for:

• Target system access security• Immunity from network outages• Faster communication if main network is high-traffic• Simpler connection with fewer variables to cause problems

To connect to an existing network, see Connecting to network topic.


• System requirements• Tutorial: standalone network for Ethernet setup• Configuring Ethernet TAP probe• What to do next


4.1 System requirementsA typical standalone network configuration requires:

• A two-node network between a non-networked PC and the Ethernet TAP probe.



• A networked PC with a second Ethernet Network Interface Card (NIC) connected tothe Ethernet TAP probe; figure below shows the standalone configuration.

Figure 4-1. Standalone TCP/IP network configuration• A PC with Microsoft® Windows® operating system installed on it.• Special crossover cables (P/N 600-11111) for setting up stand-alone PC Ethernet

communications. Do not use the straight-wired RJ-45 cable (P/N 600-11112).

4.2 Tutorial: standalone network for the Ethernet setupIf your PC is already configured for networking, skip the tutorial section and go directlyto Configuring the Ethernet TAP probe topic.

The steps required to set up a standalone network for are covered in the followingsections:

• Installing and configuring TCP/IP software• Creating Windows hosts file• Connecting Ethernet TAP probe to host computer

4.2.1 Installing and configuring TCP/IP software

Microsoft provides support for TCP/IP protocol with Windows. If your host PC does notalready have TCP/IP protocol installed, you need to add it.

If you are installing a second Ethernet adapter to dedicate to the Ethernet TAP probe, youneed to install a second instance of TCP/IP. In both instances, you bind the adapter to theTCP/IP protocol stack.

To install and configure TCP/IP, you need:

Tutorial: standalone network for the Ethernet setup



• Windows CD• A name for the Ethernet TAP probe and for the Ethernet Network Interface Card

(NIC)

If you want other users to have access to the Ethernet TAP probe over the network, donot use the instructions in this section. Instead, see Connecting to network topic.

4.2.1.1 To add TCP/IP protocol to the host PC1. Add TCP/IP to the host PC.

a. Select Start > Settings > Control Panel.

The Control Panel window appears.

b. In the Control Panel window, double-click the Network Connections icon.

The Network Connections window appears.

c. Right-click the connection name for which you want to install the TCP/IPprotocol.

A context menu appears.

d. From the context menu, select Properties.

The properties dialog box appears.

e. Click the General tab.

The General page appears.

f. Check the Internet Protocol (TCP/IP) checkbox.g. Click Install.

The Select Network Component Type dialog box appears.

h. In the Select Network Component Type dialog box, select Protocol.i. Click Add.

The Select Network Protocol dialog box appears.

j. In the Network Protocol box, select Internet Protocol (TCP/IP).k. Click OK.

The Select Network Protocol dialog box closes.

l. In the properties dialog box, click OK.

The TCP/IP protocol is added to the host PC.

Chapter 4 Setting up standalone PC Ethernet



2. Configure TCP/IP to recognize the Ethernet Network Interface Card (NIC) used toconnect to the Ethernet TAP probe.

a. Select Start > Settings > Control Panel.

The Control Panel window appears.

b. In the Control Panel window, double-click the Network Connections icon.

The Network Connections window appears.

c. Right-click the connection name for which you want to install the TCP/IPprotocol.

The context menu appears.

d. From the context menu, select Properties.

The network connection properties dialog box appears.

e. Click the General tab.

The General page of the properties dialog box appears.

f. From the General page, select the Internet Protocol (TCP/IP) protocol item.g. Click Properties.

The Internet Protocol (TCP/IP) Properties dialog box appears.

h. Select Use the following IP address option button.

The IP address text boxes associated with this selected option appear.

3. Specify an IP address and netmask.

If the PC is already on an existing network, assign the second adapter an IP andnetmask inconsistent with your network topology (use Class C if LAN is Class B, forexample). This allows the PC to easily resolve communication with the LAN versusthe Ethernet TAP probe. Valid possible internal-use IP addresses for each class are:

A 10.0.0.0 - 10.255.255.255 255.0.0.0

B 172.16.0.0 - 172.31.255.255 255.255.0.0

C 192.168.0.0 - 192.168.255.255 255.255.255.0

If the PC is to remain standalone, use the address and netmask listed below. Theseaddresses simplify configuration.

Address: 192.168.1.1

Subnet mask: 255.255.255.0




4. Confirm your settings, and close the Internet Protocol (TCP/IP) Propertieswindow.

5. When prompted, restart Windows.

If not prompted, restart Windows manually.

NOTEUnless you want to password protect access, click Cancel whenasked for a network password.

4.2.2 Creating Windows hosts file

In the following procedure, you create a hosts database that identifies your PC host andthe Ethernet TAP probe. The hosts file associates IP addresses and host names of bothdevices.

A sample hosts file is installed in your Windows directory when you add the MicrosoftTCP/IP protocol. If your PC has previously been set up with network communications, ahosts database may already exist. Before creating a new hosts database it is a good idea tomake backup copies of any hosts file or sample hosts file.

4.2.2.1 To create hosts database1. Go to the directory where the hosts file is located. Windows hosts files are located in

the %system root%\SYSTEM32\DRIVERS\ETC directory.

NOTEIf you have trouble locating this file, use Windows Find tosearch for "hosts." If you have a dual-boot system, be sureto edit the hosts file appropriate to the operating systemunder which you are installing Ethernet TAP probe.

2. Make a backup copy of any existing hosts file.

Name the backup files something other than hosts, such as hosts.bak.

3. Using any text editor, open a new text file and name it hosts (without an extension) oropen the existing hosts file.

4. In the hosts file, add an entry for the Ethernet Network Interface Card (NIC) used bythe Ethernet TAP probe.

Use the IP address you assigned during TCP/IP configuration. Assign any uniquename.




List the IP address first, followed by the name you assigned to the adapter. Forreference, you can click the Network icon in the Control panel and view theProperties for the appropriate TCP/IP connection.

The following example illustrates a hosts file for a PC in which two adapters areinstalled:

5. Add an entry for your Ethernet TAP probe.

In a true standalone configuration, use the suggested IP address (192.168.1.2) tosimplify configuration. Otherwise, use an address class-consistent with the IPassigned to the NIC that will be connected to the Ethernet TAP probe.

You can assign any unique host name to the Ethernet TAP probe.

6. Save the hosts file as text in the correct directory, and exit the editor.

Host file name should not include a file extension.

4.2.3 Connecting Ethernet TAP probe to host computer

The Ethernet TAP probe has a built-in twisted pair interface that connects directly tonetworks that use the twisted pair (10/100BaseT) cables. A twisted pair crossover cablehas been provided to connect the RJ-45 connector of the Ethernet TAP probe to theEthernet Network Interface Card (NIC) installed in your PC.




4.2.3.1 To connect to standalone PC network1. Plug one end of the supplied twisted pair crossover cable (p/n 600-11111) into the

RJ-45 connector of the Ethernet TAP probe.2. Connect the other end of the twisted pair crossover cable to the NIC installed in your

PC.


After doing the connections, turn on the power of the PC.

4.3 Configuring Ethernet TAP probeBefore you can use the TCP/IP protocol to communicate with the Ethernet TAP probe,you must store the IP address and netmask in the Ethernet TAP probe's flash EPROMusing the probe's internal setup utility.

NOTEThis chapter references only the internal setup utilitycommands used to store the IP address and netmask in flashEPROM. For more information on all the commands availablefrom the Ethernet TAP probe's internal setup utility, seeEthernet TAP Probe setup utility commands and variablestopic.

4.3.1 Starting setup utility

To access the internal setup utility of the Ethernet TAP probe, connect a terminalemulator (such as Windows® HyperTerminal) and configure it as follows:




4.3.1.1 To connect terminal to serial port1. Connect one end of the RJ-11 cable (p/n 600-12500), and appropriate adapter, to a

terminal or the serial port of your PC host.2. Connect the other end of the RJ-11 cable to the Ethernet TAP probe's RJ-11 serial

connector, labeled Config Serial, as shown in figure below.3. Set your terminal or communications software (Windows HyperTerminal, etc.) for

9600 baud, 8 data bits, 1 stop bit, and no parity. Disable hardware handshaking andXON/XOFF flow control.

4. Turn on power to the Ethernet TAP probe.

If the power is already on, then cycle power.

5. After the login banner is displayed, press Enter.


4.3.2 Storing IP address and netmask in flash EPROM

When the core> prompt appears on the terminal, you can use the netparam command toconfigure the Ethernet TAP probe's network parameters.

4.3.2.1 To store IP address and netmask in flash EPROM1. Set the Ethernet TAP probe for static IP address mode using the following command

at the core> prompt:

netparam bootconfig static

2. Enter the Ethernet TAP probe's IP address and netmask at the core> prompt. Forexample:

netparam static_ip_address 192.168.1.2:FFFF0000

NOTEThe IP address you enter must match the IP address youspecified for the Ethernet TAP probe in the hosts file(192.168.1.2 is the suggested IP address). The netmaskmust match the netmask you specified when youconfigured your PC (255.255.0.0 is the suggested netmask).The netmask is can also be entered in hex format: ffff0000

3. When the core> prompt returns, reset the Ethernet TAP probe by cycling its power orby entering the reset command.

Configuring Ethernet TAP probe



Observe the information displayed as the Ethernet TAP probe boots up. Make surethat the IP address and netmask are correct.

4. Remove the RJ-11 cable from the CONFIG serial port. It is not required for normalEthernet TAP probe operation.

After performing all the steps, restart the Windows.

4.4 What to do nextWhen the communication channel between your host and the Ethernet TAP probe hasbeen set up, you can connect the Ethernet TAP probe to your target system, as discussedin Connecting to the target system.

For additional information about using the Ethernet TAP probe with your target system,see Using the Ethernet TAP probe topic. If you need to reconnect to the Ethernet TAPprobe's internal setup utility after communications has been established, see Accessing anEthernet TAP probe remotely.

If you have problems communicating with the Ethernet TAP probe after installing thedebugger, see Troubleshooting topic for troubleshooting methods.




What to do next



Chapter 5Connecting to target systemTo run your software using the Ethernet TAP probe, you must have working targetsystem hardware, prototype hardware, or an evaluation board.

This chapter explains how to connect an Ethernet TAP probe to such hardware.


• Debug port connector information• Target system connection options• Setting debug port clock frequency• Connecting to target system serial port• What to do next


5.1 Debug port connector informationThe Ethernet TAP probe is a powerful development tool for use with a wide variety ofprocessors that use either JTAG/COP, DPI, ColdFire® BDM, ARM® JTAG, or OnCEdebug interfaces.

The following chapters describe the debug port connector specifications:

• JTAG/COP connector information• DPI connector information• ColdFire BDM connector information



• OnCE connector information• ARM JTAG connector information

5.2 Target system connection optionsCAUTION

Failure to properly connect the Ethernet TAP probe tipconnector to the target system may damage the Ethernet TAPprobe or target system. Verify all connections before applyingpower.

There are two ways to connect the Ethernet TAP probe to the target system.

• Connecting probe tip directly to debug port header• Connecting probe tip to debug port header using extension cable

5.2.1 Connecting probe tip directly to debug port header

If your target system has a debug port header, you can directly connect the probe tip onthe Ethernet TAP probe to the target system debug port header. Make sure that youproperly align the multi-pin socket probe tip with the multi-pin header on your targetsystem.

5.2.1.1 To connect probe tip to target system debug port header1. Turn off the power to the target system and the Ethernet TAP probe.2. Make sure all the pins of the probe tip socket are properly aligned with the debug

port header on the target system. Use the label on the probe tip as a guide.3. Gently (but firmly) press the probe tip onto the target system debug port header.

After doing the connections, turn on the power to the target system and Ethernet TAPprobe.

Target system connection options



Figure 5-1. Ethernet TAP probe JTAG/COP connector

5.2.2 Connecting probe tip to debug port header using extensioncable

Use the supplied flexible probe tip extension cable to connect the Ethernet TAP probe toyour target system if there is not enough clearance for the standard probe tip to fit ontothe target system debug port header.

5.2.2.1 To connect flexible probe tip extension cable for debug portheader

1. Turn off the power to the target system and the Ethernet TAP probe.2. Attach the multi-pin header end of the of the flexible probe tip extension cable to the

debug port socket of the Ethernet TAP probe tip.

Figure 5-2. Flexible probe tip extension cable attached to Ethernet TAP probe tip

The red stripe on the cable identifies pin 1. The pin assignment of the cable isidentical to that of the probe tip socket.

3. Connect the other end of the flexible probe tip extension cable to the debug portheader on your target system.

Chapter 5 Connecting to target system



After doing the connections, turn on the power to the target system and Ethernet TAPprobe.

5.3 Setting debug port clock frequencyThe debug port on your target system is a synchronous interface clocked by the TCKsignal. The base frequency is set by the debugger and can be adjusted with preferences inthe debugger.

NOTEFor directions on how to set the debug port clock frequency, seeCodeWarrior documentation.

Some slow target systems might not be able to operate at the initial default rate.Therefore, you may have to adjust the debug port clock rate.

NOTEBecause of variations in the design of target systems, it is notpossible to guarantee that all systems can be operated at themaximum debug port clock rates. These variations includecircuit impedances, trace lengths, and signal terminations. Youmay need to select a lower clock rate to get reliable operation.

5.4 Connecting to target system serial portMany target system boards have a built-in serial port. A console interface connection tothe serial port of the target system lets you query and configure the state of your targetsystem.

The Ethernet TAP probe provides a serial port which can be configured to access theserial port of the target system. This is useful if you need to access the serial port of aremotely located target system over Ethernet from the host system.

This section explains how to access the serial port of the target system in these topics:

• Connecting Ethernet TAP probe to target system• Configuring target serial port• Accessing target serial port

Setting debug port clock frequency



5.4.1 Connecting Ethernet TAP probe to target system

An RJ-11 cable (P/N 600-12500) is provided with the Ethernet TAP probe to connect tothe serial port of your target system.

5.4.1.1 To connect serial cable between Ethernet TAP probe andserial port of target system

1. Connect one end of the RJ-11 cable, and the appropriate adapter, to the serial port onyour target system board.

2. Connect the other end of the RJ-11 cable to the Ethernet TAP probe RJ-11 serialconnector, labeled Target Serial.

5.4.2 Configuring target serial portTable below shows the default settings of the Ethernet TAP target serial port.

Table 5-1. Ethernet TAP probe target serial port default settings

For this option... Select...

Baud rate 9600

Data bits data8

Stop bits stop1

Parity noparity

XON/XOFF flow control noxon

Target echo feature echo

If the Ethernet TAP probe target serial port settings do not match the serial port settingsof your target system, use the following steps.

5.4.2.1 To configure Ethernet TAP probe serial port1. Make sure network communications have already been configured correctly, for

more information, see Connecting to network topic or Setting up standalone PCEthernet topic.

2. Connect to the Ethernet TAP probe internal setup utility, for more information, seeConnecting to Ethernet TAP probe setup utility topic.

3. When the core> prompt appears on the terminal, use the tgtty command to configurethe Ethernet 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] [xon|noxon] [echo|noecho]

For example:

tgtty 19200 data8 stop2 noparity noxon echo

4. Verify the Target Serial port configuration at the core> prompt by entering the tgttycommand by itself: tgtty

5.4.2.2 To restore target serial port to default settings1. Make sure network communications has already been configured correctly, for more

information, see Connecting to network topic or Setting up standalone PC Ethernettopic.

2. Connect to the Ethernet TAP probe internal setup utility, for more information, seeConnecting to Ethernet TAP probe setup utility topic.

3. When the core> prompt appears on the terminal, use the tgtty command to reset thetarget serial port to the default settings: tgtty default

5.4.3 Accessing target serial port

You can use telnet to connect to the Ethernet TAP probe target serial port and access theserial port of your target system remotely over Ethernet.

5.4.3.1 To telnet to target serial port1. To make sure that you have physically connected the Ethernet TAP probe RJ-11

cable to your target system ,seeConnecting Ethernet TAP probe to target systemtopic.

2. To verify the serial port settings, see Configuring target serial port topic.3. Start a telnet session and connect to the Ethernet TAP 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 thesame one you entered into the hosts database file; see Connecting to network orSetting up standalone PC Ethernet topic. To identify the IP address of any probe onthe subnet, see Using efind to discover Ethernet TAP probes topic. The Ethernet TAPprobe Target Serial port number is 1082.

Connecting to target system serial port



4. You should now have access to the serial port of your target system. You can use thisconnection in the same manner as if your host computer were connected directly tothe serial port of your target system.

5.5 What to do nextIf you have not already done so, you can now install the CodeWarrior software. See thetargeting manual for information on how to configure the debugger and run a confidencetest.

For additional information about using the Ethernet TAP probe with your target system,refer to Using Ethernet TAP probe.




What to do next



Chapter 6Using Ethernet TAP probeThis chapter provides system startup procedures, explains how the Ethernet TAP probeworks, and provides important information about using the system.This chapter containsthe following sections:

• Ethernet TAP system startup• Notes on using Ethernet TAP probe• Accessing Ethernet TAP probe remotely

6.1 Ethernet TAP system startupIt helps you how to start the Ethernet TAP probe and the debugger.

Before starting the Ethernet TAP probe, make sure you have:

• Connected the Ethernet TAP probe to your network (see Connecting to network topicor Setting up standalone PC Ethernet topic)

• Connected the Ethernet TAP probe to the target system (see Connecting to targetsystem topic)

• Installed the debugger software and properly configured it to communicate with theEthernet TAP probe.

6.1.1 To start Ethernet TAP probe1. Apply power to the Ethernet TAP probe.2. Apply power to the target system.3. Start the debugger.4. Configure the debugger for the Ethernet TAP connection.

LEDs are provided to indicate the status of the Ethernet TAP probe. For a description ofthe various indicators, see Ethernet TAP Probe Status Indicators topic.



You are now ready to begin your debug session. For information on using the debugger,see the IDE User Guide and the targeting manual.

6.2 Notes on using Ethernet TAP probeIt provides information on how to use Ethernet TAP probe in different modes, Exception/Interrupt Handlers, and power source.

The following topics provide information specific to Ethernet TAP probe operation:

• Run/Pause/Mixed mode states• Breakpoints in exception/interrupt handlers• Ethernet TAP probe power source

For information on system operation, see Targeting manual.

6.2.1 Run/Pause/Mixed Mode States

When the host debugger is connected to the target system using the Ethernet TAP probe,the probe is always in one of these states (modes): run,pause, or mixed mode.

• Run mode - in this mode, all target system processor cores are executing target code.The Run/Pause LED will be green.

• Pause mode - in this mode, all target system processor cores have stopped executingtarget code. The Run/Pause LED will be red.

• Mixed mode - in this mode, some target system processor cores are in run mode andothers are in pause mode. The Run/Pause LED will be orange.

6.2.2 Breakpoints in exception/interrupt handlers

Care must be taken when setting breakpoints in exception handler code. A typicalexception consists of a preamble that saves processor context, the actual exceptionhandler, and then a postamble that restores processor context. You can use softwarebreakpoints in the actual exception handler code, but not in the preamble or postamblewhere the processor context is changing.

NOTEFor Embedded PowerPC processors, placing the CPU intodebug mode is just another interrupt. For example: your code isin an interrupt epilogue and has just placed the return address

Notes on using Ethernet TAP probe



into SRR0 when a breakpoint occurs. The breakpoint causes theIP for the address of the breakpoint to be written to SRR0,destroying your original return address. Stepping through codewhich accesses SRR0 and SRR1 exhibits the same problem.

To avoid this problem, always set your breakpoints before or after code which accessesSRR0 and SRR1, and never step through such code. For example, you can set yourbreakpoint 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."

6.2.3 Ethernet TAP probe power source

The Ethernet TAP probe draws power from the external power supply. The Ethernet TAPprobe tip draws less than 50 mA from the target in order to detect target power.

6.3 Accessing Ethernet TAP probe remotelyYou can remotely access the internal setup utility and the Target Serial port of theEthernet TAP probe after you connect the probe to your network.

If the host computer is not physically located near the Ethernet TAP probe, remote accessis useful when you need to:

• reconfigure communications• use the serial port of your target system• reset the Ethernet TAP probe through your Ethernet connection

6.3.1 To remotely connect to setup utility

Open a telnet session and connect to the Ethernet TAP probe by entering the command:

telnet hostname | ip_address

Use the host name or IP address of the probe. For static IP, the host name must be thesame one you entered into the hosts database file; see Connecting to network topic orSetting up standalone PC Ethernet topic. To identify the IP address of any probe on thesubnet, see Using efind to discover Ethernet TAP probes topic.

The login banner is displayed, followed by the core> command-line prompt.

Chapter 6 Using Ethernet TAP probe



6.3.2 To connect to your target's serial port remotely1. Make sure the Ethernet TAP probe Target Serial port is physically connected to your

target's serial port, and that it has been configured correctly (see Accessing TargetSerial Port).

2. Open a telnet session and connect to the Ethernet TAP probe Target Serial port byentering the command:

telnet {hostname | ip_address} 1082

Use the host name or IP address of the probe. For static IP, the host name must be thesame one you entered into the hosts database file; see Connecting to Network orSetting Up Standalone PC Ethernet. To identify the IP address of any probe on thesubnet, see Using Efind to Discover Ethernet TAP Probes. The Ethernet TAP probeTarget Serial port number is 1082.

You should now have access to the serial port of your target system.

Accessing Ethernet TAP probe remotely



Chapter 7Hardware specificationsThis chapter provides hardware specifications for the Ethernet TAP probe.


• Connectors and LEDs• Ethernet TAP probe specifications

7.1 Connectors and LEDsEthernet TAP probe - top view, Ethernet TAP probe - side view, Ethernet TAP probe -power end view, and Ethernet TAP probe connector - target end view shows the variousLEDs and connectors of the Ethernet TAP probe.

Figure 7-1. Ethernet TAP probe - top view



Figure 7-2. Ethernet TAP Probe - side view

Figure 7-3. Ethernet TAP Probe - power end view

NOTEThe POWER connector on your Ethernet TAP probe may be adifferent style.

Figure 7-4. Ethernet TAP probe connector - target end view

7.1.1 Run/Pause indicator

The status LED (labeled RUN/PAUSE) indicates the state of the target as follows:

• The LED is green when the target is in run mode.• The LED is red when the target is in pause mode.

Connectors and LEDs



• 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

Ethernet TAP probe.

For the definition of run and pause modes, see Run/Pause/Mixed mode states topic.

7.1.2 Target power indicator

The target power LED (labeled TGT/PWR) indicates whether the Ethernet TAP probedetects target power.

• The LED is green when target power is detected.• The LED is unlit when no target power is detected, or if the debugger has not

connected to the Ethernet TAP probe.

7.1.3 Heartbeat indicator

The Heartbeat LED (labeled HEARTBEAT) indicates the status of communicationsbetween the Ethernet TAP probe and the network as follows:

• The LED is red until the Ethernet TAP probe boot code starts running.• The LED flashes orange during configuration of the network interface.• The LED flashes green after network interface has been successfully configured.• The LED is unlit if the Ethernet TAP probe is not powered on.

7.1.4 Trigger input/output/ground block

Not used.

7.1.5 External power connector

The external power connector is located on the back of the Ethernet TAP probe. TheEthernet TAP probe cannot operate without external power.

Chapter 7 Hardware specifications



7.1.6 RJ-45 Ethernet connector with RX and TX indicators

The Ethernet TAP probe interface consists of an RJ-45 connector and a built-in twistedpair MAU that connects directly to 10/100BaseT twisted pair networks. Adapters are alsoavailable to connect to networks that use thinwire (10Base2) and thickwire (10Base5)cables. See Connecting to network or Setting up standalone PC Ethernet topic for moreinformation on connecting to an network.

The Ethernet TAP probe RX and TX indicators are integrated into the RJ-45 EthernetTAP probe connector. The RX indicator is green and flashes when data is being receivedfrom the network. The TX indicator is yellow and flashes when the Ethernet TAP probeis transmitting data to the network.

7.1.7 RJ-11 config serial connector

The Config Serial communications port on the Ethernet TAP probe supports RS-232communications protocol at 9600 baud. The serial port uses an RJ-11 six-conductorphone jack. The Config Serial port is used for configuring network communications,entering routing tables, and for diagnostics.

See Pinout definition of the config serial port topic for the pinout definition of the ConfigSerial port.

Table 7-1. Pinout definition of the config serial port

Pin Signal

1 Ready To Send (RTS)

2 Ground

3 Receive Data (RxD)

4 Transmit Data (TxD)

5 Ground

6 Clear To Send (CTS)

Pin 1 is on the right side as you look at the RJ-11 socket (locking tab on the bottom.)

7.1.8 RJ-11 target serial connector

The Ethernet TAP probe provides a target serial port which can be configured to accessyour target's serial port. This is particularly useful if your host computer is not near yourtarget and you need to access your target's serial port remotely over your network. Forpinout definition, see Pinout definition of the config serial port topic.

Connectors and LEDs



7.1.9 Probe tip cable connector

The probe tip cable is connected to the 50-pin D-style connector on the Ethernet TAPprobe.

7.1.10 Debug port connector

The debug port socket is on the end of the probe tip and is used to connect the EthernetTAP probe to a debug port header on your target system.

NOTEBe sure to connect Pin 1 of the probe tip to Pin 1 of the header.

7.2 Ethernet TAP probe specificationsThe following figure shows the dimensions of the Ethernet TAP probe.

Figure 7-5. Ethernet TAP probe dimensions




7.2.1 Electrical characteristics

The Ethernet TAP probe affects the load on only those signals that are connected to thedebug port connector. Loading depends on the method used to connect the Ethernet TAPprobe to the target system. See Connecting to target system topic for a description of eachconnection method.

The Ethernet TAP probe affects the target processor and target electrical characteristicsas little as possible. Care, however, should be taken in designing the target toaccommodate the small signal delays associated with any in-circuit emulator or other testequipment.

The Ethernet TAP probe automatically supports target signal levels from 1.8V to 3.3V.

7.2.2 Physical characteristics

The Ethernet TAP probe was carefully designed to be as small as possible. Even so, itmay not physically fit in all target systems.

If you are unable to connect to the debug port on your target system, or if your targetsystem does not have a debug port connector, see Connecting probe tip to debug portheader using extension cable topic.

The following table shows the physical characteristics of the Ethernet TAP probe.

Table 7-2. Ethernet TAP probe - physical characteristics

Physical characteristics

Power Consumption

Ethernet TAP probe power consumption from external powersupply

750 mA @ 5V maximum 350 mA @ 3.3V maximum

Ethernet TAP probe power consumption from target Less than 50 mA to detect target power

Environmental requirements

Operating temperature 0 to 40 °C (32 to 104 °F)

Storage temperature -40 to 70 °C (-40 to 158 °F)

Humidity 5% to 95% relative humidity,non-condensing

Physical

Ethernet TAP probe dimensions 6.30" x 3.68" x 1.58"(16.00 cm x 9.34cm x 4.0 cm)

Probe tip enclosure dimensions (excluding connector) approx. 2.25" x 1.75" x 0.625" (5.72 cm x 4.44 cm x 1.59 cm)

Target socket dimensions

Height (out of probe tip enclosure; above board) 0.28" (0.71 cm)

Thickness 0.20" (0.51 cm)

Pin-to-pin spacing 0.1" (0.25 cm)

JTAG/COP width 0.8" (2.0 cm)


Ethernet TAP probe specifications



Table 7-2. Ethernet TAP probe - physical characteristics (continued)

Physical characteristics

DPI width 0.5" (1.27 cm)

OnCE width 0.7" (1.78 cm)

ColdFire BDM width 1.3" (3.30 cm)

ARM JTAG width 1.0" (2.54 cm)

Black and gray cable approximately 16.0" x 1.25" x 0.126" (40.64 cm x 3.18 cm x0.32 cm)

Figure 7-6. Target connector dimensions




Ethernet TAP probe specifications



Chapter 8JTAG/COP connector informationThe CodeWarrior Ethernet TAP JTAG/COP probe has a 16-pin connector whichautomatically supports target system signal levels from 1.8V to 3.3V.

The following figure shows the pin assignments of the probe JTAG/COP connector.

Figure 8-1. Ethernet TAP probe for JTAG/COP connector pin assignments

The following table lists JTAG/COP signal names, direction, pin numbers, descriptions,and drive capabilities for the probe JTAG/COP connector.

Table 8-1. Ethernet TAP probe for JTAG/COP signal directions

JTAG/COP pin Signal mnemonic Signal direction Description

1 TDO From target system 17pF load

2 QACK From Ethernet TAP probeconnector

100Ohm pull-down

3 TDI From Ethernet TAP probeconnector

50mA driver

4 TRST From Ethernet TAP probeconnector

50mA driver




Table 8-1. Ethernet TAP probe for JTAG/COP signal directions (continued)

JTAG/COP pin Signal mnemonic Signal direction Description

5 HALTED Bi-directional Open-drain, 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted1

6 TGT PWR From target system 2MOhm pull-down, plus0.01uF load

7 TCK From Ethernet TAP probeconnector

50mA driver

8 CKSI From Ethernet TAP probeconnector

50mA driver

9 TMS From Ethernet TAP probeconnector

50mA driver

10 No Connect - n/a -

11 SRST Bi-directional Open-drain. 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted1


13 HRST Bi-directional Open-drain. 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted1


15 CKSO From target system 17pF load1

16 GND - n/a -

1. 4.7KOhm pull-up to buffered TGT PWR.

The following table provides a general description of each JTAG/COP signal and theoperational requirements.

NOTEAll JTAG/COP signals must meet accepted standards forJTAG/COP signal design. To ensure proper and stableoperation between the Ethernet TAP probe and the targetsystem, the JTAG/COP signals must meet the requirementslisted in table below.

Table 8-2. Ethernet TAP probe for JTAG/COP signal recommendations and requirements

JTAG/COPpin Signal mnemonic Requirement

1 TDO Must be wired to the target systemprocessor. TDO is an output from thetarget system processor and an input tothe Ethernet TAP probe. The TDO tracerun should be kept short and maintain a




Table 8-2. Ethernet TAP probe for JTAG/COP signal recommendations and requirements(continued)


"two-signal-width" spacing from anyother parallel dynamic signal trace. TDOshould have a series termination resistorlocated near the target systemprocessor.

2 QACK May be wired to the target systemprocessor. QACK is an input to mostPowerPC processors and must remainlow while the Ethernet TAP probe isconnected to the target system. TheEthernet TAP probe connects this signalinternally to the JTAG/COP GND pin(16) through a 100Ohm resistor.

3 TDI Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TDI output with up to 50mA.The TDI trace should be kept short andmaintain a "two-signal-width" spacingfrom any other parallel dynamic signaltrace. TDI should have an RCtermination option at the processor.

4 TRST Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TRST output with up to 50mA.To gain control of the processor, theEthernet TAP probe negates TRSTapproximately 250 milliseconds beforenegation of HRST. This allows theEthernet TAP probe to issue COPcommands through the JTAG/COPinterface and gain control of theprocessor upon negation of HRST. TheTRST trace run should be kept short andmaintain a "two-signal-width" spacingfrom any other parallel dynamic signaltrace.

5 HALTED Need not be wired to the target system.The Ethernet TAP probe does notcurrently use this signal.

6 TGT PWR Must be wired to the target system. TheEthernet TAP probe uses this signal todetermine if power is applied to thetarget system. This signal is also usedas a voltage reference for the signalsdriven by the Ethernet TAP probe (CKSI,TRST, TCK, TMS, TDI). TGT PWR (pin6) should be connected to the targetsystem Vcc through a 1KOhm pull-up.

7 TCK Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TCK output with up to 50mA.The TCK trace run should be kept as


Chapter 8 JTAG/COP connector information



Table 8-2. Ethernet TAP probe for JTAG/COP signal recommendations and requirements(continued)


short as possible and maintain a "two-signal-width" spacing from any otherparallel dynamic signal trace.

8 CKSI Need not be wired to the targetsystem.The Ethernet TAP probe doesnot currently use this signal.

9 TMS Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TMS output with up to 50mA.TMS should be kept as short as possibleand maintain a "two-signal-width"spacing from any other parallel dynamicsignal trace. TMS should have atermination option at the processor.

10 No Connect Not required for emulation

11 SRST May be wired to the target systemprocessor. During reset, the EthernetTAP probe drives SRST to groundthrough a 100Ohm resistor.


13 HRST Must be wired to the target systemprocessor. During reset, the EthernetTAP probe drives HRST to groundthrough a 100Ohm resistor.


15 CKSO Should be wired to the target systemprocessor. The Ethernet TAP probesenses CKSO to determine if theprocessor halted execution in acheckstop state.

16 GND Must be wired to the target system. GNDis connected directly to the ground insidethe Ethernet TAP probe.

8.1 Notes specific to MPC8240, MPC8241, and MPC8245CKSO is not available on the MPC8240, MPC8241, or MPC8245 processors.

SRST can be deselected in favor of the SDMA12 signal used for Extended Addressing(except on the MPC8240 processor).

QACK is an output signal only, so it need not be connected to the COP header.

The Ethernet TAP probe fully supports the MPC8240, MPC8241, and MPC8245processors despite the absence of the signals mentioned above.

Notes specific to MPC8240, MPC8241, and MPC8245



8.1.1 Signal width example

Signal line 'A' is 0.005 mil. An adjacent dynamic signal line 'B' should maintain a "two-signal-widths" distance from signal line 'A'. So that from the center of line 'A' to thecenter of line 'B', there should be 0.0025 + 0.005 + 0.005 + 0.0025 = 0.015mil.

Target system bias should maintain "one-signal-width" spacing from the signal.

Chapter 8 JTAG/COP connector information



Notes specific to MPC8240, MPC8241, and MPC8245



Chapter 9DPI connector informationThe CodeWarrior Ethernet TAP DPI probe has a 10-pin connector which automaticallysupports target system signal levels from 1.8V to 3.3V.

The following figure shows the pin assignments of the probe DPI connector.

Figure 9-1. Ethernet TAP probe for DPI connector pin assignments

The following table lists DPI signal names, direction, pin numbers, descriptions, anddrive capabilities for the probe DPI connector.

Table 9-1. Ethernet TAP probe for DPI signal directions

DPI pin Signal mnemonic Signal direction Description

1 VLSO/FRZ From target system 17pF load

2 SRST Bi-directional Open-drain. 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted

3 GND - n/a -

4 DSCK From Ethernet TAP probeconnector

50mA driver

5 GND - n/a -

6 VFLS1/FRZ From target system 22pF load




Table 9-1. Ethernet TAP probe for DPI signal directions (continued)

DPI pin Signal mnemonic Signal direction Description

7 HRST Bi-directional Open-drain. 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted1

8 DSDI From Ethernet TAP probeconnector

50mA driver

9 VDD From target system 2MOhm pull-down, plus0.01uF load

10 DSDO From target system 17pF load

1. 4.7KOhm pull-up to buffered TGT PWR.

The table below provides a general description of each DPI signal and operationalrequirements.

NOTEAll DPI signals must meet accepted standards for DPI signaldesign. To ensure proper and stable operation between theEthernet TAP probe and the target system, the DPI signals mustmeet the requirements listed in the following table.

Table 9-2. Ethernet TAP probe for DPI signal recommendations and requirements

DPI pin Signal mnemonic Requirement

1 VLSO/FRZ VFLS0/FRZ is not needed for emulation.

2 SRST Must be wired to the target system.During reset, the Ethernet TAP probedrives SRST to ground through a100Ohm resistor.


4 DSCK Must be wired to the target systemprocessor. It is driven by the EthernetTAP probe as an output with up to50mA. This signal is the clock for theDPI interface. It is good design practiceto keep the trace length short and isolatethe trace from other signals. If the tracemust be long, then termination may beneeded.


6 VFLS1/FRZ VFLS1/FRZ is not needed for emulation.




Table 9-2. Ethernet TAP probe for DPI signal recommendations and requirements(continued)

DPI pin Signal mnemonic Requirement

7 HRST Must be wired to the target system.During reset, the Ethernet TAP probedrives HRST to ground through a100Ohm resistor.

8 DSDI Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TDI output with up to 50 mA.

9 VDD Must be wired to the target system. TheEthernet TAP probe uses this signal todetermine if power is applied to thetarget system. This signal is also usedas a voltage reference for the signalsdriven by the Ethernet TAP probe(SRST, SDCK, HRST, DSDI).

10 DSDO Must be wired to the target systemprocessor. DSDO is an output from thetarget system processor and an input tothe Ethernet TAP probe. It is gooddesign practice to keep the trace lengthshort and isolate the trace from the othersignals.

Chapter 9 DPI connector information



Chapter 10ColdFire BDM connector informationThe CodeWarrior Ethernet TAP ColdFire BDM probe has a 26-pin connector whichautomatically supports target system signal levels from 1.8V to 3.3V.

The following figure shows the pin assignments of the probe BDM connector.

Figure 10-1. Ethernet TAP probe ColdFire BDM connector pin assignments



The following table lists BDM signal names, direction, pin numbers, descriptions, anddrive capabilities of the probe BDM connector.

Table 10-1. Ethernet TAP probe ColdFire BDM signal directions

BDM pin Signal mnemonic Signal direction Description

1 Reserved From target system 17pF load

2 BKPT From Ethernet TAP probeconnector

50mA driver

3 GND - n/a -

4 DSCLK From Ethernet TAP probeconnector

50mA driver

5 GND - n/a -

6 Reserved Bi-directional Open-drain, 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted

7 RESET Bi-directional Open-drain. 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted1

8 DSI From Ethernet TAP probeconnector

50mA driver


10 DSO From target system 17pF load

11 GND - n/a -

12 PST3 - n/a -

13 PST2 - n/a -

14 PST1 - n/a -

15 PST0 - n/a -

16 DDATA3 - n/a -

17 DDATA2 - n/a -

18 DDATA1 - n/a -

19 DDATA0 - n/a -

20 GND - n/a -

21 Reserved - n/a -

22 Reserved - n/a -

23 GND - n/a -

24 PSTCLK From target system 17pF load

25 Core Voltage - n/a -

26 TEA From Ethernet TAP probeconnector

50mA driver1

1. 4.7Ohm pull-up to buffered TGT PWR.



The table below provides a general description of each BDM signal and operationalrequirements.

NOTEAll ColdFire BDM signals must meet accepted standards forColdFire BDM signal design. To ensure proper and stableoperation between the Ethernet TAP probe and the targetsystem, the BDM signals must meet the requirements listed inthe following table.

Table 10-2. Ethernet TAP probe ColdFire BDM signal recommendations and requirements

BDM pin Signal mnemonic Requirement

1 Reserved Need not be wired to the target system.The Ethernet TAP probe does notcurrently use this signal.

2 BKPT Must be wired to the target system.


4 DSCLK DSCLK must be connected to the targetsystem's processor. It is driven by theEthernet TAP probe as an output with upto 50mA. This signal is the clock for theBDM interface. It is good design practiceto keep the trace length short and isolatethe trace from other signals. If the tracemust be long, then termination may beneeded.


6 Reserved Need not be wired to the target system.The Ethernet TAP does not currently usethis signal.

7 RESET Must be wired to the target system.During reset, the Ethernet TAP probedrives RESET to ground through a100Ohm resistor.

8 DSI Must be wired to the target systemprocessor. The Ethernet TAP probedrives the DSI output with up to 50mA.

9 VDD Must be wired to the target system. TheEthernet TAP probe uses this signal todetermine if power is applied to thetarget system. The signal is also used asa voltage reference for the signals drivenby the Ethernet TAP probe (BKPT,DSCLK, RESET, DSI, and TEA).


Chapter 10 ColdFire BDM connector information



Table 10-2. Ethernet TAP probe ColdFire BDM signal recommendations and requirements(continued)


10 DSO Must be wired to the target systemprocessor. It is an input to the EthernetTAP probe.


12 PST3 Need not be wired to the target system.The Ethernet TAP probe does notcurrently use this signal.




16 DDATA3 Need not be wired to the target system.The Ethernet TAP probe does notcurrently use this signal.




20 GND Must be wired to the target system. GNDis connected directly the ground insidethe Ethernet TAP probe.




24 PSTCLK Need not be wired to the target system.The Ethernet TAP probe does notcurrently use this signal.

25 Core Voltage Need not be wired to the target system.The Ethernet TAP probe does notcurrently use this signal.




Table 10-2. Ethernet TAP probe ColdFire BDM signal recommendations and requirements(continued)


26 TEA Need not be wired to the target system.The Ethernet TAP probe does notcurrently use this signal.

Chapter 10 ColdFire BDM connector information



Chapter 11OnCE connector informationThe CodeWarrior Ethernet TAP OnCE probe has a 14-pin connector which automaticallysupports target system signal levels from 1.8V to 3.3V.

The following figure shows the pin assignments of the probe OnCE connector.

Figure 11-1. Ethernet TAP probe Once connector pin assignments

The following table lists OnCE signal names, direction, pin numbers, descriptions, anddrive capabilities for the probe OnCE connector.

Table 11-1. Ethernet TAP probe OnCE signal directions

OnCE pin Signal mnemonic Signal direction Description


50mA driver

2 GND - n/a -

3 TDO From target system 17pF load

4 GND - n/a -


50mA driver

6 GND - n/a -

7 Reserved From Ethernet TAP probeconnector

50mA driver




Table 11-1. Ethernet TAP probe OnCE signal directions (continued)

OnCE pin Signal mnemonic Signal direction Description

8 No-Connect/Key - n/a -

9 RESET Bi-directional Open-drain. 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted


50mA driver


12 Reserved Bi-directional Open-drain, 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted1

13 Reserved Bi-directional Open-drain, 100Ohm toground when asserted byEthernet TAP probe, 22pFload when not asserted1


50mA driver

1. 4.7KOhm pull-up to buffered VDD.

The table below provides a general description of each OnCE signal and the operationalrequirements.

NOTEAll OnCE signals must meet accepted standards for OnCEsignal design. To ensure proper and stable operation betweenthe Ethernet TAP probe and the target system, the OnCEsignals must meet the requirements listed in the following table.

Table 11-2. Ethernet TAP probe OnCE signal recommendations and requirements

OnCE pin Signal mnemonic Requirement

1 TDI Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TDI output with up to 50 mA.The TDI trace should be kept short andmaintain a "two-signal-width" spacingfrom any other parallel dynamic signaltrace. TDI should have an RCtermination option at the processor.


3 TDO Must be wired to the target systemprocessor. TDO is an output from thetarget system processor and input to the




Table 11-2. Ethernet TAP probe OnCE signal recommendations and requirements(continued)


Ethernet TAP probe. The TDO trace runshould be kept short and maintain a"two-signal-width" spacing from anyother parallel dynamic signal trace. TDOshould have a series termination resistorlocated near the target systemprocessor.


5 TCK Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TCK output with up to 50 mA.The TCK trace run should be kept asshort as possible and maintain a "two-signal-width" spacing from any otherparallel dynamic signal trace.


7 Reserved Not required for emulation.

8 No-Connect/Key Not required for emulation. Pin 8 shouldbe clipped on the target system OnCEheader.

9 RESET Must be wired to the target systemprocessor. The Ethernet TAP probedrives the RESET output with 50mA.During reset, the Ethernet TAP probedrives RESET to ground through a100Ohm resistor.

10 TMS Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TCK output with up to 50mA.The TCK trace run should be kept asshort as possible and maintain a "two-signal-width" spacing from any otherparallel dynamic signal trace.

11 VDD Must be wired to the target system. TheEthernet TAP probe uses this signal todetermine if power is applied to thetarget system. This signal is also usedas a voltage reference for the signalsdriven by the Ethernet TAP probe (TDI,TCK, TMS, RESET, and TRST).



14 TRST Must be wired to the target systemprocessor. The Ethernet TAP probedrives the TRST output with up to 50mA. The TRST trace run should be kept

Chapter 11 OnCE connector information



Table 11-2. Ethernet TAP probe OnCE signal recommendations and requirements


short and maintain a "two-signal-width"spacing from any other parallel dynamicsignal trace.



Chapter 12ARM JTAG connector informationThe CodeWarrior Ethernet TAP ARM® JTAG probe has a 20-pin connector whichautomatically supports target system signal levels from 1.8V to 3.3V.

The following figure shows the pin assignments of the probe ARM JTAG connector.

Figure 12-1. Ethernet TAP probe ARM JTAG connector pin assignments

The following table lists ARM JTAG signal names, direction, pin numbers, descriptions,and drive capabilities for the probe ARM JTAG connector.

Table 12-1. Ethernet TAP probe ARM JTAG signal directions

ARM JTAG pin Signal mnemonic Signal direction Description

1 VTREF From target system 2MOhm pull-down, plus0.01uF load

2 VSUPPLY - n/a - VSUPPLY is not used by theEthernet TAP


50mA driver




Table 12-1. Ethernet TAP probe ARM JTAG signal directions (continued)

ARM JTAG pin Signal mnemonic Signal direction Description

4 GND - n/a -


50mA driver

6 GND - n/a -


50mA driver

8 GND - n/a -


50mA driver

10 GND - n/a -

11 RTCK From target system 17pF load

12 GND - n/a -

13 TDO From target system 17pF load2

14 GND - n/a -

15 SRST Bi-directional Open-drain. 100Ohm toground when asserted byEthernet TAP, 22pF loadwhen not asserted1

16 GND - n/a -

17 DBGRQ From Ethernet TAP probeconnector

50mA driver

18 GND - n/a -

19 DBGACK From target system 17pF load2

20 GND - n/a -

1. 100KOhm pull-up to buffered VDD.2. 100KOhm pull-down to GND.

The table below provides a general description of each ARM JTAG signal and theoperational requirements.

NOTEAll ARM JTAG signals must meet accepted standards for ARMJTAG signal design. To ensure proper and stable operationbetween the Ethernet TAP probe for ARM JTAG and the targetsystem, the ARM JTAG signals must meet the requirementslisted in the following table.

Table 12-2. Ethernet TAP probe ARM JTAG signal recommendations and requirements

ARM JTAG pin Signal mnemonic Requirement

1 VTREF Must be wired to the target system. TheEthernet TAP probe uses this signal todetermine if power is applied to the




Table 12-2. Ethernet TAP probe ARM JTAG signal recommendations and requirements(continued)


target. The signal is also used as avoltage reference for the signals drivenby the Ethernet TAP probe (TRST, TDI,TMS, TCK, SRST, DBGRQ). VTREFshould be connected to target Vccthrough a 1KOhm pull-up.

2 VSUPPLY May be wired to the target processor.The Ethernet TAP probe does notcurrently use this signal.

3 TRST Must be wired to the target system. TheEthernet TAP probe drives the TRSToutput with up to 50 mA. Note: TRSTmust not be connected to SRST. Theprobe must be able to independentlyassert these two signals.


5 TDI Must be wired to the target system. TheEthernet TAP probe drives the TDIoutput with up to 50 mA. The TDI tracerun should be kept as short as possibleand maintain a "two-signal-width"spacing from any other parallel dynamicsignal trace.


7 TMS Must be wired to the target system. TheEthernet TAP probe drives the TMSoutput with up to 50 mA. The TMS tracerun should be kept as short as possibleand maintain a "two-signal-width"spacing from any other parallel dynamicsignal trace.


9 TCK Must be wired to the target processor.The Ethernet TAP probe drives the TCKoutput with up to 50 mA. The TCK tracerun should be kept as short as possibleand maintain a "two-signal-width"spacing from any other parallel dynamicsignal trace.



Chapter 12 ARM JTAG connector information



Table 12-2. Ethernet TAP probe ARM JTAG signal recommendations and requirements(continued)


11 RTCK May be wired to the target processor.The Ethernet TAP probe does notrequire this signal.


13 TDO Must be wired to the target processor.TDO is an output from the targetprocessor and an input to the EthernetTAP probe. The TDO trace run shouldbe kept as short as possible andmaintain a "two-signal-width" spacingfrom any other parallel dynamic signaltrace. TDO should have a seriestermination resistor located near thetarget processor.


15 SRST Must be wired to the target processor.The Ethernet TAP probe drives theSRST output with up to 50 mA. Duringreset, the probe drives SRST to groundthrough a 100Ohm resistor. Note: TRSTmust not be connected to SRST. Theprobe must be able to independentlyassert these two signals.


17 DBGRQ May be wired to the target processor.The Ethernet TAP probe does notcurrently use this signal.


19 DBGACK May be wired to the target processor.The Ethernet TAP probe does notcurrently use this signal.




Chapter 13Ethernet TAP probe setup utility commandsThis chapter explains how to access the Ethernet TAP probe internal setup utility. Itdescribes all available setup utility commands and arguments.


• Connecting to Ethernet TAP probe setup utility• Ethernet TAP probe setup utility commands and variables• Commands to configure communications• Operational commands• Commands to troubleshoot communications• Utility commands• Commands for advanced troubleshooting• Built-in environment variables

NOTEThe commands described in this appendix are for referenceonly. For detailed procedures on using these commands, refer tothe applicable chapter or appendix that covers the topic ofinterest.

13.1 Connecting to Ethernet TAP probe setup utilityThere are two methods for accessing the Ethernet TAP probe internal setup utility:

• Connect to the Ethernet TAP probe serial port.

Use this method if the Ethernet TAP probe is not connected to your network.

• Telnet to the Ethernet TAP probe through an existing Ethernet connection (see Toconnect to setup utility using port.)



Use this method if the Ethernet TAP probe is currently connected to your network.TELNET is the Internet standard protocol for remote logins. Most TCP/IP networksprovide a telnet program that you can use to login across the network to another machine.Note that if you should lose your Ethernet connection by improperly configuring theEthernet TAP probe from a telnet session, then you will have to connect to the serial portto re-establish network communications.

13.1.1 To connect to setup utility using serial port1. Connect one end of the RJ-11 cable (P/N 600-12500), and appropriate adapter, to a

terminal or the serial port of your host computer.2. Connect the other end of the RJ-11 cable to the Ethernet TAP probe RJ-11 serial

connector, labeled Config Serial.3. Set your terminal or communications software (Windows® HyperTerminal, etc.) for

9600 baud, 8 data bits, 1 stop bit, no parity. Disable hardware handshaking andXON/XOFF flow control.

4. Turn on power to the Ethernet TAP probe.

If the power is already on, cycle power to the probe.



Figure 13-1. Ethernet TAP Probe with a Serial Cable Connected

13.1.2 To connect to setup utility using port1. Open a telnet session and connect to the Ethernet TAP probe.

telnet hostname

Use the hostname that you entered into the hosts database file, for more information,see Connecting to network or Setting up standalone PC Ethernet topic.

Connecting to Ethernet TAP probe setup utility





NOTEUse the help command at the core> prompt for a list of all theinternal Ethernet TAP probe commands available. Or use helpplus the command name for a brief description of the commandand a list of the command's arguments.

13.2 Ethernet TAP probe setup utility commands andvariables

The following is a list of all the Ethernet TAP probe internal setup utility commands.They are explained in greater detail, and grouped by functionality in the pages thatfollow.

Functionality Command Description

Configuration and OperationalCommands

netparam Sets non-volatile networking parameters.

tgtty Sets the target system serial portsettings.

floader Enables the flash loader program.

logout Exits the internal setup utility.

reset Reboots the Ethernet TAP probe.

who Displays open user connections.

Troubleshoot CommunicationsCommands

arp Displays the ARP table commands.

host Displays the host table commands.

netstat Displays network statistics.

ping Tests if host is connected to yournetwork.

route Sets dynamic network routing.

Utility Commands alias Manages aliases for commonly usedcommands.

batch Downloads and executes a commandfile.

history Displays command history list.

Advanced Troubleshooting Commands di Displays all the environment variables.

lsas Prints shell application assertions.

set Sets an environment variable.

unset Removes an environment variable.

Built-in Environment VariablesCommands

batchfile File containing commands to execute atboot.


Chapter 13 Ethernet TAP probe setup utility commands



Functionality Command Description

batchpath Default location to search for batch files.

env_protect Prevents changes to settings in flash.

username Defines a username which must beentered when logging in using telnet.

13.3 Commands to configure communicationsThe following internal setup utility commands are used to configure the Ethernet TAPprobe for network communications (netparam), and to communicate with your targetsystem's serial port (tgtty).

13.3.1 netparam

The netparam command displays or sets non-volatile networking parameters stored in theflash EPROM of Ethernet TAP probe. Entered without options, it displays all currentsettings. To change parameters, specify one or more options. To activate new settings, theunit must be rebooted.

13.3.1.1 Syntax

netparam [add_host host ip_address] [add_route host gateway hop_#] [bootconfig {static | dhcp }[:host]] [delete_host host ip_address] [delete_route host gateway] [rip_enable {yes | no}] [rip_method {broadcast | multicast}] [rip_version {1 | 2}] [static_ip_address address[:mask]]]

<null>

Reports the current configuration.

add_host host ip_address

Adds a hostname-address pair to the static host table. Table entries are automatically entered into the system on reset.

host Name to associate with the address ip_address.

ip_address IP address to use for host, specified in dotted-decimalnotation.


Commands to configure communications



add_routehostgatewayhop_#

Adds a route to Ethernet TAP probe static route table. Table entries are automatically entered into the system on reset. If thespecified parameters are invalid for the operating network, they are not stored.

host Destination IP address of host or host network, specified indotted-decimal notation. Default is a valid entry for host, andequivalent to 0.0.0.0.

gateway Gateway IP address for probe, specified in dotted-decimalnotation.

hop_# Decimal number of gateway hops between Ethernet TAPprobe and destination host or network.

bootconfig {static | dhcp }[:host]

Sets the IP address resolution protocol. It determines the boot method of Ethernet TAP probe. Use bootconfig to connectto the network either by DHCP or by storing the IP address in the flash EPROM of Ethernet TAP probe.

When using DHCP, you can specify the host name that you would like the probe to try to register with a name server when itacquires its network configuration.

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:00:f6:00:77:31,the default host name will be FSL007731.

static Use IP address stored in Ethernet TAP probe.

dhcp Use the network DHCP protocol to resolve IP address,netmask, and default gateway. (default)

:host Host name for the Ethernet TAP probe. If dhcp is specified,the probe will attempt to register this host name with theDHCP server. There should be no white space before :host.The efind search utility will report the host name of theprobe for both the dhcp and static options.

delete_host hostip_address

Deletes a hostname-address pair from the static host table.

host Name of host to remove.

ip_address IP address to remove, specified in dotted-decimal notation.

delete_route host gateway

Deletes a route from the static route table.

host Destination IP address of host or host network.

gateway Ethernet TAP probe gateway IP address, specified in dotted-decimal notation.

rip_enable {yes | no}

Enables or disables use of Routing Information Protocol (RIP) for automatic handling of network routing.

yes Enables using RIP.





no Disables use of RIP (default, unless previously enabled).

rip_method {broadcast | multicast}

Specifies the broadcast methods used by RIP on your network. (Default=broadcast)

rip_version {1 | 2}

Specifies which version of Routing Information Protocol is in use on your system. 1=RIP (default); 2=RIP2.

static_ip_address address[:mask]

Sets the Ethernet TAP probe IP address and optional netmask.

address IP address in dotted-decimal format (e.g., 128.8.1.1). Whenentering the IP address by itself (without also entering thenetmask), the Ethernet TAP probe uses the standard netmaskassigned to that IP address.

mask Netmask in hex format (e.g., FFFF0000) or dotted-decimalformat (e.g., 255.255.0.0). If subnetting is required, you muststore the netmask by entering it on the same command line,immediately following the IP address.

13.3.2 tgtty

The tgtty command configures the target system serial port settings.

13.3.2.1 Syntax

tgtty [default] [9600 | 19200 | 38400 | 57600 | 115200] [data8 | data5 | data6 | data7] [stop1 | stop2] [noparity|oddparity|evenparity|lowparity|highparity] [noxon | xon] [echo | noecho]

13.3.2.2 Options

Options can be combined in one statement. Entered without options the tgtty commanddisplays the current settings.

The target system serial port's default settings are:

Commands to configure communications



9600 data8 stop1 noparity noxon echo

Default Set the default target system serial settings

[9600 | 19200 | 38400 | 57600 | 115200] Choose a baud rate.

[data8 | data5 | data6 | data7] Specify data bits.

[stop1 | stop2] Specify stop bits.

[noparity | oddparity | evenparity |lowparity| highparity]

Define parity.

[noxon | xon] Enable or disable XON/XOFF flow control.

[echo | noecho] Enable or disable target system echo feature.

13.4 Operational commandsThe following commands are used to control access to the internal setup utility, to resetthe Ethernet TAP probe, to stop, rather than reset the target system after connection, andto prepare the serial port to receive a new core image.

13.4.1 floader

Use the floader command when you need to reprogram the core software stored in theflash EPROM of the Ethernet TAP probe through the serial port. This command preparesthe serial port for host floader initiation. When the load is complete, this commandreturns control to the shell and a new prompt is displayed. Do not use this commandwhen reprogramming over the network.

13.4.1.1 Syntax

floader

13.4.2 logout

Use the logout command to abort your telnet connection. Note that this command is notavailable from the serial console.




13.4.2.1 Syntax

logout

13.4.3 reset

The reset command reboots the device. Note that when you reset the Ethernet TAP probefrom a telnet session, you will lose your telnet connection to the internal setup utility.When this happens, simply open another terminal and reconnect after the Ethernet TAPprobe has booted up.

13.4.3.1 Syntax

reset

13.4.4 who

Determines if the Ethernet TAP probe is in use, and identifies who is using it.

13.4.4.1 Syntax

who

13.5 Commands to troubleshoot communicationsThe following commands are used to troubleshoot problems connecting to your network.The procedures for troubleshooting communications are covered in Troubleshooting.

Commands to troubleshoot communications



13.5.1 arp

Use the arp command to edit the arp table by assigning hostnames to specific Ethernetaddresses. Without options it displays the current arp table.

13.5.1.1 Syntax

arp [add hostname ethernet_address | delete hostname]

13.5.1.2 Options

add hostnameethernet_address Assign a hostname alias to an Ethernet address in the arptable.

delete hostname Delete a hostname alias from the arp table.

13.5.2 host

Use the host command to edit the host table by assigning hostnames to specific IP addresseswithout permanently storing the routing tables in the flash EPROM of the Ethernet TAPprobe. Without options it displays the current host table.

13.5.2.1 Syntax

host [add hostname ip_address | delete hostname ip_address]

13.5.2.2 Options

add hostnameip_address Assign a hostname alias to an IP address in the host table.

delete hostnameip_address Delete a hostname alias from the host table.




13.5.3 netstat

Entered without options the netstat command displays all the network statistics. Use witharguments to reduce the amount of data displayed.

13.5.3.1 Syntax

netstat [inet|eth|icmp|ip|tcp|udp|arp|route|host|mem]

13.5.3.2 Options

inet Display network connections.

eth Display Ethernet device status.

icmp Display ICMP protocol statistics.

ip Display IP protocol statistics.

tcp Display TCP protocol statistics.

udp Display UDP protocol statistics.

arp Display ARP table.

route Display route table.

host Display host table.

mem Display network memory statistics.

13.5.4 ping

Use the ping command to verify that the Ethernet TAP probe is connected to yournetwork.

13.5.4.1 Syntax

ping [hostname | ip_address] [size] [cnt]

Commands to troubleshoot communications



13.5.4.2 Options

hostname Use the hostname stored in Ethernet TAP probe host table(see the host command).

ip_address Use the IP address of the host you are trying to reach.

size The size, in bytes, to use for request packets.

cnt The number of packets to send.

13.5.5 route

Use the route command to test network routing without permanently storing the routingtables in the Ethernet TAP probe flash EPROM. Without options it displays the currentroute table or default gateway.

13.5.5.1 Syntax

route [add destination gateway | delete destination gateway]

13.5.5.2 Options

add destinationgateway Add a dynamic route to the route table.

delete destinationgateway Delete a dynamic route from the route table.

13.6 Utility commandsThis section describes utility commands.

13.6.1 alias

The alias command manages aliases for commonly used commands. When called withno parameters, it displays the currently set aliases. When called with the -d flag, it deletesthe specified alias. When called with a name and a string, it creates a new alias.




13.6.1.1 Syntax

alias [-d alias_name] | [alias_name [alias_string]]

13.6.1.2 Options

-d alias_name Delete the specified alias.

alias_name Set the specified alias to be alias_name.

alias_string Set alias_name to alias_string.

13.6.2 batch

The batch command downloads and executes a command file. If no parameters are given,the batch command will use the file specified by the batchpath and/or batchfileenvironment variables. If a file name is given, the batch command will look for this file inthe location specified by the batchpath environment variable. If a fully-qualified ftp or tftpURL is given, the batch command will use this file. File URLs can take the followingforms:

tftp://server[:port]/path/file

ftp://[username[:password]@]server/path/file

13.6.2.1 Syntax

batch [file_or_url]

Utility commands



13.6.2.2 Options

file_or_url Run the specifed file.

13.6.2.3 Examples

batch (requires batchfile and/or batchpath to be set)

batch setup.nrsh (requires batchpath to be set)

batch tftp://128.9.1.2/home/joe/setup.nrsh

batch ftp://128.9.1.2/pub/setup.nrsh

batch ftp://joe:[email protected]/home/joe/setup.nrsh

13.6.3 history

The history com mand displays the contents of the history substitution buffer for thecurrent command session.

13.6.3.1 Syntax

history

Use the following combinations to use the history buffer contents to repeat or alter acommand:

Enter To substitute entry with the:

!! Most recent history entry.

!srch_str Most recent history entry starting with srch_str.

!?srch_str Most recent history entry containing with srch_str.

!-n nth preceding entry in history buffer.

!n nth entry in history buffer.

^srch_str^subst_str Most recent history entry starting with srch_str, replacingsrch_str with subst_str.

^?srch_str^subst_str Most recent history entry containing srch_str, replacingsrch_str with subst_str.




13.7 Commands for advanced troubleshootingThe following commands provide additional troubleshooting methods for moreexperienced Ethernet TAP probe users. It is recommended that these commands only beused with assistance from Customer Support.

NOTEDo not confuse these commands with similar UNIX commands.They are internal Ethernet TAP probe utilities.

13.7.1 di

The di command displays all environment variables and their corresponding values. Ifspecified, the value of key is displayed. If no key is specified, all variables are displayed.

13.7.1.1 Syntax

di [ key ]

13.7.2 lsas

The lsas command prints a list of application assertions that have occurred since the lastreset.

13.7.2.1 Syntax

lsas

Commands for advanced troubleshooting



13.7.3 set

The set command sets an environment variable to the value specified. If the specifiedvariable does not exist, it is created. If the variable already exists, then it is modified.

13.7.3.1 Syntax

set key=value

13.7.3.2 Options

key Assign a name to the environment variable.

value Assign a value to the environment variable.

13.7.4 unset

The unset command destroys either the named environment variable or destroys allvariables. Note that some built-in environment variables cannot be destroyed, but will bereset to their default values.

13.7.4.1 Syntax

unset [-a | key]

13.7.4.2 Options

-a Destroy all the environment variables.

key Destroy the named environment variable.




13.8 Built-in environment variablesThe built-in environment variables listed below are used with the set, unset, and dicommands.

13.8.1 batchfile

Set the batchfile environment variable to the name of a command file to execute at boot.The value should be the name of a file that can be found in the path specified bybatchpath, or a fully-qualified ftp or tftp URL. File URLs can take the following forms:

tftp://server[:port]/path/file

ftp://[username[:password]@]server/path/file

13.8.1.1 Syntax

set batchfile=file_name

13.8.1.2 Examples

set batchfile=setup.nrsh (requires batchpath to be set)

set batchfile=tftp://128.9.1.2/home/joe/setup.nrsh

set batchfile=ftp://128.9.1.2/pub/setup.nrsh

set batchfile=ftp://joe:[email protected]/home/joe/setup.nrsh

13.8.2 batchpath

Set the batchpath environment variable to a default path to use for batch files. The valueshould be an ftp or tftp URL pointing to a directory containing command files. DirectoryURLs can take the following forms:

tftp://server[:port]/path/

Built-in environment variables



ftp://[username[:password]@]server/path/

13.8.2.1 Syntax

set batchpath=path

13.8.2.2 Examples

set batchpath=tftp://128.9.1.2/home/joe/

set batchpath=ftp://128.9.1.2/pub/

set batchpath=ftp://joe:[email protected]/home/joe/

13.8.3 env_protect

Set the env_protect environment variable to prevent changes to settings in flash. When setto on, settings can be changed, but they will not be stored to flash. The changes will belost when the Ethernet TAP probe is reset. Set to on to preserve current settings in flash.When set to off, changes will be stored to flash and will persist when the Ethernet TAPprobe is reset.

13.8.3.1 Syntax

set env_protect=[on|off]

13.8.4 username

Set the username environment variable to a user name which must be entered when loggingin via telnet.




13.8.4.1 Syntax

set username=name

Built-in environment variables



Chapter 14Network administrationThis chapter is a guide to assist network administrators in installing an Ethernet TAPprobe. The Ethernet TAP probe is an Ethernet host device that may be configured forTCP/IP using DHCP to acquire its IP configuration (the default method) or through astatic IP configuration.


• TCP/IP networks• Ethernet TAP probe network ports• Configuring Ethernet TAP probe using netparam• Using efind to discover Ethernet TAP probes

14.1 TCP/IP networksThis section provides an overview of the TCP/IP networks.

14.1.1 TCP/IP addressing and protocols

A TCP/IP network requires an Ethernet device be assigned an IP address to identify it asa host on the network. Typically, a host name and routing information are also required.

Larger TCP/IP networks include dedicated servers to provide IP addressing and packetrouting protocols, while smaller networks may configure these functions on every host onthe network.

The Ethernet TAP probe is an Ethernet device that is configured by DHCP (default) or byusing the built-in commands to set a static network configuration for your particularnetwork environment.



14.1.1.1 To install Ethernet TAP probe on TCP/IP network

The Ethernet TAP probe's default operation is to use the DHCP protocol to automaticallyacquire its network configuration. If necessary, you can change its network configurationby doing the following.

1. Configure the Ethernet TAP probe using the onboard configuration utility netparam(see Connecting to network and netparam).

2. Add an entry for the Ethernet TAP probe to the name servers on your network.

14.1.1.2 Addressing Ethernet TAP probe

Each Ethernet TAP probe has a unique Ethernet address in the form 00:00:F6:D0:B6:48. TheEthernet address of your probe is printed on a label on its underside.

To act as a host on a TCP/IP network, an Ethernet device must also have a unique IPaddress (e.g., 10.189.85.42) and, for convenience, a host name (e.g., testdev1).

The Ethernet TAP probe acts as a host on a TCP/IP network, as does each workstationthat accesses it using a debugger.

An Ethernet packet may be sent to a host using either the host IP address, or the hostname, or the host Ethernet address. A packet bearing a host IP address is deliveredautomatically, but a host name or host Ethernet address must be resolved to thecorresponding host IP address before the packet can be delivered.

14.1.1.3 IP configuration

A host such as an Ethernet TAP probe is uniquely identified on a TCP/IP network by thefollowing address information:

• An IP address (in the form 10.189.85.42).• A subnet mask that defines how the IP address is to be read.

A subnet mask of 255.255.255.0 applied to the IP address above defines host number42 on the 10.189.85 subnetwork.

• An address, known as a gateway, of the default routing device the host will use toforward packets on to the network. This is not a required entry if no routers are used.

14.1.1.4 Name servers

TCP/IP networks



Name resolution is the process of resolving a host name to its IP address. In largernetworks, this is accomplished by a Name Server, typically using the DNS protocol.Some older Windows installations (NT4 and earlier) may use Windows Internet NameService (WINS).

If you configure your Ethernet TAP probe with a static IP address, an entry must be madein your DNS and/or WINS database file designating the host name and IP address of theEthernet TAP probe.

In network environments that assign network parameters via DHCP, there may be anautomated link between the DHCP server and the DNS server such that the DNS serverautomatically receives an update with the Ethernet TAP probe's host name. This readilyworks where both the Windows DHCP server and Windows DNS server are used. It maybe made to work in UNIX environments as well, using a protocol known as DynamicDomain Name Service (DDNS); see your UNIX reference documentation for moreinformation.

For smaller networks, each workstation does its own name resolution through a simpletext file. In UNIX environments the file is known as /etc/hosts. In Windowsenvironments the file is known as hosts and is typically found in the %system_root%\system32\drivers\etc\ directory.

14.1.2 Windows name servers

Windows 7 offer several networking services, most of them using DNS to provide anaming service. If your network uses a Windows DNS or WINS server, you can accessthe Ethernet TAP probe by its host name by one of two methods:

• If you are using the Windows DHCP server, the Windows DNS or WINS server willbe automatically updated with the host name of the Ethernet TAP probe.

• If you are not using the Windows DHCP server, you must manually update theWindows DNS or WINS server, either through its GUI or by modifying the localhosts file on the Windows DNS or WINS server with the host name and IP address ofthe Ethernet TAP probe.

You can also make the Ethernet TAP probe available to selected local workstations byupdating the hosts file on each workstation that needs access to the Ethernet TAP probe.

• Windows hosts files are located in the %system_root%\system32

\ drivers\etc\ directory.

Chapter 14 Network administration



14.1.2.1 To update Windows hosts file1. Have your network administrator assign an unused IP address and hostname to each

Ethernet TAP probe.2. Enter each name/address pair into the hosts database file. For example:

128.9.230.61 elvis # Ethernet TAP 1

128.9.230.62 hayduke # Ethernet TAP 2

After doing the above steps, you can update the Windows host file.

14.1.3 Routing without RIP or RIP2

RIP and RIP2 are common routing protocols supported by the Ethernet TAP probe. Ifyour network server does not use RIP or RIP2, the Ethernet TAP probe can stillcommunicate across routers and bridges if a default gateway is acquired as part of theDHCP process or entered in the probe memory. For instructions, see Selecting dynamicor Static routing.

14.2 Ethernet TAP probe network portsSoftware uses several network ports to communicate with an Ethernet TAP. In casewhere the Ethernet TAP and host software are on the same network, you do not need tobe aware of these ports. However, in case where an Ethernet TAP is located in aprotected network, an administrator will need to provide access to these ports if you needto connect to the Ethernet TAP from another network. The table below list the ports usedby the Ethernet TAP and a brief description of each port.

Table 14-1. Ethernet TAP network ports

Port Number Description

23 Telnet access to configuration console

1080 Used by CodeWarrior to initialize the Ethernet TAP

1081 Used for firmware updates

1082 Telnet access to target serial port

41474 Used by CodeWarrior to control the Ethernet TAP

53099 Used by CodeWarrior to check Ethernet TAP status

Ethernet TAP probe network ports



14.3 Configuring Ethernet TAP probe using netparamUse the netparam command to select the network parameters:

• Address resolution protocol• Dynamic routing method• Static address resolution data• Static routing tables

CAUTIONnetparam writes its settings into non-volatile flash memoryon the Ethernet TAP probe. Each time you enter a netparamcommand, wait for the core> prompt to re-appear beforeentering the next command. The prompt indicates that thewrite is complete.

14.3.1 Configuring dynamic IP address

This section describes configuring a dynamic IP adress.

14.3.1.1 To configure dynamic IP address1. Connect to the Ethernet TAP probe internal setup utility, for more information, see

Connecting to Ethernet TAP Probe Setup Utility topic.2. At the core> prompt, use netparam to specify the protocol appropriate to your network:

netparam bootconfig dhcp[:hostname]

DHCP is the default setting. If you specify a hostname for the Ethernet TAP probe, theprobe will attempt to register the host name with the DHCP server, which may thenupdate any name servers on the network.

14.3.2 Configuring static IP address

If you do not have a DHCP server on your network or you prefer to manually configureyour network settings, the Ethernet TAP probe is capable of storing its IP address andnetmask in flash memory. When bootconfig is set to static, the Ethernet TAP probe usesthis stored information to resolve its own IP and netmask requests.




NOTEBecause this is a simple, proven way to add an Ethernet TAPprobe to any TCP/IP network, we strongly recommend using itif you have any network communications problems.

14.3.2.1 To enter IP and optional netmask in flash1. Have your network administrator assign an unused IP (Internet Protocol) address and

host name to the probe.2. Enter the name/address pair into the hosts database file. Windows hosts files are

typically located in the %system_root%\system32\drivers\etc\ directory.

The following is an example of probe entries in a hosts file:

NOTEYou should create or update the hosts file on the networkserver or on each local workstation that needs access to theprobe.

3. At the core> prompt, use netparam to set and store the IP address and netmask(subnetting only) in the Ethernet TAP probe flash EPROM.

netparam static_ip_address nnn.nnn.nnn.nnn [:ssssssss]

where nnn.nnn.nnn.nnn represents the IP address and ssssssss represents the hexadecimalsubnetting mask.

NOTEWhen specifying a netmask for subnetting, use 1's to mask thenetwork portion and 0's for the host portion (e.g., 255.255.0.0becomes 0xFFFF0000). You must enter a colon between IPaddress and netmask.

For example:

nnn.nnn.nnn.nnn:Oxnnnnnnnn

Configuring Ethernet TAP probe using netparam



14.3.3 Selecting dynamic or static routing

All but the simplest networks consist of one or more subnets. Routers forward networktraffic from one point on the network to another across these subnets. If the Ethernet TAPprobe uses DHCP to automatically acquire its network settings, it is most likely that adefault gateway setting was acquired and the probe will be accessible on other subnets.However, when using a static IP configuration or where the DHCP configuration isincomplete, you may have to provide additional routing information, including:

• Select RIP or RIP2 dynamic routing support• Store a default gateway in flash memory• Load static routing tables into flash memory

14.3.3.1 To enable dynamic or static routing

At the core> prompt, use netparam arguments to specify routing configuration:

netparam rip_enable {yes|no}

• yes - select if your network uses RIP or RIP2 to route traffic, OSPF (gated) is notsupported. Then select rip_version and rip_method.

• no - select if your network does not use RIP or RIP2 to route traffic or if you plan tostore a default gateway address or full route tables in the Ethernet TAP probe flash.

netparam rip_version {1|2}

• 1 - select if your network uses RIP to route traffic.• 2 - select if your network uses RIP2 to route traffic.

netparam rip_method {broadcast|multicast}

• broadcast - select if RIP or RIP2 uses the broadcast method to send messages to eachclient (default).

• multicast - select if RIP or RIP2 uses the multicast method to send messages toclients.




14.3.3.2 Specify default gateway or static route table (optional)

Even if your network does not use RIP or RIP2 dynamic routing, the Ethernet TAP probecan still communicate across routers and gateways if you enter a default gateway or a fullrouting table into flash memory.

If you are using a static IP configuration or your DHCP configuration does not specify adefault gateway, you can manually enter the IP address of the default gateway to use.This gateway must be accessible on your local subnet.

14.3.3.2.1 To specify default gateway

A default gateway entry must specify the IP address of the first gateway that the networktraffic from probe crosses. This gateway must be aware of the network's complete routetable. Use the following netparam syntax:

netparam add_route 0.0.0.0 gateway_ip 1

For gateway_ip, provide the IP address of the router or gateway in dot notation. The defaultvalue is 0.0.0.0.

14.3.4 Changing existing route entry

NOTEWhen entered in the Ethernet TAP probe, static routes are notupdated automatically. You must update these routes if changesin network topology affect the static routes.

Before entering static routes, make a map of all gateway paths between the Ethernet TAPprobe, as starting point, and each workstation that must have access to it.

14.3.4.1 To change existing routing entry1. At the core> prompt, delete the existing routing entry:

netparam delete_route host_ip gateway_ip

2. Enter the new route as described above:

netparam add_route host_ip gateway_ip hop_#

NOTEhost_ip can identify an individual workstation or a networkserving multiple hosts. The gateway_ip is the first gatewaythe probe traffic crosses when communicating with thedestination workstation. The hop_# is the decimal number of

Configuring Ethernet TAP probe using netparam



gateways between the probe and the destinationworkstation. For an example of static routing, see the nextsection.

14.3.5 Entering static routes

NOTEWhen entered in the Ethernet TAP probe, static routes are notupdated automatically. You must update these routes if changesin network topology affect the static routes.

Before entering static routes, make a map of all gateway paths between the Ethernet TAPprobe, as starting point, and each workstation that must have access to it.

14.3.5.1 To enter static route or default gateway1. At the core> prompt, use the netparam command to enter the first host/gateway pair:

netparam add_route host_ip gateway_ip hop_#

Wait for the core> prompt between each netparam entry.

NOTEhost_ip can identify an individual host or a network servingmultiple hosts. The gateway_ip is the first gateway theEthernet TAP probe crosses when communicating with thedestination host. The hop_# is the decimal number ofgateways between the Ethernet TAP probe and thedestination host. For more information on the netparamcommand, see Ethernet TAP probe setup utility commandstopic.

2. Add routes until all destination hosts or networks are defined.

When the core> prompt returns, reset the Ethernet TAP probe by cycling power, or byentering the reset command.

14.3.5.2 Static route example

Figure below shows three class "C" networks joined together by a single IP router,making each Ethernet TAP probe accessible from three workstations (elmer, tweety, andbrutus).




No static routing information is required to make an Ethernet TAP probe accessible froma workstation local to it on a network. For example, the Ethernet TAP probe goofy onnetwork 198.9.230.0 communicates directly with workstation elmer.

When static routing is used, a routing entry is required on an Ethernet TAP probe foreach workstation on a non-local network that accesses it. The Ethernet TAP probe goofyrequires two entries, for workstation tweety on network 198.9.231.0 and workstationbrutus on network 198.9.232.0.

Each static route entry is made using a netparam command and consists of a networkaddress and a host address. The netparam commands for the static route entries forEthernet TAP probe goofy are:

netparam add_route 198.9.231.0 198.9.230.1 1

netparam add_route 198.9.232.0 198.9.230.1 1

Figure 14-1. Three Class C networks connected by a single router

Each of the three Ethernet TAP probe hosts must have a static route entry for each remoteworkstation that accesses it.

Using efind to discover Ethernet TAP probes



14.4 Using efind to discover Ethernet TAP probesefind is a command line utility which searches for all the CodeWarrior probes on the localsubnet of each network interface of the host and lists the probes' IP addresses, as well asother information. It uses UDP broadcast packets to discover the devices. Broadcastpackets are typically limited to the local subnet and typically are not routed or passedthrough VPNs.

If your Ethernet TAP probe acquires its IP address using DHCP, but is not able to registerits host name on the network, you will need the probe's IP address. If you need to start atelnet session, you may need the probe's IP address.

The utility is provided in the following locations:

Microsoft Windows

codewarrior_installdir \ccs\bin\efind.exe

Linux/Solaris

codewarrior_installdir /ccs/bin/efind

The efind utility takes no arguments.

14.4.1 Sample output$ efindEthernet TAP and DCU search utilityFreescale Semiconductor Inc.(C) Copyright 2014, All rights reserved.Version 1.0

checking network 192.168.0.255type=EthernetTAP, probe=ONCE, name=FSL000001, ip=192.168.0.2type=EthernetTAP, probe=COP, name=etap4, ip=192.168.0.115type=DCU, probe=unknown_0x0012, name=dcu1, ip=192.168.0.107total of 3 devices found$




Using efind to discover Ethernet TAP probes



Chapter 15Ethernet TAP probe firmware (core)This chapter explains the methods for reprogramming the core image stored in the flashEPROM of the Ethernet TAP probe. Before reprogramming the flash EPROM, make sureyou have already properly configured the Ethernet TAP probe network communications.


• Ethernet TAP probe internal software overview• Reprogramming Ethernet TAP probe firmware image• What to do next

15.1 Ethernet TAP probe internal software overviewThis section provides an overview of the Ethernet TAP Probe internal software.

15.1.1 Core software

The Ethernet TAP probe core image provides tools for configuring and testing networkcommunications, for re-loading the probe core software, and the underlying softwareframework required to work with the debugger.

When the Ethernet TAP probe first powers up it loads the core software. This is indicatedby the core> prompt in the Ethernet TAP probe's setup utility. To reprogram the coreimage stored in the Ethernet TAP probe flash EPROM, seeReprogramming Ethernet TAPprobe firmware image topic.



15.1.2 Shell software

The Ethernet TAP probe shell software is basically transparent to the user, and is simplythe application that tells the probe how to control the target system. It recognizes thespecific target system processor and debug port interface, and carries out the instructionsof the debugger.

15.1.3 Determine current core version (optional)

To determine the current level of the Ethernet TAP probe core software, you can use thefollowing procedure.

15.1.3.1 To check core version1. Connect to the internal setup utility of the Ethernet TAP probe, see Connecting to

Ethernet TAP probe setup utility topic.2. When the sign-on screen appears, compare the core firmware version displayed with

the version required by the latest release of your debugger. If an update is required,continue with the remainder of the procedures in this appendix.

This is how you can check the core version.

15.2 Reprogramming Ethernet TAP probe firmware imageAt some point you may be required to reprogram the Ethernet TAP probe firmware imagestored in its flash EPROM. Typically this occurs when you are installing an update toexisting software, and the release letter specifies a later version of probe core software.The firmware is distributed in a single core image ( code.ldr).

Before proceeding, you must decide which of the Ethernet TAP probe communicationports to use for reprogramming the core image.

• Using the Ethernet port (see Reprogramming firmware through the Ethernet port)

This is the preferred method to use if your Ethernet TAP probe is already connectedto your Ethernet or stand-alone network.

• Using the serial port (see Reprogramming firmware through the serial port)

The serial port method is much slower and requires more setup steps, and thereforeshould be used only when you need to reprogram the core image on an Ethernet TAPprobe that is not connected to your network.

Reprogramming Ethernet TAP probe firmware image



A flash file loader (UPDATEETAP) utility is included with the debugger software.UPDATEETAP provides the ability to reprogram the Ethernet TAP probe core imagestored in its flash EPROM.

15.2.1 Reprogramming firmware through Ethernet port

In order to use the following instructions, the Ethernet TAP probe communications mustalready be configured (see Connecting to network or Setting up standalone PC Ethernettopic.)

15.2.1.1 To reprogram the firmware image1. Launch CCS and open the CCS command window. The procedure is slightly

different on Windows and Linux/Solaris host machines.• For Windows, run the command:

CodeWarrior_Installation\ccs\bin\ccs.exe

This will launch CCS and add a CCS icon to your taskbar. Double-click that iconin the taskbar to open the command window.

• For Linux/Solaris, run the command:

CodeWarrior_Installation/ccs/bin/ccs

This will launch CCS and open the command window automatically.

Figure 15-1. CCS icon• In the CCS Command window, enter the command:

updateetap -hostname {hostname | ip_address} -boot

NOTEThe -boot option ensures the proper initialization of theEthernet TAP probe with the new core image andguarantees a correct shell download.

2. As it executes, UPDATEETAP reports its progress. When the process is complete,UPDATEETAP reports:

Load complete.

Chapter 15 Ethernet TAP probe firmware (core)



CAUTIONDo nothing to disrupt operation while running theUPDATEETAP command. Power failures, network disruptions,and Ethernet TAP probe resets can create a non-workingstate that may require factory repair.

These procedures must be performed on each Ethernet TAP probe that you plan to usewith the current version of debugger.

15.2.2 Reprogramming firmware through serial port

Use the serial port instructions only when you need to reprogram the firmware image onan Ethernet TAP probe that is not connected to your Ethernet or a stand-alone network. Ifthe Ethernet TAP probe is connected to your network, it is recommended that you use thesimpler Ethernet instructions, as discussed in Reprogramming firmware through Ethernetport.

Before starting UPDATEETAP, you must first configure the Ethernet TAP probe to receive thenew image through its serial port.

15.2.2.1 To configure Ethernet TAP probe for FLOADER1. Connect to the Ethernet TAP probe internal setup utility using the serial port, see

Connecting Ethernet TAP probe to network topic.2. When the core> prompt appears on the terminal, enter the Ethernet TAP probe

internal FLOADER command:

floader

Entering FLOADER at the core> prompt prepares the Ethernet TAP probe to receive thenew core image through the serial port, but does not actually load the new coreimage.

Quit your terminal connection (after being prompted to do so), as the terminal you usedto connect to the internal setup utility is unavailable during the FLOADER operation.

15.2.2.2 To reprogram core firmware image1. Launch CCS and open the CCS command window. The procedure is slightly

different on Windows and Linux/Solaris host machines.

Reprogramming Ethernet TAP probe firmware image



• For Windows, run the command:

CodeWarrior_Installation\ccs\bin\ccs.exe

This will launch CCS and add a CCS icon to your taskbar. Double-click that iconin the taskbar to open the command window.

• For Linux/Solaris, run the command:

CodeWarrior_Installation/ccs/bin/ccs

This will launch CCS and open the command window automatically.

2. In the CCS Command window, enter the command:

updateetap -serial -p port [-r rate] -boot

The port should be the one to which the serial cable is connected. A rate value isneeded only in a noisy environment where UPDATEETAP's default 38400 baud will beunreliable.

CAUTIONResetting the Ethernet TAP probe ensures the properinitialization of the Ethernet TAP probe with the new coreimage, and also guarantees a correct shell download.

3. As it executes, UPDATEETAP reports its progress. When the process is complete,UPDATEETAP reports:

Load complete.

CAUTIONDo nothing to disrupt operation while running theUPDATEETAP utility. Power failures, network disruptions, andEthernet TAP probe resets can create a non-working statethat may require factory repair.

NOTEThese procedures must be performed on each Ethernet TAPprobe that you plan to use with the current version of thedebugger.

15.3 What to do nextWhen you have completed reprogramming the firmware images stored in the EthernetTAP probe flash EPROM, configure your debugging environment (if you haven't alreadydone so) as explained in the debugger manual.

Chapter 15 Ethernet TAP probe firmware (core)



What to do next



Chapter 16TroubleshootingThis chapter provides Ethernet TAP probe troubleshooting information.


• Troubleshooting communications problems• Basic troubleshooting• Dynamic troubleshooting• Advanced troubleshooting• Troubleshooting power problems

16.1 Troubleshooting communications problemsThis section explains how to troubleshoot communications problems between thedebugger and the Ethernet TAP probe.

If the debugger is unable to communicate with the Ethernet TAP probe:

• Check the cable and connections between the network cable and the Ethernet TAPprobe.

The Ethernet TAP probe connects directly to networks that use twisted pair(10/100BaseT) cables.

• Make sure communication was configured correctly for your network.• Make sure the Ethernet TAP probe is receiving power.

See Ethernet TAP probe status indicators topic for a description of the status LEDs.For more information on connecting the Ethernet TAP probe to the external powersupply, see Connecting external power supply topic.

• Make sure the Ethernet TAP probe is running the core software.



See Ethernet TAP probe status indicators topic for a description of the status LEDs.For more information on loading the core software, see Ethernet TAP probefirmware (core) topic.

• Use the communications troubleshooting utilities of Ethernet TAP probe to verifythat it is recognized on your network, or to help diagnose problems connecting toyour network.

To troubleshoot communications, see Basic troubleshooting topic.

To list all the CodeWarrior probes on your local subnets, use the efind host utility.See Using efind to discover Ethernet TAP probes topic.

• Make sure the debugger is set up correctly for Ethernet communications with theEthernet TAP probe.

If all the settings are correct and the debugger cannot communicate to the Ethernet TAPprobe, contact Customer Support for assistance.

16.2 Basic troubleshootingThis section explains how to use the basic troubleshooting utilities that Ethernet TAPprobe provides. These utilities help you diagnose communications problems.

• Using ping command• Using netstat command

16.2.1 Using ping command

Use the ping command at the core> prompt to verify that the Ethernet TAP probe is up andrunning on your network.

16.2.1.1 To verify network communications1. Connect to the Ethernet TAP probe internal setup utility, as explained in Connecting

to the Ethernet TAP Probe Setup Utility.2. Verify communications by entering this command at the core> prompt:

ping ipaddress | hostname

For example, to ping the Ethernet TAP probe elvis at IP address 128.9.230.61, enterthe command as follows:

Basic troubleshooting



ping 128.9.230.61

- or -

ping elvis

NOTEWhen first establishing communications, you will have toping the IP address you used during the setup process, asthe Ethernet TAP probe does not automatically recognizethe hostname. To ping a hostname, the Ethernet TAP probeinternal host table must first be updated. For moreinformation on updating the Ethernet TAP probe internalhost table see Using the host Command topic.

16.2.2 Using netstat command

The netstat command displays all the network statistics when entered without options.

16.2.2.1 To run netstat command1. Connect to the internal setup utility of Ethernet TAP probe.2. At the core> prompt, enter the netstat by using this syntax:

netstat [eth|icmp|ip|tcp|udp|inet|arp|route|host|mem]

Select the desired options to reduce the amount of data displayed. Table below shows thedescriptions of the netstat options.

Table 16-1. Netstat options

Option Description

eth Displays Ethernet device status.

icmp Displays ICMP protocol statistics.

ip Displays IP protocol statistics.

tcp Displays TCP protocol statistics.

udp Displays UDP protocol statistics.

inet Displays network connections.

arp Displays ARP table.

route Displays route table.

host Displays host table.

mem Displays network memory statistics.

Chapter 16 Troubleshooting



16.3 Dynamic troubleshootingThe Ethernet TAP probe provides troubleshooting utilities that let you testcommunications dynamically, without making any permanent changes to the flashEPROM of the Ethernet TAP probe. Any settings will be lost after the Ethernet TAPprobe is reset.

• Using host command• Using route command• Using arp command

16.3.1 Using host command

Use the host command to edit the host table by assigning hostnames to specific IPaddresses without permanently storing the changes in the Ethernet TAP probe flashEPROM. When entered without options, the host command displays the current hosttable. See netparam (netparamadd_host) to permanently store an address in flash.

16.3.1.1 To add a hostname to the host table1. Connect to the internal setup utility of Ethernet TAP probe, for more information, see

Connecting to Ethernet TAP probe setup utility topic.2. At the core> prompt, enter the host command by using this syntax:

host add hostname

ip_address

The system adds the specified hostname to the host table.

16.3.1.2 To remove hostname from host table1. Connect to the internal setup utility of Ethernet TAP probe.2. At the core> prompt, enter the host command by using this syntax:

host delete hostname

ip_address

Dynamic troubleshooting



The system removes the specified hostname from the host table.

Hostnames are also cleared from the host table after the Ethernet TAP probe is reset.

16.3.2 Using route command

Use the route command to test network routing without permanently storing the routingtables in the Ethernet TAP probe flash EPROM. Without options, the route commanddisplays the current route table. See Entering static routes topic.

16.3.2.1 To add route to route table1. Connect to the internal setup utility of Ethernet TAP probe, for more information, see

Connecting to Ethernet TAP probe setup utility topic.2. At the core> prompt, enter the destination command by using this syntax:

route add destinationgateway

where destination is the IP address of the host or host network, and gateway is the IPaddress of the first gateway the Ethernet TAP probe crosses when communicatingwith the destination host.

16.3.2.2 To remove route from route table1. Connect to the internal setup utility of Ethernet TAP probe, for more information, see

Connecting to Ethernet TAP probe setup utility topic.2. At the core> prompt, enter the destination command by using this syntax:

route delete destinationgateway

Routes are also cleared from the route table after the Ethernet TAP probe is reset.

16.3.3 Using arp command

The arp command allows you to edit the arp table by assigning hostnames to specificEthernet addresses. Without options it displays the current arp table.




16.3.3.1 To add hostname to arp table1. Connect to the internal setup utility of Ethernet TAP probe, for more information, see

Connecting to Ethernet TAP probe setup utility topic.2. At the core> prompt, enter the arp command by using this syntax:

arp add hostname

ethernet_address

16.3.3.2 To remove hostname from arp table1. Connect to the internal setup utility of Ethernet TAP probe.2. At the core> prompt, enter the arp command by using this syntax:

arp delete hostname ethernet_address

Hostnames are also cleared from the arp table after the Ethernet TAP probe is reset.

16.4 Advanced troubleshootingFor additional troubleshooting utilities (for advanced Ethernet TAP probe users only), seeCommands for advanced troubleshooting topic. It is recommended that the advancedtroubleshooting commands only be used with assistance from Customer Support.

16.4.1 Ethernet TAP probe status indicators

The Ethernet TAP probe uses LEDs to indicate its status. If you are troubleshootingEthernet communications problems, the information in table below may help.

Table 16-2. Ethernet TAP probe status indicators

LED Location Activity Description

TGT PWR Top Off Debugger is not connected toEthernet TAP probe. - or -Debugger is connected toEthernet TAP probe andtarget system power is notdetected.


Advanced troubleshooting



Table 16-2. Ethernet TAP probe status indicators (continued)

LED Location Activity Description

Solid green Debugger is connected toEthernet TAP probe andtarget system power isdetected.

HEARTBEAT Top Off Ethernet TAP probe is notpowered on.

Solid red Ethernet TAP probe failed toboot.

Orange heartbeat Ethernet TAP probe bootprogram running and networkinterface is initializing.

Green heartbeat Ethernet TAP probe bootprogram running and networkinterface successfullyconfigured.

Red heartbeat If DHCP is enabled, EthernetTAP probe failed to acquire itsnetwork configuration.

RUN/PAUSE Top Off Debugger is not connected toEthernet TAP probe.

Solid red Ethernet TAP probe is inpause mode.

Solid green Ethernet TAP probe is in runmode.

Solid orange Ethernet TAP probe in mixedmode.

RX ETH Ethernet Connector Off Ethernet is not receiving.

Green heartbeat Ethernet is receiving.

TX ETH Ethernet Connector Off Ethernet is not transmitting.

Orange heartbeat Ethernet is transmitting.

16.5 Troubleshooting power problemsIf the Ethernet TAP probe behaves erratically, check the connections to the externalpower supply.

The LED labeled HEARTBEAT indicates whether the Ethernet TAP probe is receivingpower. If this LED is not lit, check the connections to the external power supply.




Troubleshooting power problems



How to Reach Us:

Home Page:freescale.com

Web Support:freescale.com/support

Information in this document is provided solely to enable system andsoftware implementers to use Freescale products. There are no expressor implied copyright licenses granted hereunder to design or fabricateany integrated circuits based on the information in this document.Freescale reserves the right to make changes without further notice toany products herein.

Freescale makes no warranty, representation, or guarantee regardingthe suitability of its products for any particular purpose, nor doesFreescale assume any liability arising out of the application or use ofany 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 data sheetsand/or specifications can and do vary in different applications, andactual performance may vary over time. All operating parameters,including “typicals,” must be validated for each customer application bycustomer's technical experts. Freescale does not convey any licenseunder its patent rights nor the rights of others. Freescale sells productspursuant to standard terms and conditions of sale, which can be foundat the following address: freescale.com/SalesTermsandConditions.

Freescale, the Freescale logo, and CodeWarrior are trademarks ofFreescale Semiconductor, Inc., Reg. U.S. Pat. & Tm. Off. All otherproduct or service names are the property of their respective owners.

© 2005–2016 Freescale Semiconductor, Inc.

Document Number ETAPUGRevision 10.x, 11/2015

http://www.freescale.com

http://www.freescale.com/support

http://freescale.com/SalesTermsandConditions

Ethernet TAP Probe - Users Guide - Freescale Semiconductor

Documents

Transcript of Ethernet TAP Probe - Users Guide - Freescale Semiconductor