Microchip MPLAB X IDE用户指南：PIC单片机开发详解

需积分: 10 115 浏览量更新于2024-07-17 收藏 3.48MB PDF 举报

MPLAB® X IDE 用户指南是一份由 Microchip Technology Inc. 发布的重要文档，专为 PIC 单片机开发应用提供详细的集成开发环境（Integrated Development Environment，IDE）使用教程。这份用户手册适用于2011年至2015年期间的版本，文档编号为 DS50002027D。该指南的核心内容包括了对 MPLAB X IDE 的详细介绍，涵盖了软件安装、配置、项目管理、调试、编程以及与 Microchip PIC 处理器的交互等关键环节。用户可以通过这份指南学习如何高效地使用 MPLAB X 来设计、编译和测试他们的硬件项目，它旨在帮助开发人员简化开发流程，提升代码质量和调试效率。值得注意的是，Microchip 在文档中明确指出，提供的设备应用信息仅为方便用户参考，可能随着更新而被取代。因此，用户在实际应用过程中需要自行验证其项目是否符合自身规格要求。此外，Microchip 对此信息不做任何形式的保证，无论是明示的还是暗示的，包括但不限于性能、适销性或特定用途的适用性。特别强调，MPLAB X 在涉及生命支持和安全应用时的使用需由购买者自行承担风险，且购买者需同意赔偿并保护 Microchip 免受由此产生的任何损失、索赔或费用。此外，使用 Microchip 设备存在潜在风险，因此用户在处理此类应用时必须审慎行事。在未明示的情况下，不会默认授予任何知识产权许可。最后，用户在阅读和使用此指南时，应充分理解并接受其中的免责声明。 MPLAB® X IDE 用户指南是针对 PIC 开发者的实用工具，它不仅提供了软件操作的详细指导，还明确了使用过程中的责任和风险，是进行高效、安全单片机开发的重要参考资料。

MPLAB

X IDE User’s Guide

DS50002027D-page 16  2011-2015 Microchip Technology Inc.

FIGURE 1-3:

PIC

MCU DATA SHEET – FILE REGISTERS

File File File File

Address Address Address Address

Indirect addr.

(1)

00h Indirect addr.

(1)

80h Indirect addr.

(1)

100h Indirect addr.

(1)

180h

TMR0 01h OPTION_REG 81h TMR0 101h OPTION_REG 181h

PCL 02h PCL 82h PCL 102h PCL 182h

STATUS 03h STATUS 83h STATUS 103h STATUS 183h

FSR 04h FSR 84h FSR 104h FSR 184h

PORTA 05h TRISA 85h PORTA 105h TRISA 185h

PORTB 06h TRISB 86h PORTB 106h TRISB 186h

PORTC 07h TRISC 87h PORTC 107h TRISC 187h

08h 88h 108h 188h

09h 89h 109h 189h

PCLATH 0Ah PCLATH 8Ah PCLATH 10Ah PCLATH 18Ah

INTCON 0Bh INTCON 8Bh INTCON 10Bh INTCON 18Bh

PIR1 0Ch PIE1 8Ch EEDAT 10Ch EECON1 18Ch

PIR2 0Dh PIE2 8Dh EEADR 10Dh EECON2

(1)

18Dh

TMR1L 0Eh PCON 8Eh EEDATH 10Eh 18Eh

TMR1H 0Fh OSCCON 8Fh EEADRH 10Fh

18Fh

T1CON 10h OSCTUNE 90h 110h 190h

TMR2 11h 91h 111h 191h

T2CON 12h PR2 92h

112h 192h

SSPBUF 13h SSPADD

(2)

93h 113h 193h

SSPCON 14h SSPSTAT 94h

114h 194h

CCPR1L 15h WPUA 95h WPUB 115h 195h

CCPR1H 16h IOCA 96h IOCB 116h 196h

CCP1CON 17h WDTCON 97h

117h 197h

RCSTA 18h TXSTA 98h VRCON 118h 198h

TXREG 19h SPBRG 99h CM1CON0 119h 199h

RCREG 1Ah SPBRGH 9Ah CM2CON0 11Ah

19Ah

