Texas Instruments TMS320C2 Series Installation Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Computer Hardware
  5. TMS320C2 Series
  6. Installation manual
Texas Instruments TMS320C2 Series Installation Manual

Texas Instruments TMS320C2 Series Installation Manual

Pc emulator
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
TMS320C2xx
PC Emulator
1995
Microprocessor Development Systems
Installation
Guide

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Texas Instruments TMS320C2 Series

Summary of Contents for Texas Instruments TMS320C2 Series

  • Page 1 TMS320C2xx PC Emulator Installation Guide 1995 Microprocessor Development Systems...
  • Page 2 Printed in U.S.A., September 1995 SPRU152...
  • Page 3 TMS320C2xx PC Emulator Installation Guide SPRU152 September 1995 Printed on Recycled Paper...
  • Page 4 Running Title—Attribute Reference 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 With OS/2 ......Lists the hardware and software you’ll need to install the XDS510-PC and C source debugger; provides installation instructions for PC systems running OS/2.
  • Page 8 Contents Step 4: Setting Up the Debugger Environment ....... . . 2-10 Invoking the new or modified batch file .
  • Page 9 Running Title—Attribute Reference Figures 1–1 XDS510-PC I/O Switches ............1–2 XDS510-PC Installation .
  • Page 10 Running Title—Attribute Reference Tables 1–1 XDS510-PC Switch Settings ........... . 1–2 Your Switch Settings .
  • Page 11 Chapter 1 Installing the Emulator and C Source Debugger With OS/2 This chapter helps you with the following: Installing the XDS510-PC (the emulation controller interface hardware) in a PC. Installing the TMS320C2xx C source debugger on a PC running OS/2 . When you complete the installation, turn to the TMS320C2xx C Source De- bugger User’s Guide.

  • Page 12: What You'll Need

    What You’ll Need 1.1 What You’ll Need The following checklists detail items that are shipped with the ’C2xx C source debugger and XDS510-PC emulator and additional items you’ll need to use these tools. Hardware checklist host A 32-bit 386-based PC (or higher) or a Pentium PC with an ISA/ EISA bus and a 1.44-megabyte floppy-disk drive memory...
  • Page 13 What You’ll Need † board.dat describes your target system to the debugger. † board.cfg is the default name for the text file that describes your tar- get system to the debugger. If you plan to create a target system that contains anything other than a single ’C2xx, you must make a text file that describes the target system.

  • Page 14: Step 1: Installing The Xds510-Pc In Your Pc

    Step 1: Installing the XDS510-PC in Your PC 1.2 Step 1: Installing the XDS510-PC in Your PC This section contains the hardware installation information for the XDS510-PC emulator. Preparing the XDS510-PC for installation Before you install the XDS510-PC, you must be sure that the board’s switches are set to correctly identify the I/O space that the board can use.The emulator uses 32 bytes of the PC I/O space;...

  • Page 15: Xds510-Pc Switch Settings

    Step 1: Installing the XDS510-PC in Your PC Table 1–1. XDS510-PC Switch Settings Switch # Address Range 0x0240–0x025F 0x0280–0x029F 0x0320–0x033F 0x0340–0x035F Some of the other installation steps require you to know which switch settings you used. If you reset the I/O switches, note the modified settings here for later reference.

  • Page 16: Setting The Xds510-Pc Into Your Pc

    Step 1: Installing the XDS510-PC in Your PC Setting the XDS510-PC into your PC After you’ve prepared the XDS510-PC for installation, follow these steps. 1) Turn off the power to the PC, and unplug the power cord. 2) Remove the cover of your PC. 3) Remove the mounting bracket from an unused 16-bit slot.

  • Page 17: Connecting The Target Cable To The Xds510-Pc

    Step 1: Installing the XDS510-PC in Your PC Figure 1–3. Connecting the Target Cable to the XDS510-PC emulator connection target cable connection XDS510-PC target cable active buffer pod 14-pin keyed connector (connects to target system) Don’t connect or disconnect the target cable while the PC is powered up.

  • Page 18: Step 2: Connecting The Xds510-Pc To Your Target System

    Step 2: Connecting the XDS510-PC to Your Target System 1.3 Step 2: Connecting the XDS510-PC to Your Target System Figure 1–4 shows a typical setup using the XDS510-PC emulator, target cable, and your target system. Figure 1–5 shows how you connect the XDS510-PC emulator and target cable to your target system.

  • Page 19: Step 3: Installing The Debugger Software

    Step 3: Installing the Debugger Software / Step 4: Setting Up the Debugger Environment 1.4 Step 3: Installing the Debugger Software This section explains the process of installing the debugger software on a hard-disk system. 1) Make a backup copy of the OS/2 debugger product disk. (If necessary, refer to the OS/2 manual that came with your computer.) 2) On your hard disk or system disk, create a directory named c2xxhll .

  • Page 20: Invoking The New Or Modified Batch File

    Step 4: Setting Up the Debugger Environment Figure 1–6 (a) shows an example of a config.sys file that contains the sug- gested modifications (highlighted in bold type). Figure 1–6 (b) shows a sample batch file that you could create instead of editing the config.sys file. (For the purpose of discussion, assume that this sample file is named initdb.cmd.) The subsections following the figure explain these modifications.

  • Page 21: Modifying The Path Statement

    Step 4: Setting Up the Debugger Environment Modifying the PATH statement Define a path to the debugger directory. The general format for doing this is: PATH=C:\C2XXHLL; path2 ; path3 ;. . . This allows you to invoke the debugger without specifying the name of the directory that contains the debugger executable file.
  • Page 22 Step 4: Setting Up the Debugger Environment You can use several options when you invoke the debugger. If you use the same options over and over, it’s convenient to specify them with D_OPTIONS. The general format for doing this is: SET D_OPTIONS= [ object filename ] [ debugger options ] (Be careful not to precede the equal sign with a space.) This tells the debugger to load the specified object file and use the speci-...

  • Page 23: Identifying The Correct I/O Switches

    Step 4: Setting Up the Debugger Environment Identifying the correct I/O switches Refer to your entries in Table 1–2 (page 1-5). If you didn’t modify the I/O switches, you can skip this step. If you modified the I/O switch settings, you must use the debugger’s –p option to identify the I/O space that the emulator is using.

  • Page 24: Resetting The Emulator

    Step 4: Setting Up the Debugger Environment Resetting the emulator You must reset the emulator before invoking the debugger. Reset can occur only after you have powered up the target board. You can reset the emulator in one of three ways: Add the following line to the end of your config.sys file (as shown in Figure 1–6 (a) on page 1-10): RUN = C:\C2XXHLL\EMURST.EXE...

  • Page 25: Step 5: Describing Your Target System To The Debugger

    Step 4: Setting Up the Debugger Environment / Step 5: Describing Your Target System to the Debugger Is your port address set correctly? Check to be sure the –p option of the D_OPTIONS environment vari- able matches the I/O address defined by your switch settings (refer to Your Switch Settings , Table 1–2, and Identifying Nondefault I/O Address Space , Table 1–4).

  • Page 26: Step 6: Verifying The Installation

    Step 6: Verifying the Installation 1.7 Step 6: Verifying the Installation To ensure that you have correctly installed the XDS510-PC emulator and de- bugger software, enter this command at the system prompt: EMU2XX C:\C2XXHLL\test –N DEVICE NAME Note that emu2xx refers to the emu2xx and emu2xxo executables. You should see a display similar to this one: Run=F5 Load...

  • Page 27: Installation Error Messages

    Step 6: Verifying the Installation Installation error messages While invoking the debugger, you may see the following message: CANNOT INITIALIZE TARGET SYSTEM ! ! – Check I/O configuration – Check cabling and target power One of several of the following conditions may be the cause; check: Is the target power on? Is the XDS510-PC installed snugly? Is the device installed snugly?
  • Page 28 Step 6: Verifying the Installation Was the –f option specified on the command line or in the D_OPTIONS environment variable (where the default file specified by the –f option is board.dat) specifying a file that the debugger can’t find? If you didn’t provide any path information with the filename, the debug- ger couldn’t find the file in the current directory or in any of the directo- ries listed in the D_DIR environment variable.

  • Page 29: Installing The Emulator And C Source Debugger With Ms-Windows

    Chapter 2 Installing the Emulator and C Source Debugger With MS-Windows This chapter helps you with the following: Installing the XDS510-PC (the emulation controller interface hardware) in a PC. Installing the TMS320C2xx C source debugger on a PC running MS-Windows . When you complete the installation, turn to the TMS320C2xx C Source De- bugger User’s Guide.

  • Page 30: What You'll Need

    What You’ll Need 2.1 What You’ll Need The following checklists detail items that are shipped with the ’C2xx C source debugger and XDS510-PC emulator and additional items you’ll need to use these tools Hardware checklist host A 32-bit 386-based PC (or higher) or a Pentium PC with an ISA/EISA bus and a 1.44-megabyte floppy-disk drive memory Minimum of 8 megabytes...
  • Page 31 What You’ll Need † emu2xxw.exe is a faster version of emu2xxwm.exe for target boards that include only one ’C2xx on the emulation scan path. This file does not work with the XDS511. † emu2xxd.dll is a DLL that the debugger (emu2xxw.exe) uses. This file is for use with target boards that include only one ’C2xx on the emulation scan path.

  • Page 32: Step 1: Installing The Xds510-Pc In Your Pc

    What You’ll Need / Step 1: Installing the XDS510-PC in Your PC † The default configuration is for color monitors; an additional file, mono.clr , can be used for monochrome monitors. When you first start to use the debugger, the default screen configuration should be sufficient for your needs.

  • Page 33: Xds510-Pc I/O Switches

    Step 1: Installing the XDS510-PC in Your PC Figure 2–1. XDS510-PC I/O Switches XDS510-PC default default switch settings Table 2–1. XDS510-PC Switch Settings Switch # Address Range 0x0240–0x025F 0x0280–0x029F 0x0320–0x033F 0x0340–0x035F Some of the other installation steps require you to know which switch settings you used.

  • Page 34: Xds510-Pc Installation

    Step 1: Installing the XDS510-PC in Your PC 1) To minimize the risk of electric shock and fire hazard, be sure that all major components that you interface with Texas Instru- ments devices are limited in energy and certified by one or more of the following agencies: UV, CSA, VDE, or TUV.

  • Page 35: Connecting The Target Cable To The Xds510-Pc

    Step 1: Installing the XDS510-PC in Your PC Figure 2–3. Connecting the Target Cable to the XDS510-PC emulator connection target cable connection XDS510-PC target cable active buffer pod 14-pin keyed connector (connects to target system) Don’t connect or disconnect the target cable while the PC is powered up.

  • Page 36: Typical Setup Using The Xds510-Pc And Your Target System

    Step 2: Connecting the XDS510-PC to Your Target System 2.3 Step 2: Connecting the XDS510-PC to Your Target System Figure 2–4 shows a typical setup using the XDS510-PC emulator, target cable, and your target system. Figure 2–5 shows how you connect the XDS510-PC emulator and target cable to your target system.

  • Page 37: Step 3: Installing The Debugger Software

    Step 3: Installing the Debugger Software 2.4 Step 3: Installing the Debugger Software This section explains the process of installing the debugger software on a hard-disk system. 1) Make a backup copy of the MS-Windows debugger product disk. (If neces- sary, refer to the manual that came with your computer.) 2) On your hard disk or system disk, create a directory named c2xxhll .

  • Page 38: Command Setup For The Debugger

    Step 4: Setting Up the Debugger Environment 2.5 Step 4: Setting Up the Debugger Environment To ensure that your debugger works correctly, you must: Modify the PATH statement to identify the c2xxhll directory. Define environment variables so that the debugger can find the files it needs.
  • Page 39 Step 4: Setting Up the Debugger Environment Figure 2–6. Command Setup for the Debugger (Continued) (b) Sample initdb.bat file to use with the debugger and emulator PATH statement PATH=C:\C2XXHLL;%PATH% SET D_DIR=C:\C2XXHLL Environment variables and SET D_SRC=C:\C2XXCODE I/O space SET D_OPTIONS=–P 280 EMURST Reset the emulator...
  • Page 40 Step 4: 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 three environment variables named D_DIR, D_SRC, and D_OPTIONS. The next three bullets tell you how to set up these environment variables.

  • Page 41: Identifying The Correct I/O Switches

    Step 4: Setting Up the Debugger Environment Table 2–3. Options for Use With D_OPTIONS Option Brief Description –b[b] Select the screen size –c Clear the .bss section –f filename Identify a new board configuration file –i pathname Identify additional directories –min Select the minimal debugging mode –n processor name...

  • Page 42: Resetting The Emulator

    Step 4: Setting Up the Debugger Environment / Step 5: Describing Your Target System to the Debugger Resetting the emulator To reset the emulator, add this line to the autoexec.bat or initdb.bat file: emurst Note: The emurst program resets the ’C2xx emulator only; it doesn’t apply reset to the ’C2xx device on your target board.

  • Page 43: Step 6: Verifying The Emulator Device Driver Installation

    Step 6: Verifying the Emulator Device Driver Installation 2.7 Step 6: Verifying the Emulator Device Driver Installation The emulator device driver enables the debugger to communicate with the emulator. To ensure that the emulator driver is installed correctly, follow these steps: 1) Turn off the power to the ’C2xx target board.

  • Page 44: Step 7: Verifying The Debugger And Emulator Installation

    Step 7: Verifying the Debugger and Emulator Installation 2.8 Step 7: Verifying the Debugger and Emulator Installation To ensure that you have correctly installed the XDS510-PC emulator and de- bugger software, enter this command from the MS-Windows program manag- EMU2XX C:\C2XXHLL\TEST –N CPU_A Note that emu2xx refers to the emu2xx, emu2xxw, and emu2xxwm executables.

  • Page 45: Installation Error Messages

    Step 7: Verifying the Debugger and Emulator Installation Installation error messages While invoking the debugger, you may see the following message: CANNOT INITIALIZE THE TARGET SYSTEM ! ! – Check I/O configuration – Check cabling and target power One of several of the following conditions may be the cause; check: Is the target power on? Is the XDS510-PC installed snugly? Is the device installed snugly?

  • Page 46: Setting Up Icons For The Windows Program Manager

    Step 7: Verifying the Debugger and Emulator Installation / Setting Up Icons for the Windows Program Manager Was the –f option specified on the command line or in the D_OPTIONS environment variable (where the default file specified by the –f option is board.dat) specifying a file that the debugger can’t find? If you didn’t provide any path information with the filename, the debug- ger couldn’t find the file in the current directory or in any of the directo-...
  • Page 47 Setting Up Icons for the Windows Program Manager Step 1: From the Windows Program Manager, select File New. This displays the New Program Object dialog box: Step 2: Select Program Group, then click on the OK button. This displays a dialog box for you to enter the group name: Step 3: Enter TMS320C2xx Debugger as the Description, then click on the OK button.
  • Page 48 This displays the Program Item Properties dialog box. Enter the fol- lowing information for the ’C2xx debugger: After entering this information, click on the OK button. This displays a Texas Instruments icon in your TMS320C2xx Debugger program group. Step 6: You can also put emurst into the TMS320C2xx Debugger program group.

  • Page 49: Release Notes

    Chapter 3 Release Notes If you have used the ’C5x debugging tools, you will find some differences be- tween the ’C5x version of the debugger and the ’C2xx version. This chapter provides an overview of the differences and describes new features of the ’C2xx debugger.

  • Page 50: Differences Between The 'C5X And 'C2Xx Debuggers

    Differences Between the ’C5x and ’C2xx Debuggers / New Features of the ’C2xx Debugger 3.1 Differences Between the ’C5x and ’C2xx Debuggers The ’C2xx version of the emulator does not have all of the analysis features included in the ’C5x version. You cannot use the RUNB (run benchmark) com- mand or the analysis count events features with the ’C2xx version of the emu- lator.
  • Page 51 New Features of the ’C2xx Debugger Minimal debugging mode By default, the debugger automatically displays whatever code is currently running—assembly language or C. A DISASSEMBLY window, CPU register window, MEMORY window, CALLS window, or more windows may be dis- played. The ’C2xx debugger has a minimal debugging mode that displays the COMMAND window, WATCH window, and DISP window only.
  • Page 53 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.

Table of Contents