SW500007 Microchip Technology, SW500007 Datasheet - Page 140

• Manufacturer Part Number: SW500007
• Description: PICC-18 PRO
• Manufacturer: Microchip Technology
• Type: Compilerr
• Series: PIC18r

Specifications of SW500007

• Supported Families: PIC18
• Core Architecture: PIC
• Software Edition: Professional
• Kit Contents: Software And Docs
• Mcu Supported Families: PIC18
• Tool Function: Compiler
• Tool Type: Compiler
• Lead Free Status / RoHS Status: Not applicable / RoHS Compliant
• For Use With/related Products: PIC18 Series
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: 015P; 778-1002; 778-1002

Map Files
5.10.2.1 General Information
At the top of the map file is general information relating to the execution of the linker.
you have more than one compiler version installed to ensure the desired compiler is being executed.
the assembler. Unless either the assembler or linker have been updated independently, this should
not be of concern.
clarity and brevity, and should not be used for reference.
The Linker command line shown is the entire list of options and files that were passed to the linker
for the build recorded by this map file. Remember, these are linker options and not command-line
driver options. Typically the first options relate to general execution of the linker: path and file
names for various input and output support files; and the chip type etc. These are followed by the
memory allocation options, e.g. -A and -p. Last are the input object and library files that will be
linked to form the output.
have been specified correctly, and at the correct time. It is particularly useful when using the driver
-L- option, see Section 2.4.8.
126
When analysing a program, always confirm the compiler version number shown in the map file if
The chip selected with the --CHIP option should appear after the Machine type entry.
The Object code version relates to the file format used by relocatable object files produced by
A typical map file may begin something like the following. This example has been cut down for
The linker command line should be used to confirm that driver options that control the link step
HI-TECH Software PICC Compiler std#V9.60
Linker command line:
--edf=C:\Program Files\HI-TECH Software\pic\std\9.60\dat\en_msgs.txt \
-h+conv.sym -z -Q16F73 -ol.obj -Mconv.map -ver=PICC#std#V9.60 \
-ACODE=00h-07FFhx2 -ACONST=00h-0FFhx16 -ASTRING=00h-0FFhx16 \
-ABANK0=020h-07Fh -ABANK1=0A0h-0FFh \
-preset_vec=00h,intentry,intcode -ppowerup=CODE -pintsave_0=07Fh \
-prbit_0=BANK0,rbss_0=BANK0,rdata_0=BANK0,idata_0=CODE \
C:\DOCUME~1\user\LOCALS~1\Temp\cgta5eHNF.obj conv.obj \
C:\Program Files\HI-TECH Software\pic\std\9.60\lib\pic412-c.lib \
C:\Program Files\HI-TECH Software\pic\std\9.60\lib\pic20--u.lib
Object code version is 3.9
Machine type is 16F73
T
C
cations be reserved. For the compiler and target device used by the project, the --ROM
driver option is suitable for this task. How can the operation of this option be confirmed?
UT RIAL
ONFIRMING LINKER OPERATION
A project requires that a number of memory lo-
Linker and Utilities