MPLAB® IDE Quick Start Guide

© 2007 Microchip Technology Inc.


Note the following details of the code protection feature on Microchip devices: • • • Microchip products meet the specification contained in their particular Microchip Data Sheet. Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions. There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of intellectual property. Microchip is willing to work with the customer who is concerned about the integrity of their code. Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing the product as “unbreakable.”

• •

Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.

Information contained in this publication regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.

Trademarks The Microchip name and logo, the Microchip logo, Accuron, dsPIC, KEELOQ, KEELOQ logo, microID, MPLAB, PIC, PICmicro, PICSTART, PRO MATE, rfPIC and SmartShunt are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. AmpLab, FilterLab, Linear Active Thermistor, Migratable Memory, MXDEV, MXLAB, SEEVAL, SmartSensor and The Embedded Control Solutions Company are registered trademarks of Microchip Technology Incorporated in the U.S.A. Analog-for-the-Digital Age, Application Maestro, CodeGuard, dsPICDEM,, dsPICworks, ECAN, ECONOMONITOR, FanSense, FlexROM, fuzzyLAB, In-Circuit Serial Programming, ICSP, ICEPIC, Mindi, MiWi, MPASM, MPLAB Certified logo, MPLIB, MPLINK, PICkit, PICDEM,, PICLAB, PICtail, PowerCal, PowerInfo, PowerMate, PowerTool, REAL ICE, rfLAB, Select Mode, Smart Serial, SmartTel, Total Endurance, UNI/O, WiperLock and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. SQTP is a service mark of Microchip Technology Incorporated in the U.S.A. All other trademarks mentioned herein are property of their respective companies. © 2007, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved. Printed on recycled paper.

Microchip received ISO/TS-16949:2002 certification for its worldwide headquarters, design and wafer fabrication facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California and India. The Company’s quality system processes and procedures are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and analog products. In addition, Microchip’s quality system for the design and manufacture of development systems is ISO 9001:2000 certified.

DS51281G-page ii

© 2007 Microchip Technology Inc.

Chapter 1. What is MPLAB® IDE?
1.1 An Overview of Embedded Systems .............................................................. 1 1.2 The Development Cycle ................................................................................. 6 1.3 Project Manager ............................................................................................. 7 1.4 Language Tools .............................................................................................. 8 1.5 Target Debugging ........................................................................................... 9 1.6 Device Programming .................................................................................... 10 1.7 Components of MPLAB IDE ......................................................................... 10 1.8 MPLAB IDE Documentation ......................................................................... 11 1.9 MPLAB IDE On-line Help ............................................................................. 11 1.10 MPLAB IDE Updates and Version Numbering ........................................... 14

Chapter 2. A Basic Tutorial for MPLAB IDE
2.1 Introduction ................................................................................................... 15 2.2 MPLAB IDE Features and Installation .......................................................... 16 2.3 Tutorial Overview ......................................................................................... 18 2.4 Selecting the Device ..................................................................................... 19 2.5 Creating the Project ...................................................................................... 20 2.6 Setting Up Language Tools .......................................................................... 21 2.7 Naming the Project ....................................................................................... 22 2.8 Adding Files to the Project ........................................................................... 23 2.9 Building the Project ...................................................................................... 26 2.10 Creating Code ............................................................................................ 27 2.11 Building the Project Again .......................................................................... 29 2.12 Testing Code with the Simulator ................................................................ 30 2.13 Tutorial Summary ....................................................................................... 37

Worldwide Sales and Service .................................................................................... 40

© 2007 Microchip Technology Inc.

DS51281G-page iii

MPLAB® IDE Quick Start Guide

DS51281G-page iv

© 2007 Microchip Technology Inc.

