Texas Instruments TMS470R1x manual Glossary B-3

Page 75

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. Calls to DOS may involve switching from protected to real mode. DOS real-mode tools are no longer supported by the TMS470R1x code generation tools.

S

shell program: A utility that lets you compile, assemble, and optionally link in one step. The shell runs one or more source modules through the com- piler (including the parser, optimizer, and code generator), the assem- bler, and the linker.

structure: A collection of one or more variables grouped together under a single name.

swap file: The file where virtual memory (secondary memory) is allocated on the hard disk.

V

veneer: A sequence of instructions that serves as an alternate entry point into a routine if a state change is required.

virtual memory: The ability of a program to use more memory than a computer actually has available as RAM. This is accomplished by using a swap file on disk to augment RAM. When RAM is not sufficient, part of the program is swapped out to a disk file until it is needed again. The combination of the swap file and available RAM is the virtual memory. The TMS470R1x tools use the DOS/4GW memory extender to provide virtual-memory management (VMM). This memory extender is not pro- vided as an executable file but is embedded in several of the tools shipped by TI. Contact technical support for more information.

Glossary B-3

Image 75

Contents Getting Started Guide SPNU117B TMS470R1x Code Generation Tools Getting Started Guide Important Notice Notational Conventions About This ManualRelated Documentation From Texas Instruments Set PATH=c\tooldir%PATH%SET CDIR=pathname1 pathname2 Trademarks North America, South America, Central America If You Need AssistanceContents 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 Install Installing the Code Generation ToolsInstalling the tools on DOS systems Installing the tools on Windows 3.1x systemsAdir Cdir Coption TMP Setting Up the Code Generation EnvironmentSet ADIR=pathname1 pathname2 \tooldirSetting 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 Performance Considerations Where to Go From HereChapter TMS470R1x Code Generation Tools \setup.exe These variables are set up in the registry under \tooldir Set COPTION=option1 option2 Set ADIR= Set variablename=Where to Go From Here Setting Up the Code Generation Tools With SunOS Disk space Mount ±rF hsfs /dev/sr0 /cdrom exit Cd /cdrom/cdrom0/sunos Boot ±rMounting the CD-ROM Mount ±rt hsfs /dev/sr0 /cdrom exit Cd /cdrom/sunosCd eject Copying the filesUnmounting the CD-ROM Umount /cdrom eject /dev/sr0 exitSetting Up the Code Generation Environment ADIR=ºpathname1 pathname2 . . .º export Adir Yourpathname /tooldirSet path=/yourpathname /tooldir $path Setenv Adir ºpathname1 pathname2 . . .ºCDIR=ªpathname1 pathname2 . . .º export Cdir Setenv Cdir ªpathname1 pathname2 . . .ºSetenv Coption º±qs ±zº Source ~/.cshrc Reinitializing your shellSetenv TMP º/tempº TMP=º/tempº export TMPTo 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 Cd /cdrom/hp Mount ±rt cdfs /dev/dsk/yourcdromdevice /cdrom exitUmount /cdrom exit Setting up the software tools using a C shellSetting up the software tools using a Korn shell PATH=tooldir$PATHSetting Up the Code Generation Environment Identifying alternate directories for the assembler Adir Setenv Adir ºpathname1 pathname2 … ºADIR=ºpathname1 pathname2 … º export Adir Setenv Cdir ªpathname1 pathname2 . . .º Identifying alternate directories for the compiler CdirSpecifying a temporary file directory TMP Unsetenv variable name Where to Go From Here Getting Started With Code Generation Tools Example 5±2. file2.asm Getting Started With the Assembler and LinkerGetting 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 PMINFO32.EXE program Error MessagesTable A±1. Pminfo Fields Kernel Error Messages Action Recopy the file from the source mediaAction Make more memory available and try again Action Contact technical support Action Reinstall and run the tools on a 386 or later PCAction Rerun the program and/or restart your computer ExecutionTings Cause this errorMemory is available to non-Windows programs. Under OS/2 Increase the Dpmimemorylimit in the DOS box setDOS/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