Texas Instruments TMS470R1x manual Related Documentation From Texas Instruments

Page 6

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 direc- tory.

-In syntax descriptions, the instruction, command, or directive is in a bold typeface font and parameters are in an italic typeface. Portions of a syntax that are in bold should be entered as shown; portions of a syntax that are in italics describe the type of information that should be entered.

Here is an example of a command that you might use: mkdir tool_dir

In this example, you would type mkdir, as shown, and replace tool_dir with the name of your directory.

-Square brackets ( [ and ] ) identify an optional parameter. If you use an op- tional parameter, you specify the information within the brackets; you don't enter the brackets themselves. Here's an example of a command that has optional parameters:

SET C_DIR=pathname1 [;pathname2 . . .]

Setting the C_DIR environment variable allows you to specify one or more pathnames for the C compiler to search.

Related Documentation From Texas Instruments

The following books describe the TMS470R1x and related support tools. To obtain a copy of any of these TI documents, call the Texas Instruments Litera- ture Response Center at (800) 477±8924. When ordering, please identify the book by its title and literature number.

TMS470R1x Assembly Language Tools User's Guide (literature number SPNU118) describes the assembly language tools (assembler, linker, and other tools used to develop assembly language code), assembler directives, macros, common object file format, and symbolic debugging directives for the TMS470R1x devices.

TMS470R1x Optimizing C Compiler User's Guide (literature number SPNU119) describes the TMS470R1x C compiler. This C compiler accepts ANSI standard C source code and produces assembly language source code for the TMS470R1x devices.

iv

Image 6
Contents Getting Started Guide SPNU117B TMS470R1x Code Generation Tools Getting Started Guide Important Notice About This Manual Notational ConventionsRelated Documentation From Texas Instruments Set PATH=c\tooldir%PATH%SET CDIR=pathname1 pathname2 Trademarks If You Need Assistance North America, South America, Central AmericaContents Setting Up the Code Generation Tools With SunOS Defines terms and acronyms used in this book Page Setting Up the Code Generation Tools With DOS or Windows Hardware checklist Software checklistSystem Requirements Installing the tools on Windows 3.1x systems Installing the Code Generation ToolsInstalling the tools on DOS systems InstallSetting Up the Code Generation Environment Adir Cdir Coption TMP\tooldir Set ADIR=pathname1 pathname2Setting default shell options Coption TMS470R1x Assembly Language Tools Users GuideSet COPTION=±qs ±z Resetting defined environment variables Specifying a temporary file directory TMPVerifying that the environment variables are set Where to Go From Here Performance ConsiderationsChapter TMS470R1x Code Generation Tools \setup.exe These variables are set up in the registry under \tooldir Set COPTION=option1 option2 Set variablename= Set ADIR=Where to Go From Here Setting Up the Code Generation Tools With SunOS Disk space Mount ±rt hsfs /dev/sr0 /cdrom exit Cd /cdrom/sunos Boot ±rMounting the CD-ROM Mount ±rF hsfs /dev/sr0 /cdrom exit Cd /cdrom/cdrom0/sunosUmount /cdrom eject /dev/sr0 exit Copying the filesUnmounting the CD-ROM Cd ejectSetting Up the Code Generation Environment Setenv Adir ºpathname1 pathname2 . . .º Yourpathname /tooldirSet path=/yourpathname /tooldir $path ADIR=ºpathname1 pathname2 . . .º export AdirSetenv Cdir ªpathname1 pathname2 . . .º CDIR=ªpathname1 pathname2 . . .º export CdirSetenv Coption º±qs ±zº TMP=º/tempº export TMP Reinitializing your shellSetenv TMP º/tempº Source ~/.cshrcTo verify that the environment variables are set, enter Setting Up the Code Generation Tools on an HP Workstation An HP 9000 Series 700 PA-RISC computer Mount ±rt cdfs /dev/dsk/yourcdromdevice /cdrom exit Cd /cdrom/hpPATH=tooldir$PATH Setting up the software tools using a C shellSetting up the software tools using a Korn shell Umount /cdrom exitSetting Up the Code Generation Environment Identifying alternate directories for the assembler Adir Setenv Adir ºpathname1 pathname2 … ºADIR=ºpathname1 pathname2 … º export Adir Identifying alternate directories for the compiler Cdir Setenv Cdir ªpathname1 pathname2 . . .ºSpecifying a temporary file directory TMP Unsetenv variable name Where to Go From Here Getting Started With Code Generation Tools Getting Started With the Assembler and Linker Example 5±2. file2.asmGetting Started With the Code Generation Tools Example 5±4. Output Map File, lnker2.map Example 5±5. Sample Linker Command File, linker2.cmd Entry Point Symbol Memory Configuration Getting Started With the C Compiler Cl470 ±o ±mt funtionCl470 ±o ±k function Cl470 ±s function ±z lnk32.cmd ±o function.out Release Notes Media Contents ±2. Media Contents for PCs Release Enhancements General enhancementsAssembler enhancements Compiler enhancements Page Troubleshooting DOS Systems Troubleshooting in the Protected-Mode Environment Error Messages PMINFO32.EXE programTable A±1. Pminfo Fields Kernel Error Messages Action Recopy the file from the source mediaAction Make more memory available and try again Action Reinstall and run the tools on a 386 or later PC Action Contact technical supportExecution Action Rerun the program and/or restart your computerIncrease the Dpmimemorylimit in the DOS box set Cause this errorMemory is available to non-Windows programs. Under OS/2 TingsDOS/4G Error Messages Action Free some memory for the DOS/4G applicationAction Make sure that the filename was spelled correctly DOS/4G Error Messages Glossary Glossary Glossary B-3 Page Index Index MS-DOS Pminfo Setup.exe For DOS systems For Windows 3.1x systems Windows 95/NT systems Index-6 Important Notice