Texas Instruments TMS470R1x manual Identifying alternate directories for the assembler Adir

Page 44

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 .profile file (for Bourne or Korn shells) to change the path information, add the following to the end of the path statement:

/your_pathname /tool_dir

-If you set the path statement from the command line, use this format:

J For C shells:

set path=(/your_pathname /tool_dir $path)

J For Bourne or Korn shells: PATH=/your_pathname /tool_dir $PATH

The addition of $path or $PATH ensures that this path statement does not undo the path statements in the .cshrc or .profile file.

Identifying alternate directories for the assembler (A_DIR)

The assembler uses the A_DIR environment variable to name alternative directories for the assembler to search. To set the A_DIR environment vari- able, use this syntax:

-For C shells:

setenv A_DIR ºpathname1 [;pathname2 ]º

-For Bourne or Korn shells:

A_DIR=ºpathname1 [;pathname2 ]º export A_DIR

(Be sure to enclose the directory names within quotes.)

The pathnames are directories that contain copy/include files or macro librar- ies. You can separate the pathnames with a semicolon or a blank. Once you set A_DIR, you can use the .copy, .include, or .mlib directive in assembly source without specifying path information.

If the assembler does not find the file in the directory that contains the current source file or in directories named by the ±i option (which names alternate directories), it searches the paths named by the A_DIR environment variable. 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.

4-6

Image 44
Contents Getting Started Guide SPNU117B TMS470R1x Code Generation Tools Getting Started Guide Important Notice About This Manual Notational ConventionsSET CDIR=pathname1 pathname2 Related Documentation From Texas InstrumentsSet PATH=c\tooldir%PATH% 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 System Requirements Hardware checklistSoftware checklist Installing the Code Generation Tools Installing the tools on DOS systemsInstalling the tools on Windows 3.1x systems InstallSetting Up the Code Generation Environment Adir Cdir Coption TMP\tooldir Set ADIR=pathname1 pathname2Set COPTION=±qs ±z Setting default shell options CoptionTMS470R1x Assembly Language Tools Users Guide Verifying that the environment variables are set Resetting defined environment variablesSpecifying a temporary file directory TMP 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 Boot ±r Mounting the CD-ROMMount ±rt hsfs /dev/sr0 /cdrom exit Cd /cdrom/sunos Mount ±rF hsfs /dev/sr0 /cdrom exit Cd /cdrom/cdrom0/sunosCopying the files Unmounting the CD-ROMUmount /cdrom eject /dev/sr0 exit Cd ejectSetting Up the Code Generation Environment Yourpathname /tooldir Set path=/yourpathname /tooldir $pathSetenv Adir ºpathname1 pathname2 . . .º ADIR=ºpathname1 pathname2 . . .º export AdirSetenv Cdir ªpathname1 pathname2 . . .º CDIR=ªpathname1 pathname2 . . .º export CdirSetenv Coption º±qs ±zº Reinitializing your shell Setenv TMP º/tempºTMP=º/tempº export TMP 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/hpSetting up the software tools using a C shell Setting up the software tools using a Korn shellPATH=tooldir$PATH Umount /cdrom exitSetting Up the Code Generation Environment ADIR=ºpathname1 pathname2 … º export Adir Identifying alternate directories for the assembler AdirSetenv Adir ºpathname1 pathname2 … º 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 Cl470 ±o ±k function Getting Started With the C CompilerCl470 ±o ±mt funtion Cl470 ±s function ±z lnk32.cmd ±o function.out Release Notes Media Contents ±2. Media Contents for PCs Assembler enhancements Release EnhancementsGeneral enhancements Compiler enhancements Page Troubleshooting DOS Systems Troubleshooting in the Protected-Mode Environment Error Messages PMINFO32.EXE programTable A±1. Pminfo Fields Action Make more memory available and try again Kernel Error MessagesAction Recopy the file from the source media Action Reinstall and run the tools on a 386 or later PC Action Contact technical supportExecution Action Rerun the program and/or restart your computerCause this error Memory is available to non-Windows programs. Under OS/2Increase the Dpmimemorylimit in the DOS box set TingsAction Make sure that the filename was spelled correctly DOS/4G Error MessagesAction Free some memory for the DOS/4G application 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