IBM RISCWatch Debugger Installation Guide

IBM
RISCWatch Debugger
Installation Guide
13H6984
Twelfth edition (August 2000)
This edition of IBM RISCWatch Debugger Installation Guide applies to IBM RISCWatch Debugger Version 4.6
and to all subsequent versions of the debugger until otherwise indicated in new versions or technical newsletters.
The following paragraph does not apply to the United Kingdom or any country where such provisions
are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES
THIS MANUAL “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you.
IBM does not warrant that the contents of this publication or the accompanying source code examples, whether
individually or as one or more groups, will meet your requirements or that the publication or the accompanying
source code examples are error-free.
This publication could contain technical inaccuracies or typographical errors. Changes are periodically made to
the information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or program(s) described in this publication at any time.
It is possible that this publication may contain references to, or information about, IBM products (machines and
programs), programming, or services that are not announced in your country. Such references or information
must not be construed to mean that IBM intends to announce such IBM products, programming, or services in
your country. Any reference to an IBM licensed program in this publication is not intended to state or imply that
you can use only IBM’s licensed program. You can use any functionally equivalent program instead.
No part of this publication may be reproduced or distributed in any form or by any means, or stored in a data
base or retrieval system, without the written permission of IBM.
Requests for copies of this publication and for technical information about IBM products should be made to
your IBM Authorized Dealer or your IBM Marketing Representative.
Address comments about this publication to:
IBM Corporation
Department YM3A
P.O. Box 12195
Research Triangle Park, NC 27709
IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring
any obligation to you.
Copyright International Business Machines Corporation 1995, 2000. All rights reserved.
Printed in the United States of America.
4321
Notice to U.S. Government Users–Documentation Related to Restricted Rights –Use, duplication, or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.
RISCWatch Debugger Installation Guide
Patents and Trademarks
IBM may have patents or pending patent applications covering the subject matter in this publication. The furnishing of this publication does not give you any license to these patents. You can send license inquiries, in
writing, to the IBM Director of Licensing, IBM Corporation, 208 Harbor Drive, Stamford, CT 06904, United
States of America.
The following terms are trademarks of IBM Corporation:
AIX
AIX/Windows
IBM
OS Open
PowerPC
PowerPC Architecture
RISC System/6000
RISCTrace
RISCWatch
The following term is a registered trademark in the United States and other countries licensed exclusively
through X/Open Company Limited:
UNIX
Windows is a trademark of Microsoft Corporation.
Other terms which are trademarks are the property of their respective owners.
RISCWatch Debugger Installation Guide
Contents
Contents.......................................................................................................................... v
Introduction ................................................................................................................. 1-1
JTAG Ethernet Target ............................................................................................................. 1-1
ROM Monitor Target................................................................................................................ 1-2
OS Open Target ...................................................................................................................... 1-3
Installing RISCWatch on Windows ............................................................................ 2-1
Windows Hardware Installation ................................................................................................... 2-1
JTAG Ethernet Target Hardware Install .................................................................................. 2-1
Establishing a Network Connection with the RISCWatch Processor Probe ...................... 2-5
Setting the TCP/IP Parameters of the RISCWatch Processor Probe ................................ 2-6
ROM Monitor and OS Open Target Hardware Install ............................................................. 2-8
Windows Software Installation .................................................................................................... 2-9
TCP/IP Package Setup ......................................................................................................... 2-10
RISCWatch Environment Setup ............................................................................................ 2-10
Installing RISCWatch on the RS/6000 ....................................................................... 3-1
RS/6000 Hardware Installation ................................................................................................... 3-1
JTAG Ethernet Target Hardware Install ................................................................................. 3-1
Establishing a Network Connection with the RISCWatch Processor Probe ...................... 3-5
Setting the TCP/IP Parameters of the RISCWatch Processor Probe ................................ 3-7
ROM Monitor and OS Open Target Hardware Install ........................................................... 3-11
RS/6000 Software Installation ................................................................................................... 3-11
RISCWatch Environment Setup ........................................................................................... 3-13
Installing RISCWatch on Sun ..................................................................................... 4-1
Sun Hardware Installation ........................................................................................................... 4-1
JTAG Ethernet Target Hardware Install ................................................................................. 4-1
Establishing a Network Connection with the RISCWatch Processor Probe ...................... 4-5
Setting the TCP/IP Parameters of the RISCWatch Processor Probe ................................ 4-6
ROM Monitor and OS Open Target Hardware Install ............................................................. 4-8
Sun Software Installation ............................................................................................................ 4-8
RISCWatch Environment Setup ........................................................................................... 4-10
Ethernet Crossover Cable ........................................................................................ A-1
Other JTAG Ethernet Hardware ............................................................................... B-1
JTAG Parallel Port Hardware ................................................................................... C-1
Contents
v
JTAG Parallel Port Target .................................................................................................. C-1
Windows 95/98 ................................................................................................................... C-1
Windows NT ....................................................................................................................... C-2
RS/6000.............................................................................................................................. C-2
Sun ..................................................................................................................................... C-4
Index ............................................................................................................................ X-1
vi
RISCWatch Debugger Installation Guide
Chapter 1.
Introduction
This book describes how to install and configure the IBM RISCWatch
Debugger hardware and software.
If you are a first time RISCWatch user, you must first determine the target type
you will be using with RISCWatch. The following sections describe the three
possible target types RISCWatch supports. Once you determine the target type,
you may proceed to the chapter which details the installation procedures for the
specific workstation (host) RISCWatch will be installed on.
BEFORE BEGINNING THE HARDWARE INSTALLATION, YOU MUST REFER
TO THE ENCLOSED IBM SAFETY BOOKLET (SD21-0030-02).
JTAG Ethernet Target
The JTAG Ethernet target type requires hardware which is labeled
"RISCWatch Processor Probe". One end of the RISCWatch processor probe
connects to your host workstation via a standard ethernet setup. The other end of
the processor probe connects to the JTAG connector resident on the target
PowerPC board.
JTAG ribbon cable
Target System
Host
Workstation
PowerPC
Processor
RISCWatch
Processor Probe
Ethernet
Figure 1-1. RISCWatch JTAG Ethernet Target
By setting the RISCWatch TARGET_TYPE environment variable to “jtag_eth”,
RISCWatch will be configured to communicate with the processor probe. See the
RISCWatch User's Guide for additional information about environment variables.
When using this target type, you can direct RISCWatch to freeze or stop the
processor via execution of specific commands or debug events. When the
processor is stopped, you can access and alter all architected resources of the
processor (registers, etc) and peripherals connected to the PowerPC processor or
processor core. Use of this target type relies on internal processor resources
provided in IBM 400, 600, and 700 Series PowerPC processors. Debug of system
hardware and software is accomplished without the need of any target control
program software, so no additional code constraints are put on your PowerPC
Introduction
1-1
application. In addition, by using a standard ethernet connection, RISCWatch is
capable of running on any PowerPC board (connected to a processor probe)
defined on the network.
There are two types of RISCWatch processor probes which can be ordered. One
probe provides an added feature called RISCTrace. RISCTrace allows you to take
advantage of the real-time trace debug logic available on some IBM 400 Series
PowerPC processors. See the RISCWatch User's Guide for more information on
RISCTrace.
ROM Monitor Target
The ROM Monitor target type makes use of the standard ethernet connection
available on most host workstations and PCs.
RISCWatch can communicate with the target PowerPC over a standard TCP/IP
Ethernet network. By setting the RISCWatch TARGET_TYPE environment
variable to “rom_mon”, RISCWatch will be configured to communicate with IBM
OpenBIOS code (ROM monitor code) which is running on the target PowerPC
board.
Host
Serial
Port 1
Host
Target System
PowerPC
Processor
Serial Port 1
Software
Workstation
Ethernet controller
OpenBIOS
Ethernet driver
Ethernet
Figure 1-2. ROM Monitor Target
Please refer to the appropriate IBM PowerPC Evaluation Kit documentation for
details about setting up your target board to run OpenBIOS code. Note that the
OpenBIOS code provided in the evaluation kit can be ported to custom board
designs. Contact your local IBM representative for more information on
customizing OpenBIOS ROM Monitor code.
When using this target type, you can direct the ROM monitor code to load and
control the execution of your application. Note that RISCWatch is constantly
communicating with the ROM monitor code on the target. This means the target
PowerPC processor is always running. After loading your program with
RISCWatch, debug events are set up to control the execution of your application.
These debug events generate debug exceptions, which interrupt normal
application program flow so the ROM code running on the target system can
collect processor status and alter processor resources.
1-2
RISCWatch Debugger Installation Guide
Use of this target type relies on the dedicated exception handler and command
set API available in OpenBIOS. The ROM Monitor is ideal for debugging
application software on a working target system. Hardware debug is limited since
RISCWatch is dependent upon successful execution of the ROM Monitor code on
the target PowerPC system.
OS Open Target
The OS Open target type makes use of the standard ethernet connection
available on most host workstations and PCs.
RISCWatch can communicate with the target PowerPC over a standard TCP/IP
Ethernet network. By setting the RISCWatch TARGET_TYPE environment
variable to “osopen”, RISCWatch will be configured to communicate with IBM OS
Open Real Time Operating System which is running on the target PowerPC
board.
Target System
PowerPC
Processor
OS Open
Software
Host
Workstation
Ethernet controller
Ethernet
Debug Support
TCP/IP
Ethernet driver
Figure 1-3. OS Open Target
Please refer to the appropriate OS Open documentation for details about setting
up your target board to run and debug with RISCWatch.
Note that RISCWatch is constantly communicating with OS Open on the target.
This means the target PowerPC processor is always running. After loading your
program with RISCWatch, debug events are set up to control the execution of your
application. These debug events generate debug exceptions, which interrupt
normal application program flow so OS Open running on the target system can
collect processor status and alter processor resources.
Use of this target type is ideal for debugging OS Open applications in which
thread debug is required. Hardware debug is limited since RISCWatch is
dependent upon successful execution of OS Open code on the target PowerPC
system.
Introduction
1-3
1-4
RISCWatch Debugger Installation Guide
Chapter 2.
Installing RISCWatch on Windows
All references to Windows do not include Windows 3.1 since RISCWatch does not
support it.
Windows Hardware Installation
This chapter assumes that your Windows host machine is already network
connected or at least equipped with a 10BaseT Ethernet card.
Please follow the hardware installation instructions for the RISCWatch target you
plan to use. For example, evaluation kit users may skip directly to “ROM Monitor
and OS Open Target Hardware Install” on page 2-8.
Please see the Appendix for information and assembly drawings if your hardware
is not shown below.
JTAG Ethernet Target Hardware Install
For JTAG Ethernet targets, the following installation steps need to be performed:
1.
Verify the following hardware is available:
• One RISCWatch processor probe
• One RISCWatch processor probe AC/DC power adapter and power cord
• One RISCWatch processor probe JTAG adapter assembly (see
descriptions in step 3 below)
• One 9-pin serial cable
2.
Remove the “wrap” adapter from the front of the processor probe, if one
exists.
Installing RISCWatch on Windows
2-1
3.
Determine which JTAG adapter assembly you have by examining the following figures:
RISCWatch
Processor Probe
(front panel)
12” sixteen-pin
ribbon cable
Mictor
connector
Transition
Board
Figure 2-1. Embedded JTAG Adapter Assembly
2-2
RISCWatch Debugger Installation Guide
12” sixty-pin
ribbon cable
Buffer
Board
RISCWatch
Processor Probe
(front panel)
JTAG and trace connectors
Transition
Board
JTAG and trace
2 x 30 Mictor header
20-pin
trace
cable
16-pin
JTAG
cable
Board under test
RISCTrace 2 x 10 header
RISCWatch 2 x 8 header
Figure 2-2. Embedded JTAG Adapter with RISCTrace Assembly (No Mictor)
Installing RISCWatch on Windows
2-3
12” sixty-pin
ribbon cable
Buffer
Board
JTAG and trace connectors
JTAG and trace
2 x 30 Mictor header
RISCWatch
Processor Probe
(front panel)
Board under test
Figure 2-3. Embedded JTAG Adapter with RISCTrace Assembly (Mictor)
4.
If your JTAG adapter assembly looks like the one shown in Figure 2-1, you
have an Embedded JTAG Adapter Assembly. To assemble the adapter and
cables, perform the following steps:
a. Attach the 12” sixteen-pin ribbon cable to the 16-pin connector on the front
of the RISCWatch processor probe.
Note: Failure to use the non-keyed side may damage the processor probe.
b. If your PowerPC board uses a Mictor type JTAG header, attach the Transition Board E5903-66504 to the other end of the 12” ribbon cable and
attach the Transition Board to the Mictor on the PowerPC board. Otherwise, connect the other end of the 12” ribbon cable to the 16-pin JTAG
header on the PowerPC board.
Proceed to step 7.
5.
2-4
If your JTAG adapter assembly looks like the one shown in Figure 2-2 or Figure 2-3, you have an Embedded JTAG Adapter with RISCTrace assembly.
Use Figure 2-2 if your board does not have a Mictor. Use Figure 2-3 if your
board has a Mictor. To assemble the adapter and cables, perform the following steps:
RISCWatch Debugger Installation Guide
a. Attach the 12” sixty-pin ribbon cable to the 60-pin connector on the front of
the RISCWatch processor probe.
b. If your PowerPC board uses 3.3V I/O or less, attach the other end of the
12” sixty-pin ribbon cable to the low voltage Buffer Board E5903-26502.
c. If your PowerPC board uses 5V I/O, attach the other end of the 12”
sixty-pin ribbon cable to the 5V Buffer Board E5903-26503.
d. If your PowerPC board uses a Mictor type header for JTAG and trace,
attach the Buffer Board to your PowerPC board as shown in Figure 2-3.
Otherwise, attach the Buffer Board to the Transition Board E5903-66504.
Attach the Transition Board to your PowerPC board using the 16-pin and
20-pin cables as shown in Figure 2-2.
Proceed to step 7.
6.
Refer to the Appendix if your JTAG adapter assembly is not one of the ones
listed above.
7.
Connect the processor probe’s AC/DC power adapter to the back of the processor probe.
8.
Connect the power cord to the AC/DC power adapter and to a wall outlet.
USE ONLY THE SUPPLIED POWER CORD. Flip the on/off switch on the
front of the probe to the on position. The power light on the front of the RISCWatch processor probe will be illuminated.
9.
Proceed to the next section, “Establishing a Network Connection with the
RISCWatch Processor Probe” on page 2-5.
Establishing a Network Connection with the RISCWatch Processor Probe
1.
If your host machine is already network connected, procure a 10/100BaseT
Ethernet drop for the RISCWatch Processor probe and connect it to the back
of the probe. Proceed to the next section, “Setting the TCP/IP Parameters of
the RISCWatch Processor Probe” on page 2-6.
2.
Otherwise, hook up Ethernet cables between your host and the processor
probe according to your desired network topology.
Installing RISCWatch on Windows
2-5
a. If the connection is to be used exclusively between the host and the processor probe (a point-to-point connection), a crossover cable must be used
to connect the two nodes (see Appendix for a diagram of the wiring for a
crossover cable). Figure 2-4 shows a point-to-point Ethernet connection
using a crossover cable:
RISCWatch Processor Probe (Rear View)
RS232
Host
LAN
12V
Crossover cable
RJ-45
connector
10/100 BaseT
receptacle
Figure 2-4. 10/100BaseT Crossover Connection
b. Figure 2-4 shows a 10/100BaseT Ethernet connection using a hub:
RISCWatch Processor Probe (Rear View)
Host
RS232
LAN
12V
10/100BaseT
receptacle
RJ-45
connector
10/100BaseT
straight-through
cable
10/100BaseT Hub
Figure 2-5. 10/100BaseT Hub Connection
3.
Proceed to the next section, “Setting the TCP/IP Parameters of the RISCWatch Processor Probe” on page 2-6.
Setting the TCP/IP Parameters of the RISCWatch Processor Probe
The RISCWatch processor probe ships with a TCP/IP address of 0.0.0.0 and a
gateway address of 0.0.0.0. To change these addresses to valid addresses on
your network, a serial port connection must be made from the host to the
processor probe. Most PCs include two serial ports to support communications
via asynchronous data transfer. These ports are sometimes referred to as
2-6
RISCWatch Debugger Installation Guide
communication or COM ports. These ports are usually accessed from the back of
the system unit. This document refers to these serial ports as S1 and S2. Consult
your PC literature to determine how many serial ports are available on your unit
and where they are located.
1.
Connect the 9-pin female connector of the supplied serial cable to S1 or S2
on the PC.
2.
Connect the other end of the supplied cable to the connector labeled RS-232
on the processor probe.
3.
Select ‘Start’ from the Windows task bar.
4.
Select ‘Programs’.
5.
Select ‘Accessories’.
6.
Select ‘Utilities’ if on Windows 95/98.
7.
Select ‘HyperTerminal’.
8.
If you see a window that says “You need to install a modem before you can
make a connection. Would you like to do this now?”, click on “No”, as you do
not need a modem for a direct serial link.
9.
Select the ‘Hypertrm’ icon.
10. Enter a name, for example, “RW probe”, and select an icon.
11. Select the following communications characteristics:
a. Connect using Direct to Com1 if S1 or Com 2 if using S2
b. Bits per second - 9600
c. Data Bits 8 (default)
d. Stop Bits - 1 (default)
e. Parity - None (default)
f. Flow Control - Hardware (default)
12. Select OK.
13. Press Enter. The processor probe will respond with a status prompt consisting of a letter followed by the “>” sign.
14. Enter "lan" to display the current lan settings.
15. Determine a valid TCP/IP address and gateway for the processor probe.
a. If connecting to an existing network, obtain the TCP/IP address and gateway address from your system administrator.
b. If connecting to the processor probe via a point-to-point connection with
your PC, we suggest a TCP/IP address of “7.1.1.100”. The processor
probe’s default gateway of “0.0.0.0” is sufficient.
Installing RISCWatch on Windows
2-7
16. Change the TCP/IP address by entering "lan -i 'TCP/IP address'". For example, enter “lan -i 7.1.1.100”.
17. Change the TCP/IP gateway by entering "lan -g 'TCP/IP address'". For example, enter “lan -g 0.0.0.0”.
18. If necessary, change the processor probe’s port number. This step is only
necessary if there is a conflict using the probe’s default port number of 6470.
Conflicts should only exist if a device other than an IBM RISCWatch Processor Probe is using port number 6470. To change the port number, enter “lan
-p ‘port number’”. For example, enter “lan -p 6470”.
Note: The port number must match the host port number entry in the
Windows TCP/IP services file. Refer to “TCP/IP Package Setup” on page
2-10 for where this is entered.
19. Select File->Exit to exit the terminal session.
20. If asked to save changes to terminal settings, select No.
21. Cycle power on the processor probe for the changes to take effect. Power can
be cycled using the on/off switch on the front of the processor probe.
Note: As the probe boots, it sends ICMP address mask requests out on the
network. If a response is received, the probe sets its subnet mask to that of
the network. If multiple responses are received, the probe sets its subnet
mask to the first value it receives and issues a warning message over the
serial port. This is an error condition on the network and should be corrected.
If no response is received, the probe sets the subnet mask to one of the
following defaults based on its TCP/IP address:
a. 255.0.0.0 for Class A addresses (1.x.x.x - 127.x.x.x)
b. 255.255.0.0 for Class B addresses (128.x.x.x - 191.x.x.x)
c. 255.255.255.0 for Class C addresses (192.x.x.x - 223.x.x.x)
The processor probe also supports a “lan -s” command to set the subnet
mask. For example:
lan -s 255.255.255.0
22. Once the addresses are made valid for your network, the "telnet" utility on
your host and the "lan" command on the RISCWatch processor probe can be
used to change the addresses from then on.
23. Hardware installation for the JTAG Ethernet target is complete. Please proceed to “Windows Software Installation” on page 2-9.
ROM Monitor and OS Open Target Hardware Install
For ROM Monitor and OS Open targets, a communications link must be
established between the host PC and the target board. Please refer to
“Establishing a Network Connection with the RISCWatch Processor Probe” on
2-8
RISCWatch Debugger Installation Guide
page 2-5, substituting the ROM Monitor or OS Open target board where the
processor probe is mentioned.
Consult the appropriate ROM Monitor and OS Open documentation for
establishing TCP/IP parameters necessary for your network.
Windows Software Installation
For all RISCWatch target types, the following installation steps need to be
performed:
1.
Verify the following items are available:
• IBM or compatible PC
•
•
•
•
•
•
Minimum required: Pentium 60MHz with 8 MB of RAM and a 10BaseT
Ethernet card.
SVGA Display
Minimum required: SVGA 1024x768 or above
Supports: SVGA 1024x768, SVGA 1280x1024, SVGA 1600x1200
Microsoft Windows
RISCWatch Installation CD
One CDROM drive
Twenty megabytes of hard disk space
For JTAG Ethernet, ROM Monitor, and OS Open targets, Microsoft
Windows TCP/IP support
2.
Place the RISCWatch Installation CD in the proper drive. It will automatically
start the RISCWatch installation process.
3.
If it does not, select “Start” from the Windows task bar, select “Run” and type
“D:\WIN32\INSTALL” (assuming that your CDROM drive is the D drive) then
press Enter.
4.
When the Welcome window appears, select Continue.
5.
When the Custom Installation window appears, use the Set Location button if
you wish to change the directory where the program files will be installed
(default location is C:\RWPPC). Select to install the JTAG Ethernet files if you
plan on using the JTAG Ethernet target. Installing the documentation files is
optional.
6.
Select Install.
7.
Once the installation is completed, a RISCWatch group will be created along
with some program items. The RISCWatch “README” file will then be displayed. Please view the entire file for the latest changes to the program and
its operation.
Installing RISCWatch on Windows
2-9
TCP/IP Package Setup
For JTAG Ethernet, ROM Monitor, and OS Open targets, the Windows TCP/IP
package should be configured if not already configured.
To set the host TCP/IP address for the Ethernet connection:
1.
Select the 'My Computer' icon from the desktop.
2.
Select 'Control Panel'.
3.
Select 'Network'.
4.
Add the appropriate "Adapter" network component for the ethernet adapter
being used (if not already added).
5.
Add a "Protocol" network component of 'Microsoft - TCP/IP' (if not already
added). Specify the IP address (7.1.1.4 is recommended to maintain consistency with this document) and netmask (255.255.240.0) to be used.
6.
Edit the TCP/IP services file to establish a named communications port and
port number for your TCP/IP socket communications. Windows 95/98 places
the services file under C:\WINDOWS. Windows NT places the services file
under C:\WINDOWS\SYSTEM32\DRIVERS. Consult your TCP/IP documentation or contact your system administrator if this file cannot be found. The following lines must be added to the file:
osopen-dbg
20044/tcp
# For ROM Monitor targets
osopen-dbg
20044/udp
# For OS Open targets
jtag_eth
6470/tcp
# For JTAG Ethernet targets
Note: use underscore, not hyphen
7.
For the update to take effect, TCP/IP may need to be restarted. This may
require a reboot of the system and/or a restart of the TCP/IP package.
8.
Verify your network connection. From your host, enter "ping 'TCP/IP
address'". For example, enter “ping 7.1.1.100”. If the ping does not complete
successfully, verify that the installation steps have been followed correctly or
contact a system administrator.
9.
Proceed to “RISCWatch Environment Setup” on page 2-10.
RISCWatch Environment Setup
You must edit the RISCWatch environment file rwppc.env to make the
appropriate changes to certain RISCWatch environment variables:
2-10
1.
Double click on the “RWPPC Environment File” icon in the RISCWatch program group. This will bring up the rwppc.env file in the Notepad editor.
2.
Change the PROC variable to the processor you will be debugging. See the
README for a list of valid processors for your release.
RISCWatch Debugger Installation Guide
3.
Change the TARGET_TYPE variable to the proper target type you will be
using. Valid selections are “jtag_eth”, “rom_mon”, and “osopen”.
4.
For JTAG Ethernet, ROM Monitor, and OS Open targets, change the
TARGET_NAME variable to the TCP/IP name or address of either the RISCWatch processor probe, the ROM Monitor local address, or OS Open
address, respectively.
5.
Edit any other environment variables as desired. Environment variables are
described in “Environment Resources” on page 3-5 in the RISCWatch Debugger User’s Guide. Users that have a working directory other than the install
directory have their own copy of the rwppc.env file. Such users should
backup their copy, make a fresh one from the install directory, and then merge
their changes from the backup copy to the new one.
6.
Exit from Notepad by selecting File->Exit, and select “Yes” when asked if “Do
you want to save the changes”.
This completes the Windows installation of RISCWatch. Proceed to “Quick Start”
on page 2-1 in the RISCWatch Debugger User’s Guide.
Installing RISCWatch on Windows
2-11
2-12
RISCWatch Debugger Installation Guide
Chapter 3.
Installing RISCWatch on the RS/6000
RS/6000 Hardware Installation
This chapter assumes that your RS/6000 host machine is already network
connected or at least equipped with a 10BaseT Ethernet card.
Please follow the hardware installation instructions for the RISCWatch target you
plan to use. For example, evaluation kit users may skip directly to “ROM Monitor
and OS Open Target Hardware Install” on page 3-11.
Please see the Appendix for information and assembly drawings if your hardware
is not shown below.
JTAG Ethernet Target Hardware Install
For JTAG Ethernet targets, the following installation steps need to be performed:
1.
Verify the following hardware is available:
• One RISCWatch processor probe
• One RISCWatch processor probe AC/DC power adapter and power cord
• One RISCWatch processor probe JTAG adapter assembly (see
descriptions in step 4 below)
• One 9-pin serial cable
2.
If your RS/6000 does not have a 9 pin serial port connector, you may need to
purchase a 25-pin-to-9-pin converter of the correct gender or use the 9 pin
serial port on a PC or laptop.
3.
Remove the “wrap” adapter from the front of the processor probe, if one
exists.
Installing RISCWatch on the RS/6000
3-1
4.
Determine which JTAG adapter assembly you have by examining the following figures:
RISCWatch
Processor Probe
(front panel)
12” sixteen-pin
ribbon cable
Mictor
connector
Transition
Board
Figure 3-1. Embedded JTAG Adapter Assembly
3-2
RISCWatch Debugger Installation Guide
12” sixty-pin
ribbon cable
Buffer
Board
RISCWatch
Processor Probe
(front panel)
JTAG and trace connectors
Transition
Board
JTAG and trace
2 x 30 Mictor header
20-pin
trace
cable
16-pin
JTAG
cable
Board under test
RISCTrace 2 x 10 header
RISCWatch 2 x 8 header
Figure 3-2. Embedded JTAG Adapter with RISCTrace Assembly (No Mictor)
Installing RISCWatch on the RS/6000
3-3
12” sixty-pin
ribbon cable
Buffer
Board
JTAG and trace connectors
JTAG and trace
2 x 30 Mictor header
RISCWatch
Processor Probe
(front panel)
Board under test
Figure 3-3. Embedded JTAG Adapter with RISCTrace Assembly (Mictor)
5.
If your JTAG adapter assembly looks like the one shown in Figure 3-1, you
have an Embedded JTAG Adapter Assembly. To assemble the adapter and
cables, perform the following steps:
a. Attach the 12” sixteen-pin ribbon cable to the 16-pin connector on the front
of the RISCWatch processor probe.
Note: Failure to use the non-keyed side may damage the processor probe.
b. If your PowerPC board uses a Mictor type JTAG header, attach the Transition Board E5903-66504 to the other end of the 12” ribbon cable and
attach the Transition Board to the Mictor on the PowerPC board. Otherwise, connect the other end of the 12” ribbon cable to the 16-pin JTAG
header on the PowerPC board.
Proceed to step 8.
6.
If your JTAG adapter assembly looks like the one in Figure 3-2 or Figure 3-3,
you have an Embedded JTAG Adapter with RISCTrace assembly. Use Figure
3-2 if your board does not have a Mictor. Use Figure 3-3 if your board has a
Mictor. To assemble the adapter and cables, perform the following steps:
a. Attach the 12” sixty-pin ribbon cable to the 60-pin connector on the front of
the RISCWatch processor probe.
3-4
RISCWatch Debugger Installation Guide
b. If your PowerPC board uses 3.3V I/O or less, attach the other end of the
12” sixty-pin ribbon cable to the low voltage Buffer Board E5903-26502.
c. If your PowerPC board uses 5V I/O, attach the other end of the 12”
sixty-pin ribbon cable to the 5V Buffer Board E5903-26503.
d. If your PowerPC board uses a Mictor type header for JTAG and trace,
attach the Buffer Board to your PowerPC board as shown in Figure 3-3.
Otherwise, attach the Buffer Board to the Transition Board E5903-66504.
Attach the Transition Board to your PowerPC board using the 16- and
20-pin cables as shown in Figure 3-2.
Proceed to step 8.
7.
Refer to the Appendix if your JTAG adapter assembly is not one of the ones
listed above.
8.
Connect the processor probe’s AC/DC power adapter to the back of the processor probe.
9.
Connect the power cord to the AC/DC power adapter and to a wall outlet.
USE ONLY THE SUPPLIED POWER CORD. Flip the on/off switch on the
front of the probe to the on position. The power light on the front of the RISCWatch processor probe will be illuminated.
10. Proceed to the next section, “Establishing a Network Connection with the
RISCWatch Processor Probe” on page 3-5.
Establishing a Network Connection with the RISCWatch Processor Probe
1.
If your host machine is already network connected, procure a 10/100BaseT
Ethernet drop for the RISCWatch Processor probe and connect it to the back
of the probe. Proceed to the next section, “Setting the TCP/IP Parameters of
the RISCWatch Processor Probe” on page 3-7.
2.
Otherwise, hook up Ethernet cables between your host and the processor
probe according to your desired network topology.
Installing RISCWatch on the RS/6000
3-5
a. If the connection is to be used exclusively between the host and the processor probe (a point-to-point connection), a crossover cable must be used
to connect the two nodes (see Appendix for a diagram of the wiring for a
crossover cable). Figure 3-4 shows a point-to-point Ethernet connection
using a crossover cable:
RISCWatch Processor Probe (Rear View)
RS232
Host
LAN
12V
Crossover cable
RJ-45
connector
10/100 BaseT
receptacle
Figure 3-4. 10/100BaseT Crossover Connection
b. Figure 3-5 shows a 10/100BaseT Ethernet connection using a hub:
RISCWatch Processor Probe (Rear View)
Host
RS232
LAN
12V
10/100BaseT
receptacle
RJ-45
connector
10/100BaseT
straight-through
cable
10/100BaseT Hub
Figure 3-5. 10/100BaseT Hub Connection
3.
Assuming the host system is equipped with the appropriate ethernet adapter,
the Ethernet interface must be configured properly. To do this:
a. Log in as root or superuser (su)
b. Enter smit
c. Select Communication Applications and Services
d. Select TCP/IP
e. Select Further Configuration
3-6
RISCWatch Debugger Installation Guide
f. Select Network Interfaces
g. Select Network Interface Selection
h. Select Add a Network Interface
i. Select Add a Standard Ethernet Network Interface.
Choose "Standard Ethernet" as opposed to "IEEE 802.3 Ethernet".
Note: If you receive an error message stating that there is "No available
adapter", go directly to step 4. Skip the remaining items in step 3.
j. Select en0
k. Set the INTERNET ADDRESS field to the host TCP/IP address. An
acceptable value would be 7.1.1.4
l. Set the Network MASK field to 255.255.240.0
m. Insure that ACTIVATE is yes
n. Insure that the Use Address Resolution Protocol is yes
o. Leave the BROADCAST ADDRESS blank
p. Select Do or press Enter
Upon successful completion, a properly configured Ethernet interface has been
added. The Ethernet set-up is complete and step 4 need not be performed.
4.
Perform this step only if you received the "No available adapter" error message when trying to Add a Standard Ethernet Network Interface in step 3.
This message indicates that either the ethernet adapter is missing (or
possibly misplugged) or the Ethernet Network Interface already exists. To
determine whether the interface already exists:
a. Return to the Network Interface Selection screen in smit
b. Select Change/Show Characteristics of a Network Interface
• If en0 is not listed, insure that the RS/6000 host does have an ethernet
adapter and, if possible, verify that it is plugged correctly. If the adapter
was misplugged, repeat step 3to add the Ethernet Network Interface.
• If en0 is listed, then the Ethernet Network Interface already exists. Select
en0 and note the TCP/IP address listed for the INTERNET ADDRESS
field. This value is the host's Ethernet TCP/IP address and will be needed
later. If no TCP/IP address is listed, choose one. The TCP/IP address
7.1.1.4 is recommended to maintain consistency with the menus and
examples in this document. The Ethernet set-up is complete.
5.
Proceed to the next section, “Setting the TCP/IP Parameters of the RISCWatch Processor Probe” on page 3-7.
Setting the TCP/IP Parameters of the RISCWatch Processor Probe
The RISCWatch processor probe ships with a TCP/IP address of 0.0.0.0 and a
gateway address of 0.0.0.0. To change these addresses to valid addresses on
Installing RISCWatch on the RS/6000
3-7
your network, a serial port connection must be made from the host to the
processor probe.The RS/6000 typically includes two serial ports to support
communications via asynchronous data transfer. These ports are labeled S1 and
S2 on the back of the RS/6000's system unit.
1.
Connect the 9-pin female connector of the supplied serial cable to S1 or S2
on the RS/6000. You may need to procure a 25-pin-to-9-pin adapter of the
correct gender to make this connection.
2.
Connect the other end of the supplied serial cable to the connector labeled
RS-232 on the RISCWatch processor probe.
3.
Log in as root or superuser (su)
Proper set-up involves the configuration of tty devices for either S1 or S2. The
following steps should be taken to insure proper S1 or S2 configuration:
4.
Determine whether the tty0 or tty1 devices already exist. tty0 must exist if
using port S1 and tty1 must exist if using S2.
a. Enter smit
b. Select Devices
c. Select TTY
d. Select List All Defined TTYs
e. Perform step 5 if tty0 or tty1 is not listed. To properly configure a defined tty
device, perform step 6 for systems running AIX 4 or higher
5.
To add a tty device:
a. Select Done or PF3 to exit the List All Defined TTYs screen
b. Return to the TTY screen
c. Select Add a TTY
d. Select tty RS232 Asynchronous Terminal
e. Select sa0 - Serial Port 1 when adding tty0
sa1 - Serial Port 2 when adding tty1
f. Select s1 for the port number when adding tty0
s2 for the port number when adding tty1
g. Insure that the BAUD rate is 9600
h. Insure that the PARITY is none
i. Insure that the BITS per character is 8
j. Insure that the Number of STOP BITS is 1
k. Insure that Enable LOGIN is disabled
l. The default settings for all the other fields are satisfactory
m. Select Do or press Enter
3-8
RISCWatch Debugger Installation Guide
Upon successful completion, a properly configured tty device is created and thus,
step 6 can be skipped for the particular tty (tty0 or tty1) added. Go directly to step
7.
6.
To properly configure a previously defined tty device:
• For systems running AIX 4 or later :
a. Select Done or PF3 to exit the List All Defined TTYs screen
b. Return to the TTY screen
c. Select Change / Show Characteristics of a TTY
d. Select tty# (where # = 0 or 1)
e. Insure that the following fields are set to the indicated values:
TTY
tty# (#=0 for tty0, 1 for tty1)
TTY type
tty
TTY interface
RS232
Description
Asynchronous Terminal
Status
Available
Location
00-00-S*-00 (*=1 for tty0, 2 for tty1)
Parent Adapter
sa# (#=0 for tty0, 1 for tty1)
Port Number
s* (*=1 for tty0, 2 for tty1)
Terminal Type
dumb
Enable LOGIN
disable
f. Insure that the BAUD rate is 9600 for tty0
g. Insure that the PARITY is none
h. Insure that the BITS per character is 8
i. Insure that the Number of STOP BITS is 1
The other fields can remain at their default values.
j. Select Do or press Enter
Upon successful completion, the tty device is properly configured.
7.
Edit the file /etc/uucp/Devices and add one of the following lines:
"Direct tty0 - 9600 direct" if using S1
"Direct tty1 - 9600 direct" if using S2
8.
File the changes.
9.
Exit from root.
10. From the AIX command line, enter:
Installing RISCWatch on the RS/6000
3-9
“/usr/bin/cu -m -l tty0” if using S1
“/usr/bin/cu -m -l tty1” if using S2
11. Press Enter. The processor probe will respond with a status prompt consisting of a letter followed by the “>” sign.
12. Enter "lan" to display the current lan settings.
13. Determine a valid TCP/IP address and gateway for the processor probe.
a. If connecting to an existing network, obtain the TCP/IP address and gateway address from your system administrator.
b. If connecting to the processor probe via a point-to-point connection with
your RS/6000, we suggest a TCP/IP address of “7.1.1.100”. The processor
probe’s default gateway of “0.0.0.0” is sufficient.
14. Change the TCP/IP address by entering "lan -i 'TCP/IP address'". For example, enter “lan -i 7.1.1.100”.
15. Change the TCP/IP gateway by entering "lan -g 'TCP/IP address'". For example, enter “lan -g 0.0.0.0”.
16. If necessary, change the processor probe’s port number. This step is only
necessary if there is a conflict using the probe’s default port number of 6470.
Conflicts should only exist if a device other than an IBM RISCWatch Processor Probe is using port number 6470. To change the port number, enter “lan
-p ‘port number’”. For example, enter “lan -p 6470”.
Note: The port number must match the host port number entry in the TCP/IP
/etc/services file.
17. Enter "~." to return to the host.
18. Press Enter to quit the session.
19. As the probe boots, it sends ICMP address mask requests out on the network. If a response is received, the probe sets its subnet mask to that of the
network. For AIX to respond to ICMP requests, the following commands must
be entered as superuser (root):
• “no -o icmpaddressmask=1”
• “no -o ipforwarding=1”
Note: If multiple responses are received, the probe sets its subnet mask to
the first value it receives and issues a warning message over the serial port.
This is an error condition on the network and should be corrected. If no
response is received, the probe sets the subnet mask to one of the following
defaults based on its TCP/IP address:
a. 255.0.0.0 for Class A addresses (1.x.x.x - 127.x.x.x)
b. 255.255.0.0 for Class B addresses (128.x.x.x - 191.x.x.x)
c. 255.255.255.0 for Class C addresses (192.x.x.x - 223.x.x.x)
3-10
RISCWatch Debugger Installation Guide
The processor probe also supports a “lan -s” command to set the subnet
mask. For example:
lan -s 255.255.255.0
20. Cycle power on the processor probe for the changes to take effect. Power can
be cycled using the on/off switch on the front of the processor probe.
21. Once the addresses are made valid for your network, the "telnet" utility on
your host and the "lan" command on the RISCWatch processor probe can be
used to change the addresses from then on.
22. Verify your network connection. From your host, enter "ping 'TCP/IP
address'". For example, enter “ping 7.1.1.100”. If the ping does not complete
successfully, verify that the installation steps have been followed correctly or
contact a system administrator.
23. Hardware installation for the JTAG ethernet target is complete. Please proceed to “RS/6000 Software Installation” on page 3-11.
ROM Monitor and OS Open Target Hardware Install
For ROM Monitor and OS Open targets, a communications link must be
established between the host PC and the target board. Please refer to “Setting the
TCP/IP Parameters of the RISCWatch Processor Probe” on page 3-7, substituting
the ROM Monitor or OS Open target board where the processor probe is
mentioned.
Consult the appropriate ROM Monitor and OS Open documentation for
establishing TCP/IP parameters necessary for your network.
RS/6000 Software Installation
For all RISCWatch target types, the following installation steps need to be
performed:
1.
Verify the following items are available:
•
•
•
•
•
AIX Version 4.1 or later
AIX/Windows with X11R5 and Motif 1.2
RISCWatch Installation CD
One CDROM drive
Twenty megabytes of hard disk space
2.
Logon as root to the RISC System/6000 or use the su command to gain root
user privileges.
3.
Choose an already existing directory or create a new directory. For example:
“mkdir /usr/rwppc”
Installing RISCWatch on the RS/6000
3-11
which will contain the RISCWatch program and its associated files.
4.
Issue the cd command to make it the present working directory. For example:
“cd /usr/rwppc”
5.
Insert the RISCWatch Installation CD into the CDROM drive and mount it.
Contact your system administrator for mounting details. If a system administrator is not available, proceed with the following steps:
a. “mkdir /cdrom” if one does not exist
b. “mount -v cdrfs -r /dev/cd0 /cdrom”
6.
Issue the following command to start the installation process:
“/cdrom/aix/rw_inst”
Proceed to answer the questions as prompted.
7.
Once the installation is completed, the RISCWatch “README” file will be displayed. Please view the entire file for the latest changes to the program and
its operation.
8.
The command “unmount /cdrom” can be used to unmount the RISCWatch
Installation CD.
9.
Add the following line to every user’s .profile that will be running RISCWatch:
export UIDPATH=./%U:/usr/rwppc/%U (for Korn shell)
setenv UIDPATH ./%U:/usr/rwppc/%U (for C shell)
You must specify the %U at the end of each path in the UIDPATH line.
Note: Be sure to change the directory in the above lines if you did not install
RISCWatch in the /usr/rwppc directory. If you wish to use RISCWatch without
logging off and logging on your machine again, type in the above line at the
AIX prompt to set this environment variable immediately.
10. For JTAG ethernet, ROM Monitor, and OS Open targets, these additional
steps are required to establish communications between the host and target:
a. To modify the /etc/services file, the user must be logged in as root or
superuser (su). The following lines must be added to the file:
osopen-dbg
20044/tcp
osopen-dbg
20044/udp
jtag_eth
6470/tcp # Note: Underscore used, not hyphen
b. The AIX refresh -s inetd command must then be run to synchronize the
object data manager (ODM) database and to update the inetd daemon.
11. It may be necessary to add the chosen directory to the PATH environment
variable if it has not already been added. Furthermore, it may be necessary
to change ownership of this directory as well as all of its files if many people
will need access to the RISCWatch program
12. Exit from root or su.
3-12
RISCWatch Debugger Installation Guide
13. Proceed to “RISCWatch Environment Setup” on page 3-13.
RISCWatch Environment Setup
You must edit the RISCWatch environment file rwppc.env to make the
appropriate changes to certain RISCWatch environment variables:
1.
Bring up the rwppc.env file in your favorite editor.
2.
Change the PROC variable to the processor you will be debugging. See the
README for a list of valid processors for your release.
3.
Change the TARGET_TYPE variable to the proper target type you will be
using. Valid selections are “jtag_eth”, “rom_mon”, and “osopen”.
4.
For JTAG ethernet, ROM Monitor, and OS Open targets, change the
TARGET_NAME variable to the TCP/IP name or address of either the RISCWatch processor probe, the ROM Monitor local address, or OS Open
address, respectively.
5.
Edit any other environment variables as desired. Environment variables are
described in “Environment Resources” on page 3-5 in the RISCWatch Debugger User’s Guide. Users that have a working directory other than the install
directory have their own copy of the rwppc.env file. Such users should
backup their copy, make a fresh one from the install directory, and then merge
their changes from the old one to the new one.
This completes the RS/6000 installation of RISCWatch. Proceed to “Quick Start”
on page 2-1 in the RISCWatch Debugger User’s Guide.
Installing RISCWatch on the RS/6000
3-13
3-14
RISCWatch Debugger Installation Guide
Chapter 4.
Installing RISCWatch on Sun
All references to Solaris are references to Solaris 2.x (SunOS5) and not
references to Solaris 1.x (SunOS4).
RISCWatch version 4.3 was the last version that supported SunOS4. Users must
migrate to the Solaris version.
Sun Hardware Installation
This chapter assumes that your Sun workstation is already network connected or
at least equipped with a 10BaseT Ethernet card.
Please follow the hardware installation instructions for the RISCWatch target you
plan to use. For example, evaluation kit users may skip directly to “ROM Monitor
and OS Open Target Hardware Install” on page 4-8.
Please see the Appendix for information and assembly drawings if your hardware
is not shown below.
JTAG Ethernet Target Hardware Install
For JTAG Ethernet targets, the following installation steps need to be performed:
1.
Verify the following hardware is available:
• One RISCWatch processor probe
• One RISCWatch processor probe AC/DC power adapter and power cord
• One RISCWatch processor probe JTAG adapter assembly (see
descriptions in step 4 below)
• One 9-pin serial cable
2.
If your Sun does not have a 9 pin serial port connector, you may need to purchase a 25-pin-to-9-pin converter of the correct gender or use the 9 pin serial
port on a PC or laptop.
3.
Remove the “wrap” adapter from the front of the processor probe, if one
exists.
Installing RISCWatch on Sun
4-1
4.
Determine which JTAG adapter assembly you have by examining the following figures:
RISCWatch
Processor Probe
(front panel)
12” sixteen-pin
ribbon cable
Mictor
connector
Transition
Board
Figure 4-1. Embedded JTAG Adapter Assembly
4-2
RISCWatch Debugger Installation Guide
12” sixty-pin
ribbon cable
Buffer
Board
RISCWatch
Processor Probe
(front panel)
JTAG and trace connectors
Transition
Board
JTAG and trace
2 x 30 Mictor header
20-pin
trace
cable
16-pin
JTAG
cable
Board under test
RISCTrace 2 x 10 header
RISCWatch 2 x 8 header
Figure 4-2. Embedded JTAG Adapter with RISCTrace Assembly (No Mictor)
Installing RISCWatch on Sun
4-3
12” sixty-pin
ribbon cable
Buffer
Board
JTAG and trace connectors
JTAG and trace
2 x 30 Mictor header
RISCWatch
Processor Probe
(front panel)
Board under test
Figure 4-3. Embedded JTAG Adapter with RISCTrace Assembly (Mictor)
5.
If your JTAG adapter assembly looks like the one shown in Figure 4-1, you
have an Embedded JTAG Adapter Assembly. To assemble the adapter and
cables, perform the following steps:
a. Attach the 12” sixteen-pin ribbon cable to the 16-pin connector on the front
of the RISCWatch processor probe.
Note: Failure to use the non-keyed side may damage the processor probe.
b. If your PowerPC board uses a Mictor type JTAG header, attach the Transition Board E5903-66504 to the other end of the 12” ribbon cable and
attach the Transition Board to the Mictor on the PowerPC board. Otherwise, connect the other end of the 12” ribbon cable to the 16-pin JTAG
header on the PowerPC board.
Proceed to step 8.
6.
If your JTAG adapter assembly looks like the one in Figure 4-2 or Figure 4-3,
you have an Embedded JTAG Adapter with RISCTrace assembly. Use Figure
4-2 if your board does not have a Mictor. Use Figure 4-3 if your board has a
Mictor. To assemble the adapter and cables, perform the following steps:
a. Attach the 12” sixty-pin ribbon cable to the 60-pin connector on the front of
the RISCWatch processor probe.
4-4
RISCWatch Debugger Installation Guide
b. If your PowerPC board uses 3.3V I/O or less, attach the other end of the
12” sixty-pin ribbon cable to the low voltage Buffer Board E5903-26502.
c. If your PowerPC board uses 5V I/O, attach the other end of the 12”
sixty-pin ribbon cable to the 5V Buffer Board E5903-26503.
d. If your PowerPC board uses a Mictor type header for JTAG and trace,
attach the Buffer Board to your PowerPC board as shown in Figure 4-3.
Otherwise, attach the Buffer Board to the Transition Board E5903-66504.
Attach the Transition Board to your PowerPC board using the 16- and
20-pin cables as shown in Figure 4-2.
Proceed to step 8.
7.
Refer to the Appendix if your JTAG adapter assembly is not one of the ones
listed above.
8.
Connect the processor probe’s AC/DC power adapter to the back of the processor probe.
9.
Connect the power cord to the AC/DC power adapter and to a wall outlet.
USE ONLY THE SUPPLIED POWER CORD. Flip the on/off switch on the
front of the probe to the on position. The power light on the front of the RISCWatch processor probe will be illuminated.
10. Proceed to the next section, “Establishing a Network Connection with the
RISCWatch Processor Probe” on page 4-5 .
Establishing a Network Connection with the RISCWatch Processor Probe
1.
If your host machine is already network connected, procure a 10/100BaseT
Ethernet drop for the RISCWatch Processor probe and connect it to the back
of the probe. Proceed to the next section, “Setting the TCP/IP Parameters of
the RISCWatch Processor Probe” on page 4-6.
2.
Assuming the host system is equipped with the appropriate Ethernet adapter,
the Ethernet interface must be configured properly. To do this, the ifconfig
command can be used. Users should consult their network administrator and
Sun documentation for additional information. A host TCP/IP address of
7.1.1.4 is suggested to maintain consistency with this document.
3.
Hook up Ethernet cables between your host and the processor probe according to your desired network topology.
Installing RISCWatch on Sun
4-5
a. If the connection is to be used exclusively between the host and the processor probe (a point-to-point connection), a crossover cable must be used
to connect the two nodes (see Appendix for a diagram of the wiring for a
crossover cable). Figure 4-4 shows a point-to-point Ethernet connection
using a crossover cable:
RISCWatch Processor Probe (Rear View)
RS232
Host
LAN
12V
Crossover cable
RJ-45
connector
10/100 BaseT
receptacle
Figure 4-4. 10/100BaseT Crossover Connection
b. Figure 4-5 shows a 10/100BaseT Ethernet connection using a hub:
RISCWatch Processor Probe (Rear View)
Host
RS232
LAN
12V
10/100BaseT
receptacle
RJ-45
connector
10/100BaseT
straight-through
cable
10/100BaseT Hub
Figure 4-5. 10/100BaseT Hub Connection
4.
Proceed to the next section, “Setting the TCP/IP Parameters of the RISCWatch Processor Probe” on page 4-6.
Setting the TCP/IP Parameters of the RISCWatch Processor Probe
The RISCWatch processor probe ships with a TCP/IP address of 0.0.0.0 and a
gateway address of 0.0.0.0. To change these addresses to valid addresses on
your network, a serial port connection must be made from the host to the
processor probe. Sun workstations typically include two serial ports to support
communications via asynchronous data transfer. These ports are labeled Serial A
4-6
RISCWatch Debugger Installation Guide
and Serial B on the back of the Sun's system unit. Some models multiplex these
two ports into one physical port labeled A/B. Use A if it is available because use of
the B port requires a special demultiplexing cable from Sun.
This section refers to these ports as S1 and S2, respectively.
1.
Connect the 9-pin female connector of the supplied serial cable to S1 or S2
on the Sun. You may need to procure a 25-pin-to-9-pin adapter of the correct
gender to make this connection.
2.
Connect the other end of the supplied serial cable to the connector labeled
RS-232 on the RISCWatch processor probe.
3.
From the command line, enter:
"/usr/bin/tip -9600 /dev/ttya" if using S1
"/usr/bin/tip -9600 /dev/ttyb" if using S2
4.
Press Enter. The processor probe will respond with a status prompt consisting of a letter followed by the “>” sign.
5.
Enter "lan" to display the current lan settings.
6.
Determine a valid TCP/IP address and gateway for the processor probe.
a. If connecting to an existing network, obtain the TCP/IP address and gateway address from your system administrator.
b. If connecting to the processor probe via a point-to-point connection with
your host, we suggest a TCP/IP address of “7.1.1.100”. The processor
probe’s default gateway of “0.0.0.0” is sufficient.
7.
Change the TCP/IP address by entering "lan -i 'TCP/IP address'". For example, enter “lan -i 7.1.1.100”.
8.
Change the TCP/IP gateway by entering "lan -g 'TCP/IP address'". For example, enter “lan -g 0.0.0.0”.
9.
If necessary, change the processor probe’s port number. This step is only
necessary if there is a conflict using the probe’s default port number of 6470.
Conflicts should only exist if a device other than an IBM RISCWatch Processor Probe is using port number 6470. To change the port number, enter “lan
-p ‘port number’”. For example, enter “lan -p 6470”.
Note: The port number must match the host port number entry in the TCP/IP
/etc/services file.
10. Enter "~." to quit the session.
11. As the probe boots, it sends ICMP address mask requests out on the network. If a response is received, the probe sets its subnet mask to that of the
network. For Solaris to respond to ICMP requests, the following command
must be entered as superuser (root):
Installing RISCWatch on Sun
4-7
• “ndd -set /dev/ip ip_respond_address_mask_broadcast 1”
Note: If multiple responses are received, the probe sets its subnet mask to
the first value it receives and issues a warning message over the serial port.
This is an error condition on the network and should be corrected. If no
response is received, the probe sets the subnet mask to one of the following
defaults based on its TCP/IP address:
a. 255.0.0.0 for Class A addresses (1.x.x.x - 127.x.x.x)
b. 255.255.0.0 for Class B addresses (128.x.x.x - 191.x.x.x)
c. 255.255.255.0 for Class C addresses (192.x.x.x - 223.x.x.x)
The processor probe also supports a “lan -s” command to set the subnet
mask. For example:
lan -s 255.255.255.0
12. Cycle power on the processor probe for the changes to take effect. Power can
be cycled using the on/off switch on the front of the processor probe.
13. Once the addresses are made valid for your network, the "telnet" utility on
your host and the "lan" command on the RISCWatch processor probe can be
used to change the addresses from then on.
14. Verify your network connection. From your host, enter "ping 'TCP/IP
address'". For example, enter “ping 7.1.1.100”. If the ping does not complete
successfully, verify that the installation steps have been followed correctly or
contact a system administrator.
15. Hardware installation for the JTAG Ethernet target is complete. Please proceed to “Sun Software Installation” on page 4-8.
ROM Monitor and OS Open Target Hardware Install
For ROM Monitor and OS Open targets, a communications link must be
established between the host PC and the target board. Please refer to “JTAG
Ethernet Target Hardware Install” on page 4-1, substituting the ROM Monitor or
OS Open target board where the processor probe is mentioned.
Consult the appropriate ROM Monitor and OS Open documentation for
establishing TCP/IP parameters necessary for your network.
Sun Software Installation
For all RISCWatch target types, the following installation steps need to be
performed:
1.
4-8
Verify the following items are available:
RISCWatch Debugger Installation Guide
•
•
•
•
•
•
•
A Sun workstation
One CDROM drive
Solaris 2.4 (or higher)
A window system such as Open Windows or CDE
Motif 1.2
RISCWatch Installation CD
Twenty megabytes of hard disk space
2.
Logon as root or use the su command to gain root access.
3.
Choose an already existing directory or create a new directory which will contain the RISCWatch program and its associated files. For example, to create a
new directory rwppc within /usr:
“mkdir /usr/rwppc”
4.
Issue the cd command to make it the present working directory. For example:
“cd /usr/rwppc”
5.
Insert the RISCWatch Installation CD into the CDROM drive. It should automatically mount itself. If not, contact your system administrator for mounting
details.
6.
Issue the following command to start the installation process:
“/cdrom/cdrom0/sun/rw_inst”
Proceed to answer the questions as prompted.
7.
Once the installation is completed, the RISCWatch “README” file will be displayed. Please view the entire file for the latest changes to the program and
its operation.
8.
The command “eject cdrom0” can be used to unmount the RISCWatch Installation CD.
9.
Add the following line to every user’s .profile that will be running RISCWatch:
export UIDPATH=./%U:/usr/rwppc/%U (for Korn shell)
setenv UIDPATH ./%U:/usr/rwppc/%U (for C shell)
You must specify the %U at the end of each path in the UIDPATH line.
Note: Be sure to change the directory in the above lines if you did not install
RISCWatch in the /usr/rwppc directory. If you wish to use RISCWatch without
logging off and logging on your machine again, type in the above line at the
shell prompt to set this environment variable immediately.
10. Add the LD_LIBRARY_PATH environment variable to include the Motif libraries (/usr/dt/lib:) and, if needed, include the Open Windows libraries
(/usr/openwin/lib:). The environment variable should be added to any user’s
startup shell (.profile for Korn shell, .cshrc for C shell). For example:
Installing RISCWatch on Sun
4-9
For Korn shell:
export LD_LIBRARY_PATH=/usr/dt/lib:/usr/openwin/lib:$LD_LIBRARY_PATH
For C shell:
setenv LD_LIBRARY_PATH /usr/dt/lib:/usr/openwin/lib:$LD_LIBRARY_PATH
11. For JTAG Ethernet, ROM Monitor, and OS Open targets, an additional step is
required to establish communications between the host and target. To modify
the /etc/services file, the user must be logged in as root or superuser (su).
The following lines must be added to the file:
osopen-dbg
20044/tcp
osopen-dbg
20044/udp
jtag_eth
6470/tcp # Note: Underscore used, not hyphen
12. It may be necessary to add the chosen directory to the PATH environment
variable if it has not already been added. Furthermore, it may be necessary
to change ownership of this directory as well as all of its files if many people
will need access to the RISCWatch program
13. Exit from root or su.
14. Proceed to “RISCWatch Environment Setup” on page 4-10.
RISCWatch Environment Setup
You must edit the RISCWatch environment file rwppc.env to make the
appropriate changes to certain RISCWatch environment variables:
1.
Bring up the rwppc.env file in your favorite editor.
2.
Change the PROC variable to the processor you will be debugging. See the
README for a list of valid processors for your release.
3.
Change the TARGET_TYPE variable to the proper target type you will be
using. Valid selections are “jtag_eth”, “rom_mon”, and “osopen”.
4.
For JTAG Ethernet, ROM Monitor, and OS Open targets, change the
TARGET_NAME variable to the TCP/IP name or address of either the RISCWatch processor probe, the ROM Monitor local address, or OS Open
address, respectively.
5.
Edit any other environment variables as desired. Environment variables are
described in “Environment Resources” on page 3-5 in the RISCWatch Debugger User’s Guide. Users that have a working directory other than the install
directory have their own copy of the rwppc.env file. Such users should
backup their copy, make a fresh one from the install directory, and then merge
their changes from the old one to the new one.
This completes the Sun installation of RISCWatch. Proceed to “Quick Start” on
page 2-1 in the RISCWatch Debugger User’s Guide.
4-10
RISCWatch Debugger Installation Guide
Appendix A. Ethernet Crossover Cable
Figure A-1 shows the connections and signal assignments in a crossover cable:
RJ-45 Connector
10BaseT Cable
RJ-45
Twisted
Pair
Signal
Name
Pin
Pin
Signal
Name
1
TD +
1
1
TD +
1
TD −
2
2
TD −
2
RD +
3
3
RD +
2
RD −
6
6
RD −
3,4
(Not
used)
4, 5, 7, 8
4, 5, 7, 8
(Not
used)
Figure A-1. Wiring in a 10BaseT Crossover Cable
Ethernet Crossover Cable
A-1
A-2
RISCWatch Debugger Installation Guide
Appendix B. Other JTAG Ethernet Hardware
1.
Verify the following hardware is available:
• One RISCWatch processor probe
• One RISCWatch processor probe AC/DC power adapter and power cord
• One RISCWatch processor probe JTAG adapter assembly (see
descriptions in step 3 below)
• One 9-pin serial cable
2.
Remove the “wrap” adapter from the front of the processor probe, if one
exists.
3.
Determine which JTAG adapter assembly you have by examining the following figures:
Note:
all connectors are keyed
RISCWatch
Processor Probe
(front panel)
15” twenty-pin
ribbon cable
JTAG
adapter
sixteen-pin
ribbon cable
Figure B-1. Typical JTAG Adapter Assembly
Other JTAG Ethernet Hardware
B-1
Note:
all connectors are keyed
RISCWatch
Processor Probe
(front panel)
2” twenty-pin
ribbon cable
RISCTrace
adapter
wrap
adapter
15” twenty-pin
ribbon cables
2” sixteen-pin
ribbon cable
JTAG
adapter
splitter
adapter
2” cable
replaces
wrap adapter
sixteen-pin
connector
attaches
to JTAG
adapter
Figure B-2. JTAG Adapter with RISCTrace Assembly
RISCWatch
Processor Probe
(front panel)
60” ribbon cable
2x8 JTAG
connector
enhanced JTAG adapter
2x25 “D” receptacle
Figure B-3. Enhanced JTAG Adapter Assembly
B-2
RISCWatch Debugger Installation Guide
TracePort Analyzer
2x8 JTAG
connector
2x25 “D” receptacle
RISCWatch
Processor Probe
(front panel)
60” ribbon cable
2x10 trace
connector
enhanced JTAG adapter
with RISCTrace
power lead
Figure B-4. Enhanced JTAG Adapter Assembly with RISCTrace
4.
If your JTAG adapter assembly looks like the one shown in Figure B-1, you
have a typical JTAG adapter assembly. To assemble the adapter and cables,
perform the following steps:
a. Attach the 15” ribbon cable to the 20 pin connector on the JTAG adapter.
b. Attach the non-keyed side of the 2” cable to the 16 pin connector on the
adapter.
Note: Failure to use the non-keyed side may damage the JTAG adapter.
c. Attach the connector on the 15” ribbon cable to the front of the processor
probe.
d. Proceed to Step 8.
5.
If your adapter assembly resembles Figure B-2, you have a JTAG adapter
with RISCTrace assembly. To assemble the adapter assembly and cables,
perform the following steps:
a. Remove the “wrap” adapter, if attached to the cables (see Figure B-2).
b. Attach the non-keyed side of the 2” cable to the 16 pin connector.
Note: Failure to use the non-keyed side may damage the JTAG adapter.
c. Attach the splitter adapter to the front of the processor probe.
d. Proceed to Step 8.
6.
If your adapter assembly resembles Figure B-3, you have an enhanced JTAG
adapter assembly. To assemble the adapter assembly and cables, perform
the following steps:
a. Attach the 60” cable to the adapter.
Note: Attach the non-keyed side of the JTAG cable (2” or longer) to the 16 pin
connector.Failure to use the non-keyed side may damage the JTAG adapter.
Other JTAG Ethernet Hardware
B-3
Make sure that you attach the JTAG cable to the 16 pin connector on the top
of the enhanced JTAG adapter and not the 20 pin connector at the edge.
b. Attach the connector on the 60” ribbon cable to the front of the processor
probe.
c. If your kit includes a small adapter marked P.V. BOARD, set it aside. This
adapter is not required for normal use.
d. Proceed to Step 8.
7.
If your adapter assembly resembles Figure B-4, you have an enhanced JTAG
adapter with RISCTrace. To assemble the adapter and cables, perform the following steps:
a. Attach the 60” cable to the TracePort Analyzer.
b. Attach the power lead to the TracePort Analyzer.
c. Attach the adapter to the other side of the TracePort Analyzer.
d. Attach the non-keyed side of the JTAG cable (2” or longer) to the 16 pin
connector .
Note: Failure to use the non-keyed side may damage the adapter.
e. Attach the 2” trace cable to the 20 pin connector.
f. Attach the connector on the 60” ribbon cable to the front of the processor
probe.
g. Attach the power lead to the front of the processor probe
h. If your kit includes a small adapter marked P.V. BOARD, set it aside. This
adapter is not required for normal use.
8.
Attach the connector on the JTAG cable (2” or longer) to the JTAG header on
your PowerPC target board.
Note: The JTAG header is keyed (pin 14). Failure to align the key properly
may damage the target.
9.
If you have the JTAG adapter with RISCTrace or the enhanced JTAG adapter
with RISCTrace, attach the RISCTrace connector to the RISCTrace header on
the target board.
10. Set the processor probe configuration switches located on the back of the
processor probe. Configuration switch functions are described on the underside of the processor probe frame.
a. If using a 10Base2 Ethernet connection, set the processor probe configuration switch 1 to the “open/off” position and the other switches to the
“closed/on” position.
b. If using a 10BaseT Ethernet connection, set the processor probe configuration switches 1 and 5 to the “open/off” position, and have the other
switches set to the “closed/on” position.
B-4
RISCWatch Debugger Installation Guide
11. Hook up the processor probe to your network according to the desired network topology.
a. For customers with no current Ethernet network, a point-to-point connection should be configured. A 10Base2 connection between a host machine
and the RISCWatch processor probe requires a pair of BNC T-connectors
and 50-ohm terminators, plus a short length of 10Base2 ThinLAN cable, as
shown in Figure B-5.
RISCWatch Processor Probe (Rear View)
LAN
Host
10Base2
receptacle
10Base2 cable
50-ohm
terminator
50-ohm
terminator
BNC
T-connector
Figure B-5. 10Base2 Ethernet Point-to-Point Connection
b. For a 10Base2 connection to a site-wide LAN with multiple devices, the terminators would not be used, as shown in Figure B-6.
RISCWatch Processor Probe (Rear View)
Host
LAN
10Base2
receptacle
to another device
10Base2 cable
to another device
BNC
T-connector
Figure B-6. 10Base2 LAN Connection
Other JTAG Ethernet Hardware
B-5
c. For 10BaseT Ethernet, the connection can be made in two ways. If the
connection is to be used exclusively between the host and the evaluation
board (a 10BaseT point-to-point connection), a crossover cable must be
used to connect the two nodes (see Appendix A for a diagram of the wiring
for a 10BaseT crossover cable). Figure B-7 shows a point-to-point Ethernet connection using a 10BaseT crossover cable:
RISCWatch Processor Probe (Rear View)
LAN
Host
10BaseT
receptacle
10BaseT crossover cable
RJ-45
connector
Figure B-7. 10BaseT Crossover Connection
d. Figure B-8 shows a 10BaseT Ethernet connection using a hub:
RISCWatch Processor Probe (Rear View)
Host
LAN
10BaseT
receptacle
RJ-45
connector
10BaseT
straight-through
cable
10BaseT Hub
Figure B-8. 10BaseT Hub Connection
12. Connect the processor probe’s AC/DC power adapter to the back of the processor probe.
13. Connect the power cord to the AC/DC power adapter and to a wall outlet.
USE ONLY THE SUPPLIED POWER CORD. The power light on the front of
the RISCWatch processor probe will be illuminated. The processor probe
does not have an on/off switch.
B-6
RISCWatch Debugger Installation Guide
Appendix C. JTAG Parallel Port Hardware
JTAG Parallel Port Target
The JTAG Parallel Port target type requires hardware which is labeled
"RISCWatch Parallel Port Adapter". One end of the parallel port adapter is
connected to your host workstation via the parallel port adapter cable provided.
The other end of the parallel port adapter connects to the JTAG connector
resident on the target PowerPC board.
JTAG ribbon cable
Host
Workstation
RISCWatch
Parallel Port Adapter
Target System
PowerPC
400Series
Processor
parallel port
Figure C-1. RISCWatch JTAG Parallel Port Target
By setting the RISCWatch TARGET_TYPE environment variable to “jtag_par”,
RISCWatch will be configured to communicate to the parallel port adapter. See
the RISCWatch User's Guide for additional information about environment
variables.
When using this target type, you can direct RISCWatch to freeze or stop the
processor via execution of specific commands or debug events. When the
processor is stopped, you can access and alter all architected resources of the
processor (registers, etc) and peripherals connected to the PowerPC processor or
processor core.
Use of this target type relies on internal processor resources provided in IBM 400
Series PowerPC processors. Debug of system hardware and software is
accomplished without the need of any target control program software, so no
additional code constraints are put on your PowerPC application. Unlike JTAG
Ethernet target use, JTAG parallel port targets require a direct local connection
from your host workstation to the target board under test. There is no network link
to other workstations.
Windows 95/98
For JTAG parallel port targets, the following installation steps need to be
performed:
JTAG Parallel Port Hardware
C-1
1.
Verify the following hardware is available:
• One RISCWatch parallel port adapter
• One RISCWatch parallel port adapter cable
• One RISCWatch Parallel Port Adapter power supply for U.S.A and Canada
use only
• One RISCWatch Parallel Port Adapter power supply plug/cable assembly
for countries other than the U.S.A or Canada
YOU MUST PROVIDE A 240VA (OR LESS) POWER SUPPLY THAT IS
AGENCY-APPROVED IN THE COUNTRY YOU ARE IN.
Note: The power requirements for the adapter are 5V, 300mA, regulated, 5V
on the inner conductor, GND on the outer conductor.
2.
Plug one end of the adapter cable into the adapter and plug the other end into
the parallel port of the host platform.
3.
Attach the 16-pin cable of the RISCWatch parallel port adapter to the JTAG
header on your PowerPC target board.
Note: The JTAG header is keyed (pin 14). Failure to align the key properly
may damage the target.
4.
If you are in the U.S.A. or Canada, plug the connector of the enclosed power
supply into the parallel port adapter box and plug the power supply into the
wall outlet.
5.
If you are not in the U.S.A or Canada, attach the enclosed power supply
plug/cable assembly to your own agency-approved, 240VA (or less), 5V,
300ma, regulated power supply. The inner conductor of the plug/cable
assembly has to be connected to 5V and the outer conductor has to be connected to ground. Insert the plug/cable assembly into the parallel port adapter
box and plug the power supply into the wall outlet.
Windows NT
JTAG parallel port targets are not supported under Windows NT.
RS/6000
For JTAG parallel port targets, the following installation steps need to be
performed:
1.
C-2
Verify the following hardware is available:
RISCWatch Debugger Installation Guide
• One RISCWatch parallel port adapter
• One RISCWatch parallel port adapter cable
• One RISCWatch Parallel Port Adapter power supply for U.S.A and Canada
use only
• One RISCWatch Parallel Port Adapter power supply plug/cable assembly
for countries other than the U.S.A or Canada
YOU MUST PROVIDE A 240VA (OR LESS) POWER SUPPLY THAT IS
AGENCY-APPROVED IN THE COUNTRY YOU ARE IN.
Note: The power requirements for the adapter are 5V, 300mA, regulated, 5V
on the inner conductor, GND on the outer conductor.
2.
Plug one end of the adapter cable into the adapter and plug the other end into
the parallel port of the host platform.
Note: The RISCWatch parallel port adapter can only be attached to the
parallel port on the motherboard of the RS/6000 system unit.
3.
Attach the 16-pin cable of the RISCWatch parallel port adapter to the JTAG
header on your PowerPC target board.
Note: The JTAG header is keyed (pin 14). Failure to align the key properly
may damage the target.
4.
If you are in the U.S.A. or Canada, plug the connector of the enclosed power
supply into the parallel port adapter box and plug the power supply into the
wall outlet.
5.
If you are not in the U.S.A or Canada, attach the enclosed power supply
plug/cable assembly to your own agency-approved, 240VA (or less), 5V,
300ma, regulated power supply. The inner conductor of the plug/cable
assembly has to be connected to 5V and the outer conductor has to be connected to ground. Insert the plug/cable assembly into the parallel port adapter
box and plug the power supply into the wall outlet.
6.
Hardware installation for the JTAG parallel port target is complete. Please
proceed to “RS/6000 Software Installation” on page 3-11 to install RISCWatch then perform the following steps to install the parallel port device
driver:
a. Logon as root or use the su command to gain root user privileges.
b. Change directory to the RISCWatch install directory. For example: “cd
/usr/rwppc”.
c. Insert the RISCWatch Installation CD into the CDROM drive and mount it.
Contact your system administrator for mounting details. If a system administrator is not available, use “mkdir /cdrom” if the directory does not exist
and “mount -v cdrfs -r /dev/cd0 /cdrom”
d. Copy rwddi and rw400dd.tar from /cdrom/aix. Use “cp /cdrom/aix/rwddi .”
and “cp /cdrom/aix/rw400dd.tar .”.
JTAG Parallel Port Hardware
C-3
e. Execute “rwddi”.
Sun
For JTAG parallel port targets, the following installation steps need to be
performed:
1.
Verify the following hardware is available:
•
•
•
•
One Sparcstation
One RISCWatch parallel port adapter
One RISCWatch parallel port adapter cable
One RISCWatch Parallel Port Adapter power supply for U.S.A and Canada
use only
• One RISCWatch Parallel Port Adapter power supply plug/cable assembly
for countries other than the U.S.A or Canada
YOU MUST PROVIDE A 240VA (OR LESS) POWER SUPPLY THAT IS
AGENCY-APPROVED IN THE COUNTRY YOU ARE IN.
Note: The power requirements for the adapter are 5V, 300mA, regulated, 5V
on the inner conductor, GND on the outer conductor.
2.
Plug one end of the adapter cable into the adapter and plug the other end into
the parallel port of the host platform.
Note: The RISCWatch parallel port adapter can only be attached to the
parallel port on the motherboard of the host system unit.
3.
Attach the 16-pin cable of the RISCWatch parallel port adapter to the JTAG
header on your PowerPC target board.
Note: The JTAG header is keyed (pin 14). Failure to align the key properly
may damage the target.
4.
If you are in the U.S.A. or Canada, plug the connector of the enclosed power
supply into the parallel port adapter box and plug the power supply into the
wall outlet.
5.
If you are not in the U.S.A or Canada, attach the enclosed power supply
plug/cable assembly to your own agency-approved, 240VA (or less), 5V,
300ma, regulated power supply. The inner conductor of the plug/cable
assembly has to be connected to 5V and the outer conductor has to be connected to ground. Insert the plug/cable assembly into the parallel port adapter
box and plug the power supply into the wall outlet.
6.
Hardware installation for the JTAG parallel port target is complete. Please
proceed to “Sun Software Installation” on page 4-8 to install RISCWatch then
perform the following steps to install the parallel port device driver:
a. Logon as root or use the su command to gain root user privileges.
b. Change directory to the RISCWatch install directory. For example: “cd
/usr/rwppc”.
C-4
RISCWatch Debugger Installation Guide
c. Insert the RISCWatch Installation CD into the CDROM drive. It should
automatically mount itself. If not, contact your system administrator for
mounting details.
d. Copy rwddi, rwp and rwp.devlink from /cdrom/cdrom0/sun. Use “cp
/cdrom/cdrom0/sun/rwddi .”, “cp /cdrom/cdrom0/sun/rwp .” and “cp
/cdrom/cdrom0/sun/rwp.devlink .”.
e. Execute “rwddi -a”.
JTAG Parallel Port Hardware
C-5
C-6
RISCWatch Debugger Installation Guide
Index
A
AIX 4 operating system 3-9
C
OS Open target
RS/6000 3-11
Sun 4-8
Windows 2-8
crossover cable A-1
P
E
processor probe
existing Ethernet setup 2-5, 3-5, 4-1
Ethernet crossover cable A-1
Ethernet setup
processor probe 2-5, 3-5, 4-1
H
hardware installation
JTAG parallel port target C-1
other JTAG hardware B-1
RS/6000 3-1
JTAG Ethernet target 3-1
network connection 3-5
OS Open target 3-11
TCP/IP setup 3-7
Sun 4-1
JTAG Ethernet target 4-1
network connection 4-5
OS Open target 4-8
TCP/IP setup 4-6
Windows 2-1
JTAG Ethernet target 2-1
network connection 2-5
OS Open target 2-8
setup TCP/IP 2-6
J
JTAG Ethernet target
other hardware B-1
RS/6000 3-1
Sun 4-1
Windows 2-1
JTAG parallel port target C-1
O
operating systems
AIX 4 3-9
Windows 2-9
R
RISCWatch environment
Windows setup 2-10
RS/6000
hardware installation 3-1, 3-5, 3-7, 3-11
serial port setup 3-8
set RISCWatch environment 3-13
software installation 3-11
S
serial port setup
RS/6000 3-8
Sun 4-6
set RISCWatch environment
RS/6000 3-13
Sun 4-10
Windows 2-10
software installation
RS/6000 3-11
Sun 4-8
Windows 2-9, 2-10
Sun
hardware installation 4-1
serial port setup 4-6
set RISCWatch environment 4-10
software installation 4-8
T
TCP/IP setup
RS/6000 3-7
Sun 4-6
Windows 2-6, 2-10
V
verifying your network 3-13
Index
X-1
W
Windows 2-9
hardware installation 2-1, 2-5, 2-8
JTAG Ethernet target
hardware 2-1
software installation 2-9
TCP/IP setup 2-10
X-2
RISCWatch Debugger Installation Guide