- •Chapter 1. Introduction
- •How to Develop A Program
- •What is an Assembler?
- •Modular Programming
- •Modular Program Development Process
- •Segments, Modules, and Programs
- •Translate and Link Process
- •Filename Extensions
- •Program Template File
- •Chapter 2. Architecture Overview
- •Memory Classes and Memory Layout
- •Classic 8051
- •Extended 8051 Variants
- •Philips 80C51MX
- •Intel/Atmel WM 251
- •CPU Registers
- •CPU Registers of the 8051 Variants
- •CPU Registers of the Intel/Atmel WM 251
- •Program Status Word (PSW)
- •Instruction Sets
- •Opcode Map
- •8051 Instructions
- •Additional 251 Instructions
- •Additional 80C51MX Instructions via Prefix A5
- •Chapter 3. Writing Assembly Programs
- •Assembly Statements
- •Directives
- •Controls
- •Instructions
- •Comments
- •Symbols
- •Symbol Names
- •Labels
- •Operands
- •Special Assembler Symbols
- •Immediate Data
- •Memory Access
- •Program Addresses
- •Expressions and Operators
- •Numbers
- •Characters
- •Character Strings
- •Location Counter
- •Operators
- •Expressions
- •Chapter 4. Assembler Directives
- •Introduction
- •Segment Directives
- •Location Counter
- •Generic Segments
- •Stack Segment
- •Absolute Segments
- •Default Segment
- •SEGMENT
- •RSEG
- •BSEG, CSEG, DSEG, ISEG, XSEG
- •Symbol Definition
- •CODE, DATA, IDATA, XDATA
- •esfr, sfr, sfr16, sbit
- •LIT (AX51 & A251 only)
- •Memory Initialization
- •DD (AX51 & A251 only)
- •Reserving Memory
- •DBIT
- •DSW (AX51 & A251 only)
- •DSD (AX51 & A251 only)
- •Procedure Declaration (AX51 & A251 only)
- •PROC / ENDP (AX51 & A251 only)
- •LABEL (AX51 and A251 only)
- •Program Linkage
- •PUBLIC
- •EXTRN / EXTERN
- •NAME
- •Address Control
- •EVEN (AX51 and A251 only)
- •USING
- •Other Directives
- •_ _ERROR_ _
- •Chapter 5. Assembler Macros
- •Standard Macro Directives
- •Defining a Macro
- •Parameters
- •Labels
- •Repeating Blocks
- •REPT
- •IRPC
- •Nested Definitions
- •Nested Repeating Blocks
- •Recursive Macros
- •Operators
- •NUL Operator
- •& Operator
- •< and > Operators
- •% Operator
- •;; Operator
- •! Operator
- •Invoking a Macro
- •C Macros
- •C Macro Preprocessor Directives
- •Stringize Operator
- •Predefined C Macro Constants
- •Examples with C Macros
- •C Preprocessor Side Effects
- •Chapter 6. Macro Processing Language
- •Overview
- •Creating and Calling MPL Macros
- •Creating Parameterless Macros
- •MPL Macros with Parameters
- •Local Symbols List
- •Macro Processor Language Functions
- •Comment Function
- •Escape Function
- •Bracket Function
- •METACHAR Function
- •Numbers and Expressions
- •Numbers
- •Character Strings
- •SET Function
- •EVAL Function
- •Logical Expressions and String Comparison
- •Conditional MPL Processing
- •IF Function
- •WHILE Function
- •REPEAT Function
- •EXIT Function
- •String Manipulation Functions
- •LEN Function
- •SUBSTR Function
- •MATCH Function
- •Console I/O Functions
- •Advanced Macro Processing
- •Literal Delimiters
- •Blank Delimiters
- •Identifier Delimiters
- •Literal and Normal Mode
- •MACRO Errors
- •Chapter 7. Invocation and Controls
- •Environment Settings
- •Running Ax51
- •ERRORLEVEL
- •Output Files
- •Assembler Controls
- •Controls for Conditional Assembly
- •Conditional Assembly Controls
- •Chapter 8. Error Messages
- •Fatal Errors
- •Non–Fatal Errors
- •Chapter 9. Linker/Locator
- •Overview
- •Combining Program Modules
- •Segment Naming Conventions
- •Combining Segments
- •Locating Segments
- •Overlaying Data Memory
- •Resolving External References
- •Absolute Address Calculation
- •Generating an Absolute Object File
- •Generating a Listing File
- •Bank Switching
- •Using RTX51, RTX251, and RTX51 Tiny
- •Linking Programs
- •Command Line Examples
- •Control Linker Input with µVision2
- •ERRORLEVEL
- •Output File
- •Linker/Locater Controls
- •Locating Programs to Physical Memory
- •Classic 8051
- •Extended 8051 Variants
- •Philips 80C51MX
- •Intel/Atmel WM 251
- •Data Overlaying
- •Program and Data Segments of Functions
- •Using the Overlay Control
- •Tips and Tricks for Program Locating
- •Locate Segments with Wildcards
- •Special ROM Handling (LX51 & L251 only)
- •Bank Switching
- •Common Code Area
- •Code Bank Areas
- •Bank Switching Configuration
- •Configuration Examples
- •Control Summary
- •Listing File Controls
- •Output File Controls
- •Segment and Memory Location Controls
- •High-Level Language Controls
- •Error Messages
- •Warnings
- •Non-Fatal Errors
- •Fatal Errors
- •Exceptions
- •Chapter 10. Library Manager
- •Using LIBx51
- •Interactive Mode
- •Create Library within µVision2
- •Command Summary
- •Creating a Library
- •Adding or Replacing Object Modules
- •Removing Object Modules
- •Extracting Object Modules
- •Listing Library Contents
- •Error Messages
- •Fatal Errors
- •Errors
- •Chapter 11. Object-Hex Converter
- •Using OHx51
- •OHx51 Command Line Examples
- •Creating HEX Files for Banked Applications
- •OHx51 Error Messages
- •Using OC51
- •OC51 Error Messages
- •Intel HEX File Format
- •Record Format
- •Data Record
- •Extended 8086 Segment Record
- •Extended Linear Address Record
- •Example Intel HEX File
- •Appendix A. Application Examples
- •ASM – Assembler Example
- •Using A51 and BL51
- •Using AX51 and LX51
- •Using A251 and L251
- •CSAMPLE – C Compiler Example
- •Using C51 and BL51
- •Using C51 and LX51
- •Using C251 and L251
- •BANK_EX1 – Code Banking with C51
- •Using C51 and BL51
- •Using C51 and LX51
- •BANK_EX2 – Banking with Constants
- •Using C51 and BL51
- •Using C51 and LX51
- •Using BL51
- •Using C51 and LX51
- •Philips 80C51MX – Assembler Example
- •Philips 80C51MX – C Compiler Example
- •Appendix B. Reserved Symbols
- •Appendix C. Listing File Format
- •Assembler Listing File Format
- •Listing File Heading
- •Source Listing
- •Macro / Include File / Save Stack Format
- •Symbol Table
- •Listing File Trailer
- •Appendix D. Assembler Differences
- •Differences Between A51 and A251/AX51
- •Differences between A51 and ASM51
- •Differences between A251/AX51 & ASM51
- •Glossary
- •Index
Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
379 |
|
|
code in the Library will be not linked and located, the entries in the L51 Locate and L51 Misc options page are ignored.
Command Summary
The following table lists the commands that are available for the LIBx51 library |
10 |
manager. The usage and the syntax of these commands are described in the |
|
sections that follow. |
NOTE
Underlined characters denote the abbreviation for the particular command.
LIBx51 Command |
Description |
ADD |
Adds an object module to the library file. For example, |
|
LIB51 ADD GOODCODE.OBJ TO MYLIB.LIB |
|
adds the GOODCODE.OBJ object module to MYLIB.LIB. |
CREATE |
Creates a new library file. For example, |
|
LIB251 CREATE MYLIB.LIB |
|
creates a new library file named MYLIB.LIB. |
DELETE |
Removes an object module from the library file. For example, |
|
LIBX51 DELETE MYLIB.LIB (GOODCODE) |
|
removes the GOODCODE module from MYLIB.LIB. |
EXTRACT |
Extracts an object module from the library file. For example, |
|
LIB251 EXTRACT MYLIB.LIB (GOODCODE) TO GOOD.OBJ |
|
copies the GOODCODE module to the object file GOOD.OBJ. |
EXIT |
Exits the library manager interactive mode. |
HELP |
Displays help information for the library manager. |
LIST |
Lists the module and public symbol information stored in the library file. |
|
For example, |
|
LIB251 LIST MYLIB.LIB TO MYLIB.LST PUBLICS |
|
generates a listing file (named MYLIB.LST) that contains the module |
|
names stored in the MYLIB.LIB library file. The PUBLICS directive |
|
specifies that public symbols are also included in the listing. |
REPLACE |
Replaces an existing object module to the library file. For example, |
|
LIB51 REPLACE GOODCODE.OBJ IN MYLIB.LIB |
|
replaces the GOODCODE.OBJ object module in MYLIB.LIB. Note that |
|
Replace will add GOODCODE.OBJ to the library if it does not exist. |
TRANSFER |
Generates a complete new library and adds object modules. For example, |
|
LIB251 TRANSFER FILE1.OBJ, FILE2.OBJ TO MYLIB.LIB |
|
deletes the existing library MYLIB.LIB, re-creates it and adds the object |
|
modules FILE1.OBJ and FILE2.OBJ to that library. |
|
|
380 Chapter 10. Library Manager
Creating a Library
The CREATE command creates a new, empty library file and has the following format:
CREATE libfile
10 |
|
libfile is the name of the library file to create and should include a file extension. |
|
|
|
||
|
|
Usually, .LIB is the extension that is used for library files. |
|
|
|
Example: |
|
|
|
||
|
|
|
|
|
|
LIBX51 CREATE MYFILE.LIB |
|
|
|
* CREATE FASTMATH.LIB |
|
|
|
The TRANSFER command creates a new library file and adds object modules. |
|
|
|
The TRANSFER command must be entered in the following format: |
|
|
|
|
|
|
|
TRANSFER filename (modulename, …) , … TO libfile |
|
|
|
where |
|
|
|
filename |
is the name of an object file or library file. You may specify |
|
|
|
several files separated by a comma. |
|
|
modulename |
is the name of a module in a library file. If you do not want |
|
|
|
to add the entire contents of a library, you may select the |
|
|
|
modules that you want to add. Module names are specified |
|
|
|
immediately following the filename, must be enclosed in |
|
|
|
parentheses, and must be separated by commas. |
|
|
libfile |
is the name of the library file that should be created. The |
LIBx51 library manager will remove a previous version of the library, if this file already exists. The specified object modules are added to the new created library.
Example:
LIB251 TRANSFER FILE1.OBJ, FILE2.OBJ TO MYLIB.LIB
LIBX51 @mycmd.lin
--- content of mycmd.lin: ---
TRANSFER FILE1.OBJ, FILE2.OBJ, FILE3.OBJ TO MYLIB.LIB
Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
381 |
|
|
Adding or Replacing Object Modules
The ADD command is used to add one or more object modules to an existing library file. The ADD command must be entered in the following format:
ADD filename (modulename, …) , … TO libfile
where |
10 |
|
|
filename |
is the name of an object file or library file. You may specify |
|
several files separated by a comma. |
modulename |
is the name of a module in a library file. If you do not want |
|
to add the entire contents of a library, you may select the |
|
modules that you want to add. Module names are specified |
|
immediately following the filename, must be enclosed in |
|
parentheses, and must be separated by commas. |
libfile |
is the name of an existing library file. The specified object |
|
modules are added to this library. |
Example:
LIB51 ADD MOD1.OBJ, UTIL.LIB(FPMUL, FPDIV) TO NEW.LIB
* ADD FPMOD.OBJ TO NEW.LIB
With the REPLACE command you can update an existing object module in a library file. The REPLACE command will the object module to the library if it does not exist. The format is:
REPLACE filename IN libfile
where |
|
filename |
is the name of an object file you want to update. |
libfile |
is the name of an existing library file. The object module is |
|
replaced in this library. |
Example:
LIBX51 REPLACE MOD1.OBJ IN MYLIB.LIB
* REPLACE FPMOD.OBJ TO FLOAT.LIB
382 Chapter 10. Library Manager
Removing Object Modules
The DELETE command removes object modules from a library file. This command must be entered in the following format:
DELETE libfile (modulename , modulename … )
10 |
where |
is the name of an existing library file. The specified object |
|
libfile |
|
|
|
modules are removed from this library. |
|
modulename |
is the name of a module in the library file that you want to |
|
|
remove. Module names are entered in parentheses and are |
|
|
separated by commas. |
|
Example: |
|
|
|
|
|
LIB51 DELETE NEW.LIB (MODUL1) |
|
|
* DELETE NEW.LIB (FPMULT, FPDIV) |
|
|
Extracting Object Modules |
|
|
The EXTRACT command creates a standard object module for a specified |
|
|
module in a library file. This command must be entered in the following format: |
|
|
|
|
|
EXTRACT libfile (modulename) TO filename |
|
|
where |
|
|
libfile |
is the name of an existing library file. For the specified |
|
|
object module a standard object module will be created. |
|
modulename |
is the name of a module in the library file. Only one module |
|
|
name can be entered in parentheses. |
|
filename |
is the name of the object file that should be created from the |
library module.
Example:
LIBX51 EXTRACT FLOAT.LIB(FPMUL) TO FLOATMUL.OBJ