Texas Instruments TMS3200C3 Series Installation Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Microcontrollers
  5. TMS3200C3 Series
  6. Installation manual
Texas Instruments TMS3200C3 Series Installation Manual

Texas Instruments TMS3200C3 Series Installation Manual

Workstation emulator
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
TMS320C3x
Workstation Emulator
Installation
Guide
1994
Microprocessor Development Systems

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TMS3200C3 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Texas Instruments TMS3200C3 Series

Summary of Contents for Texas Instruments TMS3200C3 Series

  • Page 1 TMS320C3x Workstation Emulator Installation Guide 1994 Microprocessor Development Systems...
  • Page 2 Printed in U.S.A., December 1994 2617676-9741 revision A...
  • Page 3 TMS320C3x Workstation Emulator Installation Guide SPRU130 December 1994 Printed on Recycled Paper...
  • Page 4 IMPORTANT NOTICE Texas Instruments (TI) reserves the right to make changes to its products or to discontinue any semiconductor product or service without notice, and advises its customers to obtain the latest version of relevant information to verify, before placing orders, that the information being relied on is current.
  • Page 5 WARNING This equipment is intended for use in a laboratory test environment only. It generates, uses, and can radiate radio frequency energy and has not been tested for compliance with the limits of computing devices pursuant to subpart J of part 15 of FCC rules, which are designed to provide reasonable protection against radio frequency interference.

  • Page 7: Table Of Contents

    Contents Contents Installing the Emulator and C Source Debugger ........Lists the hardware and software you’ll need to install the workstation emulator and C source debugger;...
  • Page 8 Contents Interpreting the XDS510WS LEDs ..........Provides information about the eight LEDs on the workstation emulator.
  • Page 9 Running Title—Attribute Reference Figures 1–1 Typical Setup of the Emulator on Your Workstation ....... . 1–2 Rear View of the XDS510WS Emulator .
  • Page 10 viii...

  • Page 11: Installing The Emulator And C Source Debugger

    What You’ll Need Chapter 1 Installing the Emulator and C Source Debugger This chapter helps you to install the TMS320C3x XDS510WS emulator and the C source debugger on a SPARCstation running OpenWindows version 3x (or higher) under SunOS version 4.1.x (or higher) or Solaris ver- sion 2.x (or higher).

  • Page 12: What You'll Need

    What You’ll Need 1.1 What You’ll Need The following checklists describe items that you’ll need in order to use your emulator and debugger. Some of these items are shipped with your tools. Hardware checklist host A SPARCstation or 100% compatible system with a cartridge tape drive display Monochrome or color (color is recommended)

  • Page 13: Software Checklist

    What You’ll Need Software checklist operating system OpenWindows version 3.x (or higher) running under SunOS version 4.1.x (or higher) or Solaris version 2.0 (or higher). If you’re using So- laris (also known as SunOS 5.x), you must have the Binary Compati- bility Package (BCP) installed;...

  • Page 14: Step 1: Connecting The Emulator To A Workstation

    Step 1: Connecting the Emulator to Your Workstation 1.2 Step 1: Connecting the Emulator to a Workstation This section contains hardware installation information for the emulator. You must have root access to the host machine you intend to connect to the emulator.

  • Page 15: Rear View Of The Xds510Ws Emulator

    Step 1: Connecting the Emulator to Your Workstation Before you attach the emulator to the workstation, be sure the emulator is working properly. To do this, connect the emulator to the power supply and plug in the power supply (refer to Figure 1–2). Turn on the emulator.

  • Page 16: Locating A Scsi Bus With An Unused Identifier

    Step 1: Connecting the Emulator to Your Workstation Locating a SCSI bus with an unused identifier To continue this installation, you must have root access on the workstation; if you do not, contact your system administrator. Each SCSI controller in the workstation has its own SCSI bus, and a workstation usually has only one SCSI controller (unless you have added additional controller cards).

  • Page 17: Setting The Scsi Id On The Emulator

    Step 1: Connecting the Emulator to Your Workstation Setting the SCSI ID on the Emulator If the SPARCstation is already using SCSI ID 4 (see the previous section on locating SCSI IDs), then you must change the SCSI ID on the emulator. Before resetting the emulator’s SCSI ID, be sure the emulator is not turned on.

  • Page 18: Adding The Emulator To The Scsi Bus

    Step 1: Connecting the Emulator to Your Workstation Adding the Emulator to the SCSI Bus The SCSI bus is a chain with two distinct ends; it is not a loop. Although there may be SCSI devices within your host, the visible chain begins at the host and ends at one of the external SCSI devices.

  • Page 19: Terminating The Scsi Bus

    Step 1: Connecting the Emulator to Your Workstation Figure 1–6. Connector and Switch Location on the Rear of the XDS510WS Emulator on/off switch power supply connector SCSI connectors Terminating the SCSI bus You must terminate the SCSI bus at each end of its chain to reduce signal noise.

  • Page 20: Step 2: Setting Up A Workstation To Recognize The Emulator

    Step 2: Setting Up Your Workstation to Recognize the Emulator 1.3 Step 2: Setting Up a Workstation to Recognize the Emulator This step varies, depending on the operating system you are using: If you have Solaris 2.x, as the root user, enter: halt With the XDS510WS properly connected and powered up, reboot your SPARCstation with the PROM command boot –r.
  • Page 21 Step 2: Setting Up Your Workstation to Recognize the Emulator Note: If the specified directory does not exist or does not contain the specified con- figuration file, then your system was probably installed without modification privileges. Contact your system administrator for help. 2) Copy the current configuration file to a file called EMULATOR: cp filename EMULATOR Replace filename with the name of the current configuration file (see...
  • Page 22 Step 2: Setting Up Your Workstation to Recognize the Emulator Example 1–2.Setting Up the EMULATOR Configuration File # @(#) GENERIC from master 1.28 90/09/21 SMI # This config file describes an generic Sun–4c kernel, including all # possible standard devices and software options. # The following lines include support for all Sun–4c CPU types.
  • Page 23 Step 2: Setting Up Your Workstation to Recognize the Emulator 4) When you have finished editing your EMULATOR file, save the file and exit the vi editor by pressing SHIFT 5) Now, create the EMULATOR directory. Enter: config EMULATOR 6) Once you have created the EMULATOR directory, change your current di- rectory to your newly created directory by entering: cd EMULATOR 7) Now you must compile the new kernel described by your configuration file.

  • Page 24: Step 3: Allowing The Debugger To Access The Emulator

    Step 3: Allowing the Debugger to Access the Emulator / Step 4: Connecting the Emulator to Your Target System 1.4 Step 3: Allowing the Debugger to Access the Emulator The debugger accesses the emulator by reading from and writing to the device driver you defined in the EMULATOR configuration file.

  • Page 25: Step 5: Installing The Debugger Software

    Step 5: Installing the Debugger Software 1.6 Step 5: Installing the Debugger Software This section explains the process of installing the debugger software on your hard disk system. The software package is shipped on a cartridge tape. To install the emulator software, you must restore the directory from the tape. 1) Insert the product tape in a cartridge tape drive.

  • Page 26: Step 6: Making Sure The Emulator Supports The Debugger

    Step 6: Making Sure the Emulator Supports the Debugger 1.7 Step 6: Making Sure the Emulator Supports the Debugger The ROM code for the emulator does not contain the information necessary to debug a processor; that code must be downloaded from the host. This makes it easier to upgrade the emulation software.

  • Page 27: Step 7: Setting Up The Debugger Environment

    Step 7: Setting Up the Debugger Environment 1.8 Step 7: Setting Up the Debugger Environment To ensure that your debugger works correctly, you must: Modify the PATH statement to identify the c3xhll directory. Define environment variables so that the debugger can find the files it needs.

  • Page 28: Setting Up The Environment Variables

    Step 7: Setting Up the Debugger Environment Setting up the environment variables An environment variable is a special system symbol that the debugger uses for finding or obtaining certain types of information. The debugger uses four environment variables; D_DIR, D_SRC, D_OPTIONS, and DISPLAY (X Win- dow System only).
  • Page 29 Step 7: Setting Up the Debugger Environment For example, if you are running the debugger on a machine called opie and you want the ’C3x debugger display to appear on a machine called barney, the DISPLAY setup would be: setenv DISPLAY barney:0 You can also display the debugger on a different machine by using the –d option when invoking the debugger: emu3x –d barney:0...

  • Page 30: Step 8: Verifying The Installation

    0f240000 PUSH IOF 00000088 COMMAND MEMORY 000000 0000004b 00000040 00000041 00000042 000004 00000043 00000044 00000045 00000046 (c) Copyright 1989, Texas Instruments 000008 00000047 00000048 00000049 0000004a Silicon Revision 2 00000c 00000000 00000000 00000000 00000000 Emulator Revision 1 000010 00000000 00000000...

  • Page 31: Using The Debugger With The X Window System

    Using the Debugger With the X Window System 1.10 Using the Debugger With the X Window System If you’re using the X Window System to run the ’C3x debugger, you need to know about the keyboard’s special keys, the debugger fonts, and using the de- bugger on a monochrome monitor.

  • Page 32: Changing The Debugger Font

    Using the Debugger With the X Window System Changing the debugger font You can change the font of the debugger screen by using the xrdb utility and modifying the .Xdefaults file in your root directory. For example, to change the fonts of the ’C3x debugger to Courier, add the following line to the .Xdefaults file: emu3x*font:courier...

  • Page 33: Troubleshooting

    Chapter 2 Troubleshooting This chapter describes some common problems you may encounter while us- ing your emulator or debugger on your workstation. You should be familiar with the procedures described in Chapter 1 before trying to troubleshoot problems with the XDS510WS and its software. Topic Page Problems When Booting Your Workstation...

  • Page 34: Problems When Booting Your Workstation

    Problems When Booting Your Workstation 2.1 Problems When Booting Your Workstation After installing your emulator, the problems listed below may occur when you attempt to boot your workstation. The list includes suggestions for resolving the problems. Your workstation will not boot when connected to your emulator, even if your emulator is not turned on.

  • Page 35: Problems When Resetting The Emulator

    Problems When Resetting the Emulator 2.2 Problems When Resetting the Emulator After you power up the emulator and the workstation, if you have the following problems while attempting to reset the emulator, implement the applicable solutions: When executing the emurst command, you receive this message: emurst file [.out]: You forgot to specify the pathname–filename of the C3x510ws.out file.
  • Page 36 Problems When Resetting the Emulator successfully before executing emurst. The self-test has completed, once the sixth LED from the left is off and the first, second, and fifth LEDs from the left are on. When executing the emurst command, you receive this message: >>...

  • Page 37: Problems When Invoking The Debugger

    Problems When Invoking the Debugger 2.3 Problems When Invoking the Debugger If you encounter these problems when you invoke the debugger, the sug- gested solutions may resolve the problems: You receive the following message when executing the emu3x command: CANNOT INITIALIZE THE TARGET !! –...
  • Page 38 Problems When Invoking the Debugger Add to the .Xdefaults file in your home directory the line: emu3x*font: GoodFontName where GoodFontName is the name of a font that OpenWindows can find. Copy a valid font file onto 7x14.ff. Note: The operating-system window provides operating-system messages. These messages differ from the error messages that you may see in the COMMAND window of the debugger.

  • Page 39: Additional Emulator And Debugger Problems

    Additional Emulator and Debugger Problems 2.4 Additional Emulator and Debugger Problems The operating-system window displays operating-system messages. These messages differ from the error messages that you may see in the COMMAND window of the debugger. If you receive one of these operating-system mes- sages while executing the emurst or the debugger, refer to the following ex- planations.
  • Page 40 Additional Emulator and Debugger Problems In your operating-system window, you receive the following message while executing emu3x or emurst under SunOS 4.1.x: <date> <time> <hostname> vmunix: sd<n>: disk okay or under Solaris 2.x: WARNING: /sbus@1,f8000000/esp@0,800000/sd@<n>,0(sd<n>): disk okay The SPARCstation has reconnected with the XDS510WS after the XDS510WS didn’t respond to the selection.

  • Page 41: Interpreting The Xds510Ws Leds

    Chapter 3 Interpreting the XDS510WS LEDs The TMS320C3x XDS510WS emulator provides status information about its operation through eight LEDs on the front panel of the emulator chassis. Topic Page XDS510WS LED Descriptions XDS510WS LED Reference Chart...

  • Page 42: Xds510Ws Led Descriptions

    XDS510WS LED Descriptions 3.1 XDS510WS LED Descriptions On the front of the XDS510WS is a small panel of LEDs that provide status information during the operation of the emulator (refer to Figure 3–1). Figure 3–1. XDS510WS LEDs XDS510WS LEDs The LEDs are numbered from left to right, starting with LED 1 through LED 8. The three LED conditions are: Meaning LED Symbol...

  • Page 43: Led 3

    XDS510WS LED Descriptions Note: After you apply power to the target, LED 2 remains on until you invoke the debugger. When you invoke the debugger, if LED 2 fails to go off and the debugger fails to start, you should ensure that the emulation cable is firmly and correctly at- tached to both the XDS510WS and the target.

  • Page 44: Leds 7 And 8

    XDS510WS LED Descriptions If the self-test completes successfully, LEDs 4 and 6 will be off and LED 5 will be on: If these three LEDs show this pattern: there has been a communication error. These errors are generally not serious, but if you can’t continue without intervention, cycle the power on the XDS510WS, re-execute emurst, and restart the debugger.

  • Page 45: Xds510Ws Led Reference Chart

    XDS510WS LED Reference Chart 3.2 XDS510WS LED Reference Chart Figure 3–2 shows the standard LED sequences. These patterns allow you to understand quickly the operational status of the emulator and its functions. Figure 3–2. Standard LED Sequences Intermittent Key to LED Status Power-On Sequences before power-on...
  • Page 47 Index Index configuration file confirming 1-15 example 1-13 arrow keys 1-22 locating the name 1-11 assembler 1-3 modifying 1-11 to 1-14 renaming 1-11 to 1-14 copying files cp UNIX command 1-12 UNIX command 1-14 –b debugger option, with D_OPTIONS environment cp UNIX command 1-12, 1-14 variable 1-19 .cshrc file 1-18...
  • Page 48 Index default memory, default map 1-3 memory map 1-3 operating system 1-3 screen configuration file rear view 1-6, 1-10 color displays 1-4 requirements monochrome displays 1-4 cable 1-2 PC systems 1-4 display 1-2 screen sizes 1-4 hardware 1-2 SCSI ID, for the emulator 1-7 power 1-2 software 1-3 directories...
  • Page 49 Index F2 key, mapping 1-22 ipcs UNIX command 2-3 F3 key, mapping 1-22 IPCSEMAPHORE option 1-12, 2-3 F4 key, mapping 1-22 IPCSHMEM option 1-12 F5 key, mapping 1-22 F6 key, mapping 1-22 F7 key, mapping 1-22 kernel F8 key, mapping 1-22 building 1-14 F9 key, mapping 1-22 confirming 1-15...
  • Page 50 Index mono.clr file 1-4 mv UNIX command 1-14 –s debugger option, with D_OPTIONS environment variable 1-19 SCSI bus adding devices to it 1-9 to 1-10 OpenWindows, finding the font file 2-5 terminating the chain 1-10 operating system 1-3 SCSI ID optional files 1-3 assigning 1-7 options...
  • Page 51 Index workstation (continued) connecting emulator 1-9 to 1-10 modifying your configuration file 1-11 to 1-14 utilities modifying your kernel 1-11 to 1-14 emurst 1-3, 1-17, 2-4 problems when booting 2-2 ipcrm 2-3 rebooting 1-14 ipcs –st 2-3 typical setup 1-5 xev 1-22 xmodmap 1-22 xrdb 1-23...
  • Page 52 Index-6...

This manual is also suitable for:

Tms320vc33

Table of Contents