Embedded designs use inexpensive microcontrollers to put intelligence into the everyday things in our environment. such as a user test function. such as a cordless drill. 1. unattended for years!). or sub-module of another product. 1. video controllers. While a PC with a sensor and audio output could be programmed to do the same function.1. These microcontrollers combine a microprocessor unit (like the CPU in a desktop PC) with some additional circuits called “peripherals”. automobiles. Its function is to evaluate signals from a sensor and sound an alarm if the signals indicate the presence of smoke.2 Differences Between an Embedded Controller and a PC The main difference between an embedded controller and a PC is that the embedded controller is dedicated to one specific task or set of tasks. network interface circuits. cameras. or lies dormant in a low-power “sleep” mode. A PC has a relatively expensive generalized central processing unit (CPU) at its heart with many other external devices (memory. disk drives.MPLAB® IDE QUICK START GUIDE Chapter 1. such as smoke detectors. etc.7 “Components of MPLAB IDE”. as a result. can be made cheaply to include just enough computing power and hardware to perform that dedicated task. It is called an Integrated Development Environment. plus some additional circuits on the same chip to make a small control module requiring few other external devices. sampling the signal from the smoke sensor. This single device can then be embedded into other electronic and mechanical devices for low-cost digital control. It is also recommended that Section 1. it would not be a cost-effective solution (nor would it run on a nine-volt battery.).1 Description of an “Embedded System” An embedded system is typically a design making use of the power of a small microcontroller.9 “MPLAB IDE On-line Help” and Section 1. A small program in the smoke detector either runs in an infinite loop. and a low battery alert. The program would possibly have a few other functions. and with relatively few external devices. An embedded system has a low-cost microcontroller unit (MCU) for its intelligence.1 AN OVERVIEW OF EMBEDDED SYSTEMS MPLAB IDE is a Windows® Operating System (OS) software program that runs on a PC to develop applications for Microchip microcontrollers and digital signal controllers. or IDE. smart cards and security systems. The controller in these products does a tiny portion of the function of the whole device. Often. The controller adds low-cost intelligence to some of the critical sub-systems in these devices. refrigerator or garage door opener. The program then sounds the alarm. cell phones. like the Microchip PIC® MCU or dsPIC® Digital Signal Controller (DSCs). with many peripheral circuits on the same chip. An embedded controller has a single program and. An example of an embedded system is a smoke detector.10 “MPLAB IDE Updates and Version Numbering” be reviewed. What is MPLAB® IDE? 1.1. © 2007 Microchip Technology Inc. DS51281G-page 1 . A PC is designed to run many different types of programs and to connect to many different external devices. an embedded system is an invisible part. Experienced embedded systems designers may want to skip ahead to Section 1. appliances. The rest of this chapter briefly explains embedded systems development and how MPLAB IDE is used. because it provides a single integrated “environment” to develop code for embedded microcontrollers. being awakened by a signal from the sensor.

3 Components of a Microcontroller The PIC MCU has program memory for the firmware. . Some peripheral devices are called I/O ports. Analog-to-Digital Converters (ADCs) allow microcontrollers to connect to sensors and receive changing voltage levels. F 12 Decode IR RC0/T1OSO/T13CKI RC1/T1OSI/CCP2 RC2/CCP1 RC3/SCK/SCL RC4/SDI/SDA RC5/SDO RC6/TX1/CK1 RC7/RX1/DT1 In order to design such a system. produce precise waveforms. to run a program. sensor or to communicate with some external device. Peripherals on the PIC MCU called “timers” accurately measure signal events and generate and capture communications signals. DS51281G-page 2 © 2007 Microchip Technology Inc. to a local network or to the internet. It also has “file register” memory for storage of variables that the program will need for computation or temporary storage. it must be decided which peripherals are needed for an application. Other peripherals detect if the external power is dipping below dangerous levels so the microcontroller can store critical information and safely shut down before power is completely lost. Often these pins are bidirectional and can also be configured as inputs allowing the program to respond to an external switch. or coded instructions. FIGURE 1-1: PIC® MCU DATA SHEET – BLOCK DIAGRAM (EXCERPT) Data Bus<8> PORTA RA0/AN0 RA1/AN1 RA2/AN2/VREFRA3/AN3/VREF+ RA4/T0CKI RA5/AN4/LVDIN RA6 PORTB RB0/INT0 RB1/INT1 RB2/INT2 RB3/INT3 RB4/KBI0 RB5/KBI1/PGM RB6/KBI2/PGC RB7/KBI3/PGD PORTC 21 21 Table Pointer<21> Data Latch 8 8 Data RAM Address Latch Inc/Dec Logic 21 PCLATU PCLATH 12 Address<12> 4 BSR PCU PCH PCL Program Counter Address Latch Program Memory Data Latch Table Latch 16 8 ROM Latch 31 Level Stack 12 FSR0 FSR1 FSR2 Inc/Dec Logic 4 Bank0. It also has a number of peripheral device circuits on the same chip. drive speakers – just about anything that can be sent through a wire. I/O ports are pins on the microcontroller that can be driven high or low to send signals.MPLAB® IDE Quick Start Guide 1.1. Serial communication peripherals allow you to stream communications over a few wires to another microcontroller. even automatically reset the microcontroller if it gets “hung” or lost due to a power glitch or hardware malfunction. blink lights.

and with constructs that help organize the code in a maintainable structure. write the firmware – the software that will control the hardware aspects of the embedded application. From the features and performance desired. allowing function labels to identify code routines with variables that have names associated with their use. MPLAB IDE runs on a PC and contains all the components needed to design and deploy embedded systems applications. decide which PIC MCU or dsPIC DSC device is best suited to the application. or a compiler that allows a more natural language for creating programs. The typical tasks for developing an embedded controller application are: 1. After determining which peripherals and pins control the hardware. FIGURE 1-2: Example PIC® MCU DEVICE PACKAGE E E1 #leads=n1 p D1 D 2 1 B n CH x 45° A c A2 L φ α β A1 (F) 1. the size and characteristics of the physical package that must reside on the target design. DS51281G-page 3 . A language tool such as an assembler. which is directly translatable into machine code.e. Assemblers and compilers help make the code understandable. debug and program code – the intelligence of embedded systems applications – into a microcontroller. Other factors might include the power consumed by the microcontroller and its “form factor. should be used to write and edit code.. then design the associated hardware circuitry.1.” i.What is MPLAB® IDE? The peripherals and the amount of memory an application needs to run a program largely determines which PIC MCU to use. edit.4 Implementing an Embedded System Design with MPLAB IDE A development system for embedded controllers is a system of programs running on a desktop PC to help write. Create the high level design. FIGURE 1-3: Q1 Q2 Q3 Q4 Q1 1 PIC® MCU DATA SHEET – TIMING (EXCERPT) TT1P 2 3 4 TSCS 5 6 7 8 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 T1OSI OSC1 Internal System Clock SCS (OSCCON<0>) Program Counter TOSC TDLY PC PC + 2 PC + 4 © 2007 Microchip Technology Inc.

and to do “what if” checks. Of course. changing variable values and stepping through routines. each of these steps can be quite complex. DS51281G-page 4 © 2007 Microchip Technology Inc. This machine code will eventually become the firmware (the code programmed into the microcontroller). related to the source code you wrote. “Burn” the code into a microcontroller and verify that it executes correctly in the finished application. . Usually a complex program does not work exactly the way imagined. assemble and link the software using the assembler and/or compiler and linker to convert your code into “ones and zeroes” – machine code for the PIC MCUs. The important thing is to concentrate on the details of your own design. Compile.MPLAB® IDE Quick Start Guide FIGURE 1-4: PIC® MCU DATA SHEET – INSTRUCTIONS (EXCERPT) 2. Test your code. 4. 3. The debugger allows you to see the “ones and zeroes” execute. 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 “bugs” need to be removed from the design to get proper results. while relying upon MPLAB IDE and its components to get through each step without continuously encountering new learning curves.

or MPLAB ICD 2 in-circuit debugger can be used. in order to model how the firmware responds to external signals. processor description header files and library files. Once the code builds with no errors. 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. and trace the code to generate a detailed record of how the program ran. allowing you to test the code with the microcontroller in place on the application. Once the hardware is in a prototype stage. © 2007 Microchip Technology Inc. press the “build” button to try again. The MPLAB ICE 2000 emulator physically replaces the microcontroller in the target using a high-speed probe to give you full control over the hardware in your design. These debuggers can stop and start program execution. single step through code to watch variables and peripherals. MPLAB IDE supports PIC MCUs and dsPIC Digital Signal Controllers. MPLAB REAL ICE™ in-circuit emulator. you can begin testing the code with the simulator. MPLAB IDE has components called “debuggers” and free software simulators for PIC MCU and dsPIC DSC devices to help test the code. After editing. DS51281G-page 5 . Even if the hardware is not yet finished. you can control how rigorously code will be optimized for size or speed by the compiler and where individual variables and program data will be programmed into the device.What is MPLAB® IDE? Step 1 is driven by the designer. you can program a microcontroller with one of Microchip’s device programmers. Often this write-compile-fix loop is done many times for complex code as the sub-sections are written and tested. The simulator can measure code execution time. allowing you to get on to the next step. a software program that simulates the execution of the microcontroller. MPLAB IDE really helps with steps 2 through 4. a hardware debugger. If the language tools run into errors when building the application. You can also specify a “memory model” in order to make the best use of the microcontroller’s memory for your application. such as PICSTART® Plus or MPLAB PM3. although MPLAB IDE can help in modeling circuits and code so that crucial design decisions can be made. After the application is running correctly. such as MPLAB ICE 2000 in-circuit emulator. These debug tools run the code in real time on your actual application. Its Programmer’s Editor helps write correct code with the language tools of choice. When the code is built. it needs to be tested. the offending line is shown and can be “double clicked” to go to the corresponding source file for immediate editing. The Project Manager enables you to organize the various files used in your application: source files. The MPLAB REAL ICE in-circuit emulator and MPLAB ICD 2 debugger use special circuitry built into many Microchip MCUs with Flash program memory and can “see into” the target microcontrollers program and data memory. These programmers verify that the finished code will run as designed. The simulator can accept a simulated input (stimulus). MPLAB IDE goes through this loop with maximum speed.

In this process multiple tools are needed: an editor to write the code. . since it is rare that all the steps from design to implementation can be done flawlessly the first time. all the functions are integrated. allowing the engineer to concentrate on completing the application without the interruption of separate tools and different modes of operation. DS51281G-page 6 © 2007 Microchip Technology Inc.MPLAB® IDE Quick Start Guide 1. More often code is written. For instance. By using MPLAB IDE. tested and then modified in order to produce an application that performs correctly. it can be converted to executable instructions and downloaded into a microcontroller to see how it works. a project manager to organize files and settings. once code is written. a compiler or assembler to convert the source code to machine code and some sort of hardware or software that either connects to a target microcontroller or simulates the operation of a microcontroller. The Integrated Development Environment allows the embedded systems design engineer to progress through this cycle without the distraction of switching among an array of tools. usually automatically.2 THE DEVELOPMENT CYCLE The process for writing an application is often described as a development cycle. FIGURE 1-5: THE DESIGN CYCLE Compile/Assemble/ Link Code Download Code to Debugger Edit/Create/Design Source Code Analyze/Debug Code MPLAB IDE is a “wrapper” that coordinates all the tools from a single graphical user interface.

A text editor is used to write the code. Breakpoints can be set in the editor. © 2007 Microchip Technology Inc. compiler and libraries into the proper memory areas of the embedded controller. but an editor specifically designed for writing code for Microchip MCUs. The assembler and compiler convert them into intermediate modules of machine code and placeholders for references to functions and data storage. commenting and uncommenting out blocks of code. C language constructs and comments. DS51281G-page 7 . and a build process integrates all of the language tools operations. such as instruction mnemonics.3 PROJECT MANAGER The project manager organizes the files to be edited and other associated files so they can be sent to the language tools for assembly or compilation. and ultimately to a linker. the editor works with the other tools to display code execution in the debugger. It recognizes the constructs in the text and uses color coding to identify various elements. The linker resolves these placeholders and combines all the modules into a file of executable machine code. This entire operation from assembly and compilation through the link process is called a project “build”. and ensure that the modules function with each other (or are “linked”).What is MPLAB® IDE? 1. FIGURE 1-6: MPLAB® IDE PROJECT MANAGER Source Files Individual Build Options MPLAB® IDE Project Manager Object File Libraries Assembler Compiler Linker Script Linker Debug File Executable File The source files are text files that are written conforming to the rules of the assembler or compiler. The linker also produces a debug file which allows MPLAB IDE to relate the executing machine codes back to the source files. and the values of variables can be inspected by hovering the mouse pointer over the variable name. From the MPLAB IDE project manager. After the code is written. The linker has the task of placing the object code fragments from the assembler. such as finding matching braces in C. if desired. Names of variables can be dragged from source text windows and then dropped into a Watch window. The editor supports operations commonly used in writing source code. properties of the language tools can be invoked differently for each file. finding text in multiple files and adding special bookmarks. It is not a normal text editor.

a “cross-assembler” or “cross-compiler” is used.4 LANGUAGE TOOLS Language tools are programs such as cross-assemblers and cross-compilers. TRISB =0. } } COMPILER 01101111 10001000 11001101 10100001 00110011 01011101 00110001 11100101 DS51281G-page 8 © 2007 Microchip Technology Inc. watching the application execute.MPLAB® IDE Quick Start Guide 1. while (input1 = 0) { PORTB = count. the better. This means that techniques to optimize and enhance the code using machine specific knowledge are desirable. . and lets you single step through the source code. The size of programs for PCs typically extends into the megabytes for moderately complex programs. The language tools also produce a debug file that MPLAB IDE uses to correlate the machine instructions and memory locations with the source code. Some embedded systems use megabytes of storage for large tables. The size of simple embedded systems programs may be as small as a thousand bytes or less. hence they “cross-compile” code for a microcontroller that uses an entirely different set of instructions from the PC. counter++. When using language tools for embedded systems. The smaller the code produced. FIGURE 1-7: A COMPILER CONVERTS SOURCE CODE INTO MACHINE INSTRUCTIONS int main (void) { counter = 1. because that allows the smallest possible memory for the target. allows watch windows to view variable contents. Embedded system language tools also differ somewhat for compilers that run and execute on a PC because they must be very space conscious. user text messages or data logging. This bit of integration allows the MPLAB IDE editor to set breakpoints. which reduces cost. Most people are familiar with language tools that run on a PC such as Visual Basic or C compilers. These tools differ from typical compilers in that they run on a PC but produce code to run on another microprocessor. A medium size embedded system might need 32K or 64K of code for relatively complex functions.

” These last steps. like a simulator. A simulator is a software debugger. This process is called debugging. and it is difficult to understand exactly what is going wrong in the hardware. Usually a simulator runs somewhat slower than an actual microcontroller. it will run as designed. which use microcontrollers that have special built-in debugging features. and the engineer is tasked with reviewing the code and its operation in the application to determine how to modify the original source code to make it execute as desired. the code could be changed. As noted previously. the code does not function exactly as anticipated. recompiling. DS51281G-page 9 . As deadlines loom. and single step to follow instructions as the hardware interacts with its specialized circuitry. many things outside the scope of the simulator come into play. and the debugger functions for the simulator are almost identical to the hardware debuggers. That's where an integrated development environment is most important. and often has the most influence on producing delays in getting a product out. or it can be special instrumentation to analyze the program as it executes in the application. With MPLAB IDE many tools can be selected. allows the engineer to inspect variables at various points in the code. A hardware debugger. reprogrammed into the microcontroller and plugged into the target for retest. The microcontroller can then be plugged into the application and. Using all tools within a single environment will reduce the time around the “cycle. A programmer simply burns the machine code from the PC into the internal memory of the target microcontroller. Using just a programmer. getting the application to function as originally designed is the last step before going into deployment of the product. where critical bugs are worked out. but this could be a long. which use specialized hardware in place of the actual target microcontroller. Doing fine “tweaks” to the code. but once a microcontroller is programmed with the firmware. Simulators are built into MPLAB IDE so a program can be tested without any additional hardware. since the CPU in the PC is being used to simulate the operations of the microcontroller. however. and the learning curve from simulator to low-cost in-circuit debugger to powerful in-circuit emulator is small. hopefully. the execution of the code is tested on a debugger. the simulator can be used to test how the code will operate. are a test for the embedded systems designer. The debugger can be a software program that simulates the operation of the microcontroller for testing.5 TARGET DEBUGGING In a development environment. there are many simulators for each of the PIC MCU and the dsPIC DSC processors. laborious cycle if the code is complex. downloading and testing all require time. Usually. This is where a hardware debugger is useful. Hardware debuggers can be in-circuit emulators. In the case of MPLAB IDE. or they can be in-circuit debuggers.What is MPLAB® IDE? 1. but they all will have a similar interface. © 2007 Microchip Technology Inc. Debugging usually becomes urgent near the end of the project design cycle. allowing a new tool to be learned with ease. The right tool can save time. There are two types of hardware that can be used with MPLAB IDE: programmers and hardware debuggers.

7 COMPONENTS OF MPLAB IDE The MPLAB IDE has both built-in components and plug-in modules to configure the system for a variety of software and hardware tools. or can be used with the linker to build a project from separate source files. allowing updated revisions to be programmed into an embedded application later in its life cycle. • Debugger The Microchip debugger allows breakpoints. DS51281G-page 10 © 2007 Microchip Technology Inc. . It works in conjunction with the editor to reference information from the target being debugged back to the source code.MPLAB® IDE Quick Start Guide 1. libraries and recompiled objects.1 MPLAB IDE Built-In Components The built-in components consist of: • Project Manager The project manager provides integration and communication between the IDE and the language tools. • Assembler/Linker and Language Tools The assembler can be used stand-alone to assemble a single file. the firmware can be programmed into the application at the time of manufacture. The linker is responsible for positioning the compiled code into memory areas of the target microcontroller.7. MPLAB IDE can be set to the programmer function. and the part can be “burned”. 1. it needs to be tested on its own. Using In-Circuit Serial Programming™ (ICSP™) programming capability. Optional in-circuit emulators and in-circuit debuggers are also available to test code as it runs in the applications hardware. single stepping. watch windows and all the features of a modern debugger for the MPLAB IDE. • Editor The editor is a full-featured programmer's text editor that also serves as a window into the debugger. Engineering prototype programmers allow quick prototypes to be made and evaluated. A device can be programmed with the in-circuit debugger or a device programmer.6 DEVICE PROGRAMMING After the application has been debugged and is running in the development environment. 1. The target application can now be observed in its nearly final state. • Execution Engines There are software simulators in MPLAB IDE for all PIC MCU and dsPIC DSC devices. Devices that support in-circuit debugging can even be plugged back into the MPLAB ICD 2 after manufacturing for quality tests and development of next generation firmware. Some applications can be programmed after the device is soldered on the target PC board. These simulators use the PC to simulate the instructions and some peripheral functions of the PIC MCU and dsPIC DSC devices.

Always try to review this section before working with a new device/tool combination. optimized code.7. • In-Circuit Debugger MPLAB ICD 2 and PICkit 2 provide economic alternatives to an emulator.What is MPLAB® IDE? 1. MPLAB IDE comes with extensive on-line help. Check the Microchip web site for downloadable PDF versions of all these documents. For this reason. CCS and Byte Craft. single step and monitor registers and variables. microEngineering Labs. set breakpoints. If questions arise while using MPLAB IDE. 1. menu lists may be in different order. • “MPLAB® IDE User’s Guide” (DS51519) Other documents exist for various Microchip software and hardware tools that work with MPLAB IDE. IAR. as well as the MPLAB ICD 2 debugger and MPLAB REAL ICE in-circuit emulator can program code into target devices.10 “MPLAB IDE Updates and Version Numbering”) some details in this documentation may change. Along with compilers from HI-TECH. be sure to check the on-line help for answers. • Programmers MPLAB PM3. 1. the on-line help is the best reference to the version of MPLAB IDE being used. which is constantly being updated. PICSTART® Plus.8 MPLAB IDE DOCUMENTATION The following documents are available to help you use MPLAB IDE: • “MPLAB® IDE Quick Chart” (DS51410) • “MPLAB® IDE Quick Start Guide” (DS51281) – Chapters 1 and 2 of user’s guide. Most importantly. • In-Circuit Emulators The MPLAB REAL ICE and MPLAB ICE 2000 systems are in-circuit emulators for PIC MCU and dsPIC DSC devices. MPLAB ICD 2 can download code into a target microcontroller inserted in the application. MPLAB IDE offers full control over programming both code and data. © 2007 Microchip Technology Inc. They connect to the PC via I/O ports and allow full control over the operation of microcontroller in the target applications. or may have new items. as well as the Configuration bits to set the various operating modes of the target microcontrollers or digital signal controllers. By using some of the on-chip resources.9 MPLAB IDE ON-LINE HELP Since MPLAB IDE is under a constant state of change (see Section 1. DS51281G-page 11 . PICkit™ 1 and 2. Dialogs might not appear exactly as they do in this manual.2 Additional Optional Components for MPLAB IDE Optional components can be purchased and added to the MPLAB IDE: • Compiler Language Tools MPLAB C18 and MPLAB C30 C compilers from Microchip provide fully integrated. they are invoked by the MPLAB IDE project manager to compile code that is automatically loaded into the target debugger for instant testing and verification. the on-line help lists any restrictions that might exist for a particular tool in support of a particular device.

FIGURE 1-8: DEBUGGER>SETTINGS. compared to the actual device being simulated. emulator or in-circuit debugger might have.MPLAB® IDE Quick Start Guide The Limitations tab in the Debugger>Settings dialog displays any restrictions the simulator. . General limitations are shown in the text area. FIGURE 1-9: SIMULATOR LIMITATIONS DETAIL DS51281G-page 12 © 2007 Microchip Technology Inc. LIMITATIONS TAB Press the Details button to show specific limitations of the device being debugged. help on general limitations related to the debugger can also be accessed. From this display.

select Help>Topics to get a list of help on MPLAB IDE and all of its components. as an index and with a search utility for help on any MPLAB IDE topic. FIGURE 1-10: MPLAB® IDE HELP>TOPICS MENU MPLAB IDE Help covers all aspects of MPLAB IDE and all of the Microchip tools. such as the Microchip Update Notification system. DS51281G-page 13 . FIGURE 1-11: MPLAB® IDE HELP DIALOG © 2007 Microchip Technology Inc. It also directs users to other types of assistance. It can be viewed in an outline.What is MPLAB® IDE? From the main MPLAB IDE Help menu.

although based on production releases that are fully tested. it is considered “best practice” to not update to the new release unless there is a compelling reason to do so. for quick critical fixes or for previews of new features. If the version number ends with a digit other than zero.20. e. v7.11. Microchip Technology is continually designing new microcontrollers with new features. DS51281G-page 14 © 2007 Microchip Technology Inc. MPLAB IDE is scheduled for a version update approximately every four months to add new device support and new features. v7.10 MPLAB IDE UPDATES AND VERSION NUMBERING MPLAB IDE is an evolving program with thousands of users. Additional “interim” releases are produced in between these major releases.microchip. Interim releases are typically provided for early adopters of new devices or components. The on-line help is the best source for any questions about MPLAB IDE.10 or v7. To be notified of updates to MPLAB IDE and its components. for projects that are midway through development when a new version of MPLAB IDE is released. MPLAB IDE v7. The start of a new project is the best time to update to a new release. such as a bug fix on a bug that inhibits the current efforts. Each new release of the MPLAB IDE software has new features implemented.g. Many new MPLAB IDE features come from customer requests and from internal usage. subscribe to the Development Tools section of the Customer Change Notification service on www. . unless a new device or component is being used or a particular problem has been fixed in an interim release that enables more productive use of MPLAB IDE.55.MPLAB® IDE Quick Start Guide 1. The version numbering scheme for MPLAB IDE reflects whether it is a major production release or an interim release.. Continued new designs and the release of new microcontrollers ensure that MPLAB IDE will continue to evolve. and therefore these releases are not recommended for rigorous design use. v7. this identifies an interim release. so the printed documentation will inevitably “lag” the on-line help. e. may have components that are not as fully tested. It is advised that production releases be used for development work.22 or v7.g. These interim releases.. this identifies a major production release.00. If the version number ends in a zero.

How to make projects.MPLAB® IDE QUICK START GUIDE Chapter 2. edit code and test an application will be the subject of a short tutorial. A Basic Tutorial for MPLAB IDE 2. Someone unfamiliar with MPLAB IDE will get a basic understanding of using the system to develop an application. The initial use of MPLAB IDE is covered here. It is followed by a simple step-by-step tutorial that creates a project and explains the elementary debug capabilities of MPLAB IDE. The complete feature set of MPLAB IDE is covered in later chapters. the basic concepts of the Project Manager. project manager and design desktop for application development of embedded designs using Microchip PIC MCUs and dsPIC DSCs. By going through the tutorial. Editor and Debugger can be quickly learned. These basic steps will be covered in the tutorial: • • • • • • • • • • • • MPLAB IDE Features and Installation Tutorial Overview Selecting the Device Creating the Project Setting Up Language Tools Naming the Project Adding Files to the Project Building the Project Creating Code Building the Project Again Testing Code with the Simulator Tutorial Summary © 2007 Microchip Technology Inc.1 INTRODUCTION The MPLAB Integrated Development Environment (IDE) is a comprehensive editor. This section details the installation and uninstall of MPLAB IDE. No previous knowledge is assumed. DS51281G-page 15 . and comprehensive technical details of MPLAB IDE and its components are omitted in order to present the basic framework for using MPLAB IDE.

use Windows Explorer to find and execute the CD-ROM file. locate the download (. administrative access is required in order to install software on a PC.2 MPLAB IDE FEATURES AND INSTALLATION MPLAB IDE is a Windows® Operating System (OS) based Integrated Development Environment for the PIC MCU families and the dsPIC Digital Signal • If downloading MPLAB IDE from the Microchip web site (www. • Make timing measurements with the simulator or emulator. • Program firmware into devices with device programmers (for details. • If installing from a CD-ROM.2. If no on-screen menu appears. menu. . Find MPLAB IDE on the list and click on it.exe. compile and link source code. consult the user’s guide for the specific device programmer).MPLAB® IDE Quick Start Guide 2. • View variables in Watch windows. select the file and save it to the PC. 2. DS51281G-page 16 © 2007 Microchip Technology Inc. • Debug the executable logic by watching program flow with the built-in simulator or in real time with in-circuit emulators or in-circuit debuggers.microchip. place the disk into a CD drive. Check the release notes or readme files for details. The MPLAB IDE provides the ability to: • Create and edit source code using the built-in editor. To uninstall MPLAB IDE: • Select Start>Settings>Control Panel to open the Control Panel. Unzip the file and execute the resulting file to install. • Assemble. • Double click on Add/Remove Programs. Note: Selected third party tools are also supported by MPLAB IDE. • Click Change/Remove to remove the program from your system.1 Install/Uninstall MPLAB IDE To install MPLAB IDE on your system: Note: For some Windows OSs. Follow the on-screen menu to install MPLAB IDE.

2.xx>MPLAB IDE. A screen will display the MPLAB IDE logo followed by the MPLAB IDE desktop (Figure 2-1). FIGURE 2-1: MPLAB® IDE DESKTOP © 2007 Microchip Technology Inc. double click on the icon installed on the desktop after installation or select Start>Programs>Microchip>MPLAB IDE vx.A Basic Tutorial for MPLAB IDE 2. DS51281G-page 17 .2 Running MPLAB IDE To start MPLAB IDE.

3 TUTORIAL OVERVIEW In order to create code that is executable by the target PIC MCU. the built-in assembler and linker will be used. New features will be added as additional parts are released. Device selection should be completed before starting a project. compilers. • Test Code with Simulator Finally. the code will be tested with the simulator. the project manager controls this process. All projects will have these basic steps: • Select Device The capabilities of MPLAB IDE vary according to which device is selected. • Build Project The project will be built – causing the source files to be assembled and linked into machine code that can run on the selected PIC MCU. linkers. one of the Microchip compilers or other third party tools might be selected. a template file and a linker script. source files need to be put into a project. The code can then be built into executable code using selected language tools (assemblers. • Create Project MPLAB IDE Project Wizard will be used to Create a Project. It is easy to get started using these two files. DS51281G-page 18 © 2007 Microchip Technology Inc. None of the functions described in this tutorial will be removed. Both of these files exist in sub-folders within the MPLAB IDE folder. For other projects. Note: Some aspects of the user interface will change in future product releases and the screen shots in this tutorial may not exactly match the appearance of the MPLAB IDE desktop in later releases. The Project Wizard will easily guide us through most of these steps. • Put Files in Project Two files will be put into the project. but more features may be added. In MPLAB IDE. • Select Language Tools In the Project Wizard the language tools will be selected. etc. For this tutorial. • Create Code Some code will be added to the template file to send an incrementing value out an I/O port.The on-line help is the most up-to-date reference for the current version of MPLAB IDE.). .MPLAB® IDE Quick Start Guide 2.

it would be written as Configure>Select Device.g.. Choose Configure>Select Device. e. dsPIC DSC devices cannot be supported on MPLAB ICE 2000. DS51281G-page 19 .4 SELECTING THE DEVICE To show menu selections in this document. In the Device dialog. select the PIC18F8722 from the list if it’s not already selected. • A yellow light indicates preliminary support for an upcoming part by the particular MPLAB IDE tool component.A Basic Tutorial for MPLAB IDE 2. the menu item from the top row in MPLAB IDE will be shown after the menu name like this MenuName>MenuItem. Support may be forthcoming or inappropriate for the tool. FIGURE 2-2: SELECT DEVICE DIALOG The “lights” indicate which MPLAB IDE components support this device. • A green light indicates full support. Components with a yellow light instead of a green light are often intended for early adopters of new parts who need quick support and understand that some operations or functions may not be available. To choose the Select Device entry in the Configure menu. © 2007 Microchip Technology Inc. • A red light indicates no support for this device.

click on Next> to advance. If it does not. A project is the way the files are organized to be compiled and assembled. FIGURE 2-4: PROJECT WIZARD – SELECT DEVICE DS51281G-page 20 © 2007 Microchip Technology Inc. Make sure that it says PIC18F8722. From the Welcome dialog.MPLAB® IDE Quick Start Guide 2. Click Next>. . FIGURE 2-3: PROJECT WIZARD WELCOME The next dialog (Step One) allows you to select the device. select the PIC18F8722 from the drop down menu. which we’ve already done. We will use a single assembly file for this project and a linker script. Choose Project>Project Wizard.5 CREATING THE PROJECT The next step is to create a project using the Project Wizard.

which calls _mplink.exe (output conversion to Hex file).A Basic Tutorial for MPLAB IDE 2. MPLAB IDE will call the linker and Hex converter seperately. mp2cod. © 2007 Microchip Technology Inc. and the MPLIB™ librarian executable will be: C:\Program Files\Microchip\MPASM Suite\mplib. mplink. use the browse button to set them to the proper files in the MPLAB IDE subfolders. If MPLAB IDE was installed into the default directory. Click on each one to see its location. with no COD file generation. By default.exe (output conversion to COD file) and mp2hex.exe (linker).exe Note: There is also a wrapper executable.exe.6 SETTING UP LANGUAGE TOOLS Step Two of the Project Wizard sets up the language tools that are used with this project. Then “MPASM” and “MPLINK” should be visible in the Toolsuite Contents box. the MPASM™ assembler executable will be: C:\Program Files\Microchip\MPASM Suite\mpasmwin. click Next>. Select “Microchip MPASM Toolsuite” in the Active Toolsuite list box. DS51281G-page 21 .exe If these do not show up correctly. FIGURE 2-5: PROJECT WIZARD – SELECT LANGUAGE TOOLS When you are finished.exe the MPLINK™ linker executable will be: C:\Program Files\Microchip\MPASM Suite\_mplink.

MPLAB® IDE Quick Start Guide 2. Click Next>. . . FIGURE 2-6: PROJECT WIZARD – NAME PROJECT DS51281G-page 22 © 2007 Microchip Technology Inc.7 NAMING THE PROJECT Step Three of the wizard allows you to name the new project and put it into a folder. This sample project will be called C:\Projects\MyProject.

for use with this device when MPLAB ICD 2 is being used (hence the “i” in the name). and contain information that will help you write and organize your code. There is a linker script for each device. They have the essential sections for any source file. FIGURE 2-7: PROJECT WIZARD – SELECT TEMPLATE FILE Press Add>> to move the file name to the right panel. The template files are simple files that can be used to start a project. the full path to the file will be: C:\Program Files\Microchip\MPASM Suite\Template\Object \18F8722. Since the simulator is being used.lkr Note: There is another linker script named 18f8722i. See the device data sheet for details.8 ADDING FILES TO THE PROJECT Step Four of the Project Wizard allows file selection for the project. add the second file for our project. There is also a linker script named 18f8722_e. click on the “A” three times until a “C” appears.A Basic Tutorial for MPLAB IDE 2.lkr. If MPLAB IDE is installed in the default location. Click on the “A“ at the start of the line with the file name three times until a “C” appears. There are two template files for each Microchip PIC MCU and dsPIC DSC device: one for absolute code (no linker used) in the Code directory and one for relocatable code (linker used) in the Object directory. choose the file named 18F8722.lkr for use with the device extended instruction set. The extended instruction set will not be used in this tutorial. A source file has not yet been selected. so we will use an MPLAB IDE template file. To copy this linker script into our project. in the Object directory. Since we will be using the linker in this tutorial. These files define the memory configuration and register names for the various parts. DS51281G-page 23 .lkr. we don’t need to use that linker script. Next. the linker script. The full path is: C:\Program Files\Microchip\MPASM Suite\LKR\18f8722. This will enable this file to be copied to our project directory. © 2007 Microchip Technology Inc. Use the file named 18f8722. That linker script reserves areas in memory for MPLAB ICD 2.

MPLAB® IDE Quick Start Guide FIGURE 2-8: PROJECT WIZARD – SELECT LINKER SCRIPT Make sure that your dialog looks like the picture above. . and then press Next> to finish the Project Wizard. FIGURE 2-9: PROJECT WIZARD – SUMMARY DS51281G-page 24 © 2007 Microchip Technology Inc. the toolsuite and the new project file name. The final screen of the Project Wizard is a summary showing the selected device.

In case of error. It should look like Figure 2-10. files can be manually deleted by selecting them and using the right mouse click menu. © 2007 Microchip Technology Inc. select View>Project. review the Project Window on the MPLAB IDE desktop. DS51281G-page 25 . FIGURE 2-10: PROJECT WINDOW TIP: Files can be added and projects saved by using the right mouse button in the project window. If the Project Window is not open.A Basic Tutorial for MPLAB IDE After pressing the Finish button.

Select “Errors only” from the “Diagnostic level” drop-down list. do the following: • • • • Select Project>Build Options>Project and click on the MPASM Assembler tab. There should be no errors or warnings on any step. To turn off the display of warnings. Click OK. Hover the mouse over icons to see pop-up text of what they represent. you may ignore them for this project as they will not prevent the project from building. . if you do receive errors. Select “Output” from the “Categories” drop-down list. If you receive warnings. To build the project. The Output window shows the result of the build process. Errors will prevent the project from building.MPLAB® IDE Quick Start Guide 2. go back to the previous sections and check the project assembly steps. OUTPUT WINDOW FIGURE 2-11: DS51281G-page 26 © 2007 Microchip Technology Inc. we can assemble and link the current files.9 BUILDING THE PROJECT From the Project menu. They don’t have any of our code in them yet. However. select either: • Project>Build All • Right click on the project name in the project window and select Build All • Click the Build All icon on the Project toolbar. but this ensures that the project is set up correctly.

you could put information about your design here. or by selecting it with the cursor and using the right mouse button to bring up the context menu: FIGURE 2-12: PROJECT CONTEXT MENU (RIGHT MOUSE CLICK) The file has some comments at the beginning. TEMPLATE FILE FIGURE 2-13: The code in the first part of the file is for more advanced functions such as setting up interrupts and Configuration bits in a final application. Note: Line numbers are shown here. © 2007 Microchip Technology Inc. DS51281G-page 27 . The new code will be placed in the file at the point after the symbol Main is defined. and then checking/unchecking “Line Numbers” on the 'ASM' File Type tab of the Editor Options dialog. and this area can be used as a standard comment information header for the file. Line numbers may be toggled on/off by right clicking in the editor window.10 CREATING CODE Open the template file in the project by double clicking on its name in the Project Window. These details can be ignored at this point with focus on writing the code. For now you’ll leave this as it is. Scroll down to the bottom of the file.A Basic Tutorial for MPLAB IDE 2. selecting Properties. but if this were a real project.

go to Delay subroutine . display on PORTC .F. Type in this code beneath Main: clrf movwf movwf Init clrf IncCount incf movf movwf call goto Delay movlw movwf DelayOuter movlw movwf DelayInner decfsz goto decfsz goto return WREG PORTC TRISC . set inner delay loop DS51281G-page 28 © 2007 Microchip Technology Inc.A COUNT.F.A DelayOuter . set outer delay loop . . clear PORTC .W.A DVAR.A PORTC Delay IncCount . increase count and . configure PORTC as all outputs COUNT.A COUNT. you are automatically in the editor.MPLAB® IDE Quick Start Guide FIGURE 2-14: TEMPLATE FILE – MAIN When any source file is opened. initialize counter .F.A DelayInner DVAR2.A 0xFF DVAR. infinite loop 0x40 DVAR2.

and ours can be added at the end using the same format. There is already one variable in this section of the template file. so only 1 byte each needs to be reserved. If the code assembled with no errors. FIGURE 2-15: TEMPLATE FILE – ADD VARIABLES Add these three lines 2. DVAR and DVAR2. DS51281G-page 29 . the Output Window will look like Figure 2-16.11 BUILDING THE PROJECT AGAIN Select Project>Build All to assemble and link the code.A Basic Tutorial for MPLAB IDE In this bit of code. we used three variables named COUNT. as there will be no need to keep track of banks (banksel) for each variable. Each variable is 8-bit. These variables need to be defined in the template file in the UDATA_ACS section for uninitialized data using Access RAM. Using the Access bank will make the code simpler. FIGURE 2-16: BUILD OUTPUT WINDOW © 2007 Microchip Technology Inc.

Most of the MPLAB IDE debugging operations are the same as the simulator but. Select Project>Set Language Tool Locations. TRISC and PORTC. check the following items and then build the project again: • If the assembler reported errors in the Output window. software or hardware is needed that will execute the PIC MCU instructions.ASM). unlike the simulator. Build options can be set for each file that access other features of the language tools.MPLAB® IDE Quick Start Guide If the code did not assemble and link successfully. For this tutorial use MPLAB SIM simulator. the MPLAB SIM simulator can be used to test the code.exe) and review their location in the display. Hardware tools such as MPLAB ICE or MPLAB ICD 2 can execute code in real devices. The simulator is a software program that runs on the PC to simulate the instructions of the PIC MCU. Make sure the new variables and the special function registers. double click on the error and MPLAB IDE will open the corresponding line in the source code with a green arrow in the left margin of the source code window. If the location is correct. • Check the spelling and format of the code entered in the editor window. However. If it is not. the output file generated by the language tool will be loaded. The default search paths can be empty.12 TESTING CODE WITH THE SIMULATOR In order to test the code. are in upper case. 2. MPLAB ICD 2 in-circuit debugger and MPLAB ICE 2000 in-circuit emulator.” since the simulator program is dependent upon the speed of the PC. such as report outputs and compiler optimizations. If hardware is not available. Upon a successful build. It does not run in “real time. These are optional hardware tools to test code on the application PC board. Note: The real power of projects is evident when there are many files to be compiled/assembled and linked to form the final executable application – as in a real application. Click MPASM Assembler (mpasmwin. A debug execution tool is a hardware or software tool that is used to inspect code as it executes a program (in this case 18F8722TMPO. DS51281G-page 30 © 2007 Microchip Technology Inc. these tools allow the target PIC MCU to run at full speed in the actual target application. the simulator accurately measures the time it would take to execute the code if it were operating in real time in an application. change it and then click OK. overhead from the operating system and how many other tasks are running. the complexity of the code. Note: Other debug execution tools include MPLAB REAL ICE in-circuit emulator. • Check that the correct assembler (MPASM assembler) and linker for PIC MCU devices is being used. This file contains the object code that can be programmed into a PIC MCU and debugging information so that source code can be debugged and source variables can be viewed symbolically in Watch windows. click Cancel. Click on the plus boxes to expand the Microchip MPASM toolsuite and its executables. Projects keep track of all of this. .

After selecting MPLAB SIM. you should save your workspace setup. 1 2 3 The status bar on the bottom of the MPLAB IDE window should change to “MPLAB SIM”. Additional menu items should now appear in the Debugger menu. This is done from the Debugger>Select Tool pull down menu. FIGURE 2-17: MPLAB® IDE DESKTOP WITH MPLAB SIM AS DEBUGGER 3 2 4 1 Now that your project is set up and the debug tool is selected. Additional toolbar icons should appear in the Debug Tool Bar. the following changes should be seen (see corresponding numbers in Figure 2-17). DS51281G-page 31 . © 2007 Microchip Technology Inc.A Basic Tutorial for MPLAB IDE Select the simulator as the debug execution tool. 4 An MPLAB SIM tab is added to the Output window. TIP: Position the mouse cursor over a toolbar button to see a brief description of the button’s function. Select File>Save Workspace.

This will execute the currently indicated line of code and move the arrow to the next line of code to be executed.. where your code was inserted. i. etc. There are shortcuts for these commonly used functions in the Debug Tool Bar. TABLE 2-1: Run Halt Animate Step Into Step Over Step Out Reset F6 F7 F8 DEBUG SHORT CUT ICONS Toolbar Buttons Hot Key F9 F5 Debugger Menu TIP: Click on the appropriate icon on the toolbar or use the hot key shown next to the menu item. This was part of the template file. DS51281G-page 32 © 2007 Microchip Technology Inc.MPLAB® IDE Quick Start Guide Next.e. FIGURE 2-18: CODE AFTER PROCESSOR RESET To single step through the application program. . interrupt vectors. it jumps over the vector areas (reset vector. This is usually the best method for repeated stepping. select Debugger>Step Into.) to the user memory space in program memory. select Debugger>Reset>Processor Reset and a green arrow shows where the program will begin. The first instruction in memory jumps to the label called Main.

watch the values being sent to PORTC. FIGURE 2-20: WATCH – SELECT PORTC © 2007 Microchip Technology Inc. press the Step Into icon or select Debugger>Step Into to single step to the code at Main. FIGURE 2-19: CODE AFTER STEP INTO In order to see if the code is operating as intended. into the watch. There are two pull downs on the top of the Watch window.A Basic Tutorial for MPLAB IDE Next. Select PORTC from the list and then click Add SFR to add it to the window. sending incrementing values out PORTC. DS51281G-page 33 . PORTC. Select View>Watch to bring up an empty Watch window. The one on the left labeled “Add SFR” can be used to add the Special Function Register.

it is good idea to again save your workspace using File>Save Workspace. . Use this pull down to add the COUNT variable into the Watch window. DS51281G-page 34 © 2007 Microchip Technology Inc.MPLAB® IDE Quick Start Guide The pull down on the right. File Register or Editor window or by clicking directly in the window under symbol name and typing in the item. value and name of the two registers. WATCH – RESET VALUES FIGURE 2-22: Now that Watch windows have been added. FIGURE 2-21: WATCH – SELECT VARIABLE “COUNT” The Watch window should now show the address. At this point in the program. allows symbols to be added from the program. they will both be zero. Note: Items can also be added to the Watch window by either dragging them from the SFR. Select COUNT from the list and then click Add Symbol to add it to the window.

FIGURE 2-23: DEBUG CONTEXT MENU (RIGHT MOUSE CLICK ON LINE) Select Set Breakpoint from the context menu. DS51281G-page 35 . (You can also double click on a line to add a breakpoint. display COUNT on PORTC and click the right mouse button.A Basic Tutorial for MPLAB IDE You could continue single stepping through the code. set a breakpoint just before the first value is sent out to PORTC.) FIGURE 2-24: EDITOR WINDOW – SET BREAKPOINT © 2007 Microchip Technology Inc. To set a breakpoint. but instead. put the cursor on the line following line: movwf PORTC . A red “B” will show on the line.

DS51281G-page 36 © 2007 Microchip Technology Inc. Then. right click on the line movf COUNT. A text message “Running…” will briefly appear on the status bar before the application halts at this first breakpoint. FIGURE 2-26: WATCH – NEXT BREAKPOINT This would seem to indicate that the program is working as designed. the data book could be used to determine how long each instruction would take in your delay loop and you would come up with a pretty accurate number. . or run the code more times to verify that it is executing properly. If you set your breakpoint as was initially done. To use the Stopwatch. You can also use the MPLAB IDE Stopwatch to measure the delay. To exit out of the delay loop. You can single step through the code. PORTC still has a value of zero. on the instruction that moves COUNT to PORTC.A . Your main interest should be the time each new value of COUNT is being displayed. If you single step into the delay loop. FIGURE 2-25: WATCH – AT BREAKPOINT Press the Run icon to execute the code until it hits this point again. The Watch window should now show both values incremented by one from their previous value. you will get stuck executing thousands of steps until reaching the end. Finally. but since the breakpoint is at the line before the move to PORTC executes. The Watch window should now show that the variable COUNT was incremented by one. select Debugger>Reset>Processor Reset. remove the breakpoint on PORTC by right clicking on the line and selecting “Remove Breakpoint”. increase count and and select “Set Breakpoint”. If you are interested in calculating your delay time.W. you can run to the next breakpoint at the same place to measure the time.MPLAB® IDE Quick Start Guide Select Debugger>Run to run the application. use Debugger>Step Out.

FIGURE 2-27: STOPWATCH – AT FIRST BREAKPOINT Execute Run again to go around the loop once. .add files for the project: a template file for the device selected and a linker script to build it properly. With the default processor frequency of 20 MHz. Tasks completed include: • Selecting the device – the PIC18F8722. select Debugger>Settings. To change the Processor Frequency.8596 milliseconds.4 microseconds to reach the first breakpoint. the Stopwatch should show that it took 1. Osc/Trace the MPLAB IDE built in MPASM assembler and MPLINK linker language tools. and note that the Stopwatch shows that it took about 9. DS51281G-page 37 . • And finally. FIGURE 2-28: STOPWATCH – AFTER DELAY 2. © 2007 Microchip Technology Inc. These are the essential steps for getting started with MPLAB IDE. • Using the Project Wizard to create a project. • Building the project. and using the wizard to: . Press Debugger>Run to run and then halt at the breakpoint.A Basic Tutorial for MPLAB IDE Use Debugger>StopWatch to bring up the Stopwatch dialog.13 TUTORIAL SUMMARY By completing this tutorial. building and testing a simple project. You are now ready to continue exploring the capabilities of MPLAB IDE. • Writing some simple code to send a changing value out an I/O port. you can change the values in the delay loop. testing the code with the simulator. To change this. you have performed the major steps for creating.

MPLAB® IDE Quick Start Guide NOTES: DS51281G-page 38 © 2007 Microchip Technology Inc. .

A Basic Tutorial for MPLAB IDE NOTES: © 2007 Microchip Technology Inc. DS51281G-page 39 .

Qingdao Tel: 86-532-8502-7355 Fax: 86-532-8502-7205 China .Fuzhou Tel: 86-591-8750-3506 Fax: 86-591-8750-3521 China .Shenyang Tel: 86-24-2334-2829 Fax: 86-24-2334-2393 China .6166 Fax: 81-45-471-6122 Korea . MI Tel: 248-538-2250 Fax: 248-538-2260 Kokomo Kokomo.Hong Kong SAR Tel: 852-2401-1200 Fax: 852-2401-3431 China . IN Tel: 765-864-8360 Fax: 765-864-8387 Los Angeles Mission Viejo. Canada Tel: 905-673-0699 Fax: 905-673-6509 ASIA/PACIFIC Asia Pacific Office Suites 3707-14.Munich Tel: 49-89-627-144-0 Fax: 49-89-627-144-44 Italy .Manila Tel: 63-2-634-9065 Fax: 63-2-634-9069 Singapore Tel: 65-6334-8870 Fax: 65-6334-8850 Taiwan .com Web Address: www.Wuhan Tel: 86-27-5980-5300 Fax: 86-27-5980-5118 China .com Atlanta Duluth. Ontario.Milan Tel: 39-0331-742611 Fax: 39-0331-466781 Netherlands .New Delhi Tel: 91-11-4160-8631 Fax: 91-11-4160-8632 India .Paris Tel: 33-1-69-53-63-20 Fax: 33-1-69-30-90-79 Germany .Pune Tel: 91-20-2566-1512 Fax: 91-20-2566-1513 Japan . AZ 85224-6199 Tel: 480-792-7200 Fax: 480-792-7277 Technical Support: http://support. Chandler.Penang Tel: 60-4-646-8870 Fax: 60-4-646-5086 Philippines . CA Tel: 408-961-6444 Fax: 408-961-6445 Toronto Mississauga. MA Tel: 774-760-0087 Fax: 774-760-0088 Chicago Itasca.Madrid Tel: 34-91-708-08-90 Fax: 34-91-708-08-91 UK .Shenzhen Tel: 86-755-8203-2660 Fax: 86-755-8203-1760 China .Hsin Chu Tel: 886-3-572-9526 Fax: 886-3-572-6459 Taiwan .Xian Tel: 86-29-8833-7252 Fax: 86-29-8833-7256 ASIA/PACIFIC India .Daegu Tel: 82-53-744-4301 Fax: 82-53-744-4302 Korea .Beijing Tel: 86-10-8528-2100 Fax: 86-10-8528-2104 China .Wels Tel: 43-7242-2244-39 Fax: 43-7242-2244-393 Denmark .Seoul Tel: 82-2-554-7200 Fax: 82-2-558-5932 or 82-2-558-5934 Malaysia . TX Tel: 972-818-7423 Fax: 972-818-2924 Detroit Farmington Hills. 37th Floor Tower 6. GA Tel: 678-957-9614 Fax: 678-957-1455 Boston Westborough.microchip.Kaohsiung Tel: 886-7-536-4818 Fax: 886-7-536-4803 Taiwan . CA Tel: 949-462-9523 Fax: 949-462-9608 Santa Clara Santa Clara.Chengdu Tel: 86-28-8665-5511 Fax: 86-28-8665-7889 China .WORLDWIDE SALES AND SERVICE AMERICAS Corporate Office 2355 West Chandler Blvd.Shunde Tel: 86-757-2839-5507 Fax: 86-757-2839-5571 China .microchip. . IL Tel: 630-285-0071 Fax: 630-285-0075 Dallas Addison.Bangkok Tel: 66-2-694-1351 Fax: 66-2-694-1350 EUROPE Austria .Taipei Tel: 886-2-2500-6610 Fax: 886-2-2508-0102 Thailand .Shanghai Tel: 86-21-5407-5533 Fax: 86-21-5407-5066 China .Drunen Tel: 31-416-690399 Fax: 31-416-690340 Spain .Sydney Tel: 61-2-9868-6733 Fax: 61-2-9868-6755 China .Bangalore Tel: 91-80-4182-8400 Fax: 91-80-4182-8422 India . The Gateway Harbour City.Wokingham Tel: 44-118-921-5869 Fax: 44-118-921-5820 06/25/07 DS51281G-page 40 © 2007 Microchip Technology Inc. Kowloon Hong Kong Tel: 852-2401-1200 Fax: 852-2401-3431 Australia .Yokohama Tel: 81-45-471.Copenhagen Tel: 45-4450-2828 Fax: 45-4485-2829 France .

Sign up to vote on this title
UsefulNot useful