- •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
16 Chapter 1. Introduction
|
How to Develop A Program |
||
1 |
|||
This section presents an overview of the Ax51 macro assembler, Lx51 |
|||
linker/locater and how it is used. |
|||
|
What is an Assembler? |
||
|
|||
|
An assembler is a software tool designed to simplify the task of writing computer |
||
|
programs. It translates symbolic code into executable object code. This object |
||
|
code may then be programmed into a microcontroller and executed. Assembly |
||
|
language programs translate directly into CPU instructions which instruct the |
||
|
processor what operations to perform. Therefore, to effectively write assembly |
||
|
programs, you should be familiar with both the microcomputer architecture and |
||
|
the assembly language. |
||
|
Assembly language operation codes (mnemonics) are easily remembered (MOV |
||
|
for move instructions, ADD for addition, and so on). You can also symbolically |
||
|
express addresses and values referenced in the operand field of instructions. |
||
|
Since you assign these names, you can make them as meaningful as the |
||
|
mnemonics for the instructions. For example, if your program must manipulate a |
||
|
date as data, you can assign it the symbolic name DATE. If your program |
||
|
contains a set of instructions used as a timing loop (a set of instructions executed |
||
|
repeatedly until a specific amount of time has passed), you can name the |
||
|
instruction group TIMER_LOOP. |
||
|
An assembly program has three constituent parts: |
||
|
|
Machine instructions |
|
|
|
Assembler directives |
|
|
|
Assembler controls |
|
A machine instruction is a machine code that can be executed by the machine. Detailed discussion of the machine instructions can be found in the hardware manuals of the 8051 or derivative microcontroller. Appendix A provides an overview about machine instructions.
Keil Software — A51/AX51/A251 Macro Assembler and Utilities |
17 |
|
|
Assembler directives are used to define the program structure and symbols, and generate non-executable code (data, messages, etc.). Refer to “Chapter 4.
Assembler Directives” on page 99 for details on all of the assembler directives. |
1 |
|
|
Assembler controls set the assembly modes and direct the assembly flow. |
|
“Chapter 7. Invocation and Controls” on page 195 contains a comprehensive |
|
guide to all the assembler controls. |
|
Modular Programming |
|
Many programs are too long or complex to write as a single unit. Programming |
|
becomes much simpler when the code is divided into small functional units. |
|
Modular programs are usually easier to code, debug, and change than monolithic |
|
programs. |
|
The modular approach to programming is similar to the design of hardware that |
|
contains numerous circuits. The device or program is logically divided into |
|
“black boxes” with specific inputs and outputs. Once the interfaces between the |
|
units have been defined, the detailed design of each unit can proceed separately. |
|
The benefits of modular programming are: |
|
Efficient Program Development: programs can be developed more quickly |
|
with the modular approach since small subprograms are easier to understand, |
|
design, and test than large programs. With the module inputs and outputs |
|
defined, the programmer can supply the needed input and verify the correctness |
|
of the module by examining the output. The separate modules are then linked |
|
and located by the linker into an absolute executable single program module. |
|
Finally, the complete module is tested. |
|
Multiple Use of Subprograms: code written for one program is often useful in |
|
others. Modular programming allows these sections to be saved for future use. |
|
Because the code is relocatable, saved modules can be linked to any program |
|
which fulfills their input and output requirements. With monolithic |
|
programming, such sections of code are buried inside the program and are not so |
|
available for use by other programs. |
|
Ease of Debugging and Modifying: modular programs are generally easier to |
|
debug than monolithic programs. Because of the well defined module interfaces |
|
of the program, problems can be isolated to specific modules. Once the faulty |
|
18 |
Chapter 1. Introduction |
|
|
module has been identified, fixing the problem is considerably simpler. When a program must be modified, modular programming simplifies the job. You can
1 link new or debugged modules to an existing program with the confidence that the rest of the program will not change.
The following figure shows an overview of the steps involved in creating a program for the x51.
Assembler
Source File
Ax51
Macro Assembler
|
|
|
Listing |
|
|
|
|
File |
|
Object |
Object File |
|
|
|
from Intel |
Object |
Library |
||
File from |
||||
ASM51 or |
File |
File |
||
Cx51 |
||||
PL/M-51 |
|
|
||
|
|
|
LIBx51 Library Manager
Lx51 Linker / Locator
MAP
File
Library |
Absolute |
File |
Object |
|
File |
OHx51 |
|
µVision2 |
In-Circuit |
|
Object HEX Converter |
|
Debugger |
Emulator |
|
|
|
|
|
|
|
|
|
|
|
HEX
File
PROM Programmer
