Manuel d'utilisation / d'entretien du produit TMS470R1x du fabricant Texas Instruments
Aller à la page of 83
Getting Started Guide 1997 Microcontroller Products.
Printed in U.S.A., March 1997 M414003-9741 revision B SPNU1 17B.
TMS470R1x Code Generation T ools Getting Started Guide Release 1.20 Literature Number: SPNU1 17B Manufacturing Part Number: M414003-9741 revision B March 1997 Printed on Recycled Paper.
IMPORT ANT NOTICE T exas 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.
iii Preface Read This First About This Manual The TMS470R1x Code Generation T ools Getting Started Guide tells you how to install release 1.20 of the TMS470R1x code generation tools on your sys- tem.
Notational Conventions / Related Documentation From T exas Instruments iv Here is an example of a command that you might enter: set PATH=c: tool_dir ;%PATH% T o 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 .
Related Documentation From T exas Instruments / T rademarks v Read This First TMS470R1x C Source Debugger User ’s Guide (literature number SPNU124) describes the TMS470R1x emulator and simulator versions of the C source debugger interface.
If Y ou Need Assistance vi If Y ou Need Assistance . . . World-W ide Web Sites TI Online http://www .ti.com Semiconductor Product Information Center (PIC) http://www .
Contents vii Contents 1 Setting Up the Code Generation T ools With DOS or Windows 3.1x 1-1 . . . . . . . . . . . . . . . . . . Provides installation instructions for PCs running DOS or Windows 3.1x. 1.1 System Requirements 1-2 . . . . . . . . . . . . .
Contents viii 3 Setting Up the Code Generation T ools With SunOS 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provides installation instructions for the code generation tools for SP ARCstations running SunOS. 3.1 System Requirements 3-2 .
Contents ix Contents 5 Getting Started With the Code Generation T ools 5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Provides an overview of how to invoke and use the assembler , linker , and compiler. 5.1 Getting Started With the Assembler and Linker 5-2 .
x.
1-1 Setting Up the Code Generation T ools With DOS or W indows 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.
System Requirements 1-2 1.1 System Requirements T o install and use the code generation tools, you need the items listed in the following hardware and software checklists.
Installing the Code Generation T ools 1-3 Setting Up the Code Generation T ools With DOS or Windows 3.1x 1.2 Installing the Code Generation T ools This section helps you install the code generation tools on your hard-disk system. The code generation tools package is shipped on CD-ROM.
Setting Up the Code Generation Environment 1-4 1.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environ- ment 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.
Setting Up the Code Generation Environment 1-5 Setting Up the Code Generation T ools With DOS or Windows 3.1x Identifying the directory that contains the executable files (P A TH statement) Y ou must .
Setting Up the Code Generation Environment 1-6 Setting default shell options (C_OPTION) Y ou might find it useful to set the compiler , assembler , and linker shell default options using the C_OPTION environment variable.
Setting Up the Code Generation Environment 1-7 Setting Up the Code Generation T ools With DOS or Windows 3.1x 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 .
Performance Considerations 1-8 1.4 Performance Considerations Y ou 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.
2-1 Setting Up the Code Generation T ools W ith W indows 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 .
System Requirements 2-2 2.1 System Requirements T o install and use the code generation tools, you need the items listed in the following hardware and software checklists.
Installing the Code Generation T ools 2-3 Setting Up the Code Generation T ools With Windows 95 and Windows NT 2.2 Installing the Code Generation T ools This section helps you install the code generation tools on your hard-disk sys- tem. The code generation tools package is shipped on CD-ROM.
Setting Up the Code Generation Environment 2-4 2.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environ- ment 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.
Setting Up the Code Generation Environment 2-5 Setting Up the Code Generation T ools With Windows 95 and Windows NT Identifying the directory that contains the executable files (P A TH statement) Y ou.
Setting Up the Code Generation Environment 2-6 Identifying alternate directories for the compiler to search (C_DIR) The compiler uses the C_DIR environment variable to name alternate direc- tories that contain #include files and function libraries. T o set the C_DIR envi- ronment variable, use this syntax: set C_DIR= pathname 1 [; pathname 2 .
Setting Up the Code Generation Environment 2-7 Setting Up the Code Generation T ools With Windows 95 and Windows NT 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 T ools User ’ s Guide .
Where to Go From Here 2-8 2.4 Where to Go From Here Y our code generation tools are now installed on your Windows 95 or Windows NT system. Now you should do each of the following tasks: T urn to Chapter 5, Getting Started With the Code Generation T ools .
3-1 Setting Up the Code Generation T ools 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 SP ARCstation run- ning SunOS version 4.1.x (or higher) or Solaris version 2.
System Requirements 3-2 3.1 System Requirements T o install and use the code generation tools, you need the items in the following hardware and software checklists.
Installing the Code Generation T ools 3-3 Setting Up the Code Generation T ools With SunOS 3.2 Installing the Code Generation T ools This section helps you install the code generation tools on your hard-disk sys- tem. The software package is shipped on a CD-ROM.
Installing the Code Generation T ools 3-4 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.
Setting Up the Code Generation Environment 3-5 Setting Up the Code Generation T ools With SunOS 3.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environ- ment variables that set certain software tool parameters you normally use.
Setting Up the Code Generation Environment 3-6 Identifying the directory that contains the executable files (path statement) Y ou 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.
Setting Up the Code Generation Environment 3-7 Setting Up the Code Generation T ools With SunOS For more information on the –i option, see the TMS470R1x Assembly Lan- guage T ools User ’s Guide or the TMS470R1x Optimizing C Compiler User ’s Guide .
Setting Up the Code Generation Environment 3-8 (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 3-9 Setting Up the Code Generation T ools With SunOS T o 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 to Go From Here 3-10 V erifying that the environment variables are set T o 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 Y our code generation tools are now installed.
4-1 Setting Up the Code Generation T ools 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 P A-RISC computer with HP-UX 9.
System Requirements 4-2 4.1 System Requirements T o install and use the code generation tools, you need the items in the following hardware and software checklists.
Installing the Code Generation T ools 4-3 Setting Up the Code Generation T ools on an HP Workstation 4.2 Installing the Code Generation T ools This section helps you install the code generation tools on your hard-disk sys- tem. The software package is shipped on a CD-ROM.
Installing the Code Generation T ools 4-4 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) Y ou can move the setenv and set path commands into your .
Setting Up the Code Generation Environment 4-5 Setting Up the Code Generation T ools on an HP Workstation 4.3 Setting Up the Code Generation Environment Before or after you install the code generation tools, you can define environ- ment variables that set certain software tool parameters you normally use.
Setting Up the Code Generation Environment 4-6 Identifying the directory that contains the executable files (path statement) Y ou 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.
Setting Up the Code Generation Environment 4-7 Setting Up the Code Generation T ools on an HP Workstation Identifying alternate directories for the compiler (C_DIR) The compiler uses the C_DIR environment variable to name alternate direc- tories that contain #include files and libraries.
Setting Up the Code Generation Environment 4-8 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 4-9 Setting Up the Code Generation T ools on an HP Workstation T o 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 to Go From Here 4-10 V erifying that the environment variables are set T o 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 Y our code generation tools are now installed.
5-1 Getting Started With the Code Generation T ools 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 T ools User ’ s Guide and the TMS470R1x Optimizing C Compiler User ’s Guide .
Getting Started With the Assembler and Linker 5-2 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 T ools User ’s Guide .
Getting Started With the Assembler and Linker 5-3 Getting Started With the Code Generation T ools 3) Now enter the following command to assemble file2.
Getting Started With the Assembler and Linker 5-4 Example 5–4. Output Map File, lnker2.map ***************************************************** TMS470 COFF Linker Version 1.20 ***************************************************** Sat Feb 8 15:24:43 1997 OUTPUT FILE NAME: <prog.
Getting Started With the Assembler and Linker 5-5 Getting Started With the Code Generation T ools The two files, file1 and file2, can be linked together with or without a com- mand file.
Getting Started With the Assembler and Linker 5-6 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: <prog.
Getting Started With the C Compiler 5-7 Getting Started With the Code Generation T ools 5.2 Getting Started With the C Compiler The TMS470R1x C compiler consists of many phases, including parsing, opti- mization, and code generation. The simplest way to compile is to use the shell program, which is included with the compiler .
Getting Started With the C Compiler 5-8 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.
6-1 Release Notes Release Notes This chapter describes the media contents of the TMS470R1x tools kit. The tools are supported on SP ARCstations, 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.
Media Contents 6-2 6.1 Media Contents The CD-ROM included in the TMS470R1x tools kit for SP ARCstations and HP workstations contains the files listed in T able 6–1. The CD-ROM included in the TMS470R1x tools kit for PCs contains the files listed in T able 6–2.
Media Contents 6-3 Release Notes T able 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.
Release Enhancements 6-4 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 .
Release Enhancements 6-5 Release Notes 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. Y ou must link with the –a linker option, which creates an absolute, execut- able output module, to enable conditional linking.
6-6.
A-1 T roubleshooting DOS Systems Appendix A T roubleshooting 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.
T roubleshooting in the Protected-Mode Environment A-2 A.1 T roubleshooting in the Protected-Mode Environment Getting 32-bit programs to execute properly under DOS can be frustrating. Y our computer ’s configuration and memory management can cause problems that may be difficult to find because many programs are interacting.
T roubleshooting in the Protected-Mode Environment A-3 T roubleshooting DOS Systems 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.
T roubleshooting in the Protected-Mode Environment A-4 PMINFO provides the information shown in T able A–1. T able A–1. PMINFO Fields Measurement Purpose CPU performance Shows the CPU processor eq.
Kernel Error Messages A-5 T roubleshooting DOS Systems 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 A-6 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.
Kernel Error Messages A-7 T roubleshooting DOS Systems 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.
Kernel Error Messages A-8 29: memory error , out of range 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.
DOS/4G Error Messages A-9 T roubleshooting DOS Systems 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 re- lated to an unknown path name, corrupt files, or memory problems.
DOS/4G Error Messages A-10 3301 ”unhandled EMPTYFWD, GA TE16, or unknown relocation” 3302 ”unhandled ALIAS16 reference to unaliased object” 3304 ”unhandled or unknown relocation” Descripti.
Glossary B-1 Glossary Appendix A 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, direc- tives, and macro definitions.
Glossary B-2 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, T roubleshooting DOS Systems , to assist you in debugging.
Glossary B-3 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 .
B-4.
Index Index-1 Index @ shell option 6-5 A A_DIR environment variable for DOS systems 1-5 for HP workstations 4-6 for SP ARCstations 3-6 to 3-7 for Windows 3.
Index Index-2 D directives MEMORY 5-5 SECTIONS 5-5 directories, software tools for DOS systems 1-5 for HP workstations 4-3, 4-6 for SP ARCstations 3-4, 3-6 for Windows 3.
Index Index-3 I installation, software for DOS systems 1-3 for HP workstations 4-3 to 4-4 for SP ARCstations 3-3 for Windows 3.1x systems 1-3 for Windows 95/NT systems 2-3 interlist utility definition.
Index Index-4 .profile file for HP workstations 4-5 to 4-10 for SP ARCstations 3-5 to 3-10 protected-mode environment, troubleshooting A-2 programs, definition B-3 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.
Index Index-5 virtual memory , definition B-3 W walkthrough assembler 5-2 to 5-4 C compiler 5-7 to 5-8 linker 5-2 to 5-4 Windows 3.1x systems requirements 1-2 setting up the environment 1-4 software i.
Index-6.
IMPORT ANT NOTICE T exas 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.
Un point important après l'achat de l'appareil (ou même avant l'achat) est de lire le manuel d'utilisation. Nous devons le faire pour quelques raisons simples:
Si vous n'avez pas encore acheté Texas Instruments TMS470R1x c'est un bon moment pour vous familiariser avec les données de base sur le produit. Consulter d'abord les pages initiales du manuel d'utilisation, que vous trouverez ci-dessus. Vous devriez y trouver les données techniques les plus importants du Texas Instruments TMS470R1x - de cette manière, vous pouvez vérifier si l'équipement répond à vos besoins. Explorant les pages suivantes du manuel d'utilisation Texas Instruments TMS470R1x, vous apprendrez toutes les caractéristiques du produit et des informations sur son fonctionnement. Les informations sur le Texas Instruments TMS470R1x va certainement vous aider à prendre une décision concernant l'achat.
Dans une situation où vous avez déjà le Texas Instruments TMS470R1x, mais vous avez pas encore lu le manuel d'utilisation, vous devez le faire pour les raisons décrites ci-dessus,. Vous saurez alors si vous avez correctement utilisé les fonctions disponibles, et si vous avez commis des erreurs qui peuvent réduire la durée de vie du Texas Instruments TMS470R1x.
Cependant, l'un des rôles les plus importants pour l'utilisateur joués par les manuels d'utilisateur est d'aider à résoudre les problèmes concernant le Texas Instruments TMS470R1x. Presque toujours, vous y trouverez Troubleshooting, soit les pannes et les défaillances les plus fréquentes de l'apparei Texas Instruments TMS470R1x ainsi que les instructions sur la façon de les résoudre. Même si vous ne parvenez pas à résoudre le problème, le manuel d‘utilisation va vous montrer le chemin d'une nouvelle procédure – le contact avec le centre de service à la clientèle ou le service le plus proche.
