PIC16F873A-I/SS Microchip Technology, PIC16F873A-I/SS Datasheet - Page 641

• Manufacturer Part Number: PIC16F873A-I/SS
• Description: IC MCU FLASH 4KX14 EE 28SSOP
• Manufacturer: Microchip Technology
• Series: PIC® 16Fr

Specifications of PIC16F873A-I/SS

• Core Size: 8-Bit
• Program Memory Size: 7KB (4K x 14)
• Core Processor: PIC
• Speed: 20MHz
• Connectivity: I²C, SPI, UART/USART
• Peripherals: Brown-out Detect/Reset, POR, PWM, WDT
• Number Of I /o: 22
• Program Memory Type: FLASH
• Eeprom Size: 128 x 8
• Ram Size: 192 x 8
• Voltage - Supply (vcc/vdd): 4 V ~ 5.5 V
• Data Converters: A/D 5x10b
• Oscillator Type: External
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 28-SSOP
• Controller Family/series: PIC16F
• No. Of I/o's: 22
• Eeprom Memory Size: 128Byte
• Ram Memory Size: 192Byte
• Cpu Speed: 20MHz
• No. Of Timers: 3
• Core: PIC
• Processor Series: PIC16F
• Data Bus Width: 8 bit
• Maximum Clock Frequency: 20 MHz
• Data Ram Size: 192 B
• Data Rom Size: 128 B
• On-chip Adc: Yes
• Number Of Programmable I/os: 22
• Number Of Timers: 3
• Operating Supply Voltage: 2 V to 5.5 V
• Mounting Style: SMD/SMT
• A/d Bit Size: 10 bit
• A/d Channels Available: 5
• Height: 1.75 mm
• Interface Type: I2C, SPI, USART
• Length: 10.2 mm
• Maximum Operating Temperature: + 85 C
• Minimum Operating Temperature: - 40 C
• Supply Voltage (max): 5.5 V
• Supply Voltage (min): 4 V
• Width: 5.3 mm
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With: AC164307 - MODULE SKT FOR PM3 28SSOPAC164020 - MODULE SKT PROMATEII 44TQFPXLT28SS-1 - SOCKET TRANSITION ICE 28SSOP
• Lead Free Status / Rohs Status: Details
• Other names: PIC16F873AI/SS

32.3.3
32.3.4
1997 Microchip Technology Inc.
MPLINK Linker
MPLIB Librarian
MPLINK is a linker for the Microchip C compiler, MPLAB-C, and the Microchip relocatable assem-
bler, MPASM. MPLINK is introduced with MPLAB-C v2.00 and can only be used with these or
later versions.
MPLINK allows you to produce modular, re-usable code with MPLAB-C and MPASM. Control
over the linking process is accomplished through a linker “script” file and with command line
options. MPLINK ensures that all symbolic references are resolved and that code and data fit into
the available PICmicro device.
MPLINK combines multiple input object modules generated by MPLAB-C or MPASM, into a sin-
gle executable file. The actual addresses of data and the location of functions will be assigned
when MPLINK is executed. This means that you will instruct MPLINK to place code and data
somewhere within the named regions of memory, not to specific physical locations.
Once the linker knows about the ROM and RAM memory regions available in the target PICmicro
device and it analyzes all the input files, it will try to fit the application’s routines into ROM and
assign it’s data variables into available RAM. If there is too much code or too many variables to
fit, MPLINK will give an error message.
MPLINK also provides flexibility for specifying that certain blocks of data memory are re-usable,
so that different routines (which never call each other and don’t depend on this data to be
retained between execution) can share limited RAM space.
MPLIB is a librarian for use with COFF object modules created using either MPASM v2.0,
MPASMWIN v2.0, or MPLAB-C v2.0 or later.
MPLIB manages the creation and modification of library files. A library file is a collection of object
modules that are stored in a single file. There are several reasons for creating library files:
• Libraries make linking easier. Since library files can contain many object files, the name of
• Libraries help keep code small. Since a linker only uses the required object files contained
• Libraries make projects more maintainable. If a library is included in a project, the addition
• Libraries help convey the purpose of a group of object modules. Since libraries can group
a library file can be used instead of the names of many separate object when linking.
in a library, not all object files which are contained in the library necessarily wind up in the
linker’s output module.
or removal of calls to that library will not require a change to the link process.
together several related object modules, the purpose of a library file is usually more under-
standable that the purpose of its individual object modules. For example, the purpose of a
file named “math.lib” is more apparent that the purpose of 'power.o', 'ceiling.o', and 'floor.o'.
Section 32. Development Tools
DS31032A-page 32-7
32