Release Notes for MPLAB® X IDE v1.95

October 29, 2013


Table of Contents

1        System Requirements

2        Java Standard Edition (SE) Requirements

3        Language Tool Support

4        Documentation Support

5        Installing MPLAB X IDE

6        Uninstalling MPLAB X IDE

7        What's New in v1.95

8        Repairs and Enhancements Made in v1.95

9        Checksum Changes

10      Known Issues

11      Unsupported Features and Tools

12      Microchip Plug-In Support

13      MPLAB Starter Kit Support

14      Version Control Systems Support

15      Collaborative Projects Support

16      Third Party Support

17      Customer Support

1      System Requirements

1.1      Minimum Configurations

Microsoft Windows XP Professional SP3/ Windows 7 Professional/ Windows 8 Professional:

·         Processor: 2.6 GHz Intel Pentium IV or equivalent

·         Memory: 768 MB

·         Disk space: 400 MB of free disk space

Ubuntu 9.10:

·         Processor: 2.6 GHz Intel Pentium IV or equivalent

·         Memory: 768 MB

·         Disk space: 400 MB of free disk space

Macintosh OS X 10.5 Intel:

·         Processor: Dual-Core Intel (32 or 64-bit)

·         Memory: 768 MB

·         Disk space: 400 MB of free disk space

1.2      Recommended Configurations

Microsoft Windows XP Professional SP3/Windows 7 Professional/ Windows 8 Professional:

·         Processor: Dual-Core Intel (32 or 64-bit)

·         Memory: 2 GB

·         Disk space: 500 MB of free disk space

Ubuntu 9.10:

·         Processor: Dual-Core Intel (32 or 64-bit)

·         Memory: 2 GB

·         Disk space: 500 MB of free disk space

Macintosh OS X 10.6 Intel:

·         Processor: Dual-Core Intel (32 or 64-bit)

·         Memory: 2 GB

·         Disk space: 500 MB of free disk space

1.3      Other Configurations

MPLAB X IDE may also run on the various other Linux distributions such as Oracle Enterprise Linux 5, Ubuntu 8.x and 10.04, Red Hat Enterprise Linux and many others.

1.4      Development Tool Support

1.4.1      Windows OS

Support on the 64-bit Windows OSs is tool-dependent, as shown in the following table.

Table: 64-Bit Windows OS USB Device Driver Support by Tool

Tool Name

64-Bit Support

No 64-Bit Support

MPLAB PM3 Device Programmer*

Assy# 10-00398

Assy# 10-00359

MPLAB REAL ICE In-Circuit Emulator



MPLAB ICD 3 In-Circuit Debugger



PICkit 2 Programmer/Debug Express



PICkit 3 Programmer/Debug Express



Starter Kits**



* MPLAB PM3 not supported fully in MPLAB X IDE at this time. See future releases.

** The PIC32 Starter Kit on 64-bit OSs uses the Microchip 64-bit driver.

1.4.2      Mac OS

Our hardware device drivers are not supported on 32-bit Mac hardware. To tell if you have 32-bit hardware, look at the core chips in your system. Known 32-bit chip sets for Mac hardware are:

·         Intel Core Solo

·         Intel Core Duo

Click the link for Apple's site concerning 32-bit vs 64-bit processors:

2      Java Standard Edition (SE) Requirements

Information about the Java Runtime Environment (JRE) required for MPLAB X IDE to run is discussed below.

2.1      Windows and Linux OSs

The current version of the JRE used with MPLAB X IDE on these operating systems is v1.7.x (JRE 7).

MPLAB X IDE now includes the correct JRE for your system, so you do not need to download it separately. This JRE is used solely with MPLAB X IDE and is not registered on your computer for general use.

2.2      Mac OS

The current version of the JRE used with MPLAB X IDE on this operating system is v1.6.x (JRE 6).

Note: JRE 1.6.26 causes unexpected behavior in MPLAB X IDE. Do not use.

For Mac OS versions 10.6 or earlier, JRE 6 should already be installed and available to MPLAB X IDE. For Mac OS X Lion or Mountain Lion (version 10.7 or 10.8, respectively), you will need to download JRE 6.

2.2.1      Downloading Java 6 (with JRE 6)

