TMS470R1x Code Generation Tools Release 1.
Printed in U.S.A.
TMS470R1x Code Generation Tools Getting Started Guide Release 1.
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. TI warrants performance of its semiconductor products and related software to the specifications applicable at the time of sale in accordance with TI’s standard warranty.
Preface Read This First About This Manual The TMS470R1x Code Generation Tools Getting Started Guide tells you how to install release 1.20 of the TMS470R1x code generation tools on your system.
Notational Conventions / Related Documentation From Texas Instruments Here is an example of a command that you might enter: set PATH=c:\tool_dir;%PATH% To change your path statement to use the tools, enter the command text as shown in bold and replace tool_dir with the name of your tools directory. - In syntax descriptions, the instruction, command, or directive is in a bold typeface font and parameters are in an italic typeface.
Related Documentation From Texas Instruments / Trademarks TMS470R1x C Source Debugger User’s Guide (literature number SPNU124) describes the TMS470R1x emulator and simulator versions of the C source debugger interface. This book discusses various aspects of the debugger interface, including window management, command entry, code execution, data management, and breakpoints. It also includes a tutorial that introduces basic debugger functionality.
If You Need Assistance If You Need Assistance . . . - - - World-Wide Web Sites TI Online Semiconductor Product Information Center (PIC) Microcontroller Home Page http://www.ti.com http://www.ti.com/sc/docs/pic/home.htm http://www.ti.com/sc/micro North America, South America, Central America Product Information Center (PIC) (972) 644-5580 TI Literature Response Center U.S.A. (800) 477-8924 Software Registration/Upgrades (214) 638-0333 U.S.A. Factory Repair/Hardware Upgrades (281) 274-2285 U.S.
Contents Contents 1 Setting Up the Code Generation Tools With DOS or Windows 3.1x . . . . . . . . . . . . . . . . . . 1-1 Provides installation instructions for PCs running DOS or Windows 3.1x. 1.1 1.2 1.3 1.4 1.5 2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software checklist . . . .
Contents 3 Setting Up the Code Generation Tools With SunOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Provides installation instructions for the code generation tools for SPARCstations running SunOS. 3.1 3.2 3.3 3.4 4 Setting Up the Code Generation Tools on an HP Workstation . . . . . . . . . . . . . . . . . . . . . . . 4-1 Provides installation instructions for HP 9000 Series 700 PA-RISC computers running HP-UX. 4.1 4.2 4.3 4.4 viii System Requirements . . . . . . . . . .
Contents 5 Getting Started With the Code Generation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Provides an overview of how to invoke and use the assembler, linker, and compiler. 5.1 5.2 6 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Describes the media contents and the enhancements for this release. 6.1 6.2 A Media Contents . . . . . . . . . . . . . . . . . .
x
Chapter 1 Setting Up the Code Generation Tools With DOS or Windows 3.1x This chapter helps you install release 1.20 of the TMS470R1x code generation tools and set up your code-development environment on a 32-bit x86-based or Pentium PC running MS-DOS, PC-DOS, or Windows 3.1x. These tools include an optimizing C compiler and a full set of assembly language tools for developing and manipulating assembly language and object (executable) code.
System Requirements 1.1 System Requirements To install and use the code generation tools, you need the items listed in the following hardware and software checklists.
Installing the Code Generation Tools 1.2 Installing the Code Generation Tools This section helps you install the code generation tools on your hard-disk system. The code generation tools package is shipped on CD-ROM. The installation instructions vary according to your operating system. Installing the tools on DOS systems To install the tools on a DOS system, follow these steps: 1) Insert the TMS470R1x Code Generation Tools CD-ROM into your CD-ROM drive.
Setting Up the Code Generation Environment 1.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environment variables that set certain software tool parameters you normally use. An environment variable is a special system symbol that you define and associate to a string. A program uses this symbol to find or obtain certain types of information.
Setting Up the Code Generation Environment Identifying the directory that contains the executable files (PATH statement) You must include the tool_dir directory in your PATH statement so that you can specify the assembler and compiler tools without specifying the name of the directory that contains the executable files. - If you modify your autoexec.
Setting Up the Code Generation Environment Setting default shell options (C_OPTION) You might find it useful to set the compiler, assembler, and linker shell default options using the C_OPTION environment variable. If you do this, the shell uses the default options and/or input filenames that you name with C_OPTION every time you run the shell.
Setting Up the Code Generation Environment Specifying a temporary file directory (TMP) The compiler shell program creates intermediate files as it processes your program. By default, the shell puts intermediate files in the current directory. However, you can name a specific directory for temporary files by using the TMP environment variable. Using the TMP environment variable allows use of a RAM disk or other file systems.
Performance Performance Considerations Considerations / Where to Go From Here 1.4 Performance Considerations You may notice a speed degradation when you use the code generation tools with DOS or Windows 3.1x. This speed degradation may occur when you use DOS with the tools to get appropriate host memory support. If you encounter error messages when you use the tools on a PC with DOS, run PMINFO to determine your system configuration before you contact technical support.
Chapter 2 Setting Up the Code Generation Tools With Windows 95 and Windows NT This chapter helps you install release 1.20 of the TMS470R1x code generation tools and set up your code-development environment on a 32-bit x86-based or Pentium PC running Windows 95 or Windows NT. These tools include an optimizing C compiler and a full set of assembly language tools for developing and manipulating assembly language and object (executable) code.
System Requirements 2.1 System Requirements To install and use the code generation tools, you need the items listed in the following hardware and software checklists.
Installing the Code Generation Tools 2.2 Installing the Code Generation Tools This section helps you install the code generation tools on your hard-disk system. The code generation tools package is shipped on CD-ROM. To install the tools on a PC running Windows 95 or Windows NT, follow these steps: 1) Insert the TMS470R1x Code Generation Tools CD-ROM into your CDROM drive. 2) Start Windows. 3) If you are running Windows 95, select Run from the Start menu.
Setting Up the Code Generation Environment 2.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environment variables that set certain software tool parameters you normally use. An environment variable is a special system symbol that you define and assign to a string. A program uses this symbol to find or obtain certain types of information.
Setting Up the Code Generation Environment Identifying the directory that contains the executable files (PATH statement) You must include the tool_dir directory in your PATH statement so that you can specify the assembler and compiler tools without specifying the name of the directory that contains the executable files. - You can change the path information in one of the following ways: J J If you are running Windows 95, modify your autoexec.
Setting Up the Code Generation Environment Identifying alternate directories for the compiler to search (C_DIR) The compiler uses the C_DIR environment variable to name alternate directories that contain #include files and function libraries. To set the C_DIR environment variable, use this syntax: set C_DIR=pathname1 [;pathname2 . . .] The pathnames are directories that contain #include files or libraries (such as stdio.h). You can separate the pathnames with a semicolon or with a blank.
Setting Up the Code Generation Environment For more information about shell options, see the TMS470R1x Optimizing C Compiler User’s Guide. For more information about linker options, see the TMS470R1x Assembly Language Tools User’s Guide. Specifying a temporary file directory (TMP) The compiler shell program creates intermediate files as it processes your program. By default, the shell puts intermediate files in the current directory.
Where to Go From Here 2.4 Where to Go From Here Your code generation tools are now installed on your Windows 95 or Windows NT system. Now you should do each of the following tasks: - 2-8 Turn to Chapter 5, Getting Started With the Code Generation Tools. This chapter provides you with an overview of how to invoke and use the assembler, linker, and compiler. Read Chapter 6, Release Notes. This chapter explains the new features included in release 1.20 of the code generation tools.
Chapter 3 Setting Up the Code Generation Tools With SunOS This chapter helps you install release 1.20 of the TMS470R1x code generation tools and set up your code-development environment on a SPARCstation running SunOS version 4.1.x (or higher) or Solaris version 2.5.x (or higher). These tools include an optimizing C compiler and a full set of assembly language tools for developing and manipulating assembly language and object (executable) code.
System Requirements 3.1 System Requirements To install and use the code generation tools, you need the items in the following hardware and software checklists. Hardware checklist Host SPARCstation compatible system with a SPARCstation 2 class or higher performance Display Monochrome or color monitor (color recommended) Disk space 4M bytes of disk space Required hardware CD-ROM drive Optional hardware Mouse Software checklist 3-2 Operating system SunOS version 4.1.
Installing the Code Generation Tools 3.2 Installing the Code Generation Tools This section helps you install the code generation tools on your hard-disk system. The software package is shipped on a CD-ROM. To install the tools on a SPARCstation running SunOS or Solaris, you must mount the CD-ROM, copy the files to your system, and unmount the CD-ROM. Note: If you are running SunOS 4.1.x, 5.0, or 5.1, you must have root privileges to mount or unmount the CD-ROM.
Installing the Code Generation Tools Copying the files Be sure you are not logged on as root. After you mount the CD-ROM, you must create the directory that will contain the tools software and copy the software to that directory. 1) Create a tools directory on your hard disk. To create this directory, enter: mkdir /your_pathname /tool_dir 2) Copy the files from the CD-ROM to your hard-disk system: cp –r * /your_pathname /tool_dir Unmounting the CD-ROM You must unmount the CD-ROM after copying the files.
Setting Up the Code Generation Environment 3.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environment variables that set certain software tool parameters you normally use. An environment variable is a special system symbol that you define and assign to a string. A program uses this symbol to find or obtain certain types of information.
Setting Up the Code Generation Environment Identifying the directory that contains the executable files (path statement) You must include the tool_dir directory in your path statement so that you can specify the assembler and compiler tools without specifying the name of the directory that contains the executable files. - If you modify your .cshrc file (for C shells) or .
Setting Up the Code Generation Environment For more information on the –i option, see the TMS470R1x Assembly Language Tools User’s Guide or the TMS470R1x Optimizing C Compiler User’s Guide. Identifying alternate directories for the compiler to search (C_DIR) The compiler uses the C_DIR environment variable to name alternate directories that contain #include files and function libraries. To set the C_DIR environment variable, use this syntax: - For C shells: setenv C_DIR “pathname1 [;pathname2 . . .
Setting Up the Code Generation Environment (Be sure to enclose the options within quotes.) Environment variable options are specified in the same way and have the same meaning as they do on the command line.
Setting Up the Code Generation Environment To set the TMP environment variable, use this syntax: - For C shells: setenv TMP ”pathname” For Bourne or Korn shells: TMP=”pathname” export TMP (Be sure to enclose the directory name within quotes.
Where Here Settingto UpGo theFrom Code Generation Environment / Where to Go From Here Verifying that the environment variables are set To verify that the environment variables are set, enter: set This command lists the path and environment variables and their current values. 3.4 Where to Go From Here Your code generation tools are now installed. Now you should do each of the following tasks: - 3-10 Go to Chapter 5, Getting Started With the Code Generation Tools.
Chapter 4 Setting Up the Code Generation Tools on an HP Workstation This chapter helps you install release 1.20 of the TMS470R1x code generation tools and set up your code-development environment on an HP 9000 Series 700 PA-RISC computer with HP-UX 9.0x. These tools include an optimizing C compiler and a full set of assembly language tools for developing and manipulating assembly language and object (executable) code.
System Requirements 4.1 System Requirements To install and use the code generation tools, you need the items in the following hardware and software checklists. Hardware checklist Host An HP 9000 Series 700 PA-RISC computer Display Monochrome or color monitor (color recommended) Disk space 4M bytes of disk space Required hardware CD-ROM drive Optional hardware Mouse Software checklist 4-2 Operating system HP-UX 9.
Installing the Code Generation Tools 4.2 Installing the Code Generation Tools This section helps you install the code generation tools on your hard-disk system. The software package is shipped on a CD-ROM. To install the tools on an HP workstation, you must mount the CD-ROM, copy the files to your system, and unmount the CD-ROM. Note: If you are running HP-UX 9.0x, you must have root privileges to mount or unmount the CD-ROM. If you do not have root privileges, get help from your system administrator.
Installing the Code Generation Tools Setting up the software tools using a C shell If you are using a C shell, enter the following: setenv C_DIR ”tool_dir” setenv A_DIR ”tool_dir” set path=(tool_dir $path) You can move the setenv and set path commands into your .login or .cshrc file to avoid entering these commands each time you invoke a new shell.
Setting Up the Code Generation Environment 4.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environment variables that set certain software tool parameters you normally use. An environment variable is a special system symbol that you define and assign to a string. A program uses this symbol to find or obtain certain types of information.
Setting Up the Code Generation Environment Identifying the directory that contains the executable files (path statement) You must include the tool_dir directory in your path statement so that you can specify the assembler and compiler tools without specifying the name of the directory that contains the executable files. - If you modify your .cshrc file (for C shells) or .
Setting Up the Code Generation Environment Identifying alternate directories for the compiler (C_DIR) The compiler uses the C_DIR environment variable to name alternate directories that contain #include files and libraries. To set the C_DIR environment variable, use this syntax: - For C shells: setenv C_DIR “pathname1 [;pathname2 . . .]” - For Bourne or Korn shells: C_DIR=“pathname1 [;pathname2 . . .]” export C_DIR (Be sure to enclose the directory names within quotes.
Setting Up the Code Generation Environment Environment variable options are specified in the same way and have the same meaning as they do on the command line.
Setting Up the Code Generation Environment To set the TMP environment variable, use this syntax: - For C shells: setenv TMP ”pathname” For Bourne or Korn shells: TMP=”pathname” export TMP (Be sure to enclose the directory name within quotes.
Where Here Settingto UpGo theFrom Code Generation Environment / Where to Go From Here Verifying that the environment variables are set To verify that the environment variables are set, enter: set This command lists the path and environment variables and their current values. 4.4 Where to Go From Here Your code generation tools are now installed. Now you should do each of the following tasks: - 4-10 Go to Chapter 5, Getting Started With the Code Generation Tools.
Chapter 5 Getting Started With the Code Generation Tools This chapter helps you start using the assembler, linker, and compiler by providing a quick walkthrough of these tools. For more information about invoking and using these tools, see the TMS470R1x Assembly Language Tools User’s Guide and the TMS470R1x Optimizing C Compiler User’s Guide. Topic Page 5.1 Getting Started With the Assembler and Linker . . . . . . . . . . . . . . . . . 5-2 5.2 Getting Started With the C Compiler . . . . . . . . . . .
Getting Started With the Assembler and Linker 5.1 Getting Started With the Assembler and Linker This section provides a quick walkthrough of the assembler and linker so that you can get started without reading the entire TMS470R1x Assembly Language Tools User’s Guide. Example 5–1 through Example 5–6 show the most common methods for invoking the assembler and linker. 1) Create two short source files to use for the walkthrough; call them file1.asm and file2.asm. (See Example 5–1 and Example 5–2.
Getting Started With the Assembler and Linker 3) Now enter the following command to assemble file2.asm: asm470 file2.asm –l This time, the assembler creates an object file called file2.obj. The –l (lowercase L) option tells the assembler to create a listing file; the listing file for this example is called file2.lst. It is not necessary to create a listing file, but it gives you information and assures you that the assembly has resulted in the desired object code.
Getting Started With the Assembler and Linker Example 5–4. Output Map File, lnker2.map ***************************************************** TMS470 COFF Linker Version 1.20 ***************************************************** Sat Feb 8 15:24:43 1997 OUTPUT FILE NAME: ENTRY POINT SYMBOL: 0 SECTION ALLOCATION MAP output section –––––––– .
Getting Started With the Assembler and Linker The two files, file1 and file2, can be linked together with or without a command file. However, using a command file allows you to configure your memory using the MEMORY and SECTIONS directives: - The MEMORY directive lets you specify a model of target memory so that you can define the types of memory your system contains and the address ranges they occupy.
Getting Started With the Assembler and Linker Example 5–6. Linker Map File (linker2.map) Linked Using a Linker Command File ***************************************************** TMS470 COFF Linker Version 1.20 ***************************************************** Sat Feb 8 15:36:45 1997 OUTPUT FILE NAME:
Getting Started With the C Compiler 5.2 Getting Started With the C Compiler The TMS470R1x C compiler consists of many phases, including parsing, optimization, and code generation. The simplest way to compile is to use the shell program, which is included with the compiler. This section provides a quick walkthrough so that you can get started without reading the entire TMS470R1x Optimizing C Compiler User’s Guide. 1) Create a sample file called function.
Getting Started With the C Compiler 3) Also by default, the shell creates a COFF object file as output; however, if you use the –z option, the output is an executable object module. The following examples show two ways of creating an executable object module: a) The example in step 2 creates an object file called function.obj. To create an executable object module, run the linker separately by invoking lnk470 as in the following example: lnk470 –c function.obj lnk32.cmd –o function.out –l rts32.
Chapter 6 Release Notes This chapter describes the media contents of the TMS470R1x tools kit. The tools are supported on SPARCstations, HP workstations, and PCs with DOS, Windows 3.1x, Windows 95, or Windows NT. This chapter also contains documentation of tools and features that are new or have been changed since the last release. Topic Page 6.1 Media Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 6.2 Release Enhancements . . . . . . . . . .
Media Contents 6.1 Media Contents The CD-ROM included in the TMS470R1x tools kit for SPARCstations and HP workstations contains the files listed in Table 6–1. The CD-ROM included in the TMS470R1x tools kit for PCs contains the files listed in Table 6–2. Table 6–1. Media Contents for SPARCstations and HP Workstations File Description README.
Media Contents Table 6–2. Media Contents for PCs File Description readme.1st Online release bulletin abs470.exe Absolute lister ac470.exe ANSI C parser ar470.exe Archiver asm470.exe Assembler cg470.exe Code generator cl470.exe Compiler shell program clist.exe C source interlist utility hex470.exe Hex conversion utility intvecs.asm Sample interrupt vector setup file lnk470.exe COFF linker lnk16.cmd Sample 16-bit linker command file lnk32.
Release Enhancements 6.2 Release Enhancements Release 1.20 of the TMS470R1x code generation tools contains general enhancements as well as enhancements specific to the assembler and compiler. The following sections list these enhancements. General enhancements The TMS470R1x general enhancements include the following items: - All known bugs have been removed. COFF version 2 is supported. Section names are no longer limited to eight characters, and filenames are no longer limited to 14 characters.
Release Enhancements The section in which the entry point of a C program is defined cannot be marked as a conditionally linked section. The compiler marks all function veneers as conditionally linked. You must link with the –a linker option, which creates an absolute, executable output module, to enable conditional linking. The –j linker option disables conditional linking. For information on the .
6-6
Appendix AppendixAA Troubleshooting DOS Systems DOS/4GW is a memory manager that is embedded into the DOS version of the TMS470R1x code generation tools, so you may occasionally see DOS/4GW error messages while you are using the tools. The executable files for DOS/4GW are not shipped as such, nor is any documentation provided on this tool, except for the list of error messages. Section A.2, Kernel Error Messages, and Section A.
Troubleshooting in the Protected-Mode Environment A.1 Troubleshooting in the Protected-Mode Environment Getting 32-bit programs to execute properly under DOS can be frustrating. Your computer’s configuration and memory management can cause problems that may be difficult to find because many programs are interacting. This list of error messages is reproduced in Section A.2 on page A-5 and Section A.
Troubleshooting in the Protected-Mode Environment The PMINFO32.EXE program Purpose: Run PMINFO.EXE to determine the performance of protected/ real-mode switching and extended memory. Notes: The time-based measurements made by PMINFO may vary slightly from run to run. If this error message appears: DOS/16M error: [17] system software does not follow VCPI or DPMI specifications check for a statement in your CONFIG.SYS containing NOEMS. If such a statement exists, remove it and reboot your computer.
Troubleshooting in the Protected-Mode Environment PMINFO provides the information shown in Table A–1. Table A–1. PMINFO Fields Measurement Purpose CPU performance Shows the CPU processor equivalent and the speed of the CPU (in MHz) According to BIOS Shows the configured memory in DOS and extended memory as provided by the BIOS (interrupts 12h and 15h, function 88h) SETUP Shows the configuration obtained directly from the CMOS RAM as set by the computer’s setup program.
Kernel Error Messages A.2 Kernel Error Messages This section describes error messages from the DOS/16M kernel embedded in the TMS470R1x code generation tools. Kernel error messages can occur because of severe resource shortages, corruption of the executable file, corruption of memory, operating system incompatibilities, or internal errors. All of these messages are quite rare.
Kernel Error Messages 9: cannot allocate tstack Description There is not enough memory to load DOS/4G. Action Make more memory available and try again. 10: cannot allocate memory for GDT Description There is not enough memory to load DOS/4G. Action Make more memory available and try again. 11: no passup stack selectors – GDT too small Description This error indicates an internal error in DOS/4G or an incompatibility with other software. Action Contact technical support.
Kernel Error Messages 17: system software does not follow VCPI or DPMI specifications Description Some memory-resident program has put your 386 or 486 CPU into virtual 8086 mode. This is done to provide special memory services to DOS programs, such as EMS simulation (EMS interface without EMS hardware) or high memory. In this mode, it is not possible to switch into protected mode unless the resident software follows a standard that DOS/16M supports (DPMI, VCPI, and XMS are the most common).
Kernel Error Messages 29: Description Memory was probably corrupted during execution of your program. Writing through an invalid or stale alias selector may cause this error. Action Check your source code for references to variables that are not declared or are no longer in scope. 32: 33: 34: DPMI host error (possibly insufficient memory) DPMI host error (need 64K XMS) DPMI host error (cannot lock stack) Description Memory under DPMI is probably insufficient.
DOS/4G Error Messages A.3 DOS/4G Error Messages DOS/4G errors are more common than kernel errors when using DOS/4G or DOS/4GW with the TMS470R1x code generation tools. They are usually related to an unknown path name, corrupt files, or memory problems. Memory problems can include inadequate memory, poor configuration, or corrupted memory. 1000 ”can’t hook interrupts” Description A DPMI host has prevented DOS/4G from loading. Action Contact technical support.
DOS/4G Error Messages 3301 ”unhandled EMPTYFWD, GATE16, or unknown relocation” 3302 ”unhandled ALIAS16 reference to unaliased object” 3304 ”unhandled or unknown relocation” A-10 Description If your program was built for another platform that supports the LINEXE format, it may contain a construct that DOS/4G does not currently support, such as a call gate. One of these messages may also appear if your program has a problem mixing 16- and 32-bit code. A linker error is another likely cause.
Glossary Appendix AppendixBA Glossary A asm470: The name of the command that invokes the assembler for the TMS470R1x. assembler: A software program that creates a machine-language program from a source file that contains assembly language instructions, directives, and macro definitions. The assembler substitutes absolute operation codes for symbolic operation codes and absolute or relocatable addresses for symbolic addresses.
Glossary DOS/4GW: A memory extender that is bound with the DOS version of the TMS470R1x code generation tools. The executable DOS/4GW file is not shipped separately but is embedded within the other executables. Error messages from DOS/4GW are included in Appendix A, Troubleshooting DOS Systems, to assist you in debugging. If you receive one of these error messages, contact technical support for assistance, and remember that the tools are shipped as object files with the memory extender embedded.
Glossary P pragma: Preprocessor directive that provides directions to the compiler about how to treat a particular statement. protected-mode programs: 32-bit extended DOS programs. These programs require an extended memory manager and run on 80386, 80486, and Pentium based PCs only. Protected-mode programs can use all available RAM on a computer up to 64M bytes. R real-mode: 16-bit native DOS mode. This mode limits the available memory to 640K bytes.
B-4
Index Index @ shell option 6-5 A A_DIR environment variable for DOS systems 1-5 for HP workstations 4-6 for SPARCstations 3-6 to 3-7 for Windows 3.1x systems 1-5 for Windows 95/NT systems 2-5 asm470 definition B-1 invoking 5-2 assembler, definition B-1 assembler walkthrough 5-2 to 5-4 assistance from TI vi CD-ROM (continued) requirements for DOS systems 1-2 for HP workstations 4-2 for SPARCstations 3-2 for Windows 3.
Index D directives MEMORY 5-5 SECTIONS 5-5 directories, software tools for DOS systems 1-5 for HP workstations 4-3, 4-6 for SPARCstations 3-4, 3-6 for Windows 3.1x systems 1-5 for Windows 95/NT systems 2-5 disk space requirements for HP workstations 4-2 for SPARCstations 3-2 display requirements for DOS systems 1-2 for HP workstations 4-2 for SPARCstations 3-2 for Windows 3.
Index I installation, software for DOS systems 1-3 for HP workstations 4-3 to 4-4 for SPARCstations 3-3 for Windows 3.1x systems 1-3 for Windows 95/NT systems 2-3 interlist utility definition B-2 described 5-8 enhancements 6-5 invoking assembler 5-2 to 5-4 compiler 5-7 to 5-8 linker 5-2 to 5-6 modifying PATH statement for DOS systems 1-5 for HP workstations 4-6 for SPARCstations 3-6 for Windows 3.
Index .profile file for HP workstations 4-5 to 4-10 for SPARCstations 3-5 to 3-10 protected-mode environment, troubleshooting programs, definition B-3 A-2 R real-mode, definition B-3 reinitializing .cshrc file 3-9, 4-9 .profile file 3-9, 4-9 shell 3-9, 4-9 related documentation iv requirements. See hardware checklist; software checklist resetting environment variables for DOS systems 1-7 for HP workstations 4-9 for SPARCstations 3-9 for Windows 3.
Index virtual memory, definition W walkthrough assembler 5-2 to 5-4 C compiler 5-7 to 5-8 linker 5-2 to 5-4 B-3 Windows 3.
Index-6
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. TI warrants performance of its semiconductor products and related software to the specifications applicable at the time of sale in accordance with TI’s standard warranty.
