Table of Contents
Advertisement
8051 FLASH Professional Starter System Starter Manual V1.00
IDE Overview Continued
Project Based Development
Back in the old days of DOS development tools, it was necessary to run separate command line driven
programs to compile, link and then produce a hex file. This was not only time consuming, but could
also lead to a lot of compilation and linking errors due to typing errors.
The Keil µVision Integrated Development Environment (IDE) takes care of all file management for you,
so all you have to worry about is actually writing code that works! The table below show the different
file contained within a typical Keil C51 project.
Files contained within a typical µVision project
Extension Example
.prj
example.prj
.c
cfile1.c
cfilen.c
.a51
a51file1.a51
a51filen.a51
.h
Reg51.h
Evalu8r.h
.obj
cfile1.obj
cfilen.obj
a51file1.obj
a51filen.obj
.lst
example.prj
-
example
.m51
example.m51
.hex
example.hex
.ini
example.ini
Figure 1
Description
Project File:
Contains names of all source files associated with the project and includes
information for compiling, assembling & linking to generate an executable target program.
C Source File: This file is an ASCII text file containg a program written in C51. It is possible to
have as many source files as are required. Eg. 1 to n
Assembler Source File: This file is an ASCII text file containg a program wriiten in A51. It is
possible to have as many source files as are required. Eg. 1 to n
Include (header) File: This type of file can be used to declare microcontroller-specific register
information or as a convenient way of including variable declarations.
Object File: When a C or assembler source file is 'compiled', the compiler translates the source into
an object file.
List File: A LIST file is created by the compiler when the project or a module within the project is
compiled. The file is an ASCII log file of the compilation process and details any errors found.
OMF51 - Absolute Object File: This file has no file extension. This file conains the actual executable
code after a project build. It also contains any symbolic information if the 'debug' options are enable within
µVision.
Map File: A MAP file is created by the compiler when the project or a module within the project is
compiled.
Intel Hex File: This is a standard output format which can be downloaded to many emulators or device
programmers. The actual executable 8051 code is contained in an encoded format within this file.
D-Scope Initialisation File: This file contains a script which dScope executes when launching a project.
11
Advertisement
Table of Contents