1Bh BAUDCTL 9Bh CM2CON1 11Bh 19Bh

PWM1CON 1Ch 9Ch 11Ch 19Ch

ECCPAS 1Dh

9Dh 11Dh PSTRCON 19Dh

ADRESH 1Eh ADRESL 9Eh ANSEL 11Eh SRCON 19Eh

ADCON0 1Fh ADCON1 9Fh ANSELH 11Fh 19Fh

General

Purpose

96 Bytes

20h

General

Purpose

80 Bytes

A0h

General

Purpose

80 Bytes

120h

1A0h

EFh 16Fh

accesses

70h-7Fh

F0h accesses

70h-7Fh

170h accesses

70h-7Fh

1F0h

7Fh FFh 17Fh 1FFh

Bank 0 Bank 1 Bank 2 Bank 3

Unimplemented data memory locations, read as ‘0’.

Note 1: Not a physical register.

2: Address 93h also accesses the SSP Mask (SSPMSK) register under certain conditions.

What is MPLAB X IDE?

 2011-2015 Microchip Technology Inc. DS50002027D-page 17

In addition to memory, the microcontroller has a number of peripheral device circuits on

the same chip (Figure 1-4). Some peripheral devices are called input/output (I/O) ports.

I/O ports are pins on the microcontroller that can be used as outputs and driven high or

low to send signals, blink lights, drive speakers – just about anything that can be sent

through a wire. Often these pins are bidirectional and can also be configured as inputs,

allowing the program to respond to an external switch, a sensor, or to communicate

with some external device.

FIGURE 1-4:

PIC

MCU DATA SHEET – BLOCK DIAGRAM (EXCERPT)

To design such a system, choose which peripherals are necessary for the application.

The following is a list of common peripherals:

• Analog-to-Digital Converters (ADCs) allow microcontrollers to connect to sensors

and receive changing voltage levels.

• Serial communication peripherals that allow streaming communications over a

few wires to another microcontroller, to a local network, or to the Internet.

• Peripherals on the PIC MCU called “timers” accurately measure signal events and

generate and capture communications signals, produce precise waveforms, even

automatically reset the microcontroller if it gets “hung” or lost due to a power glitch

or hardware malfunction.

• Other peripherals detect when the external power is dipping to dangerous levels,

so that the microcontroller can store critical information and safely shut down

before power is completely lost.

PORTA

PORTB

PORTC

RA4/T0CKI

RA5/AN4/LVDIN

RB0/INT0

RC0/T1OSO/T13CKI

RC1/T1OSI/CCP2

RC2/CCP1

RC3/SCK/SCL

RC4/SDI/SDA

RC5/SDO

RC6/TX1/CK1

RC7/RX1/DT1

RA3/AN3/V

REF

RA2/AN2/V

REF

RA1/AN1

RA0/AN0

RB1/INT1

Data Latch

Data RAM

Address Latch

Address<12>

Bank0, F

BSR

FSR0

FSR1

FSR2

Inc/Dec

Logic

Decode

12 4

PCH PCL

PCLATH

31 Level Stack

Program Counter

Address Latch

Program

Data Latch

Table Pointer<21>

Data Bus<8>

Table Latch

ROM Latch

RB2/INT2

RB3/INT3

PCLATU

PCU

RA6

RB4/KBI0

RB5/KBI1/PGM

RB6/KBI2/PGC

RB7/KBI3/PGD

Memory

Inc/Dec Logic

What is MPLAB X IDE?

 2011-2015 Microchip Technology Inc. DS50002027D-page 19

1.2.3 Implementing an Embedded System Design with MPLAB X IDE

A development system for embedded controllers is a system of programs running on a

computer that help to write, edit, debug and program code – which is the intelligence

of embedded systems applications – into a microcontroller. MPLAB X IDE is such a

system, it contains all the components needed to design and deploy embedded

systems applications.

The typical tasks for developing an embedded controller application are:

1. Create the high level design. From the features and performance desired, decide

which PIC MCU or dsPIC DSC device is best suited to the application, then

design the associated hardware circuitry. After determining which peripherals

and pins control the hardware, write the firmware – the software that will control

the hardware aspects of the embedded application. A language tool such as an

assembler, which is directly translatable into machine code, or a compiler that

allows a more natural language for creating programs, should be used to write

and edit code. Assemblers and compilers help make the code understandable,

allowing function labels to identify code routines with variables that have names

associated with their use, and with constructs that help organize the code in a

maintainable structure.

2. Compile, assemble and link the software using the assembler and/or compiler

and linker to convert your code into “ones and zeros” – machine code for the PIC

MCUs. This machine code will eventually become the firmware (the code pro-

grammed into the microcontroller).

3. Test your code. Usually a complex program does not work exactly the way

imagined, and “bugs” need to be removed from the design to get proper results.

The debugger allows you to see the “ones and zeros” execute, related to the

source code you wrote, with the symbols and function names from your program.

Debugging allows you to experiment with your code to see the value of variables

at various points in the program, and to do “what if” checks, changing variable

values and stepping through routines.

4. “Burn” the code into a microcontroller and verify that it executes correctly in the

finished application.

Of course, each of these steps can be quite complex. The important thing is to concen-

trate on the details of your own design, while relying upon MPLAB X IDE and its com-

ponents to get through each step without continuously encountering new learning

curves.

MPLAB

X IDE User’s Guide

DS50002027D-page 20  2011-2015 Microchip Technology Inc.

Step 1 is driven by the designer, although MPLAB X IDE can help in modeling circuits

and code so that crucial design decisions can be made.

MPLAB X IDE really helps with steps 2 through 4. Its Programmer’s Editor helps write

correct code with the language tools of choice. The editor is aware of the assembler

and compiler programming constructs and automatically “color-keys” the source code

to help ensure it is syntactically correct. The Project Manager enables you to organize

the various files used in your application: source files, processor description header

files and library files. When the code is built, you can control how rigorously code will

be optimized for size or speed by the compiler and where individual variables and pro-

gram data will be programmed into the device. You can also specify a “memory model”

in order to make the best use of the microcontroller’s memory for your application. If

the language tools run into errors when building the application, the offending line is

shown and can be double clicked to go to the corresponding source file for immediate

editing. After editing, you will rebuild and try your application again. Often this

write-compile-fix loop is done many times for complex code as the sub-sections are

written and tested. MPLAB X IDE goes through this loop with maximum speed, allowing

you to get on to the next step.

When the code builds with no errors, it needs to be tested. MPLAB X IDE has compo-

nents called “debuggers” and free software simulators for all PIC MCU and dsPIC DSC

devices to help test the code. Even if the hardware is not yet finished, you can begin

testing the code with the simulator, a software program that simulates the execution of

the microcontroller. The simulator can accept a simulated input (stimulus), in order to

model how the firmware responds to external signals. The simulator can measure code

execution time, single step through code to watch variables and peripherals, and trace

the code to generate a detailed record of how the program ran.

When the hardware is in a prototype stage, a hardware debugger, such as an in-circuit

emulator or an in-circuit debugger, can be used. These debug tools run the code in real

time on your actual application by using special circuitry built into many devices with

Flash program memory. They can “see into” the target microcontroller’s program and

data memory, and stop and start program execution, allowing you to test the code with

the microcontroller in place on the application.

After the application is running correctly, you can program a microcontroller with one of

Microchip’s devices or development programmers. These programmers verify that the

finished code will run as designed. MPLAB X IDE supports most PIC MCUs and all

dsPIC DSCs.

剩余329页未读，继续阅读

qq_34073648

粉丝: 0
资源: 1

Microchip MPLAB X IDE用户指南：PIC单片机开发详解

mplab中git的用法.pdf

MPLAB® X IDE 用户指南

MPLAB XIDE 开发环境.zip

MPLAB® IDE中文用户指南+MPLAB® IDE英文用户指南+MPLAB® IDE中文快速入门指南.7z

用于MPLAB® X IDE的代码性能分析插件.pdf

MPLAB_X_IDE用户指南.zip_mplab_mplab x_mplab x ide

MPLAB X IDE User's Guide

MPLAB®代码配置器MCCv3.xx_用户指南.pdf

MPLAB X IDE 用户指南.pdf

MPLAB® X IDE用户指南

最新资源