View CC78K0_644082.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

User's Manual
CC78K0
C Compiler Ver. 3.50 or Later Operation
Target Devices 78K0 Series
Document No. U16613EJ1V0UM00 (1st edition) Date Published June 2003 N CP(K)
(c) Printed in Japan
[MEMO]
2
User's Manual U16613EJ1V0UM
Windows and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. PC/AT is a trademark of International Business Machines Corporation. i386 is a trademark of Intel Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. SPARCstation is a trademark of SPARC International, Inc. SunOS and Solaris are trademarks of Sun Microsystems, Inc. HP9000 Series 700 and HP-UX are trademarks of Hewlett-Packard Company.
* The information in this document is current as of February, 2003. The information is subject to change without notice. For actual design-in, refer to the latest publications of NEC Electronics data sheets or data books, etc., for the most up-to-date specifications of NEC Electronics products. Not all products and/or types are available in every country. Please check with an NEC Electronics sales representative for availability and additional information. * No part of this document may be copied or reproduced in any form or by any means without the prior written consent of NEC Electronics. NEC Electronics assumes no responsibility for any errors that may appear in this document. * NEC Electronics does not assume any liability for infringement of patents, copyrights or other intellectual property rights of third parties by or arising from the use of NEC Electronics products listed in this document or any other liability arising from the use of such products. No license, express, implied or otherwise, is granted under any patents, copyrights or other intellectual property rights of NEC Electronics or others. * Descriptions of circuits, software and other related information in this document are provided for illustrative purposes in semiconductor product operation and application examples. The incorporation of these circuits, software and information in the design of a customer's equipment shall be done under the full responsibility of the customer. NEC Electronics assumes no responsibility for any losses incurred by customers or third parties arising from the use of these circuits, software and information. * While NEC Electronics endeavors to enhance the quality, reliability and safety of NEC Electronics products, customers agree and acknowledge that the possibility of defects thereof cannot be eliminated entirely. To minimize risks of damage to property or injury (including death) to persons arising from defects in NEC Electronics products, customers must incorporate sufficient safety measures in their design, such as redundancy, fire-containment and anti-failure features. * NEC Electronics products are classified into the following three quality grades: "Standard", "Special" and "Specific". The "Specific" quality grade applies only to NEC Electronics products developed based on a customerdesignated "quality assurance program" for a specific application. The recommended applications of an NEC Electronics product depend on its quality grade, as indicated below. Customers must check the quality grade of each NEC Electronics product before using it in a particular application. "Standard": Computers, office equipment, communications equipment, test and measurement equipment, audio and visual equipment, home electronic appliances, machine tools, personal electronic equipment and industrial robots. "Special": Transportation equipment (automobiles, trains, ships, etc.), traffic control systems, anti-disaster systems, anti-crime systems, safety equipment and medical equipment (not specifically designed for life support). "Specific": Aircraft, aerospace equipment, submersible repeaters, nuclear reactor control systems, life support systems and medical equipment for life support, etc. The quality grade of NEC Electronics products is "Standard" unless otherwise expressly specified in NEC Electronics data sheets or data books, etc. If customers wish to use NEC Electronics products in applications not intended by NEC Electronics, they must contact an NEC Electronics sales representative in advance to determine NEC Electronics' willingness to support a given application. (Note) (1) "NEC Electronics" as used in this statement means NEC Electronics Corporation and also includes its majority-owned subsidiaries. (2) "NEC Electronics products" means any product developed or manufactured by or for NEC Electronics (as defined above).
M8E 02. 11-1
User's Manual U16613EJ1V0UM
3
Regional Information
Some information contained in this document may vary from country to country. Before using any NEC Electronics product in your application, pIease contact the NEC Electronics office in your country to obtain a list of authorized representatives and distributors. They will verify:
* * * * *
Device availability Ordering information Product release schedule Availability of related technical literature Development environment specifications (for example, specifications for third-party tools and components, host computers, power plugs, AC supply voltages, and so forth) Network requirements
*
In addition, trademarks, registered trademarks, export restrictions, and other legal issues may also vary from country to country. [GLOBAL SUPPORT] http://www.necel.com/en/support/support.html
NEC Electronics America, Inc. (U.S.)
Santa Clara, California Tel: 408-588-6000 800-366-9782
NEC Electronics (Europe) GmbH
Duesseldorf, Germany Tel: 0211-65 03 01 * Sucursal en Espana Madrid, Spain Tel: 091-504 27 87 * Succursale Francaise Velizy-Villacoublay, France Tel: 01-30-67 58 00 * Filiale Italiana Milano, Italy Tel: 02-66 75 41 * Branch The Netherlands Eindhoven, The Netherlands Tel: 040-244 58 45 * Tyskland Filial Taeby, Sweden Tel: 08-63 80 820 * United Kingdom Branch Milton Keynes, UK Tel: 01908-691-133
NEC Electronics Hong Kong Ltd.
Hong Kong Tel: 2886-9318
NEC Electronics Hong Kong Ltd.
Seoul Branch Seoul, Korea Tel: 02-558-3737
NEC Electronics Shanghai, Ltd.
Shanghai, P.R. China Tel: 021-6841-1138
NEC Electronics Taiwan Ltd.
Taipei, Taiwan Tel: 02-2719-2377
NEC Electronics Singapore Pte. Ltd.
Novena Square, Singapore Tel: 6253-8311
J03.4
4
User's Manual U16613EJ1V0UM
INTRODUCTION
The purpose of this manual is to enable complete understanding of the functions and operation of the CC78K0 (78K0 Series C Compiler). This manual does not explain how to write CC78K0 source programs. "Language manual"). [Target Devices] Software for 78K0 Series microcontrollers can be developed by using the CC78K0. To use this software, the RA78K0 (78K0 Series Assembler Package) (sold separately) and the target model's device file are required. [Target Readers] This manual is written for users who have the knowledge gained from reading through the user's manual for the device once and have software programming experience. However, since knowledge about C compilers and the C language is not particularly needed, first-time users of C compilers can use this manual. [Organization] The organization of this manual is described below. CHAPTER 1 OVERVIEW This chapter describes the role and position of the CC78K0 in microcontroller development. CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION This chapter describes how to install the CC78K0, the file names of the supplied programs, and the operating environment for programs. CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING This chapter uses sample programs to describe how to run the CC78K0 and presents examples showing the processes from compiling to linking. CHAPTER 4 CC78K0 FUNCTIONS This chapter describes optimization methods and ROMization functions in the CC78K0. CHAPTER 5 COMPILER OPTIONS This chapter describes the functions of the compiler options, specification methods, and prioritization. CHAPTER 6 C COMPILER OUTPUT FILES This chapter describes the output of various list files output by the CC78K0. CHAPTER 7 USING C COMPILER This chapter introduces techniques to aid in the skillful use of the CC78K0. Therefore, before reading this manual, please read "CC78K0 C Compiler Language User's Manual (U16628E)" (hereafter called the
User's Manual U16613EJ1V0UM
5
CHAPTER 8 STARTUP ROUTINES The CC78K0 provides startup routines as samples. This chapter describes the uses of the startup routines and provides suggestions on how to improve them. CHAPTER 9 ERROR MESSAGES This chapter describes the error messages output by the CC78K0. APPENDICES The appendices provide and a sample program, a list of the cautions encountered during use, lists of the restrictions related to the CC78K0 and an index. [How to Read This Manual] First, those who want to see how to actually use CC78K0, read CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING. Users with a general knowledge of C compilers or users who have read the Language manual can skip CHAPTER 1 OVERVIEW. [Related Documents] The table below shows the documents (such as user's manuals) related to this manual. not marked as such. Documents related to development tools (user's manuals)
Document Name CC78K0 C Compiler Ver.3.50 or Later Operation Language RA78K0 Assembler Package Ver.3.60 or Later Operation Assembly language Structured assembly language SM78K0 System Simulator ID78K Series Integrated Debugger Ver.2.30 or Later ID78K0-NS Integrated Debugger Ver.2.51 or Later RX78K0 Real-Time OS Operation Operation Operation Basics Installation PM plus Ver.5.10 Document No. This document U16628E U16629E U16630E U11789E To be prepared U15185E U16488E U11537E U11536E To be prepared
The related
documents indicated in this publication may include preliminary versions. However, preliminary versions are
6
User's Manual U16613EJ1V0UM
[Conventions] The meanings of the symbols used in this manual are explained. RTOS: ...: [ ]: : " ": ` ': Boldface: _: :
...
Real-time OS for 78K0 Series RX78K0 Repeat in the same format. Characters enclosed in these brackets can be omitted. Characters enclosed in these brackets are as shown (character string). Characters enclosed in these brackets are as shown (character string). Characters enclosed in these brackets are as shown (character string). Characters in bold face are as shown (character string). Underlining at important locations or in examples is the input character sequence. At least one space Indicates an omission in a program description Characters between parentheses are as shown (character string). Delimiter Backslash
:
(): /: \:
[File Name Conventions] The conventions for specifying the input files that are designated in the command line are shown below. (1) Specifying disk file names [drive-name] [\] [[path-name]...] primary-name [.[file-type]] <1> <2> <3> <4> <5>
<1> Specifies the name of the drive (A: to Z:) storing the file. <2> Specifies the name of the root directory. <3> Specify the subdirectory name. Specify a character string of a length allowed by the OS. Characters that can be used: All the characters allowed by the OS, except parentheses (()), semicolons (:), and commas (,). Note that a hyphen (-) cannot be used as the first character of a path name. <4> Primary name Specify a character string of a length allowed by the OS. Characters that can be used: All the characters allowed by the OS, except parentheses (( )), semicolons (:), and commas (,). Note that a hyphen (-) cannot be used as the first character of a path name. <5> File type Specify a character string of a length allowed by the OS. Characters that can be used: All the characters allowed by the OS, except parentheses (( )), semicolons (:), and commas (,). Example: C:\nectools32\smp78k0\CC78K0\prime.C Remarks 1. A space cannot be specified before and after `:', `.', or `\'. 2. Uppercase and lowercase letters are not distinguished (not case-sensitive).
User's Manual U16613EJ1V0UM
7
(2) Specifying device file names The following logical devices are available.
Logical Device CON PRN AUX NUL Output to the console. Output to the printer. Output to an auxiliary output device. Dummy output (nothing is output.) Description
8
User's Manual U16613EJ1V0UM
CONTENTS CHAPTER 1 OVERVIEW...........................................................................................................................12 1.1 Microcontroller Application Product Development and Role of CC78K0 ............................13 1.2 Development Procedure Using CC78K0..................................................................................15
1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 1.2.6 1.2.7 1.2.8 1.2.9 Using editor to create source module files....................................................................................... 16 C compiler........................................................................................................................................ 17 Assembler........................................................................................................................................ 18 Linker............................................................................................................................................... 19 Object converter .............................................................................................................................. 20 Librarian........................................................................................................................................... 21 Debugger ......................................................................................................................................... 22 System simulator ............................................................................................................................. 23 PM plus............................................................................................................................................ 24
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION ...................................................................25 2.1 Host Machines and Supply Media ............................................................................................25 2.2 Installation ..................................................................................................................................26
2.2.1 Installation of Windows version........................................................................................................ 26 2.2.2 Installation of UNIX version ............................................................................................................. 26
2.3
Installation of Device Files........................................................................................................27
2.3.1 Installation of Windows version........................................................................................................ 27 2.3.2 Installation of UNIX version ............................................................................................................. 27
2.4
Directory Configuration.............................................................................................................28
2.4.1 Windows version directory configuration ......................................................................................... 28 2.4.2 UNIX version directory configuration ............................................................................................... 29
2.5
Uninstallation Procedure ..........................................................................................................29
2.5.1 Uninstallation of Windows version ................................................................................................... 29 2.5.2 Uninstallation of UNIX version ......................................................................................................... 30
2.6
Environment Settings................................................................................................................30
2.6.1 2.6.2 2.6.3 2.6.4 Host machine (for PC-9800 Series and IBM PC/AT compatibles) ................................................... 30 Environment variables ..................................................................................................................... 30 File organization .............................................................................................................................. 31 Library files ...................................................................................................................................... 32
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING ................................................................34 3.1 PM plus .......................................................................................................................................34
3.1.1 Position of CC78K0P.DLL (tools DLL) ............................................................................................. 34 3.1.2 Execution environment .................................................................................................................... 34 3.1.3 CC78K0 option setting menu ........................................................................................................... 35 (1) Option menu items .................................................................................................................. 35 (2) Compiler Options dialog box ................................................................................................... 35 (3) Browse for Folder dialog box................................................................................................... 36 3.1.4 Description of each part of dialog box............................................................. 38 (1) Screen when "Preprocessor" is selected................................................................................. 40 (2) Screen when "Memory Model" is selected .............................................................................. 41 (3) Setting screen when "Data Assign" is selected ....................................................................... 42 (4) Screen when "Optimize" is selected ........................................................................................ 43 (5) Screen when "Debug" is selected............................................................................................ 47 (6) Screen when "Output" is selected ........................................................................................... 48 (7) Screen when "Extend" is selected ........................................................................................... 53 (8) Screen when "Others" is selected ........................................................................................... 54 (9) Screen when "Startup Routine" is selected ............................................................................. 56
3.2
Procedure from Co m piling to Linking ( When Not Using Flash Me m ory Self Rewrite Mode) ....58
3.2.1 MAKE from PM plus ........................................................................................................................ 58 3.2.2 Starting up PM plus ......................................................................................................................... 58 3.2.3 Creating project ............................................................................................................................... 58
User's Manual U16613EJ1V0UM
9
3.2.4 Setting compiler and linker options ..................................................................................................59 3.2.5 Building project ................................................................................................................................61 3.2.6 Compiling to linking in command line (for DOS prompt and EWS) ..................................................62 (1) When parameter file is not used ..............................................................................................62 (2) When parameter file is used ....................................................................................................64
3.3
Compiling to Linking (When Using Flash Memory Self Rewrite Mode)................................65
3.3.1 Compiling to linking via PM plus ......................................................................................................65 (1) Compiling to linking program for boot area ..............................................................................65 (2) Compiling to linking program for flash area .............................................................................70 3.3.2 Compiling to linking in command line (for DOS prompt and EWS) ..................................................74 (1) When parameter file is not used ..............................................................................................74 (2) When parameter file is used ....................................................................................................76
3.4 3.5
I/O Files of C Compiler...............................................................................................................77 Execution Start and End Messages .........................................................................................79
(1) (2) Execution start message .........................................................................................................79 Execution end message ..........................................................................................................79
CHAPTER 4 CC78K0 FUNCTIONS ..........................................................................................................81 4.1 Optimization Method..................................................................................................................81 4.2 ROMization Function .................................................................................................................83
4.2.1 Linking..............................................................................................................................................83
CHAPTER 5 COMPILER OPTIONS ..........................................................................................................84 5.1 Specifying Compiler Options....................................................................................................84 5.2 Prioritization of Compiler Options............................................................................................85 5.3 Descriptions of Compiler Options............................................................................................87
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) (12) (13) (14) (15) (16) (17) (18) (19) Device type specification (-C) ..................................................................................................88 Object module file creation specification (-O/-NO)...................................................................91 Memory assignment specification (-R/-NR, -RD/-NR, -RK/-NR, -RS/-NR, -RC/-NR) ...............92 Optimization specification (-Q/-NQ) .........................................................................................96 Debugging information output specification (-G/-NG) ..............................................................99 Preprocess list file creation specification (-P, -K)...................................................................100 Preprocess specification (-D, -U, -I).......................................................................................103 Assembler source module file creation specification (-A, -SA) ..............................................106 Error list file creation specification (-E, -SE) ..........................................................................110 Cross-reference list file creation specification (-X).................................................................114 List format specification (-LW, -LL, -LT, -LF, -LI) ...................................................................116 Warning output specification (-W)..........................................................................................121 Execution state display specification (-V/-NV) .......................................................................122 Parameter file specification (-F).............................................................................................123 Temporary file creation directory specification (-T)................................................................124 Help specification (--/-?/-H)....................................................................................................125 Function expansion specification (-Z/-NZ) .............................................................................126 Device file search path (-Y) ...................................................................................................128 Static model specification (-SM) ............................................................................................129
CHAPTER 6 C COMPILER OUTPUT FILES...........................................................................................131 6.1 Object Module File ...................................................................................................................131 6.2 Assembler Source Module File...............................................................................................131 6.3 Error List File ............................................................................................................................135
6.3.1 Error list file with C source .............................................................................................................135 6.3.2 Error list file with error message only .............................................................................................137
6.4 6.5
Preprocess List File .................................................................................................................138 Cross-Reference List File ........................................................................................................140
CHAPTER 7 USING C COMPILER .........................................................................................................143 7.1 Efficient Operation (EXIT Status Function) ...........................................................................143 7.2 Setting Up Development Environment (Environment Variables) ........................................144 10
User's Manual U16613EJ1V0UM
7.3
Interrupting Compilation .........................................................................................................144
CHAPTER 8 STARTUP ROUTINES .......................................................................................................145 8.1 File Organization ......................................................................................................................145
8.1.1 BAT directory contents .................................................................................................................. 146 8.1.2 SRC directory contents .................................................................................................................. 147
8.2 8.3
Batch File Description .............................................................................................................148
8.2.1 Batch files for creating startup routines.......................................................................................... 148
Startup Routines ......................................................................................................................149
8.3.1 Overview of startup routines .......................................................................................................... 149 (1) Function ................................................................................................................................ 149 (2) Configuration ......................................................................................................................... 150 (3) Uses of startup routines ........................................................................................................ 151 8.3.2 Description of sample program (cstart.asm) .................................................................................. 152 (1) Preprocessing ....................................................................................................................... 152 (2) Initial settings......................................................................................................................... 155 (3) ROMization processing ......................................................................................................... 156 (4) Starting main function and postprocessing............................................................................ 159 8.3.3 Revising startup routines ............................................................................................................... 161 (1) When revising startup routine................................................................................................ 161 (2) Link directive file.................................................................................................................... 163 (3) When using RTOS ................................................................................................................ 164
8.4
ROMization Processing in Startup Module for Flash Area ..................................................171
CHAPTER 9 ERROR MESSAGES..........................................................................................................172 9.1 Error Message Format.............................................................................................................172 9.2 Types of Error Messages ........................................................................................................172 9.3 List of Error Messages ............................................................................................................173
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10) Error message for a command line .................................................................... 174 Error message for an internal error and memory ............................................... 177 Error message for a character ........................................................................... 178 Error message for configuration element ........................................................... 178 Error message for conversion ............................................................................ 180 Error message for an expression ....................................................................... 181 Error message for a statement ........................................................................... 184 Error message for a declaration and function definition ..................................... 185 Error message for a preprocessing directive ...................................................... 190 Error message for fatal file I/O and running on an illegal operating system ....... 194
APPENDIX A SAMPLE PROGRAMS .....................................................................................................196 A.1 C Source Module File ..............................................................................................................196 A.2 Execution Example ..................................................................................................................197 A.3 Output List ................................................................................................................................198
(1) (2) (3) (4) Assembler source module file ............................................................................................... 198 Preprocess list file ................................................................................................................. 204 Cross-reference list file.......................................................................................................... 206 Error list file ........................................................................................................................... 207
APPENDIX B LIST OF USE-RELATED CAUTIONS ..............................................................................208 APPENDIX C LIST OF RESTRICTIONS RELATED TO CC78K0..........................................................219 C.1 Details About Restrictions and Prevention Methods ...........................................................220 APPENDIX D INDEX................................................................................................................................225
User's Manual U16613EJ1V0UM
11
CHAPTER 1 OVERVIEW
The CC78K0 C compiler program translates C source programs written in ANSI-C 78K0 Series into the machine language for the 78K0 Series.
Note
or the C language for the
The CC78K0 can be run on WindowsTM 98/Me/2000/XP or Windows NTTM 4.0 when using PM plus included in the assembler package for the 78K0 Series. If PM plus is not used, the compiler can be run from the DOS prompt (Windows 98/Me) or command prompt (Windows NT 4.0/2000/XP) (for the Windows version). Note ANSI-C is the C language that conforms to the standard set by the American National Standards Institute.
12
User's Manual U16613EJ1V0UM
CHAPTER 1 OVERVIEW
1.1
Microcontroller Application Product Development and Role of CC78K0
The position of CC78K0 in product development is shown below. Figure 1-1. Development Process for Microcontroller Application Products
Product Planning
System Design
Hardware Design
Software Design
Production
Coding
Mistakes
Errors
Bugs
Compile/Assemble
CC78K0 C Compiler
Inspection
Debugging
System Evaluation
Product Creation
User's Manual U16613EJ1V0UM
13
CHAPTER 1 OVERVIEW
The software development process is shown below. Figure 1-2. Software Development Process
Software Development
Write Program Specification
Create Flow Chart
Coding
Edit Source Modules
... Depends on 78K Series C language or ANSI-C
Compile
... Use the editor to create the C source module files.
YES Errors? NO Link
... Link to the reference library and function library.
File Conversion
... Convert the file to the hexadecimal format.
Debug
... Use the hardware debugger (in-circuit emulator, etc.) to verify the operation.
NO OK YES System Evaluation
14
User's Manual U16613EJ1V0UM
CHAPTER 1 OVERVIEW
1.2
Development Procedure Using CC78K0
The development procedure using CC78K0 is shown below. Figure 1-3. Program Development Procedure Using CC78K0
C source Structured assembler source
Include file
Structured assembler
C compiler
Assembler source
Assembler source
Assembler Real-time OS
Object module file Library file
Librarian
Assemble list
Library file
Linker
Load module file
List converter
System simulator Object converter Integrated debugger
Absolute assemble list Hexadecimal object
Dedicated parallel interface
RS-232C
In-circuit emulator
PROM programmer
User's Manual U16613EJ1V0UM
15
CHAPTER 1 OVERVIEW
1.2.1 Using editor to create source module files One program is divided into several functional modules. One module is the coding unit and becomes the input unit to the compiler. A module that is the input unit to the C compiler is called a C source module. After each C source module is coded, use the editor to save the source module to a file. A file created in this way is called a C source module file. The C source module files become the CC78K0 input files. Figure 1-4. Creating Source Module Files
Program
Source Module
Source Module
END
Source Module END END
Source Module
Write to file (editor)
END Source Module File
16
User's Manual U16613EJ1V0UM
CHAPTER 1 OVERVIEW
1.2.2 C compiler The C compiler inputs the C source modules and converts the C language into machine language. If description errors are detected in the C source module, compiling errors are output. If there are no compiling errors, the object module files are output. To correct and check the programs at the assembly language level, assembler source module files can be output. If you want to output assembler source module files, specify the -A or -SA option in the specification for creating assembler module files when compiling (for information about the options, see CHAPTER 5 COMPILER OPTIONS). Figure 1-5. C Compiler Function
C source module file
C Compiler
Object module file
Assembler source module file
User's Manual U16613EJ1V0UM
17
CHAPTER 1 OVERVIEW
1.2.3 Assembler Assembling is performed by using the assembler included in the RA78K0 Assembler Package (sold separately). The assembler is the program that inputs an assembler source module file and translates assembly language into machine language. If description errors were discovered in the source module, the assemble errors are output. If there are no assemble errors, the output is the object module file that includes machine language information and location information such as at which address each machine language code should be placed in memory. In addition, information during assembly is output as an assemble list file. Figure 1-6. Assembler Function
Assembler source module file
Assembler
Assemble list file
Object module file
18
User's Manual U16613EJ1V0UM
CHAPTER 1 OVERVIEW
1.2.4 Linker Linking is performed by using the linker included in the RA78K0 Assembler Package (sold separately). The linker inputs multiple object module files output by the compiler or object module files output by the assembler, and links them to the library files (even if there is one object module, linking must be performed). One load module file is output. In this case, the linker determines the location addresses of relocatable segments in the input module. This determines the values of relocatable symbols and external reference symbols, and embeds the correct values in the load module file. The linker outputs the linking information as a link map file. Figure 1-7. Linker Function
Multiple object module files
Library file
....
Linker
Link map file
Load module file
User's Manual U16613EJ1V0UM
19
CHAPTER 1 OVERVIEW
1.2.5 Object converter The object converter uses the converter included in the RA78K0 Assembler Package (sold separately). The object converter inputs a load module file output by the linker and converts its file format. The result is output as an intel-standard hexadecimal object module file. Symbol information is output as a symbol table file. Figure 1-8. Object Converter Function
Load module file
Object Converter
Hexadecimal object module file
Symbol table file
20
User's Manual U16613EJ1V0UM
CHAPTER 1 OVERVIEW
1.2.6 Librarian Clearly defined modules having a general interface are formed into a library for convenience. By creating the library, many object modules form one file and become easy to handle. The linker has functions to extract only the needed modules from the library file and link them. Therefore, if multiple modules are registered in one library file, the names of the module files needed when linking no longer have to be individually specified. The librarian is used to create and update library files. The librarian uses the librarian included in the RA78K0 Assembler Package (sold separately). Figure 1-9. Librarian Function
Object module files output by compiler
Object module file output by assembler
...
Librarian
Library file
User's Manual U16613EJ1V0UM
21
CHAPTER 1 OVERVIEW
1.2.7 Debugger Source debugging using a graphical user interface becomes possible by loading the load module files output by the linker into the IE (in-circuit emulator) by using the ID78K0-NS (78K0 Series integrated debugger). To debug, the -G option specifying the output of debugging information is specified when the target source program is compiled (-G is the default option). By making this specification, the symbols and line numbers needed in debugging are added to the object module. For information on the compiler options, see CHAPTER 5 COMPILER OPTIONS. Figure 1-10. Debugger Function
* Object information * Debugging information
Integrated Debugger
Parallel interface
In-circuit emulator
22
User's Manual U16613EJ1V0UM
CHAPTER 1 OVERVIEW
1.2.8 System simulator Source debugging using a graphical user interface becomes possible by downloading the load module files output from the linker by using the SM78K0 (78K0 Series system simulator). SM78K0 is software that has the same operating image as the ID78K0-NS and performs simulations on the host machine. In addition to simulating machine instructions in the SM78K0, the on-chip peripherals for the devices and the interrupts can be simulated. hardware development. Figure 1-11. Simulator Function Load module file Since external parts and procedures are provided to construct dummy target systems, the programs including the operation of the target system are debugged at an early stage independent of
* Object information * Debugging information
Simulator
User's Manual U16613EJ1V0UM
23
CHAPTER 1 OVERVIEW
1.2.9 PM plus PM plus is software that uses the DLL files added to CC78K0 and is able to start CC78K0 on Windows 98/Me/2000/XP or Windows NT 4.0. Editing the source, automatically creating the MAKEFILE, and compiling to linking can be performed from the startup screen of PM plus. Thus, editing to debugging can be performed using GUI images. PM plus is included to the RA78K0 Assembler Package. The installer for the RA78K0 Assembler Package is used to install and to make the settings. If CC78K0 will be started from PM plus, install the RA78K0 Assembler Package before installing the compiler. Figure 1-12. PM plus Function
Remark
Build analyzes and executes the make file to create the executable file. The dependency relationships described in the make file basically remove unused assembling, compiling, and linking and can create efficient executable files.
24
User's Manual U16613EJ1V0UM
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
This chapter explains the procedure to install the files stored in the supply media of the CC78K0 to the user development environment (host machine) and the procedure to uninstall them from the user development environment.
2.1
Host Machines and Supply Media
This C compiler supports the development environments listed in Table 2-1. Table 2-1. Supply Media and Recording Formats for C Compiler
Host Machine PC-9800 Series IBM PC/ATTM and compatibles OS Japanese Windows (98/Me/2000/XP/NT 4.0)Note Japanese Windows (98/Me/2000/XP/NT 4.0)Note English Windows (98/Me/2000/XP/NT 4.0)Note HP-UXTM (Rel. 10.10 and later) SunOS (Rel. 4.1.4 and later) SolarisTM (Rel. 2.5.1 and later)
TM
Supply Media CD-ROM
Recording Format Standard Windows installer supported
HP9000 Series 700TM SPARCstation Family
TM
CD-ROM
cp command
Note PM plus is required if the C compiler is used on Windows. The C compiler can be started up from the DOS prompt (Windows 98/Me) or command prompt (Windows NT 4.0/2000/XP) if PM plus is not used.
User's Manual U16613EJ1V0UM
25
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
2.2
Installation
2.2.1 Installation of Windows version The procedure for installing to the host machine the files provided in the CC78K0's supply media is described below. (1) Starting up Windows Power on the host machine and peripherals and start Windows. (2) Set supply media Set the CC78K0's supply media in the appropriate drive (CD-ROM drive) of the host machine. The setup programs will start automatically. Perform the installation by following the messages displayed in the monitor screen. Caution If the setup program does not start automatically, execute SETUP.EXE in the CC78K0\DISK1 folder. (3) Confirmation of files Using Windows Explorer, etc., check that the files contained in the CC78K0's supply media have been installed to the host machine. For the details of each folder, refer to 2.4.1 Windows version directory configuration. 2.2.2 Installation of UNIX version Install the UNIX version with the following procedure. Installation to /nectools is assumed here. (1) Login Log in to the host machine. (2) Directory selection Go to the install directory. %cd /nectools (3) Setting of supply media Set the CD-ROM in the CD-ROM drive and close the tray. (4) Execute the cp command for the files to copy the files from the CD-ROM (copy the files after checking that the CD-ROM has been set in the CD-ROM drive). (5) Add /nectools/bin to the environmental variable PATH.
26
User's Manual U16613EJ1V0UM
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
2.3
Installation of Device Files
2.3.1 Installation of Windows version Use the device file installer to install the device files. The device file installer is installed at the same time as the CC78K0. 2.3.2 Installation of UNIX version Either specify the directory for device files with the -y option (example: -y/nectools/dev), or copy the device files to a directory with the compiler execution format (example: /nectools/bin).
User's Manual U16613EJ1V0UM
27
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
2.4
Directory Configuration
2.4.1 Windows version directory configuration The standard directory displayed during installation is "NECTools32" of the Windows system. The configuration under the install directory is as follows. Note that the drive and install directory can be changed during installation. When performing MAKE operation with PM plus, perform installation of tools (CC78K0, RA78K0) to the same drive and directory. The descriptions in this manual assume installation to the standard directory with "NECTools32", which is the default program name, according to the setup program default directions. Figure 2-1. Directory Configuration
NECTools32\ bin\ CC78K0.exe, CC78K0p.dll,etc. inc78k0\ *.h lib78k0\Note 2 (For link) cl0*.lib s0*.rel src\CC78K0\ bat\ mkstup.bat *.bat src\ cstart*.asm rom.asm *.asm Executable form of compiler PM plus Tools DLL
Header files for standard library
Libraries (runtime and standard libraries) Object files for startup routines
Assemble batch files for startup routinesNote 1
Source files for startup routines Source files for ROMization routines Source files for some standard functions
lib\Note 2 (For modifications) cl0*.lib Libraries (runtime and standard libraries) s0*.rel Object files for startup routines smp78k0\CC78K0\ prime.c sample.bat readme.doc lk78k0.dr hlp\ CC78K0*.hlp On-line help files
Source program for verifying installation Batch files for verifying installation Link directive file for reference
Notes 1. This batch file cannot be used in PM plus. To use the batch file, run it from the DOS prompt (Windows 98/Me) or command prompt (Windows NT 4.0/2000/XP). 2. The startup routines and libraries in the lib78k0 directory are identical to those in the src\CC78K0 directory. If a startup routine is modified, change the source in the src\CC78K0 directory. Since assembled files by the batch file are stored in src\CC78K0\lib, copy lib78k0 directory and link.
28
User's Manual U16613EJ1V0UM
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
2.4.2 UNIX version directory configuration The file organization when the cp command was used for installation to /nectools is shown below.
nectools/ bin/ CC78K0, etc. Executable form of compiler
inc78k0/ *.h lib78k0/Note (For link) cl0*.lib s0*.lib src/CC78K0/ bat/ mkstup.sh *.sh src/ cstart*.asm rom.asm *.asm
Header files for standard library
Libraries (runtime and standard libraries) Object files for startup routines
Assemble batch files for startup routines
Source files for startup routines Source files for ROMization routines Source files for some standard functions
lib/Note (For modifications) Libraries (runtime and standard libraries) cl0*.lib s0*.rel Object files for startup routines smp78k0/CC78K0/ prime.c sample.sh readme.doc lk78k0.dr
Source program for verifying installation Batch files for verifying installation Link directive file for reference
Note The startup routines and libraries in the lib78k0 directory are identical to those in the src/CC78K0 directory. If a startup routine is modified, change the source in the src/CC78K0 directory. Since assembled files by the batch file are stored in src/CC78K0/lib, copy lib78k0 directory and link.
2.5
Uninstallation Procedure
2.5.1 Uninstallation of Windows version The procedure for uninstalling the files installed to the host machine is described below. (1) Windows startup Power on the host machine and peripherals and start Windows. (2) Opening Control Panel window Press the Start button and select [Settings]-[Control Panel] to open the window. (3) Opening of window Double-click the [Add/Remove Programs] icon in the window to open the window.
User's Manual U16613EJ1V0UM
29
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
(4) Deletion of CC78K0 After selecting "NEC CC78K0 78K/0 C Compiler Vx.xx" from the list of installed software displayed in the <> tab in the window, click the [Add/Remove...] button. When the window is opened, click the [Yes] button. (5) Confirmation of files Using Windows Explorer, etc., check that the files installed to the host machine have been uninstalled. For the details of each folder, refer to 2.4.1 Windows version directory configuration. 2.5.2 Uninstallation of UNIX version Delete the files copied in 2.3.2 Installation of UNIX version with the rm command.
2.6
Environment Settings
2.6.1 Host machine (for PC-9800 Series and IBM PC/AT compatibles) The CC78K0 handles 32 bits and runs on models equipped with the i386TM CPU or later versions. Since handling 32 bits is implemented by using DOS Extender, it is designed to run on the following operating systems. DOS prompt in Windows 98/Me Command prompt in Windows 2000/XP/NT 4.0
2.6.2 Environment variables Set the following environment variables for EWS and DOS prompt (Windows 98/Me) or command prompt (Windows 2000/XP/NT 4.0) operation. Table 2-2. Environment Variables
Environment Variable PATH TMP Description Specifies the directory where the executable form of the compiler is located. Specifies the directory where temporary files are created (only valid for PC-9800 Series and IBM PC/AT compatibles). Specifies the kanji code (2-byte code) in the source files. sjis Shift JIS (Default for PC-9800 Series and HP9000 Series 700) euc EUC (Default for SPARCstation) none No 2-byte codes (Default for IBM PC/AT compatibles) Specifies the directory where the standard header files of the compiler are located. (required only for EWS) Specifies the directory where the compiler's libraries are located. (required only for EWS)
LANG78K
INC78K0
LIB78K0
Specification Example For PC-9800 Series and IBM PC/AT compatibles
PATH = %PATH%;C:\NECTools32\bin set TMP = C:\ set LANG78K = sjis
30
User's Manual U16613EJ1V0UM
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
For HP9000 Series 700 and SPARCstation Example using csh set path = ($path /nectools/bin) setenv LANG78K euc setenv INC78K0 /nectools/inc78k0 setenv LIB78K0 /nectools/lib78k0/lib
Example using sh PATH = $PATH:/nectools/bin LANG78K = euc INC78K0 = /nectools/inc78k0 LIB78K0 = /nectools/lib78k0 export PATH LANG78K INC78K0 LIB78K0
2.6.3 File organization The table below lists the contents of each directory. The files for PC-9800 Series and IBM PC/AT compatibles are described. The directory structure and file organization are the ones obtained when the installer was used. Remark Some of the file extensions differ in UNIX. Table 2-3. File Organization (* = Alphanumeric Symbols)
Directory Name BIN\ File Name CC78K0.exe CC78K0.msg *.hlp *.dll INC78K0\ SRC\CC78K0\BAT\
Note 2
Description Compiler Message file Help files DLL files Header files for standard library Assemble batch files for startup routines For updating rom.asm Batch files for updating standard functions (partial) Source files for startup routines Source files for ROMization routine Source files for standard functions (partial) On-line help file
*.h
Note 1
mkstup.bat reprom.bat *.bat
Note 3
SRC\CC78K0\SRC
cstart*.asmNote 4 rom.asm *.asmNote 5 *.hlp
HLP
Notes 1. See 10.2 Header Files in the Language manual (U16628E). 2. The batch files in this directory cannot be used in PM plus. Use these batch files only when the source must be revised. 3. Refer to the contents in Table 8-1 BAT Directory Contents. 4. * = B | E | N (B: when the boot area is specified, E: when the flash area is specified, N: when the standard libraries are not used) 5. Refer to the contents in Table 8-2 SRC Directory Contents. Remark A command file (EXE file type) is the file first read into memory when the program starts.
User's Manual U16613EJ1V0UM
31
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
2.6.4 Library files * These files consist of standard libraries, runtime libraries, and startup routines. Table 2-4 lists the directory contents.
Table 2-4. Library Files
Directory Name Normal LIB78K0\ cl00.lib cl00r.lib cl00o.lib cl00sm.lib cl00f.lib cl0.lib cl0r.lib cl0o.lib cl0sm.lib cl0f.lib s0.rel s0l.rel s0sm.rel s0sml.rel File Name Boot Area cl00.lib cl00r.lib cl00o.lib cl00sm.lib cl00f.lib cl0.lib cl0r.lib cl0o.lib cl0sm.lib cl0f.lib s0b.rel s0lb.rel s0smb.rel s0smlb.rel Flash Area cl00e.lib cl00re.lib cl00oe.lib cl00sme.lib cl00fe.lib cl0e.lib cl0re.lib cl0oe.lib cl0sme.lib cl0fe.lib s0e.rel s0le.rel s0sme.rel s0smle.rel Object files for startup routines
Note 2
File Role
Library (runtime and standard libraries)Note 1 (without multiply/divide instruction)
Library (runtime and standard libraries)Note 1 (with multiply/divide instruction)
Notes 1. The rule for naming libraries is given below.
lib78k0\cl0.lib None o Use the function interface that conforms to the CC78K0 V3.50 specification (when compile option -ZO is not specified) Use the function interface that conforms to the CC78K0 V2.11 specification (when compile option -ZO is specified) None f None r None sm Normal model Static model When normal function interface is used When pascal function interface is used (when compile option -ZR is specified) Standard library and runtime library (floating point library is not used) For floating point library
32
User's Manual U16613EJ1V0UM
CHAPTER 2 PRODUCT OVERVIEW AND INSTALLATION
None e For normal/boot area For flash memory area
Notes 2. The rule for naming startup routines is given below.
lib78k0\s0.rel None sm None l None b e Normal For boot area For flash memory area When standard library functions are not used When standard library functions are used Normal model Static model
User's Manual U16613EJ1V0UM
33
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
This chapter uses the CC78K0 and the RA78K0 Assembler Package to describe the procedure from compiling to linking. By actually performing the processes from compiling to linking of the `prime.c' sample program following the execution procedure given in this chapter, you can become familiar with the operations of compiling, assembling, and linking (see APPENDIX A SAMPLE PROGRAMS for information about the sample program). How to execute on PM plus is described for the PC-9800 Series and IBM PC/AT compatible machines. For other machines, how to execute from the command line is described (for information on installation, see 2.2 Installation).
3.1
PM plus
This section describes the user interface when the CC78K0 is started in PM plus included in the RA78K0 Assembler Package. If the CC78K0 is started from PM plus, CC78K0P.DLL included in CC78K0 is referenced. 3.1.1 Position of CC78K0P.DLL (tools DLL) The tools DLL file, such as the CC78K0P.DLL file, is needed to run the Windows version of the 78K0 Series C compiler (CC78K0) from PM plus in Windows 98/Me/2000/XP or Windows NT 4.0. 3.1.2 Execution environment This environment conforms to PM plus. The display mode switches between Japanese and English according to the operating system (Windows English version/Japanese version).
34
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.1.3 CC78K0 option setting menu (1) Option menu items The item "Compiler Options..." is added to the [Tools] menu in PM plus by the tools DLL file included in the CC78K0 C Compiler Package. (2) Compiler Options dialog box Select the [Compiler Options...] menu under [Tools] in PM plus to call the option setting function for the tools DLL. The dialog box is shown below.
User's Manual U16613EJ1V0UM
35
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(3) Browse for Folder dialog box In the dialog box, when the Browse... button is clicked for the following path settings, the following dialog box appears. Only the folders can be specified in this dialog box. * Include file path * Object module file output path * Assembler module file output path * Error list file output path * Cross-reference list file output path * Preprocessor list file output path * Temporary file path
When the Browse... button is clicked in the parameter file specification, the following dialog box appears. This dialog box is as follows.
36
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
Current directory: Project file directory File type: Parameter file (*.pcc)
User's Manual U16613EJ1V0UM
37
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.1.4 Description of each part of dialog box Each part of the dialog box is described.
Command line option
OK button
Cancel button
Apply button
Help button
* [OK] button The settings edited in this dialog box are set, and the dialog box closes. If a source file is selected in this source list, the options are set for this file. If nothing is selected, the options are set for all of the source files. * [Cancel] button The options are not set, and the dialog box closes. The ESC key has the same effect as the [Cancel] button no matter where the focus is in the dialog box. * [Apply] button This button is effective only when option settings have been changed. The edited contents in this dialog box are applied and the dialog box remains displayed. * [Help] button The help file for this dialog box opens.
38
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
* Command Line Options: The option character string currently set is displayed. The option character string entered in [Other Options:] of dialog box is reflected and displayed in real time. Nothing can be input in this display area. Even though the default option of the CC78K0 is the "specified" state (i.e., a check box is checked, etc.), nothing is displayed in this area by default. Options that do not fit in the option character display area can be checked by scrolling with the * Setting of compiler options The compiler options are divided into the following nine options and set respectively. Each setting screen is displayed by clicking the corresponding tab at the top of the dialog box. Preprocessor (default) Memory Model Data Assign Optimize Debug Output Extend Others Startup Routine button.
User's Manual U16613EJ1V0UM
39
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(1) Screen when "Preprocessor" is selected
* Define Macro[-d]: The macro name and definition name specified by the -D option is input to the combo box. For the macro name, multiple macro definitions can be performed at once by delimiting with `,'. * Undefine Macro[-u]: The macro name specified by the -U option is input to the combo box. For the macro name, multiple macro definitions can be invalidated at once by delimiting with `,'. * Include Search Path[-i]: The directory that contains include files specified by the -I option is input to the combo box. Multiple directories can be specified at once by delimiting with `,'. The [Browse..] button can also be used for specification. Unexisted path cannot be specified.
40
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(2) Screen when "Memory Model" is selected
* Static Model[-sm]: Use a static model by checking the check box and specify a number of bytes of the common area. * Extend a Static Model If the -SM option is specified and you wish to extend a static model, select this check box. Select the area to be used for arguments and auto variables by clicking the appropriate radio button. The information of the selected radio button is saved even if the check box is left unchecked. * Control Object Output Old Calling Sequence[-zo] Select this check box to enable the -ZO option. Regard All Function as _ _pascal Except Varargs[-zr] Select this check box to enable the -ZR option. Output the Object for Flash Memory[-zf] Select this check box to enable the -ZF option. Using Prologue/Epilogue Library[-zd] Select this check box to enable the -ZD option.
User's Manual U16613EJ1V0UM
41
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(3) Setting screen when "Data Assign" is selected
* Assign External Variable to SADDR Area Check the check box to validate the -RD option. The type of an external variable to be assigned to the saddr area is selected by checking the radio button. * Assign Static Variable to SADDR Area Check the check box to validate the -RS option. The type of a static variable to be assigned to the saddr area is selected by checking the radio button. * Assign Local Variable to SADDR Area[Static Model Only] Check the check box to validate the -RK option. The type of an automatic variable to be assigned to the saddr area is selected by checking the radio button. * Assign Bit Field from MSB[-rb] Check the check box to validate the -RB option. * Packing structure members[-rc] Check the check box to validate the -RC option.
42
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(4) Screen when "Optimize" is selected (a) When "Integrated Recommendable Optimizing Option" is selected in the [Group:] drop-down list box
* Integrated Recommendable Optimizing Option The "Integrated Recommendable Optimizing Option" integrates optimization options according to purpose, instead of specifying them individually. Accordingly this option makes the optimization option easier to set. There are three settings: "Exec Time [-qx1]", "Default [-qx2]", and "Code Size [-qx3]". Their meanings are as follows. Exec Time[-qx1]: Default[-qx2]: Code Size[-qx3]: -QX1 option. Select this option when the efficiency of executing speed is important. -QX2 option. Select this option when both the efficiency of executing speed and the efficiency of object code size are equally important. -QX3 option. Select this option when the efficiency of object code size is important.
User's Manual U16613EJ1V0UM
43
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(b) When "Char Expression Behavior, Automatic Allocation" is selected in the [Group:] drop-down list box
* Char Expression Behavior Assign char without Sign Expand Check this check box to validate the -QC option (do not execute integrate promotion). Select the type of non sign-expanded char operation by checking a radio button. Change Plain char to unsigned char[-qu] Check this check box to validate the -QU option. * Automatic Allocation Use SADDR Area for norec + Register Variable Check this check box to validate the -QR option and select a variable to be assigned by checking a radio button. Use Register for Auto Variable[-qv] Check this check box to validate the -QV option. * Jump Optimization[-qj] Check this check box to validate the -QJ option.
44
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(c) When "Optimize Object Size by Calling Library" is selected in the [Group:] drop-down list box
* Optimize Object Size by Calling Libraries Check this check box to validate the -QL option and specify the level of the object size priority optimization by checking a radio button. When the number n of -QLn becomes greater, the object code size becomes smaller, and accordingly the executing speed becomes slower. A device may have some limitations in operation if -QL4 (max.) is specified.
User's Manual U16613EJ1V0UM
45
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(d) When "Others" is selected in the [Group:] drop-down list box
* Output The Object Using [HL+B] Operand (Static Model Only)[-qe] Check this check box to perform code output that [HL+B] is used for operand. * Output The Object Using [HL], bit Operand[-qh] Check this check box to perform code output that [HL].bit is used for operand. * Aggressive Optimization Check this check box to validate the -QW option.
46
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(5) Screen when "Debug" is selected
* Output Debugging Information Check this check box to validate the -G option and select a file that should output debug information by checking a radio button. If [Debug] is disabled by a PM plus option, it is not possible to perform settings in the dialog box, and debug information is not output.
User's Manual U16613EJ1V0UM
47
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(6) Screen when "Output" is selected (a) When "Object Module File, Assembler Source Module File" is selected in the [Group:] drop-down list box
* Object Module File To specify an object module file output path, input the path name in the combo box. Specification is also possible using the [Browse...] button. When universal options are specified in PM plus, processing is always performed assuming that the path name is specified. When the source file is specified, processing is performed as a path name if a path exists, and as a file name if no path exists. * Create Assembler Source Module File To enable the -A/-SA/-LI options, select this check box, and select with/without C source to attach to the assembler source module file and with/without include file contents by clicking the appropriate radio button. To specify the output path of the assembler source module file, input the path name in the combo box. Specification is also possible using the [Browse...] button. When universal options are specified in PM plus, processing is always performed assuming that the path name is specified. When the source file is specified, processing is performed as a path name if a path exists, and as a file name if no path exists. * [Assembler Options[H]] button Specify assembler options for the assembler source module file. If no option is specified, processing is performed assuming that all assembler options have been specified.
48
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
* dialog box When the [Assembler Options[H]] button under the tab in the dialog box is clicked, the following dialog box appears.
* Use Assembler common option Select this check box to enable all the options set in the dialog box. * Assembler Source Options To enable options for the output assembler source of the compiler, input a character string including the option name in the combo box. Past inputs can be selected by clicking the button at the right of the combo box.
Caution Do not describe chip type specification (-C), device file specification (-Y), and parameter file specification (-F) because they are set separately with this tools DLL. * Command Line Options: This edit box is a read-only box. The option character strings that are currently set are displayed. If the character strings do not all fit in the box, they can be viewed by scrolling with the edit box. Assembler common options and output assembler options are displayed as the option character strings. button. All the character strings specified by setting a button or inputting in a box are immediately displayed in this
User's Manual U16613EJ1V0UM
49
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(b) When "Error List File, Cross-reference List File" is selected in the [Group:] drop-down list box
* Create Error List File Select this check box to enable the -E/-SE option. Also select whether or not to attach the C source to the error list by selecting the appropriate radio button. To specify the error list file output path, input the path name in the combo box. Specification is also possible using the [Browse...] button. When universal options are specified, processing is always performed assuming that the path name is specified. When the source file is specified, processing is performed as a path name if a path exists, and as a file name if no path exists. * Create Cross Reference List File[-x] Select this check box to enable the -X option. To specify the cross-reference list file output path, input the path name in the combo box. Specification is also possible using the [Browse...] button. When universal options are specified, processing is always performed assuming that the path name is specified. When the source file is specified, processing is performed as a path name if a path exists, and as a file name if no path exists.
50
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(c) When "Preprocess List File, List Format" is selected in the [Group:] drop-down list box
* Create Preprocess List File Check this check box to validate the -P option and the specification for the following preprocess list files. Delete Comment[-kc] Check this check box to validate the -KC option. Execute #define[-kd] Check this check box to validate the -KD option. Execute #if, #ifdef, #ifndef[-kf] Check this check box to validate the -KF option. Execute #include[-ki] Check this check box to validate the -KI option. Execute #line[-kl] Check this check box to validate the -KL option. Add Line No. and Paging[-kn] Check this check box to validate the -KN option. To specify the preprocess list file output path, input the path name in the combo box. Specification is also possible using the [Browse...] button. When universal options are specified, processing is always performed assuming that the path name is specified. When the source file is specified, processing is performed as a path name if a path exists, and as a file name if no path exists.
User's Manual U16613EJ1V0UM
51
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
* Add Form Feed at End of List File[-lf] Check this check box to validate the -LF option. * List setting The list is output in the following format specified when the output option of each list is set. Columns per Line[-lw]: Specifies the number of characters in one line by using the -LW option. To increase/decrease the number of characters in the box, click Lines per Page[-ll]: Specifies the number of lines in one page by using the -LL option. To increase/decrease the number of characters in the box, click Expand TAB Character[-lt]: Specifies the length of tab character by using the -LT option. To increase/decrease the number of characters in the box, click button. button. button.
52
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(7) Screen when "Extend" is selected
* Change Source Regulation Disable Extensions (ANSI Standard Only)[-za] Check this check box to validate the -ZA option. Treat int and short as char[-zi] Check this check box to validate the -ZI option. Treat long as int[-zl] Check this check box to validate the -ZL option. This option is default setting in a static model. Enable C++ Comment, Ignore from // Till End of Line[-zp] Check this check box to validate the -ZP option. Comment Can Nest[-zc] Check this check box to validate the -ZC option. Not Expand Argument and Return Value[-zb] Check this check box to validate the -ZB option. Kanji Code of Source Select the type (SJIS/EUC/None) of Kanji code used in the comment of the source by selecting the appropriate radio button.
User's Manual U16613EJ1V0UM
53
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(8) Screen when "Others" is selected
* Verbose Compile Messages[-v] Select this check box to enable the -V option. * Warning Level[-w]: Use the button to change the -W option level.
* Temporary File Creation Directory[-t]: Input the directory in which to store the temporary files specified with the -T option in the combo box. * Parameterfile: Input the parameter file name specified with the -F option in the combo box. Past inputs can be selected by clicking the * Other Options: If a compiler option other than the various option specification items must be specified, input that option in the combo box. Past inputs can be selected by clicking the button at the right of the combo box. button at the right of the combo box.
54
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
* [Reset] button Clicking this button sets the default option settings. * [Option file read...] button Clicking this button causes the option information file containing the option settings to be read. * [Option file save...] button This button is enabled only when information has been set with the [OK] button or the [Apply] button. Option settings are saved as an option information file. * Use Command File By selecting this check box, the option character string is output to the command file, so awareness of restrictions on the length of the option character string is not required. This check box is selected by default.
User's Manual U16613EJ1V0UM
55
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(9) Screen when "Startup Routine" is selected
dialog box settings cannot be performed when a source is specified. * Using Startup Routine Select this check box to use the standard startup routine provided for this C compiler. * Using Fixed Area of Standard Library Select this check box to use the fixed area used by the standard library. * Select Object Select the desired startup routine for the normal, boot, or flash area by selecting the corresponding radio button. If the [Output the Object for Flash Memory[-zf]] check box under the tab is not selected, the startup routine for the normal or boot areas can be selected, and if the check box is selected, only the startup routine for the flash area can be selected. * Startup Routine: Indicates the file name of the startup routine to be used.
56
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
* Using Library Select this check box to use the standard library provided for this C compiler. * Using Floating Point in sprintf,sscanf,printf,scanf,vprintf,vsprintf Select this check box to use the sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions supporting floating points. If the [Static Model[-sm]:], [Output Old Calling Sequence[-zo]], or [Regard All Function as _ _pascal Except Varargs[-zr]] option is specified, the sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions supporting floating points cannot be used. * Not Using Multiplication and Division Code Select this check box to use products that do not have multiply and divide instructions. * Library: Displays the file name of the library to be used.
User's Manual U16613EJ1V0UM
57
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.2
Procedure from Compiling to Linking (When Not Using Flash Memory Self Rewrite Mode)
3.2.1 MAKE from PM plus The MAKE method using PM plus with a PC-9800 Series or IBM PC/AT compatible is described below. PM plus is a software program used for the integrated management of tools as the core of the development environment. Using PM plus enables handling application programs and environment settings as projects. Program creation using an editor, source management, compilation, and debugging can be performed as a continuous series of operations. 3.2.2 Starting up PM plus When a development tool packages are correctly installed, the [NECTools32] menu is created in the Programs folder displayed from the Start button, and PM plus and other programs are registered in this menu. Click [PM plus] from the menu to start up PM plus. 3.2.3 Creating project Register a project first to start a series of development operations using PM plus. To register a project, first create the workspace in which that project is managed. For the procedure to create a workspace, refer to the PM plus Ver. 5.10 User's Manual (U16569E).
58
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.2.4 Setting compiler and linker options A minimum number of options are set for build in the MAKE file created automatically upon completion of project creation. Project-specific options are set in the [Tools] menu. If the [Compiler Options...] in the [Tools] menu is selected, the dialog box appears. An example changing the Optimize option from default [-QCJLVW] to Code Size[-qx3] is shown below. Figure 3-1. Selection of Optimize Options
If "Using Startup Routine" is selected in the <> tab of the dialog box, the standard startup routine for this compiler gets linked before all sources (not displayed to the dialog box). When "Using Library" is selected, the standard library for this compiler gets linked behind all libraries. If C source is included in the source file settings, stack symbol automatic generation option -S is automatically specified to the linker. The name of the startup routine file does not affect the load module file name.
User's Manual U16613EJ1V0UM
59
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
Figure 3-2. Linker Options Dialog Box
60
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.2.5 Building project Projects are built with the set options. Building of an entire project is done by selecting [Build] from the [Build] menu, or by clicking the tool bar. PM plus MAKE is started up by the automatically created MAKE file. Upon completion of build, a message dialog box appears. Check that build has been completed normally. Caution The contents displayed in the window during build are saved as the "Project file name + .plg" file name to the project directory. button on the
User's Manual U16613EJ1V0UM
61
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.2.6 Compiling to linking in command line (for DOS prompt and EWS) (1) When parameter file is not used The command below is used to start the CC78K0, assembler, and linker in a command line. Assembling is not needed when there is no assembler description in C source. In this case, link the object module file output from a C compiler (: space). >[path name]CC78K0[ option] C source name[ option] >[path name]RA78K0[ option] assembler source name[ option] >[path name]LK78K0 object module name[ option]
Caution
To link libraries created by users, be sure to specify the libraries attached to the compiler and the floating point libraries at the end of the library list. To use the sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions supporting floating points, specify the floating point libraries attached to the compiler and the libraries attached to the compiler, in this order. To use the sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions not supporting floating points, specify the libraries attached to the compiler and the floating point libraries attached to the compiler, in this order. Also, specify the startup routine attached to the C compiler before the user programs. The library and object module file specification order during linking is shown below. (Library specification order) When using sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions not supporting floating points 1. User program library file (specified with -B option) 2. Library file attached to C compiler (specified with -B option) 3. Floating point library file attached to C compiler (specified with -B option) When using sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions supporting floating points 1. User program library file (specified with -B option) 2. Floating point library file attached to C compiler (specified with -B option) 3. Library file attached to C compiler (specified with -B option) (Specification order of other files) 1. Object file of startup routine attached to CC78K0 2. Object module file of user program
62
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
The following shows an example of linking C source s1.c and assembler source s2.asm.
C>CC78K0 -c054 s1.c -e -a -iC:\nectools32\inc78k0 -yC:\nectools32\dev C>ra78k0 -c054 s2.asm -e -yC:\nectools32\dev C>lk78k0 s01.rel s1.rel s2.rel -bC:\nectools32\lib78k0\cl0.lib -s -osample.lmf -yC:\nectools32\dev Remark When specifying multiple compiler options, delimit between compiler options by a space. It does not matter whether a description is written in uppercase or lowercase (non case sensitive). For detailed information, see CHAPTER 5 COMPILER OPTIONS. The -i option specification, -b option path specification, and -y option specification can be omitted depending on the condition. For details, see CHAPTER 5 COMPILER OPTIONS and RA78K0 Assembler Package Operation User's Manual (U16629E).
User's Manual U16613EJ1V0UM
63
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(2) When parameter file is used When multiple options are input in starting a compiler, assembler, or linker, the same specification may be repeated several times if sufficient information for startup has not been specified in the command line. In such cases, a parameter file should be used. Specify the parameter file specification option in the command line when using a parameter file. Caution Parameter files cannot be specified by means of the option setting of PM plus.
The following shows the startup method for a compiler, assembler, and linker by using a parameter file. >[path name]CC78K0 -F parameter file name >[path name]RA78K0 -F parameter file name >[path name]LK78K0 -F parameter file name
The following shows a usage example.
Example
C>CC78K0 C>ra78k0 C>lk78k0
-Fpara.pcc -Fpara.pra -Fpara.plk
Parameter files are created by an editor. All options and output file names that should be specified in a command line can be written. The following shows examples of creating parameters by the editor. (Contents of para.pcc) -c054 s1.c -e -a -iC:\nectools32\inc78k0 -yC:\nectools32\dev (Contents of para.pra) -c054 s2.asm -e -yC:\nectools32\dev (Contents of para.plk) s01.rel s1.rel s2.rel -bC:\nectools32\lib78k0\cl0.lib -s -osample.lmf -yC:\nectools32\dev The -i option specification, -b option path specification, and -y option specification can be omitted depending on the condition. For details, see CHAPTER 5 COMPILER OPTIONS and RA78K0 Assembler Package Operation User's Manual (U16629E).
64
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.3
Compiling to Linking (When Using Flash Memory Self Rewrite Mode)
This function is available only for the device having the flash memory self rewriting function. 3.3.1 Compiling to linking via PM plus PM plus is used on the PC-9800 Series and IBM PC/AT compatibles to illustrate the MAKE technique. Be sure to execute compiling to linking in the following order. (1) Compiling to linking program for boot area (a) Creating a project Create a project for the boot area and register the source file. (b) Compiler, linker, and object converter options settings Only the minimum options required for build are set in MAKE file automatically created when project creation is ended. Project-specific options are set with the [Tools] menu. Selecting [Compiler Options] in the [Tools] menu displays the dialog box.
User's Manual U16613EJ1V0UM
65
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
<1> Setting compiler option Do not specify the -ZF option in the <> tab. Figure 3-3. Compiler Options Dialog Box
Select "Boot" in the [Select Object] box under the <> tab. Figure 3-4. Selection of Boot Area Object
66
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
<2> Setting linker option Specify flash start address specification option -ZB and then click the [OK] button. Since "Using Startup Routine" and "Using Library" check boxes are selected under the <> tab, it is not necessary to specify the startup routine and library in the dialog box. Also, since C source (boot.c) is included in the source file specification, stack symbol automatic generation option -S is automatically set. Remark For information about the linker options, refer to RA78K0 Assembler Package Operation User's Manual (U16629E).
User's Manual U16613EJ1V0UM
67
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
<3> Setting object converter option Do not specify the object converter option -ZF.
Caution After the program for boot area is compiled and object-converted, write in the HEX file (e.g. boot.hex) with a flash programmer. the program for boot area again. After writing, be sure to save the load module file (e.g. boot.lmf) and HEX file created in the above procedure. Do not build
68
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(c) Building project Projects are built with the set options. Build of an entire project is done by selecting [Build] from the [Build] menu, or by clicking the the tool bar. PM plus MAKE is started up by the automatically created MAKE file. Upon completion of build, a message dialog box appears. Check that build has been completed normally. Caution The contents displayed in the window during build are saved as the "Project file name + .plg" file name to the project directory. button on
User's Manual U16613EJ1V0UM
69
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(2) Compiling to linking program for flash area (a) Creating a project Create a project for the flash area and register the source file. (b) Compiler, linker, and object converter option settings Only the minimum options required for build are set in MAKE file automatically created when project creation is ended. Project-specific options are set with the [Tools] menu. Selecting [Compiler Options] in the [Tools] menu displays the dialog box. <1> Setting compiler option Specify the -ZF option in the <> tab. Figure 3-5. Compiler Options Dialog Box
Flash is automatically selected in the [Select Object] box under the <> tab.
70
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
<2> Setting linker option Specify the load module file for the boot area to be linked and then click the [OK] button. Since the "Using Startup Routine" and "Using Library" check boxes are selected under the <> tab in the dialog box, it is not necessary to specify the startup routine and library in the dialog box. Also, since C source (flash.c) is included in the source file specification, stack symbol automatic generation option -S is automatically set. Remark For information about the linker options, refer to RA78K0 Assembler Package Operation User's Manual (U16629E).
Figure 3-6. Linker Options Dialog Box
User's Manual U16613EJ1V0UM
71
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
<3> Setting object converter option (for flash area) Be sure to specify the object converter option -ZF. By specifying the -ZF option, HEX file for boot area (e.g. flash.hxb) and HEX file for flash area (e.g. flash.hxf) are output. The flash.hxb and the boot.hex that is generated when the program for boot area is built have the same contents. However, when the HEX file for boot area is already written and the program for flash area is built again, it is recommended to confirm that there is no difference in the saved boot.hex and the created flash.hxb. Figure 3-7. Object Converter Options Dialog Box
72
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(c) Building project Projects are built with the set options. Build of an entire project is done by selecting [Build] from the [Build] menu, or by clicking the the tool bar. PM plus MAKE is started up by the automatically created MAKE file. Upon completion of build, a message dialog box appears. Check that build has been completed normally. Caution The contents displayed in the window during build are saved as the "Project file name + .plg" file name to the project directory. button on
User's Manual U16613EJ1V0UM
73
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.3.2 Compiling to linking in command line (for DOS prompt and EWS) (1) When parameter file is not used The command below is used to start the CC78K0, assembler, and linker in a command line. Assembling is not needed when there is no assembler description in C source. In this case, link the object module file output from a C compiler (: space). >[path name]CC78K0[ option] C source name[ option] >[path name]RA78K0[ option] assembler source name[ option] >[path name]LK78K0[ option] object module name, etc.[ option]
The following shows examples of compiling and linking the C source for boot area and the C source for flash area. (a) Compiling to linking, object-converting program for boot area Examples <1> Compiling program for boot area C> CC78K0 -cf0078 boot.c -iC:\nectools32\inc78k0 -yC:\nectools32\dev <2> Linking program for boot area C> lk78k0 s01b.rel boot.rel -bC:\nectools32\lib78k0\cl0.lib -s -oboot.lmf -zb2000h -yC:\nectools32\dev <3> Object-converting program for boot area C> oc78k0 boot.lmf -u0FFh -oboot.lmf -yC:\nectools32\dev Caution After the program for boot area is compiled and object-converted, write in the HEX file (e.g. boot.hex) with a flash programmer. After writing, be sure to save the load module file (e.g. boot.lmf) and HEX file created in the above procedure. Do not build the program for boot area again. (b) Compiling to linking program for flash area Examples <4> Compiling program for flash area C> CC78K0 -cf0078 flash.c -zf -iC:\nectools32\inc78k0 -yC:\nectools32\dev <5> Linking program for flash area C> lk78k0 boot.lmf s0le.rel flash.rel -bC:\nectools32\lib780\ cl0e.lib -s -oflash.lmf -yC:\nectools32\dev <6> Object-converting program for flash area C> oc78k0 flash.lmf -u0FFh -r -oflash.lmf -yC:\nectools32\dev Caution By specifying the -ZF option when object-converting, HEX file for boot area (e.g. flash.hxb) and HEX file for flash area (e.g. flash.hxf) are output. The flash.hxb and the boot.hex that is generated when the program for boot area is built have the same contents. However, when the HEX file for boot area is already written and the program for flash area is built again, it is recommended to confirm that there is no difference in the saved boot.hex and the created flash.hxb.
74
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
Remark
When specifying multiple compiler options, delimit between compiler options by a space. It does not matter whether a description is written in uppercase or lowercase (non case sensitive). For detailed information, see CHAPTER 5 COMPILER OPTIONS.
The -i option specification, -b option path specification, and -y option specification can be omitted depending on the condition. For details, see CHAPTER 5 COMPILER OPTIONS and RA78K0 Assembler Package Operation User's Manual (U16629E). Caution When linking a library created by a user or a floating-point library, be sure to specify the library attached to the CC78K0 at the end of the library line. When linking a program for flash area and a program for boot area, specify the load module file for boot area in the beginning, and specify the startup routine for flash area before the user program. The following shows the library and object module file specification orders when linking. (Library specification order) When using sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions not supporting floating points 1. User program library file (specified with -B option) 2. Library file attached to C compiler (specified with -B option) 3. Floating point library file attached to C compiler (specified with -B option) When using sprintf, sscanf, printf, scanf, vprintf, and vsprintf functions supporting floating points 1. User program library file (specified with -B option) 2. Floating point library file attached to C compiler (specified with -B option) 3. Library file attached to C compiler (specified with -B option) Specify the library for boot area when linking the program for boot area, and the library for flash area when linking the program for flash area. (Specification order of other files) 1. Load module file for boot area of user program 2. Startup routine object module file for flash area attached to CC78K0 3. Object module file for flash area of user program
User's Manual U16613EJ1V0UM
75
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
(2) When parameter file is used When multiple options are input in starting a compiler, assembler, or linker, the same specification may be repeated several times if sufficient information for startup has not been specified in the command line. In such cases, a parameter file should be used. Specify the parameter file specification option in the command line when using a parameter file. Caution Parameter files cannot be specified by means of the option setting of PM plus. The following shows the startup method for a compiler, assembler, and linker by using a parameter file. >[path name]CC78K0 -F parameter file name >[path name]RA78K0 -F parameter file name >[path name]LK78K0 -F parameter file name
The following shows a usage example.
Example
C>CC78K0 C>lk78k0
-Fpara.pcc -Fpara.plk
Parameter files are created by Editor. All options and output file names that should be specified in a command line can be written. The following shows examples of creating parameters by Editor. (Contents of para.pcc) -cf0078 boot.c -iC:\nectools32\inc78k0 -yC:\nectools32\dev (Contents of para.pra) s0lb.rel boot.rel -bC:\nectools32\lib78k0\cl0.lib -s -oboot.lmf -zb2000h -yC:\nectools32\dev Remark The -i option specification, -b option path specification, and -y option specification can be omitted depending on the condition. For details, see CHAPTER 5 COMPILER OPTIONS and RA78K0 Assembler Package Operation User's Manual (U16629E).
76
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.4
I/O Files of C Compiler
The CC78K0 inputs the C source module files written in the C language. These are converted into machine language and output as object module files. After compiling, the assembler source module files are output so that the user can check and revise the contents at the assembly language level. Based on the compiler options, the list files such as the preprocess list, crossreference list, and error list are output. If there is a compiler error, the error message is output to the console and the error list file. If errors occur, various files other than an error list file cannot be output. The CC78K0 I/O files are shown below. Table 3-1. C Compiler I/O Files
Type File Name C source module file Description * Source file written in the C language * File created by the user * File referenced by a C source module file * File written in the C language * File created by the user * File created by the user when the user wants to specify multiple commands that cannot be specified in the command line when the C compiler is run * Binary image file containing machine language information, relocatable information related to the location address of the machine language, and symbol information * ASCII image file of the object code output by the compiler * List file output by the preprocess instructions such as #include * ASCII image file * List file containing the function name and variable name information used in the C source module file * List file containing the source file and compiler error messages Default File Type C
Input Files
Include file
H
Parameter file
PCC
Object module file
REL
Assembler source module file Output Files Preprocess list file
ASM PPL
Cross-reference list file
XRF
Error list file
ECC CER HER ERNote $nn (file name fixed)
Note The following four file types are available for error list files. CER: Error list files with C source corresponding to *.C' files (output by specifying the -SE option) HER: Error list files with C source corresponding to *.H' files (output by specifying the -SE option) ER: Error list files with C source corresponding to files other than the above (output by specifying the -SE option) ECC: Error list files without C source corresponding to all of the source files (output by specifying the -SE option)
I/O File
Temporary file
* Intermediate file for compiling * The file is renamed to an appropriate name when compiling ends without error and is deleted when compiling ends in error.
User's Manual U16613EJ1V0UM
77
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
Figure 3-8. C Compiler I/O Files
Parameter files
C source module files
Include files
Temporary files
Preprocess list files
CC78K0
Assembler source module files
Object module files
Error list files
Cross-reference list files
Remark If there are compiling errors, a variety of files other than the error list and cross reference files cannot be output. A temporary file is renamed to an appropriate name when the compiling ends without error. If compiling ends in error, the temporary files are deleted.
78
User's Manual U16613EJ1V0UM
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
3.5
Execution Start and End Messages
(1) Execution start message When the CC78K0 starts, the execution start message is displayed on the console.
78K/0 Series C Compiler Vx.xx
[xx xxx xxxx]
Copyright (C) NEC Electronics Corporation xxxx,xxxx
(2) Execution end message If compiler errors were not detected in the compilation result, the compiler outputs the following message to the console and returns control to the operating system.
Target chip : uPD780xx Device file : Vx.xx Compilation complete, 0 error(s) and 0 warning(s) found.
If compiler errors were detected in the compilation result, the compiler outputs the error messages and the number of errors to the console and returns control to the operating system.
PRIME.C(18) : W745 Expected function prototype PRIME.C(20) : W745 Expected function prototype PRIME.C(26) : W622 No return value PRIME.C(37) : W622 No return value PRIME.C(44) : W622 No return value Target chip : uPD780xx Device file : Vx.xx Compilation complete, 0 error(s) and 5 warning(s) found.
If a fatal error was detected where the compiling process cannot continue during compilation, the compiler outputs a message to the console, stops compilation, and returns control to the operating system.
User's Manual U16613EJ1V0UM
79
CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING
An example that outputs an error is shown below.
C>CC78K0 -c054 -e prime.c -m 78K/0 Series C Compiler Vx.xx [xx xxx xxxx]
Copyright (C) NEC Electronics Corporation xxxx,xxxx A018 Option is not recognized '-m' Please enter ` CC78K0 Program aborted. . . . -- ` , if you want help messages.
In this example, since a nonexistent compiler option was input, an error results and the compiler stops. If the compiler outputs error messages and stops the compilation, find the sources of these error messages in CHAPTER 9 ERROR MESSAGES and correct.
80
User's Manual U16613EJ1V0UM
CHAPTER 4 CC78K0 FUNCTIONS
4.1
Optimization Method
Optimization is performed to create efficient object module files in the CC78K0. Table 4-1 Optimization Methods lists the supported optimization methods.
Table 4-1. Optimization Methods (1/2)
Phase Syntax Analyzer <1> Contents Execute during constant computations compilation. True or false decision based on partial evaluation of a logical expression Offset calculations of pointers, arrays, etc. Register management Use the special instructions of the target CPU. Use short instructions. a=3*5; a=15; 0 && (a || b) 0 1 || (a && b) 1 Calculate the offsets during compilation. Effectively use unused registers. a=a+1; Use the inc instruction. Use the move instruction to substitute array elements. If there is an instruction with the same operation, use the instruction with fewer bytes. mov a, #0 or xor a, a (differs depending on the device) The intermediate code that was output is reprocessed. Example
<2>
<3> <4>
Code Generator
<5>
<6>
<7>
Change long jump instructions to short jump instructions. Delete common partial expressions.
<8>
a=b+c; d=b+c+e;
a=b+c; d=a+e;
<9>
Move outside an instruction loop.
for (i=0; i<10; i++) { ... a=b+c; ... } a=b+c; for (i=0; i<10; i++) { ... ... } a=a; After a=b;, a is not referenced (a is an automatic variable) Delete Delete
Optimizer <10> Delete unused instructions. <11> Delete copies.
a=b; c=a+d; c=b+d; a is not referenced any more (a is an automatic variable). The calculation whose result remains in the register as valid before other calculations is executed.
<12> Change the calculation order in an expression.
User's Manual U16613EJ1V0UM
81
CHAPTER 4 CC78K0 FUNCTIONS
Table 4-1. Optimization Methods (2/2)
Phase <13> Contents Memory device allocation (temporary variables) Peephole optimization Example Variables used locally are allocated to registers.
<14> Optimizer
Replacement of special patterns Examples a*1 a, a+0 a Examples a*2 a+a, a<< 1 Data is allocated to rapidly accessible memory. Examples Registers, saddr (only when -QR is specified) Consecutive jump instructions are combined into one instruction. Variables are automatically allocated to registers.
<15> <16>
Decrease the strength of the calculation. Memory device allocation (register variables) Jump optimization (-QJ option) Register allocation (-QV, -QR options)
<17> <18>
Remark
<1> to <7> are performed regardless of the optimization option specifications. The optimizations in <8> to <13>, <17>, and <18> are performed when optimization options are specified. Future support is planned for the optimizations in <8> to <13>. <14> and <15> are performed regardless of the optimization option specifications. <16> is performed when there are register declarations in the C source program. However, the saddr area is only allocated when the -QR option is specified. For information about the optimization options, see CHAPTER 5 COMPILER OPTIONS.
82
User's Manual U16613EJ1V0UM
CHAPTER 4 CC78K0 FUNCTIONS
4.2
ROMization Function
ROMization means that the initial values, such as the initial values of external variables, are placed in the ROM. These values are copied to RAM when the system is executed. The CC78K0 provides startup routines with the processing of programs in ROM as samples. For ROMization, using the startup routines in ROM eliminates the problem of describing ROMization processes for startup. For information about the startup routines, see 8.3 Startup Routines. How to store a program on ROM is described below. The startup routine is described using the example of s0l.rel (which is used when ROMization processing is required and the standard libraries are used). 4.2.1 Linking During linking, the startup routine, object module files, and libraries are linked. The startup routine initializes the object program. (1) s0l.rel: Startup routine (when stored on ROM) The copy routine for the initialization data is included, and the beginning of the initial data is indicated. The label _@cstart (symbol) is added to the start address. (2) cl0*.lib: Library attached to CC78K0. The library files of the CC78K0 include the following two libraries.
<1> Runtime library @@ is added to the symbol head of the runtime library name. For the special library cstart, however, _@ is added to the symbol head. <2> Standard library _ is added to the symbol head of the standard library name. (3) *.lib: Library created by a user. _ is added to the symbol head. The CC78K0 provides various kinds of startup routines and libraries. For details of startup routine, refer to CHAPTER 8 STARTUP ROUTINES. For details of libraries, refer to 2.3.4 Library files.
Caution
User's Manual U16613EJ1V0UM
83
CHAPTER 5 COMPILER OPTIONS
When the C compiler is started, the compiler options can be specified. The compiler options provide instructions for compiler operation and indicate the information required beforehand in program execution. The compiler options are not only specified individually, but multiple options can also be simultaneously specified. The user selects the compiler options to match the objectives and to perform the tasks efficiently.
5.1
Specifying Compiler Options
Compiler options can be specified in the following ways. (1) Specified in the command line when the C compiler starts. (2) Specified in the dialog box of PM plus. (3) Specified in the parameter file. For the specification methods for the compiler options described above, see CHAPTER 3 PROCEDURE FROM COMPILING TO LINKING. Specify the suboption or file name after a compiler option without inserting a blank, such as a space. Spaces are required between the compiler options. Example (: blanks such as spaces) CC78K0-c054prime.c-aprime.asm-qx3
84
User's Manual U16613EJ1V0UM
CHAPTER 5 COMPILER OPTIONS
5.2
Prioritization of Compiler Options
For the compiler options shown in the following table, the prioritization is explained in a case where two or more options along the vertical axis and options along the horizontal axis are simultaneously specified. Table 5-1. Prioritization of Compiler Options
-NO -R -Q -G -K -D -U -SA -LW -LL -LT -LF -LI Vertical axis x x x x x -G -P -NP -D -U -A -E -X -x x x x x x x x x x x x -SA Horizontal axis
[Location marked by x] If an option in the horizontal axis is specified, the option in the vertical axis becomes invalid. [Location marked by ] If an option in the horizontal axis is not specified, the option in the vertical axis becomes invalid. [Location marked by O] The option specified last out of an option in the horizontal axis and an option in the vertical axis has priority.
User's Manual U16613EJ1V0UM
85
CHAPTER 5 COMPILER OPTIONS
Example 1
C>CC78K0 -c054 -e sample.c -no -r -g
The -RD and -G options become invalid. Example 2
C>CC78K0 -c054 -e sample.c -p -k
Since the -P option is specified, the -K option is valid. Example 3
C>CC78K0 -c054 -e sample.c -utest -dtest=1
Since the -D option is specified last, the -U option becomes invalid, and the -D option has priority. As with the -O and -NO options, the option specified last has priority even if N can be added before the option name. Example 4
C>CC78K0 -c054 -e sample.c -o -no
Since the -NO option is specified last, the -O option becomes invalid, and the -NO option has priority. Options not described in Table 5-1 Prioritization of Compiler Options are not particularly affected by other options. However, if the help specification option "- -" was specified, all of the option specifications become invalid. The help specification option cannot be specified in PM plus. To reference help in PM plus, press the help button in each option dialog box of PM plus.
86
User's Manual U16613EJ1V0UM
CHAPTER 5 COMPILER OPTIONS
5.3
Descriptions of Compiler Options
This section describes each compiler option in detail. This example illustrates starting the CC78K0 in the command line. To start in PM plus, specify the command, device type specification, and options left out of the C source in the dialog box. Example In command line
C>CC78K0
-c054
prime.c
-g
Example When using PM plus Figure 5-1. Compiler Options Dialog Box
User's Manual U16613EJ1V0UM
87
CHAPTER 5 COMPILER OPTIONS
(1) Device type specification (-C) -C Device type specification
Description format Default interpretation
-C device-type None
[Function] The -C option specifies the target device designated for compilation. [Application] Be sure to specify this option. The C compiler compiles for the specified target device and generates the object code for it. [Description] Refer to the advice about use in the supplemental product materials of the device file for the target devices that can be specified by the -C option and the corresponding device type. When CC78K0 is used, device files are required. Use the device file by copying it to the BIN directory or to the DEV directory. [Caution] The -C option cannot be omitted. However, if the following description is in the C source, the specification can be omitted from the command line. pc (device type)
#pragma
If different devices were specified in the C source and the command line, the device in the command line has priority. It is not necessary for this option to be set by the compiler option when PM plus is used, because the setting of this option is determined by the project setting.
88
User's Manual U16613EJ1V0UM
CHAPTER 5 COMPILER OPTIONS
-C
Device type specification
[Use Example] The specification is made in the command line. The target device is the PD78054. C>CC78K0 -c054 prime.c
This specification is made in the C source and the compiler is started.
#pragma #define TRUE #define FALSE #define SIZE char main() { int i, M
pc(054) 1 0 200
mark[SIZE+1];
prime,
k,
count;
Therefore, the target device specification can be omitted from the command line.
C>CC78K0
prime.c
User's Manual U16613EJ1V0UM
89
CHAPTER 5 COMPILER OPTIONS
-C
Device type specification
Different devices are specified in the C source and the command line and the compiler is started. C source #pragma #define TRUE #define FALSE #define SIZE char main() { int i, prime, k, count; pc(054) 1 0 200
mark[SIZE+1];
Command line C>CC78K0 -c014 prime.c
After the command line is executed, compiling is executed as follows. 78K/0 Series C Compiler Vx.xx [xx xxx xxxx]
Copyright (C) NEC Electronics Corporation xxxx,xxxx SAMPLE\PRIME.C(1) : W832 Duplicated chip specifier sample\prime.c(18): W745 Expected function prototype sample\prime.c(20): W745 Expected function prototype sample\prime.c(26): W622 No return value sample\prime.c(37): W622 No return value sample\prime.c(44): W622 No return value Target chip : uPD78014 Device file : Vx.xx Compilation complete, 0 error(s) and 6 warning(s) found.
The target device specification in the command line has priority.
90
User's Manual U16613EJ1V0UM
CHAPTER 5 COMPILER OPTIONS
(2) Object module file creation specification (-O/-NO)
-O/-NO
Object module file creation specification
Description formats Default interpretation
-O [output-file-name] -NO -O [input-file-name.rel]
[Function] The -O option specifies the output of the object module file. In addition, the output destination or output file name is specified. The -NO option specifies not to output the object module file. [Application] If you want to change the output destination or the output file name of the object module file, specify the -O option. If only the output of the assembler source module file is the target for compilation, specify the -NO option. Consequently, the compilation time is reduced. [Description] If there is a compilation error even when the -O option is specified, the object module file is not output. If the drive name is omitted when the -O option is specified, the object module file is output to the current drive. If both the -O and -NO options are simultaneously specified, the last specified one is valid. [Cautions] To change the output destination when using PM plus, specify the new output destination in the <> combo box in the <

▲Up To Search▲

Price & Availability of CC78K0

	To Download CC78K0 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .