Release Notes for MPLAB® X IDE v2.20

September 2, 2014

 

Table of Contents

1        System Requirements

2        Java® Standard Edition (SE) Requirements

3        Development Tool Support

4        Language Tool Support

5        Documentation Support

6        Installing MPLAB X IDE

7        Uninstalling MPLAB X IDE

8        What's New in v2.20

9        Repairs and Enhancements Made in v2.20

10      Checksum Changes

11      Known Issues

12      Unsupported Tools

13      Microchip Plug-In Support

14      MPLAB Starter Kit Support

15      Version Control Systems Support

16      Collaborative Projects Support

17      Third Party Support

18      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

Mac OS® X 10.5 Intel:

·         Processor: Intel® Core™ Duo or Intel Core 2 Duo

·         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: Intel Core Duo or Intel Core 2 Duo

·         Memory: 2 GB

·         Disk space: 500 MB of free disk space

Ubuntu 9.10:

·         Processor: Intel Core Duo or Intel Core 2 Duo

·         Memory: 2 GB

·         Disk space: 500 MB of free disk space

Mac OS X 10.6 Intel:

·         Processor: Intel Core Duo or Intel Core 2 Duo

·         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      Unsupported Configurations

MPLAB X IDE does not support Virtual Machines.

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® Operating Systems

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® Operating System

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: http://support.apple.com/kb/DL1572
  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>Terminal.app) 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      Development Tool Support

3.1      Windows Operating System

Microchip hardware tool support on Windows OS systems is shown in the following table.

Table: Windows OS USB Device Driver Support by Tool

Tool Name

32-Bit Support

64-Bit Support

No 64-Bit Support

MPLAB® PM3 Device Programmer*

All

Assy# 10-00398

Assy# 10-00359

MPLAB® REAL ICE™ In-Circuit Emulator

All

All

None

MPLAB ICD 3 In-Circuit Debugger

All

All

None

PICkit® 2 In-Circuit Debugger

All

All

None

PICkit 3 In-Circuit Debugger

All

All

None

Starter Kits**

All

All

None


* MPLAB X IDE has basic programming features for MPLAB PM3. For other programming options, see MPLAB IPE.

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

3.2      Mac OS X Operating System

Microchip 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:

http://support.apple.com/kb/HT3696

3.3      Linux Operating System

No known support issues.

4      Language Tool Support

4.1      Compilers

Current compiler versions supported are:

Compiler

Toolchain

Versions

HI-TECH® PICC PRO

HI-TECH PICC

9.70 and later

HI-TECH PICC-18 PRO

HI-TECH PICC18

9.63 and later

MPLAB C Compiler for PIC18 MCUs

C18

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

C30

C24

dsPIC

3.23 and later

MPLAB C Compiler for PIC32 MCUs

C32

1.11 and later

MPLAB XC8

XC8

1.0 and later

MPLAB XC16

XC16

1.0 and later

MPLAB XC32

XC32

1.0 and later

See “Known Problems” for migration issues.

4.2      Assemblers/Linkers

Current assembler versions supported are:

Assembler

Version

In IDE?

Related Toolchain(s)

MPASM™ Assembler

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

Yes

MPASM
C18 (1)

MPLINK™ Linker

4.39 and later

Yes

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

No

C32

  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.

5      Documentation Support

5.1      Help

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

For some tools, individual help files are available under Help>Tool Help Contents. This allows you to narrow down content searches for one tool instead of all tools.

5.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 installation readmes and user’s guides.

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

6      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 (http://www.microchip.com/mplabx), locate the download (.exe) file, select the file and save it to the PC. Execute the file to install.

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

8      What's New in v2.20

·         PIC18 Runtime Breakpoints – Support of using Runtime BP’s on PIC18 devices.

·         Program OSCAL Reset – You can now reprogram the OSCAL value where it resides in the reset vector of certain devices.

·         Signed Mac Installers – The MPLAB X IDE installer is now “signed” for Max OS X 10.7 and greater computers.

·         Parallel Make Set as Default – The checkbox “Use parallel make…” on the Tools>Options, Embedded button, Project Options tab, will be selected by default. This check box may be unselected for MPASM and C18 toolchains based on the version of the language tool being used.

·         Dynamic Compiler Pre-Parser Assistance for Macros and Built-ins – Whenever you cause the makefiles to be regenerated (for example, modifying project properties), dynamic invocations for the modified project’s compiler will be made in order to get all the compiler internally-defined macros and built-in functions. As soon as they are available, the Editor is updated with and made aware of this information.

·         OTP User Memory Support – The new dsPICEV devices have one-time programmable user OTP memory. Support includes a new display and options on the debug/program tools to select and program/read the memory.

·         MPLAB XC16: Alternate Vector Table Support (Dual Boot/Partition Devices) – Support for 16-bit devices with Dual Boot capabilities and Alternate Vector Table entries will be displayed in the Program Memory window. The Alternate Vector Table, when enabled by AIVTDIS, will be located at the value in BSLIM and indicated by the address of the Vector in the Opcode field, with the name of the Vector in the DisAssembly field.

·         MPLAB XC16: Response File Support – When MPLAB XC16 version 1.22 and above is installed, the option “Use response file to link” is enabled by default (Project Properties window, “xc16-ld” category, “General” option category). When enabled, a response file is created in either nbproject\$conf.debug or nbproject\$conf.production and the linker will be invoked with c:\XXXXX\bin\xc16-gcc @nbproject\$conf.debug (or production).

9      Repairs and Enhancements Made in v2.20

SSR

Description

Device(s)

MPLABX-2294

Dashboard shows negative free memory for PIC24F08KL201

PIC24F08KL201

MPLABX-2289

Language Tool Help Does Not Prompt up Any Help Window for MAC OSx 10.9

 

MPLABX-2288

MPLAB X IDE incorrectly dereferences final level for arrays of pointers *[ ] as **[ ] for PIC32 devices

PIC32 devices

MPLABX-2266

Disassembly listing view is missing instructions compared to compiler listing file for section of code

PIC16F1459

MPLABX-2251

"Power from target voltage" not always set to VDD nominal when changing devices.

PIC12F609, PIC24F08KM202

MPLABX-2238

IDE Watch window of STKPTR not displaying the actual value of 'STKPTR' after a reset.

All ME2 Enhanced Midrange parts (i.e. PIC16F1939)

MPLABX-2060

Tool does not have the ability to program Reset vector of Program Memory Osc Cal value

PIC12F529T39A

MPLABX-1985

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

PIC32MZ family and possibly PIC32MX as well

MPLABX-1838

Stimulus status bar messages are cleared before they can be read

 

MPLABX-336

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

PIC24F08KA101/2, PIC24F16KA101/2

UDBC-787

OPA1CON0 named as OPA1CON in PIC16F753 device family.

PIC16F753

10   Checksum Changes

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

10.1   Checksum Changes in v2.15

Config2's checksum mask was modified from 0xFFFF to 0xBFFF for the following devices:

 PIC24FJ128GB202

 PIC24FJ128GB204

 PIC24FJ128GA202

 PIC24FJ128GA204

 PIC24FJ64GB202

 PIC24FJ64GB204

 PIC24FJ64GA202

 PIC24FJ64GA204

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

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

·         Installation Issues

·         Build Issues

·         Software/Hardware Conflicts

·         Compiler-Related Issues

·         IDE Issues

·         UDBC Issues

·          

11.1   Installation Issues

For Linux 64-bit systems: To install and run MPLAB X IDE (and all Microchip compilers) requires the installation of 32-bit libraries.

11.2   Build Issues

·         If your code is building too slowly, you may be able to improve compiler build speed by using parallel make, depending on your computer’s configuration. See MPLAB X IDE Help for details.
Parallel Make: Tools>Options (Windows, Linux OS) or mplab_ide>Preferences (Mac OS X), Project Options tab.

For MPLAB XC16 and MPLAB C30 C compilers, when using the parallel make option, procedural abstraction must be disabled to prevent an error.
Procedural Abstraction: File>Project Properties, compiler category, “Optimizations” option category: uncheck “Unlimited procedural abstraction”.

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

11.3   Software/Hardware Conflicts

·         Apple OS X Mavericks: When updating to Mavericks, Java 6 and all MPLAB X IDE driver links 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:

http://www.microchip.com/forums/m614572-p2.aspx

http://forums.ni.com/t5/Multifunction-DAQ/No-supported-devices-found/td-p/1856299/page/2

·         (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).

11.4   Compiler-Related Issues

·         If you receive an error message like “make[ ]: *** Access is denied”, your anti-virus software may be interfering with the compiler make. A work-around it to disable your anti-virus software. See an example here:
http://www.microchip.com/forums/m746128.aspx

·         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 show MPLAB X IDE where to find the compiler’s bin directory:

·         Select Tools>Options, Embedded button, Build Tools tab.

·         Click the Add button under the “Toolchain” list.

·         Browse to find the bin directory under your compiler installation directory and click OK. This will add the compiler and version to the “Toolchain” list.

·         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:
$InstallationDir/tracelibs_hdrs/16-bit
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.

11.5   IDE Issues

The following are enumerated issues for the MPLAB X IDE.

SSR

Description

Device(s)

MPLABX-2306

Project configuration.xml removes prior tool settings when changing tools

 

MPLABX-2303

For the device PIC12LF1840T48A, the __EEPROM_DATA macro is shown as 'unexpected token'

PIC12LF1840T48A

MPLABX-2301

When upgrading MPLAB X IDE versions, the project voltage settings default to the lowest voltage

 

MPLABX-2300

Halting in memory window does not always synch to source, when source is available

 

MPLABX-2299

Build buttons when pressed under a debug session fail to build

 

MPLABX-2298

If a hex file is imported that contains an invalid code protect bit combination and programmed into the device, the device will no longer read or program correctly.

PIC12F529T48A

MPLABX-2297

When using MPLAB XC8 PRO, a step over on a printf performs a step into

 

MPLABX-2293

For MPLAB XC32 the __VERSION__ macro is not recognized - "Unable to resolve identifier"

 

MPLABX-2287

make 4.0 requires escaping single quotes even on a macro definitions.

 

MPLABX-2286

Stepping over __delay_ms() xc8 built-in function fails to pause at Breakpoint on next code line.

PIC18F devices

MPLABX-2283

Set PC at Cursor' not working using the simulator and MPLAB XC8 on a PIC18F14k50

PIC18F14K50

MPLABX-2265

Project selection in Logic Analyzer window doesn't work when there is a main project is selected

 

MPLABX-2252

On building in MPLABX IDE and REAL ICE as debugging tool for PIC32MX1xx/2xx devices the -mreserve=boot option with same value is being passed twice by the MPLAB X IDE

PIC32MXx1xx/2xx

MPLABX-2250

PICkit 3 fails to connect and/or program a PIC12F629 when powering from the tool using 5.0 volts

PIC12F629

MPLABX-2248

A #include statement cannot find the htc.h header file (red bang)

PIC18F family

MPLABX-2247

Timer1 unfreezes when single stepping too close to the statement that sets T1CON.ON

PIC32MZ family

MPLABX-2220

PICkit 3, MPLAB ICD 3 unable to program config4L bit 5 to high; MPLAB PM3 works fine for the PIC18F25J50 device

PIC18F25J50

MPLABX-2218

In Windows, killing the build process does not stop make in the background

 

MPLABX-2216

Changing a compiler option in MPLAB XC32 in a non-active configuration does not get saved to configurations.xml

 

MPLABX-2184

You can render an older PIC32 SKDE useless by setting code protect on it (old style SKDE).

 

MPLABX-2182

User directory dependency is required to be passed to the prjMakeFileGenerator.bat

 

MPLABX-2174

Sometimes an exception is thrown when deleting a project using the context menu action.

 

MPLABX-2166

When part is halted, 'Watches' window is preventing the writing of 'TOSH', 'TOSL', and 'PCL' SFRs

Enhanced Midrange inlcuding ME2: i.e. PIC16F1934

MPLABX-2156

"Any label following a '<' symbol somewhere is source within an asm file will not appear in the navigation pane.

PIC16F devices

MPLABX-2153

If Low Voltage programming is enabled in the program options for PIC16LF1827, MPLAB X IDE reports invalid device ID upon connect and fails programming operation.

PIC16LF1827

MPLABX-2147

MPLAB X IDE asks the user to enable the secure boot segment option when programming an Image that does not touch boot /secure segments.

dsPIC30F6014A

MPLABX-2141

Plib-related identifiers cannot be navigated via Right-click / Navigate / Go-to-Declaration

 

MPLABX-2134

In dsPIC30 C Template, configuration_bits.c source code is incorrect.

dsPIC30

MPLABX-2118

When using Locate Headers, if you select add to project the header will be added again, even though the header was already added.

 

MPLABX-2113

Overriding build options on a file, once requested, persist as defaults even after removing the override and then re-enabling it.

 

MPLABX-2112

On startup logging defaults to opening files in the home directory, i.e., MPLAB X IDE creates files ${HOME}/MPLABXLog*.xml

When navigating to the diagnostics page and selecting the browse, the correct path is updated in the IDE.

 

MPLABX-2102

Under some cases intermediate object files may be left if no longer used in the project on a clean

PIC18F

MPLABX-2095

Communications issues occur when using PIC16F506 and powering the target board with MPLAB ICD 3 at 5 volts for some customers

PIC16F506

MPLABX-2088

SPBRGH1 register does not display correct value in watch window.

PIC18F86K22, PIC18F86K22

MPLABX-2084

MPLAB XC8 does not have library support built into the IDE. Libraries of common source can be created using the command line as there cannot be mixed assembly and C. Review compiler guide for details.

 

MPLABX-2083

MPLAB IPE icon appears in toolbar instead of MPLAB X IDE icon

 

MPLABX-2071

Network License Management dialog always shows none for roamable licenses

 

MPLABX-2070

Network License Manager shows a blank screen under Windows 8

 

MPLABX-2069

Code folding does not work for inline asm code in MPLAB C18 when _asm and _endasm directives are used. The work-around is to put the code block near the end of the code/file.

 

MPLABX-2028

On selecting the external memory option in the linker options for MPLAB XC8 linker, In MPLAB X IDE the 'option description' is incorrect for 8 bit mode.

 

MPLABX-2026

Named elements in C99 structure initializers are incorrectly flagged as errors

 

MPLABX-2022

When hexmate reports a conflict, the reported address does not always reflect the address in MPLAB X IDE. For example, on a 16-bit device, 0x1000 is address 0x800 in MPLAB X IDE.

 

MPLABX-2015

Some compiler built in functions are shown as unrecognized in the editor like __delay_ms(x).

 

MPLABX-2013

Opening a project containing loadables does not recreate the makefiles for loadables that are projects.A workaround: open the loadable projects and that will force makefile generation. You can open the loadable project by right clicking in the main project and selecting "Load Required Projects" or by double clicking in the loadables (nodes under the Loadables virtual folder).

 

MPLABX-2009

s' is sometimes added to the document when saving using 'Alt+F+S'

 

MPLABX-2004

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

PIC24FJ128GA010

MPLABX-2003

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

 

MPLABX-1978

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

PIC32MX family

MPLABX-1971

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

 

MPLABX-1969

In the Project Properties dialog, for any MPLAB XC assembler, adding “ASM include dirs” results in .d files contain in this path.

 

MPLABX-1962

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

PIC16F684-ICE

MPLABX-1951

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

 

MPLABX-1945

Sporadic Trace window refresh issues show incorrect trace data. Using the mouse wheel more likely to cause this issue than using the window scroll bar.

Workaround: Put focus on another window and then return to the trace window.

 

MPLABX-1944

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.

 

MPLABX-1936

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

 

MPLABX-1903

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

 

MPLABX-1873

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

 

MPLABX-1823

On startup, Project is not selected in Project View.

 

MPLABX-1822

Parser syntax highlighting incorrectly marks C++ brace initialization.

 

MPLABX-1817

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

 

MPLABX-1798

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

 

MPLABX-1781

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

 

MPLABX-1778

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

 

MPLABX-1765

MPLAB X IDE hangs on project rename.

 

MPLABX-1754

Power Monitor data is not updated after single stepping. Only Run is supported.

 

MPLABX-1733

Multiple Configuration settings are displayed for code guard enabled devices

dsPIC33FJ256GP710, PIC24HJ and all the code guard devices

MPLABX-1731

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

 

MPLABX-1727

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

All

MPLABX-1725

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

 

MPLABX-1719

Package feature needs to be aware of libraries and loadables

 

MPLABX-1716

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

 

MPLABX-1700

Peripheral window settings not saved

 

MPLABX-1682

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

dsPIC33EP512GM710

MPLABX-167

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

PIC32MX devices

MPLABX-1666

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

 

MPLABX-1649

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

 

MPLABX-1610

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.

PIC18F4550

MPLABX-1587

Unable to live parse 'bool' enum in editor.

 

MPLABX-1553

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.

 

MPLABX-1546

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

 

MPLABX-1535

Cannot program a dsPIC33FJ128GP804 using PICkit 2 consistently.

dsPIC33FJ128GP804

MPLABX-1503

PIC32 SKDE does not support self test

 

MPLABX-1495

MPLAB XC8 does not support library projects

 

MPLABX-1473

WREG is not updated in PICkit 2 using headers

 

MPLABX-1434

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

 

MPLABX-1412

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

 

MPLABX-1293

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

 

MPLABX-1285

The Preparser of MPLABX flags this as an error "#error "__XC16__ not defined" when defined globally

 

MPLABX-1278

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.

 

MPLABX-1277

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

 

MPLABX-1274

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

PIC18

MPLABX-1264

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

 

MPLABX-1245

Customizing make and makeClean have no response.

 

MPLABX-1221

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

PIC18F67J11

MPLABX-1170

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.

PIC32 MCUs

MPLABX-1152

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

http://netbeans.org/bugzilla/show_bug.cgi?id=211182

 

MPLABX-1102

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

 

MPLABX-1101

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.

 

MPLABX-938

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

MPLABX-913

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.

 

MPLABX-861

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

 

MPLABX-822

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

 

MPLABX-764

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

 

MPLABX-752

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:

movflatt_kesk

 

MPLABX-609

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

 

MPLABX-598

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

 

MPLABX-484

MPLAB X IDE only supports subversion1.6

 

MPLABX-324

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

dsPIC33F, dsPIC30F, PIC24F, PIC24H

MPLABX-311

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

 

MPLABX-303

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.

 

MPLABX-282

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

PIC24HJ128GP306, dsPIC33FJ64GP206

MPLABX-264

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

 

MPLABX-224

Cannot debug an AC162065 header using ICD2, ICD3, RealIce or PICkit3 as debugger

pic24fj128ga010

MPLABX-180

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

PIC32

11.6   UDBC Issues

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

SSR

Description

Device(s)

UDBC-888

Checksum for PIC16F161x device is not matching with programming spec.

PIC16(L)F1614/5/8/9

UDBC-887

Incorrect PLLDIV config macro generated for PIC24FJ128GA202

 

UDBC-884

Reset value of CORCON is incorrect in MPLAB X IDE

All 16-bit devices

UDBC-882

RF6 bit of PORTF register is incorrectly implemented as r/w for PIC32MX430F064H device

PIC32MX430F064H

UDBC-881

[PIC32MX1xx/2xx] ODCB bit implementation for r/w operation doesn't match the datasheet

PIC32MX1xx/2xx

UDBC-876

PIC18F43/44/45/46K20 CLKI option incorrect name

PIC18F43/44/45/46K20

UDBC-869

The POR value is not correct for ANCON0 and ANCON1

PIC18F25K80 PIC18LF25K80 PIC18F26K80 PIC18LF26K80 PIC18F45K80 PIC18LF45K80 PIC18F46K80 PIC18LF46K80 PIC18F65K80 PIC18LF65K80 PIC18F66K80 PIC18LF66K80

UDBC-868

RA7 is missing from the TRISAbits union for the PIC18F24K50.h under the MPLAB XC8 compiler

PIC18F24K50

UDBC-867

Linker error "Settings in '__FBS.sec' are not valid for target device 24F04KL101 " though valid settings are made for the device. A workaround is to define this way:

#pragma config BWRP = OFF, BSS = OFF

PIC24F04KL101

UDBC-863

In dsPIC33EP256MU806.h, SFR blocks are missing for UART3, UART4, SPI3 and SPI4.

dsPIC33EP256MU806

UDBC-862

There are some missing definitions in the .include files for PIC18F25K50.inc and PIC18F45K50.inc files.

Missing registers:

POSTINC0
POSTDEC0
PREINC0
PLUSW0

INDF1
POSTINC1
POSTDEC1
PREINC1
PLUSW1

INDF2
POSTINC2
POSTDEC2
PREINC2
PLUSW2

PIC18F25K50, PIC18F45K50

UDBC-858

Unrecognized macro value generated for configuration bit settings for BORV with PIC24F04KA201.

PIC24F04KA201

UDBC-856

Incorrect POR, MCLR values for UART2: TXSTA2

PIC18F46K80 PIC18F25K80 PIC18F26K80 PIC18F45K80 PIC18F46K80 PIC18F65K80 PIC18F66K80 PIC18LF25K80 PIC18LF26K80 PIC18LF45K80 PIC18LF46K80 PIC18LF65K80 PIC18LF66K80

UDBC-850

Bit aliases in configuration registers don't appear to be supported...

 

UDBC-849

For dsPIC33EP512MU814 family the DMA memory is excluded from total device RAM (GPRs)

dsPIC33EP512MU814 family

UDBC-846

RETCFG is missing description in the support header files.

PIC24F16KM204 family

UDBC-844

TMR1CS0/TMR1CS1 bit type is not defined in header file for PIC16F707.

PIC16F707

UDBC-843

The common memory range and RAM bank ranges is incorrect for 16F570 device

 

UDBC-841

[PIC32MX] RG2 and RG3 bits of PORTG register are implemented as r/w even though 64 and 100 pin PIC32MX430/450/470 devices do not have RG2 and RG3 pins.

64 and 100 pin PIC32MX430/450/470 devices

UDBC-839

RF2 and RF6 PORTF bits are implemented even though PIC32MX430-64pin USB devices do not have RF2 and RF6 pins.

PIC32MX430- 64pin devices

UDBC-838

ANSELx reset values may not correspond with the datasheet for some of the PIC32 devices.

PIC32

UDBC-837

PIC16LF1554 device does not reflect the PWM3 and PWM4 registers

 

UDBC-836

PIC18F85K90 has T7CKI pin described in the include file, but should be removed.

PIC18F85K90

UDBC-835

TMR7 is not supported by PIC18F85K22 but the support files have most of the interrupt fields

PIC18F85K22

UDBC-830

TCK5 and TCK2 peripheral pin selection pins and groups are swapped in the support files.

PIC32MX330, PIC32MX350, PIC32MX370, PIC32MX430, PIC32MX450, PIC32MX470

UDBC-824

The PIC16LF1613 and PIC12LF1612, RAMBANKS: 1A0-1EF,220-26F,2A0-2EF,320-32F are unimplemented, but they are added in the support files.

PIC16LF1613, PIC12LF1612

UDBC-823

Bitfield CCP1TSEL0 of CCPTMRS register is incorrectly defined as CCPTSEL0 in "PIC12F1612.h" header

PIC12F1612

UDBC-821

Description of BORV in incorrect and is similar to BOREN. The description of BORV needs to be "Brown-out Voltage Level".

PIC24F16KM204 family of devices.

UDBC-820

SCANIE bit of PIE4 register is incorrectly defined as SCANIF in "PIC16LF1613.h" header

PIC16LF1613

UDBC-805

BOREN is not recognized as a configuration word for dsPIC33EP128GM304

dsPIC33EP128GM304

UDBC-804

The struct definitions for RB0-RB3 are missing.

PIC16F570

UDBC-802

The configuration bit is named POSCMOD in the support files, but is POSCMD in the datasheet.

PIC24F16KM204 family

UDBC-793

Current programming spec checksum calculation does not match calculated checksum for these device families.

dsPIC33EPxxxMU20x, dsPIC33EPxxxMU50x

UDBC-786

The linker script has incorrect debug reserve addresses. Modifying the linker script address builds the code.

Modified linker script for PIC16f818:

#IFDEF _DEBUG

CODEPAGE NAME=page START=0x0 END=0x2FF

CODEPAGE NAME=debug START=0x300 END=0x3FF PROTECTED

#ELSE //no debug

As per datasheet of PIC16F818, last 100h words are used for debug reserved resources.

PIC16F818

UDBC-783

Support header files may contain a misspelling CCP2RH should be CCPR2H

PIC16(L)F182x

UDBC-781

WPUC does NOT exist on this device. Header file is correct.

PIC16(L)F1503

UDBC-780

dsPIC33EP256MU506 has PTG0IE and PTG0IF is incorrectly entered as PTGDIE and PTGDIF.

dsPIC33EP256MU506

UDBC-770

Incorrect description of P2SEL bit of APFCON register in PIC16F1454 datasheet.

PIC16F1454

UDBC-764

RTCCON bit implementation in compiler header file doesn't match the datasheet for PIC32MZxxxx devices

PIC32MZxxxx devices

UDBC-756

The .pic files for PIC12F1571, PIC12F1572, PIC12LF1571 and PIC12LF1572 are missing the pin lists entries.

PIC12(L)F157x

UDBC-753

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

dsPIC33EP64GS506

UDBC-752

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

PIC18F45K50

UDBC-748

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

PIC32MX420F032H

UDBC-711

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

PIC18F97J94

UDBC-692

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.

MCP19114

UDBC-681

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.

PIC12LF1552

UDBC-670

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

PIC32MX Family

UDBC-669

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

PIC32MX3xx/4xx

UDBC-664

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

dsPIC30F

UDBC-654

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

PIC18FxxJ60

UDBC-629

[PIC18] Default config value for CONFIG4L incorrect for devices

PIC18(L)F24/5K50

UDBC-613

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));

PIC24FJ32MC101/102/104

UDBC-608

Missing certain PORTB bits declaration for PIC18F14K22LIN.

PIC18F14K22LIN

UDBC-589

Corrected issue with configuration word bit for CP.

PIC12F529T39A, PIC12F529T48A

UDBC-517

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.

PIC10(L)F320

UDBC-515

Configuration bit name is PLL_96MHZ_ON, should be PLL96MHZ_ON

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

UDBC-44

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

UDBC-43

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

dsPIC33FJ256MC710, dsPIC33FJ128MC710, dsPIC33FJ128MC708, and dsPIC33FJ64MC710

11.7   Starter Kit Issues

The following are enumerated issues for MPLAB Starter Kits used with MPLAB X IDE.

SSR

Description

Device(s)

MPLABX-180

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

PIC32 devices

12   Unsupported Tools

The following tools are not supported in MPLAB X IDE now nor will be in the future.

Unsupported Tool*

Recommended Supported Tool

MPLAB® ICE 2000

MPLAB® REAL ICE™ In-Circuit Emulator

MPLAB ICE 4000

MPLAB REAL ICE In-Circuit Emulator

MPLAB ICD 2

MPLAB ICD 3

PICkit® 1

PICkit 3

PROMATE® II

MPLAB PM3

PICSTART® Plus

PICkit 3

MPLAB VDI

MPLAB Harmony

AN851 Bootloader

N/A

AN901/908

N/A

 

* For IDE support, use MPLAB IDE v8 or lower.

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

14   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:

http://www.microchip.com/devtools

15   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 - http://www.nongnu.org/cvs/

·         Subversion v1.6 (v1.7 causes issues) - http://subversion.tigris.org/

·         Mercurial - http://mercurial.selenic.com/

16   Collaborative Projects Support

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

·         Kenai – http://kenai.com/

·         Bugzilla – http://bugzilla.org/

·         JIRA – http://www.atlassian.com/software/jira/overview

17   Third Party Support

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

18   Customer Support

18.1   The Microchip Web Site

Microchip provides online support via our web site at http://www.microchip.com. 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 (http://forum.microchip.com), 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

18.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 http://www.microchip.com/pcn 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.

18.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: http://support.microchip.com

Internal ID: v2.20.rc6