Please follow the instructions below if this applies to you.

  1. Visiting this Apple Knowledge Base article:
  2. Click the Download button in the upper right corner of the page to download Java 6.

Java 6 and 7 should be able to coexist on your machine. The default Java Virtual Machine (JVM) used to run applications will continue to be Java 7 after the update is applied. The MPLAB X IDE installer will find and use Java 6 once it is installed.

2.2.2      How to Check Your Computer's Java Version

If you're not sure what version of Java is installed on your computer, open a Terminal (Applications>Utilities> and type this at the shell prompt:

java –version

This will report which default version you have installed on your computer. If Java is not installed, it will open a window with a message about Java missing. In that case, see above to install Java 6.

If you have more than one Java version installed on your machine, you can locate each of them by executing these commands:

/usr/libexec/java_home -v 1.6

/usr/libexec/java_home -v 1.7

3      Language Tool Support

3.1      Compilers

Current compiler versions supported are:






9.70 and later



9.63 and later

MPLAB C Compiler for PIC18 MCUs


3.36 upgrade and later

MPLAB C Compiler for PIC24 MCUs and dsPIC DSCs

MPLAB C Compiler for PIC24 MCUs

MPLAB C Compiler for dsPIC DSCs




3.23 and later

MPLAB C Compiler for PIC32 MCUs


1.11 and later



1.0 and later



1.0 and later



1.0 and later

See “Known Problems” for migration issues.

3.2      Assemblers/Linkers

Current assembler versions supported are:




Related Toolchain(s)

MPASM Assembler

5.42 (Linux/Mac OSs)
5.43 (Windows OS)
and later versions


C18 (1)


4.39 and later


MPLAB Assembler/Linker for PIC24 MCUs and dsPIC DSCs

3.23 and later

No (2)

ASM30 (2)
C30, C24, dsPIC

MPLAB Assembler/Linker for PIC32 MCUs

1.11 and later



  1. The MPASM assembler and MPLAB Linker may be used with, but are not a part of, the MPLAB C Compiler for PIC18 MCUs toolchain.
  2. Beginning with MPLAB X IDE v1.30, this ASM30 toolchain will no longer be distributed with the IDE. However, it will continue to be supported.
    Consider using the assembler/linker that comes with one of the supported compilers for the latest versions of the assembler/linker. See compiler documentation for details.

4      Documentation Support

4.1      Help

Current help files (Help>Help Contents) are for all tools currently supported in MPLAB X IDE. As other tools or plug-ins are added, their help files will be added to the Help window.

4.2      User’s Guide and Release Notes

The MPLAB X IDE User’s Guide (DS52027) may be found in the MPLAB X IDE install with the Readmes. On the MPLAB X IDE Start Page tabbed window, “Learn & Discover” tab, click “Release Notes and Support Documentation” to see links to all readmes and the user’s guide.

4.3      Data Sheets

To view the device data sheet, you can click on the PDF icon on the Dashboard window (Window>Dashboard) to open a local copy or search the Microchip website.

Another method is to add the local PDF to the Favorites window (Window>Favorites) which allows shortcuts to common content. Right click in the windows to Add to Favorites.

You can also add the PDF to the “Important Files” folder of your project. Right click on this folder and select “Add Existing Item”. Browse to the location of the PDF. The file will be added to the folder. Double click on it to launch it from this location.

If you want to create your own logical folder, right click on the project where you want to add the folder and select "New Logical Folder" from the context menu. This will create a logical folder with a default name of “New Folder”. Then right click on this new folder and select "Rename". Type the name you want and hit return. To add a file to this folder, right click on the folder and select "Add Existing Item".

5      Installing MPLAB X IDE

Basic steps for installing MPLAB X IDE are given below. For more information see the MPLAB X IDE Help file.

To install MPLAB X IDE on your system:

For some Windows OSs, administrative access is required in order to install software on a PC.

·         If installing from a CD-ROM, place the disk into a CD drive. Follow the on-screen menu to install MPLAB X IDE. If no on-screen menu appears, use Windows Explorer to find and execute the CD-ROM menu, menu.exe.

