Example: bankruptcy

PICkit 3 Programmer/Debugger User's Guide

2009 Microchip Technology 3 programmer /DebuggerUser s GuideDS51795A-page ii 2009 Microchip Technology contained in this publication regarding deviceapplications and the like is provided only for your convenienceand may be superseded by updates. It is your responsibility toensure that your application meets with your MAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KIND WHETHER EXPRESS ORIMPLIED, WRITTEN OR ORAL, STATUTORY OROTHERWISE, RELATED TO THE INFORMATION,INCLUDING BUT NOT LIMITED TO ITS CONDITION,QUALITY, PERFORMANCE, MERCHANTABILITY ORFITNESS FOR PURPOSE.

Jan 02, 2008 · This user's guide describes how to use PICkit 2. Other useful documents are listed below. The following Microchip documents are available and recommended as supplemental reference resources. 44-Pin Demo Board User’s Guide (DS41296) Consult this document for …

Tags:

  Reference, Programmer

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of PICkit 3 Programmer/Debugger User's Guide

1 2009 Microchip Technology 3 programmer /DebuggerUser s GuideDS51795A-page ii 2009 Microchip Technology contained in this publication regarding deviceapplications and the like is provided only for your convenienceand may be superseded by updates. It is your responsibility toensure that your application meets with your MAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KIND WHETHER EXPRESS ORIMPLIED, WRITTEN OR ORAL, STATUTORY OROTHERWISE, RELATED TO THE INFORMATION,INCLUDING BUT NOT LIMITED TO ITS CONDITION,QUALITY, PERFORMANCE, MERCHANTABILITY ORFITNESS FOR PURPOSE.

2 Microchip disclaims all liabilityarising from this information and its use. Use of Microchipdevices in life support and/or safety applications is entirely atthe buyer s risk, and the buyer agrees to defend, indemnify andhold harmless Microchip from any and all damages, claims,suits, or expenses resulting from such use. No licenses areconveyed, implicitly or otherwise, under any Microchipintellectual property Microchip name and logo, the Microchip logo, Accuron, dsPIC, KEELOQ, KEELOQ logo, MPLAB, PIC, PICmicro, PICSTART, rfPIC, SmartShunt and UNI/O are registered trademarks of Microchip Technology Incorporated in the and other , Linear Active Thermistor, MXDEV, MXLAB, SEEVAL, SmartSensor and The Embedded Control Solutions Company are registered trademarks of Microchip Technology Incorporated in the Age.

3 Application Maestro, CodeGuard, dsPICDEM, , dsPICworks, dsSPEAK, ECAN, ECONOMONITOR, FanSense, In-Circuit Serial Programming, ICSP, ICEPIC, Mindi, MiWi, MPASM, MPLAB Certified logo, MPLIB, MPLINK, mTouch, PICkit , PICDEM, , PICtail, PIC32 logo, PowerCal, PowerInfo, PowerMate, PowerTool, REAL ICE, rfLAB, Select Mode, Total Endurance, WiperLock and ZENA are trademarks of Microchip Technology Incorporated in the and other is a service mark of Microchip Technology Incorporated in the other trademarks mentioned herein are property of their respective companies.

4 2009, Microchip Technology Incorporated, Printed in the , All Rights Reserved. Printed on recycled 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.

5 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.

6 We at Microchip are committed to continuously improving the code protection features of ourproducts. Attempts to break Microchip s code protection feature may be a violation of the Digital Millennium Copyright Act. If such actsallow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that 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.

7 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 3 USER S Guide 2009 Microchip Technology iiiTable of ContentsPreface .. 1 Chapter 1. Introduction .. PICkit 3 Programmer/Debugger Defined .. How the PICkit 3 Programmer/Debugger Helps You .. PICkit 3 Programmer/Debugger Components.

8 Device and Feature Support .. 13 Chapter 2. Theory of Introduction .. PICkit 3 vs. PICkit 2 .. Debugger to Target Communication .. Communication Connections .. Debugging .. Requirements for Debugging .. Programming .. Resources Used by the Debugger .. 22 Chapter 3. Introduction .. Installing the Software .. Connecting the Target .. Setting Up the Target Board .. Setting Up MPLAB IDE .. 25 Chapter 4. General Introduction .. Starting the MPLAB IDE Software .. Creating a Project .. Viewing the Project.

9 Building the Project .. Setting Configuration Bits .. Setting the Debugger or programmer .. Debugger/ programmer Limitations .. 29 Chapter 5. PICkit 3 Debug Introduction .. PICkit 3 Debug Express Kit Contents .. Installing the Hardware and Software .. 31 PICkit 3 User s GuideDS51795A-page iv 2009 Microchip Technology 6. Troubleshooting First Introduction .. The 5 Questions to Answer First .. Top 10 Reasons Why You Can t Debug .. Other Things to Consider .. 36 Chapter 7. Frequently Asked Questions (FAQs) Introduction.

10 How Does It Work .. What s Wrong .. 38 Chapter 8. Error Introduction .. Specific Error Messages .. General Corrective Actions .. 44 Chapter 9. Debugger Function Introduction .. Debugging Functions .. Debugging Dialogs/Windows .. Programming Functions .. Settings Dialog .. 56 Chapter 10. Hardware Introduction .. Highlights .. Declaration of Conformity .. USB Port/Power .. PICkit 3 Programmer/Debugger .. Standard Communication Hardware .. Target Board Considerations .. 63 Appendix A.


Related search queries