- •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
360 Chapter 9. Linker/Locator
9 |
Error Messages |
The Lx51 linker/locator generates error messages that describe warnings, non- |
|
fatal errors, fatal errors, and exceptions. |
Fatal errors immediately abort the Lx51 linker/locator operation.
Errors and warnings do not abort the Lx51 linker/locator operation; however, they may result in an output module that cannot be used. Errors and warnings generate messages that may or may not have been intended by the user. The listing file can be very useful in such an instance. Error and warning messages are displayed in the listing file as well as on the screen.
This section displays all the Lx51 linker/locator error messages, causes, and any recovery actions.
Warnings
Warning Warning Message and Description
1UNRESOLVED EXTERNAL SYMBOL SYMBOL: external-name
MODULE: filename (modulename)
The specified external symbol, requested in the specified module, has no corresponding PUBLIC symbol in any of the input files.
2REFERENCE MADE TO UNRESOLVED EXTERNAL SYMBOL: external-name
MODULE: filename (modulename)
ADDRESS: code-address
The specified unresolved external symbol is referenced at the specified code address.
3ASSIGNED ADDRESS NOT COMPATIBLE WITH ALIGNMENT
SEGMENT: segment–name
The address specified for the segment is not compatible with the alignment of the segment declaration.
4DATA SPACE MEMORY OVERLAP FROM: byte.bit address
TO: byte.bit address
The specified area of the on-chip data RAM is occupied by more than one segment.
Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
361 |
|
||||||
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
||
|
|
Warning |
Warning Message and Description |
|
|
|
||
|
|
5 |
CODE SPACE |
MEMORY OVERLAP |
|
9 |
||
|
|
|
FROM: byte |
address |
|
|
|
|
|
|
|
TO: |
byte |
address |
|
|
|
The specified area of the code memory is occupied by more than one segment.
6XDATA SPACE MEMORY OVERLAP FROM: byte address
TO: byte address
The specified area of the external data memory is occupied by more than one segment.
7MODULE NAME NOT UNIQUE
MODULE: filename (modulename)
The specified module name is used for more than one module. The specified module name is not processed.
8MODULE NAME EXPLICITLY REQUESTED FROM ANOTHER FILE
MODULE: filename (modulename)
The specified module name is requested in the invocation line of another file that has not yet been processed. The specified module name is not processed.
9EMPTY ABSOLUTE SEGMENT
MODULE: filename (modulename)
The specified module contains an empty absolute segment. This segment is not located and may be overlapped with another segment without any additional message.
10CANNOT DETERMINE ROOT SEGMENT
The Linker/Locator has recognized the C51 compiler or PL/M-51 input files and tries to process a flow analysis. However, it is impossible to determine the root segment. This error occurs if the main program is called by an assembly module. In this case, the available references (calls) must be modified with the OVERLAY control.
11CANNOT FIND SEGMENT OR FUNCTION NAME
NAME: overlay-control-name
A segment or function name defined in the OVERLAY control cannot be found in the object modules.
12NO REFERENCE BETWEEN SEGMENTS SEGMENT1: segment-name
SEGMENT2: segment-name
An attempt was made to delete a reference or call between two non-existent functions or segments, with the OVERLAY control.
|
362 |
|
|
Chapter 9. Linker/Locator |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Warning |
Warning Message and Description |
|
|
9 |
|
|
|
|
|
|
|
13 |
RECURSIVE CALL TO SEGMENT |
|
|||
|
|
|
SEGMENT: segment-name |
|
||
|
|
|
CALLER: segment-name |
|
||
|
|
|
The specified segment is called recursively from CALLER specified segments. |
|
||
|
|
|
|
Recursive calls are not allowed in C51 and PL/M-51 programs. |
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
14INCOMPATIBLE MEMORY MODEL MODULE: filename (modulename)
MODEL: memory model
The specified module is not compiled in the same memory model as the former compiled modules. The memory model of the improper module is showed by MODEL.
15MULTIPLE CALL TO SEGMENT SEGMENT: segment-name CALLER1: segment-name
CALLER2: segment-name
The specified segment is called from two levels, CALLER1, and CALLER2; e.g., main and interrupt program. This has the same effect as a recursive call and may thus lead to the overwriting of parameters or data.
16UNCALLED SEGMENT, IGNORED FOR OVERLAY PROCESS
SEGMENT: segment-name
This warning occurs when functions, which were not previously called, are contained in a program (e.g., for test purposes). The function specified is excluded from the overlay process in this case. It is possible that the program then occupies more memory as during a call of the specified segment.
17INTERRUPT FUNCTION IN BANKS NOT ALLOWED SYMBOL: function-name
SPACE: code-bank
The specified C function is an interrupt function (a C51 function) that was specified to be located in a code bank. Interrupt functions cannot be located in a code bank.
18no generated by Lx51
19COMMON CODE SEGMENTS LOCATED TO BANKED AREA
Some segments that are usually located to the common area located into the banked area. This warning just informs you, that you might free up some code space by locating program code into banks. The warning is not generated for the default setting of the BANKAREA (0 - 0xFFFF).
20L51_BANK.A51: NBANKS < NUMBER OF CODE BANKS
The setting for NBANKS in the L51_BANK.A51 module is smaller than the number of banks used in your application.
Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
363 |
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Warning |
Warning Message and Description |
|
|
|
|
|
|
|
|
|
9 |
|
21 |
SEGMENT LOCATED OUTSIDE BANKED AREA |
|
|
||
|
|
|
A segment that should be located in the code banking area is located outside the |
|
|
|
|
|
|
address range of the BANKAREA directive. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
22SEGMENT SIZE UNDERFLOW: OLD SIZE + CHANGE < 0
SEGMENT: segment–name
The size change specified in the SEGSIZE control causes the segment size to be less than zero.
23UNRESOLVED EXTERNAL SYMBOL DURING LINK PROCESS
During the link run one or more external symbols have no corresponding PUBLIC symbol in any of the input files.
24INCOMPATIBLE CPU MODE MODULE: module-name
MODE: cpu-mode
The specified module is not translated with the same CPU mode as the former Lx51 input modules. The CPU mode of the invalid module is displayed by MODE. The CPU mode of other input modules is displayed in the Lx51 listing file.
25DATA TYPES DIFFERENT SYMBOL: symbol-name
MODULE: module-name
The definition of the specified symbol in the specified module is not identical with the public definition of that symbol. The module which contains the public symbol can be determined with the IXREF listing. This warning is disabled with
WARNINGLEVEL (0) control.
26DATA TYPES SLIGHTLY DIFFERENT SYMBOL: symbol-name
MODULE: module-name
The definition of the specified symbol in the specified module is not 100% identical with the public definition of that symbol. This warning is the result when unsigned signed mismatches occur, i.e. unsigned char does not match char. The module which contains the public symbol can be determined with the IXREF listing. This warning is disabled with WARNINGLEVEL (1) control.
27INCOMPATIBLE INTERRUPT FRAME SIZE MODULE: module-name
FRAME: frame-size
The specified module is not translated with the same interrupt frame size assumptions as the former input modules. The frame size of the invalid module is displayed by FRAME. The frame size of other input modules is displayed in the Lx51 listing file.
|
364 |
|
|
Chapter 9. Linker/Locator |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Warning |
Warning Message and Description |
|
|
9 |
|
|
|
|
|
|
|
28 |
DECRESING SIZE OF SEGMENT |
|
|||
|
|
|
SEGMENT: segment-name |
|
||
|
|
|
The size specified in the SEGSIZE control has caused Lx51 to decrease the size |
|
||
|
|
|
of the specified segment. |
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
29SEGMENT LOCATED OUTSIDE CLASS AREA
SEGMENT: segment-name
The specified segment is located outside the memory class limits specified by the CLASSES control.
30MEMORY SPACE OVERLAP FROM: address
TO: address
The specified area of the physical memory is occupied by more than one segment.