·         If downloading MPLAB X IDE from the Microchip web site (, locate the download (.exe) file, select the file and save it to the PC. Execute the file to install.

6      Uninstalling MPLAB X IDE

Virus protection software can interfere with the Uninstaller. If your uninstall fails, refer to your virus protection software documentation to determine how to exclude “Uninstall MPLAB X IDE.exe” from virus scans.

To uninstall MPLAB X IDE:

For Windows OS:

·         Select Start>Settings>Control Panel to open the Control Panel.

·         Double click on “Add/Remove Programs”. Find MPLAB X IDE on the list and click on it.

·         Click Change/Remove to remove the program from your system.

For Mac OS:

·         Select Finder.

·         Go to Applications>microchip>mplabx>Uninstall MPLAB X IDE.

For Linux OS:

·         $ sudo /opt/microchip/mplabx/Uninstall\ MPLAB\ X\ IDE

Uninstalling Multiple Installations

If you install MPLAB X IDE in the default directory and then install MPLAB X IDE again in another directory, the Windows uninstall manager will only uninstall the latest (or one) version. There will not be two registry entries for the same version to uninstall. To uninstall the second installation, use “Uninstall MPLAB X IDE.exe” found under the MPLABX directory.

7      What's New in v1.95

·         Limited SQTP injection support in Aux memory

·         ICSP cable support for UNI/O programming and byte width

·         Watches window: You are now able to enter/change an Enum label (text), in addition to an integer value, in a Watches window. Note that Enum labels are case-sensitive.

8      Repairs and Enhancements Made in v1.95





MPLAB X IDE is not displaying the correct RAM Reserved resources for Debug Executive (Enhanced Midrange devices).

Enhanced Midrange devices


Cannot enter debug mode on a PIC12HV752 header.



Incorrect reporting of RAM reserved resources on PIC32MX devices. In addition, there is no boot memory reserved resources reported.

PIC32MX370F512L but most likely any PIC32MX


MPLAB X IDE shows that data breakpoint is available, but these devices do not support it.

PIC12F1571/72 and PIC16(L)F1713/16


Changing an existing data breakpoint to select a different symbol doesn't take effect even when the breakpoint window shows otherwise. The address changes back to old address.

dsPIC33FJ256GP710A and possibly others


RAM memory size display in the Dashboard doesn't show the right information for PIC24F16KA101 and PIC24F16KA102. The RAM graph provides twice the amount that is actually available.



XC16 assembler compare and branch instructions are not recognized by the editor



RealICE properties are empty for PIC32MX350F128L and PIC32MX450F128L

PIC32MX350F128L, PIC32MX450F128L


If you open a project from another user who had enabled trace and provided a path that does not exist on your system, you can program and debug run but when you halt, the following message will appear in the output window:


An Error occurred while running

Failed to read emulation memory.

The trace window will have nothing in it.

If you provide a valid (for your system) path, no errors will occur and the trace window is populated as expected.



Green cursor does not advance when using Software Breakpoints and the Reset at Main feature is enabled



Package project ignores contents of Loadables folder


MPLABX-1774 should not be packaged


9      Checksum Changes

The following sections detail changes to checksum calculations per MPLAB X IDE version.

9.1      Checksum Changes in v1.80

For all 16-bit devices supporting the boot and secure segment code protect fuses, the pre-programmed checksum calculation will only be based upon the (GSS) General Segment Code Protection fuse (Standard Security Mode only) and not on either the (BSS) Boot Segment Program Flash Code Protect fuses or the (SSS) Secure Segment Program Flash fuses.

10   Known Issues

The following is a list of known problems. For information on common problems, error messages and limitations please see the online help file for MPLAB X IDE. MPLABX-nnnn represents internal tracking numbers.

·         Compiler-Related Issues

·         Build Issues

·         Software/Hardware Conflicts

·         IDE Issues

·         UDBC Issues

10.1   Compiler-Related Issues

·         Auto-discovery of toolsuite: After installing the MPLAB XC32 toolsuite to a non-default directory, MPLAB X IDE may not auto-discover the location of the toolsuite. In this case, you must manually add the toolsuite's bin directory to MPLAB X IDE using the instructions located here:

·         For MPLAB C Compiler for 16-bit Devices (C30) versions less than v3.30, the compiler does not include the files needed for instrumented trace. For those versions, MPLAB X IDE provides the files in:
MPLAB X IDE adds the -I to the compiler and the -l pointing to the directory above. However, for Mac the directory is not appended correctly. If you are using an C30 version less than 3.30, to be able to build a project with trace you need to go to the project properties (right click on project, select properties), then click on the pic30-gcc node. This will bring up the options available for the compiler. Click on the ... button on the Include directories option and add the directory listed above. Then click on the pic30-ld node. Select the libraries option category in the combo box, click on the ... button on the Library directories and add the same directory.

·         PICC18 version 9.66 and earlier compilers have an issue when creating debug builds for REAL ICE, ICD3 and PICKit3 on some PIC18 devices. The space that needs to be reserved for the debug executive is dependent on the IDE version you are using. If you are using the latest MPLAB X IDE but one of the older compilers indicated above, the reserved space for the debug executive may not be adequate and result in the Debug executive overwriting user's code and causing subsequent code failure. The memory ranges required by your debugger are indicted in that debugger's on-line help. To ensure they are not available to the compiler, remove these ranges using the compiler's —ROM option or its equivalent in the IDE. The map file produced by the compiler will allow you to confirm that the correct regions were reserved.

·         Microchip recommends upgrading to the latest compiler.

10.2   Build Issues

·         Do not use spaces or odd characters (e.g., %, #) in file names or paths as they can cause build issues. GNU make works well if there are no spaces or any special characters in the file name or path name. Otherwise the make program may crash in certain scenarios.

10.3   Software/Hardware Conflicts

·         Apple OS X Mavericks: When updating to Mavericks OS, Java 6 and all MPLAB X IDE drivers will be uninstalled. Re-install Java 6 and MPLAB X IDE after the OS update.

·         Some applications, plug-ins or widgets may take control of, or interfere with, the system provided HID USB driver, which can cause problems communicating with the PICkit 3. If you cannot connect to the PICkit 3, review the Task Manager for these types of programs and close them.

For more information, see forum posts:

·         (MPLABX-1778) Some applications associate themselves with HTML files, which can cause issues when attempting to view HTML files from the MPLAB X IDE Start page. Ensure only a browser is associated with these types of files (.html, .htm).

10.4   IDE Issues

The following are enumerated issues for the MPLAB IDE.





An array residing in the external memory may not be displayed properly in the watch window.



Clicking over the __delay_ms() and eeprom routines in the code, the pic18.h may be opened instead of pic.h.



RAM memory display is incorrect in dashboard for 16F1xxx devices. The mirrored banks and unused banks are not calculated correctly. Please use the compiler map file for accurate information regarding your RAM usage.



Strings for negative values of Enums are incorrectly displayed in the watch window.



Changing PIC32 registers in the CPU memory view or Watch Window has no effect

PIC32 family


The compiler properties dialog box shows App IO settings for PIC32MX devices that don't support it

PIC32MX family


Programming Address ranges show as invalid in dialog settings

PIC24FJ128GA010 and family


When importing a creating a MPLAB C18 project, an exception occurs in the MPLAB X IDE, although the import happens correctly.



When an include to path to the system include .inc for the assembler is included, .d files contain this path.



Cannot debug devices supported by AC162065/AC244022 header using power from PICkit 3 or ICD3

PIC24FJ128GA006, PIC24FJ128GA008, PIC24FJ128GA010, PIC24FJ64GA006, PIC24FJ64GA008, PIC24FJ64GA010, PIC24FJ96GA006, PIC24FJ96GA008, PIC24FJ96GA010


Cannot debug devices supported by AC244026/AC244027 header

PIC16F722,PIC16F723, PIC16F724,PIC16F726, PIC16F727,PIC16LF722, PIC16LF723,PIC16LF724, PIC16LF726,PIC16LF727


Cannot communicate with a AC162055 below 3.375 volts and cannot erase USER ID below 4.5v



Cannot connect to devices or debug supported by AC2440022 header using MPLAB X IDE



MPLAB X IDE reports invalid device ID for the devices supported by AC244034 header



Browsing for files or a project does not expand the Desktop in the search pull-down menu.



Sporadic switching of tool from MPLAB REAL ICE in-circuit emulation to MPLAB X Simulator can occur when the project using REAL ICE is closed and reopened. The selected debug tool will be the Simulator. Workaround: Check the selected tool and switch back to the emulator.



Remaining a file in a project library throws an exception when using the MPLAB X IDE.



Debug mode does not detect device ID for PIC18F14K50. The device is detected correctly under Programmer mode.



RAM size mentioned in the Project Dashboard for PIC16F1507 is incorrect (doesn't match the size in the datasheet)



When checksum is calculated in makefile, the path to checksum.jar is hardcoded instead of using existing PATH_TO_IDE_BIN



Refresh button on the project properties does not always reconnect to the device.

Does not reconnect when:

  1. Project is modified like changing hex files
  2. Opening existing projects



Setting a program breakpoint at program memory address 0x4000 inadvertently sets a program breakpoint at program memory address 0x0000

Enhanced midrange devices including ME2, i.e. PIC16F1939


For PIC24HJ128GP502 the checksum is placing the incorrect value in the USER ID



Dashboard window reports incorrect number of bytes - 684 for PIC12LF1501



Stimulus status bar messages are cleared before they can be read



On startup, Project is not selected in Project View.



Parser syntax highlighting incorrectly marks C++ brace initialization.



Renaming and Moving projects may cause MPLAB X IDE to freeze.



"Read Device Memory to file" does not create file. This occurs specifically on a Windows 7 machine.



checksum.jar fails with "Exception: null" when running with a dsPIC30F3012.X as part of inserting checksum in user ID memory

dsPIC30F3012 and most likely similar ones.


Cannot save settings for a individual file when override build option is enabled.



Creating makefiles using prjMakefilesGenerator with MPLAB XC8 creates makefiles that use ELF



The Navigate feature does not work as expected on declarations in pmgt.h



Certain windows are displaying incomplete texts on MAC OSx: Select Datasheet Location and Options>Embedded>Diagnostics.



MPLAB X IDE puts a comma for various include file paths specified under the Build Options, causing build fail for PIC32 asm projects



Deselecting 'Maintain Active connection' flag does not take effect until the next run of MPLAB X IDE.



Start page links do not work if installed in the 64-bit OS default directory 'Program Files(x86)'



MPLAB X IDE hangs on project rename.



Multiple Configuration settings are displayed for code guard enabled devices

dsPIC33FJ256GP710, PIC24HJ and all the code guard devices


Can't reorder Logic Analyzer pins without first removing them. There is an option that lets you do this, it just has no effect.



Highlighted selection (SFR/bit) in watch window gets deselected if stepping through project too fast.



The ! character is valid but it is not being handled correctly by MPLAB X IDE.



MPLAB XC8 Trace does not work as intended with MPLAB X IDE. There may be two problems here: 1) The second byte of the transfer is always zeroed, and 2) Possibly the ID byte, as written in the __it_log_dc routine, may be incorrect.

Tested with PIC18F47J13 but this does not look like a device specific issue


Package feature needs to be aware of libraries and loadables



Project does a full compile after any changes to REAL ICE settings.



Stopwatch Start/Stop condition should only populate list of available breakpoints from active project, not all projects that are open.



Peripheral window settings not saved



Explicit read operation immediately following exiting Programmer-To-Go mode fails



Exception generated when a Makefile project is created for a MPLAB IDE v8 project having a COFdebug image file.



Cannot add a new .inc file via the New File Dialog to an MPASM toolchain project.



For the PIC18F4550, 44pin TQFP package, there is the ability to use an alternate PGC, PGD *and* VPP pin. Debugging will not be allowed if these pins are used with MCLR disabled.



Unable to live parse 'bool' enum in editor.



Dragging and dropping variable from source to variables window does not add variable into the variable window until after debug session has ended.



For speed, a clean in the IDE is done by issuing 'rm -r dist/ build/'. The IDE avoids running 'make clean' because it takes longer, especially in Windows. If you run 'make clean' from the command line and have the GNUbins in your path, clean will run and the .clean-pre and .clean-post will work.



If sh.exe (cygwin or Mingw) is in the path, the IDE might hang As a workaround, please remove sh.exe from the path.



Cannot program a dsPIC33FJ128GP804 using PICkit 2 consistently.



Not all elements in an array is being properly displayed when using the Linear addressing scheme for the PIC16F1xxx



PIC32 SKDE does not support self test



MPLAB XC8 does not support library projects



WREG is not updated in PICkit 2 using headers



There are USB issues on Windows XP 64 with Microchip Bulk tools. PICkit3 should work.



Some symbols are not recognized within the parser. Try to compile as the preparser and compiler are two separate entities. It is still necessary for us to create a closer linkage between these two.



CCS compiler fails If there are spaces in the directory names.



SetPC is not implemented on 8- and 16-bit Starter Kits.



When adding a file to a project while in a debug session if you try to edit the properties and then halt the session it still prevents you from editing the properties.



There are times when including headers the files are not located and the pre-parser bangs or fails to parse correctly



Using MPLAB XC8, the MPLAB X Editor flags the PIC18 Config macros __CONFIG() as errors Red bangs (!). The project will build.



Default installation in some Linux distros looks bad. Run mplab_ide with the --laf Nimbus look and feel.



Currently changing any tool options will force a total rebuild of all files.



Customizing make and makeClean have no response.



Invalid device ID reported for PIC18F67J11 device using PICkit 2 with MPLAB X IDE.



The MPLAB XC32 compiler might place a function parameter in a CPU register so it does not update in the watch. Define variable as volatile for debugging.



Open Project': Unable to browse to root directory using keyboard. Submitted Issuezilla on Netbeans:



Compile file by right click assemble is not implemented for .asm or .s files



Without any optimizations the caller address cannot be identified when an INT routine is serviced, the return address should be on the stack and thus displayable.



On a dsPIC33EP512MU810 the Preserve Memory Range results in failure to program. The issue seems to have to do with reading auxiliary memory prior to programming the device.



Trace window is blank in MPLAB X IDE when first opened, and no trace data is available



For 16-bit devices with EDS: When declaring a larger array outside of internal RAM in extended data space, the internal RAM usage shows 100%.

16-bit Devices


When adding a library function or macro to a program, MPLAB X IDE may flag it as an error (bang in a red circle) but the program compiles and runs with no problems. This is a communication error between MPLAB X IDE and the compiler. The issue is being worked on.



On Mac sometimes the Project configuration drop-down resets using the scroll up/down on the trackpad.



Microstick does not disconnect properly under Linux and requires a physical disconnection from the PC.



No GOTO navigation is supplied to include files for MPASM but is available for labels using ':' after



No formatting customization for Assembly. Use the global settings for tab and indent under Tools>Options, Editor.



When Find... or Find In Projects... is used to search for text, the resulting display in the Search Results output window does not display tab characters that were in the original text file. For example, searching for latt_kesk in the line:

movf latt_kesk

will display:




Project properties for ICD3 does not show UserID memories for PIC32 devices



-merrata-exchange compiler option does not get imported from an MPLAB 8 project to an MPLAB X project.



Renaming a file in the project gets confused. Best to remove the file, rename in explorer, and then add it back.



MPLAB X IDE only supports subversion1.6



For PIC24KA devices, self-programming is not supported on the simulator.

PIC24F04KA200/1, PIC24F08KA101/2, PIC24F16KA101/2


For PIC24KA devices, EEPROM programming is not supported on the simulator.

PIC24F08KA101/2, PIC24F16KA101/2


Simulation of stalls during the RAW data dependencies are not supported.

dsPIC33F, dsPIC30F, PIC24F, PIC24H


It appears that the HI-TECH or MPLAB XC8 toolchain does not pass preprocessor defines to the CND background parsing system.



Mac OS 10.5 (32 bit) seems to think REALICE was ICD3 and PICkit 3 was PICkit 2. If the tool is plugged into the SAME USB port, then this problem can occur.



Occasionally on PICkit 2 programming will fail on PIC24HJ128GP306, dsPIC33FJ64GP206 in debug mode.

PIC24HJ128GP306, dsPIC33FJ64GP206


C18 integration - Setting linker option Hex file format =INHX8S or INHX8M causes build failure.



SKDE PIC32: Calling DBG_PRINTF back to back can lock up MPLAB X IDE and MPLAB IDE v8.



For PIC32 devices, the Address Breakpoint accepts only a Physical Address and not virtual.

PIC32MX devices

10.5   UDBC Issues

The following are enumerated issues for the device data base incorporated into MPLAB X IDE.





"Data sheet is incorrect for PIC10(L)F320 A1 revision, which were only released as engineering samples. Production was released at revision A2 which has the correct memory mapping per the data sheet.



The OP1IN- VirtualPin assignment incorrect



The pic files for 12F1571, 12F1572, 12LF1571 and 12LF1572 are missing the pin lists entries.



In p33EP64GS506.gld(linker file) because of this extra _ReservedTrap8, vector address of the remaining interrupt source is shifted by one.

For Example: Vector address of MI2C1 - I2C 1 Master Event should be 000036, but it is taken as 000038



The WPUB Register is missing from the pic18f45k50.h header file



AD2PCFGL register is missing the PCFGn field definitions

dSPIC33FJxxxGP706, dSPIC33FJxxxGP708


DMA0-DMA3 interrupt flag and enable bits are implemented as readable and writable for PIC32MX420F032H for the simulator.



RJPU bit is not defined in PIC18F97J94 datasheet but is included in PIC18F97J94.h header file of XC8



MCP19114: PMADRH width not defined correctly. The data sheet for this part has a 4-bit wide register for PMADRH, but the PIC file contains a 3-bit wide register. Writing 0xF to PMADRH results in 0x7 when it should be 0xF.



TRIGSEL bits in ADCON2 SFR are 3 bits wide but the data sheet in Table 3-6 incorrectly shows them to be 4 bits wide.



PMMODE- Bit16 (Busy) is implemented as r/w bit for PIC32MX devices.

PIC32MX Family


SPI2CON- Bit16 implementation does not match the datasheet for PIC32MX3xx/4xx devices



Not enough FUID macros, highest byte not handled by FUID macros.



CM bit of RCON register is absent in C include files of PIC18FxxJ60 family.



[PIC18] Default config value for CONFIG4L incorrect for devices



PIC24FJ32MC101/102/104 header files contain IC and OC modules but block definitions are missing. For example, Input Capture block needs to be defined:

extern volatile IC IC1 attribute((sfr));


extern volatile IC IC5 attribute((sfr));



Missing certain PORTB bits declaration for PIC18F14K22LIN.



Corrected issue with configuration word bit for CP.

PIC12F529T39A, PIC12F529T48A


Incorrect values for flash_write field in .ini file for PIC16L/F1938/39 devices.

PIC16F1938, PIC16F1939 , PIC16LF1938, PIC16LF1939


Configuration bit name is PLL_96MHZ_ON, should be PLL96MHZ_ON

PIC24FJ128GB106, PIC24FJ128GB108, PIC24FJ128GB110, PIC24FJ192GB106, PIC24FJ192GB108, PIC24FJ192GB110, PIC24FJ256GB106, PIC24FJ256GB108, PIC24FJ256GB110, PIC24FJ64GB106, PIC24FJ64GB108, PIC24FJ64GB110


MPASM PIC16F648A include file config bit typo: DATA_CP macros should be _DATA_CP.



Several devices from DS70286A (including the dsPIC33FJ256GP710) show ~60 shadow variables but they should only have 16 shadow variables.

dsPIC33FJ256GP710, dsPIC33FJ128GP710, dsPIC33FJ128GP708, dsPIC33FJ128GP706, dsPIC33FJ64GP710, dsPIC33FJ64GP708, and dsPIC33FJ64GP706


Four devices from data sheet DS70287A do not have the correct shadow registers displayed in the SFR window.

dsPIC33FJ256MC710, dsPIC33FJ128MC710, dsPIC33FJ128MC708, and dsPIC33FJ64MC710

10.6   Other Issues

The following are enumerated issues for other tools used with MPLAB X IDE.





[MPLAB XC32 C Compiler] In MPLAB X IDE Project Properties window, “XC32 (Global Options)” category, “All Options” option category, “Don’t delete intermediate files” checkbox: When the checkbox is checked, it causes the XC32 compiler to generate bad paths in the Compilation units. This only affects Windows operating systems.

PIC32 devices

11   Unsupported Features and Tools

The following features are still under development:

·         Code Profiling (partially complete)

The following tools are not supported now nor will be in the future:

·         MPLAB ICE 2000

·         MPLAB ICE 4000

·         MPLAB ICD 2

·         PICkit 1

·         PROMATE II

·         PICSTART Plus

·         MPLAB VDI

·         AN851 Bootloader

·         AN901/908

12   Microchip Plug-In Support

MPLAB X IDE supports a number of Microchip plug-ins under Tools>Plugins, Plugins dialog, Available Plugins tab.

If you do not see any plugins listed on the Available Plugins tab, go to MPLAB X IDE help to see how to configure update centers in the Plugins dialog: Help>Help Contents, Help dialog, MPLAB X IDE>Additional Tasks>Add Plug-In Tools.

13   MPLAB Starter Kit Support

A variety of starter kits are supported in MPLAB X IDE. Please go to the development tools page on the Microchip website to see a list of these tools:

14   Version Control Systems Support

MPLAB X IDE has a built-in local file history feature, compliments of the NetBeans platform. This feature provides built-in versioning support for local projects and files, similar to conventional version control systems. Available tools include a local DIFF and file restoration. For more on Local History options, see the MPLAB X IDE Help.

Source control program support includes:

·         CVS -

·         Subversion v1.6 (v1.7 causes issues) -

·         Mercurial -

15   Collaborative Projects Support

Collaborate on code development with your group using a team server supported inside MPLAB X IDE. Supported programs are:

·         Kenai –

·         Bugzilla –

·         JIRA –

16   Third Party Support

See the Readme for Third Party Tools.htm for more on supported third-party tools.

17   Customer Support

17.1   The Microchip Web Site

Microchip provides online support via our web site at This web site is used as a means to make files and information easily available to customers. Accessible by using your favorite Internet browser, the web site contains the following information:

·         Product Support - Data sheets and errata, application notes and sample programs, design resources, user's guides and hardware support documents, latest software releases and archived software

·         General Technical Support - Frequently Asked Questions (FAQs), technical support requests, online discussion groups/forums (, Microchip consultant program member listing

·         Business of Microchip - Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factory representatives

17.2   myMICROCHIP Personalized Notification Service

Microchip's personal notification service helps keep customers current on their Microchip products of interest. Subscribers will receive e-mail notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool.

Please visit to begin the registration process and select your preferences to receive personalized notifications. A FAQ and registration details are available on the page, which can be opened by selecting the link above.

When you are selecting your preferences, choosing “Development Systems” will populate the list with available development tools. The main categories of tools are listed below:

·         Compilers – These include all MPLAB C compilers; all MPLAB assemblers (including MPASM™ assembler); all MPLAB linkers (including MPLINK™ object linker); and all MPLAB librarians (including MPLIB™ object librarian), as well as HI-TECH C compilers.

·         Emulators – These include the MPLAB REAL ICE™ and MPLAB ICE 2000 in-circuit emulators

·         In-Circuit Debuggers – These include the MPLAB ICD 3, MPLAB ICD 2, PICkit™ 3 and PICkit 2 in-circuit debuggers.

·         MPLAB X IDE – This includes MPLAB X IDE, the Windows® Integrated Development Environment for development systems tools, MPLAB X IDE Project Manager, MPLAB Editor and MPLAB SIM simulator, as well as general editing and debugging features.

·         Programmers –These include the MPLAB PM3 and PRO MATE II device programmers and the PICSTART® Plus and PICkit 1, 2 and 3 development programmers.

·         Starter/Demo Boards – These include MPLAB Starter Kit boards, PICDEM demo boards, and various other evaluation boards.

17.3   Additional Support

Users of Microchip products can receive assistance through several channels:

·         Distributor or Representative

·         Local Sales Office

·         Field Application Engineer (FAE)

·         Technical Support

Customers should contact their distributor, representative or field application engineer (FAE) for support. Local sales offices are also available to help customers. A listing of sales offices and locations is available on our website.

Technical support is available through the web site at:

Internal ID: v1.95.rc7