Release Notes for MPLAB® IDE v8.80
Includes MPLAB Editor v4.56
October 17, 2011
Table of Contents
3 Minimum Required Configuration
4 Installing/Uninstalling MPLAB IDE
5 Network Administrator Information
6 Multiple Installations, Instances and Tool Usage
8 Repairs and Enhancements Made in v8.80
10 Linker Script Usage in MPLAB IDE Projects
11 Debug/Release Selection for Language Tools
14 Microchip Command-Line and Utility Support
PC operating system support for MPLAB IDE is specified in the sections below.
Tools associated with MPLAB IDE may not support the same operating systems as MPLAB IDE. See individual tool readme's for more information.
This tool has been tested under:
Windows® 2000 SP4, Windows XP SP2, Windows Vista™ and Windows 7 OSs
This tool has been tested under:
Windows XP 64, Windows Vista 64 and Windows 7 64 OSs
Support on the 64-bit OSs is tool dependent, as shown in the following table.
Table: 64-Bit OS USB Device Driver Support by Tool
Tool Name |
64-Bit Support |
No 64-Bit Support |
MPLAB ICD 2 In-Circuit Debugger |
P/N 10-00397 |
P/N 10-00319 |
MPLAB PM3 Device Programmer |
P/N 10-00398 |
P/N 10-00359 |
MPLAB REAL ICE In-Circuit Emulator |
All |
None |
MPLAB ICD 3 In-Circuit Debugger |
All |
None. |
PICkit 2 Programmer/Debug Express |
All |
None |
PICkit 3 Programmer/Debug Express |
All |
None |
MPLAB ICE 2000 In-Circuit Emulator |
All |
None |
Starter Kits** |
All |
None |
* MPLAB ICE 2000 In-Circuit Emulator parallel port not
supported on 64-bit OSs.
** The PIC32 Starter Kit on 64-bit OSs uses the Microchip 64-bit driver
specified below.
64-bit drivers are NOT located in the same place as 32-bit drivers, since 64-bit drivers support multiple tools where as 32-bit drivers are tool specific. By default they are in:
C:\Program Files (x86)\Microchip\MPLAB IDE\Drivers64
IMPORTANT NOTICE: Beginning with MPLAB IDE v7.51, MPLAB IDE and its related components (except those listed below) will no longer be tested on Windows 98, Windows ME, or Windows NT® OSs. MPLAB IDE and its related components may continue to work under these operating systems, but their operation will no longer be verified through testing.
· Microchip will continue to support Visual ProCMD and PM3CMD on Windows 98.
The following documents may be found on our website or MPLAB IDE CD-ROM:
· MPLAB IDE Quick Start (DS51281)
· MPLAB IDE User's Guide (DS51519)
On-line help (Help>Topics) is also available for this tool:
· System>MPLAB IDE
· System>Editor
The default locations of the Help files are:
· C:\Program Files\Microchip\MPLAB IDE\Core\hlpMPLABIDE.chm
· C:\Program Files\Microchip\MPLAB IDE\Core\hlpMPLABEditor.chm
On-line Web Seminars are also available for this and other tools:
· Introduction to Microchip’s Development Tools
The following minimum configuration is required to run MPLAB IDE:
· PC-compatible Pentium®-class system
· Supported Windows operating system (see section 1)
· 128 MB memory (512 MB recommended)
· 400 MB of hard disk space
· Internet Explorer 5.0 or greater for installation and on-line Help
Basic steps for installing/uninstalled MPLAB IDE are given below. For more information see the MPLAB IDE Help file.
To install MPLAB 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 IDE. If no on-screen menu appears, use Windows Explorer to find and execute the CD-ROM menu, menu.exe.
· If downloading MPLAB IDE from the Microchip web site (www.microchip.com), locate the download (.zip) file, select the file and save it to the PC. Unzip the file and execute the resulting setup.exe file to install.
To uninstall MPLAB IDE:
· Select Start>Settings>Control Panel to open the Control Panel.
· Double click on “Add/Remove Programs”. Find MPLAB IDE on the list and click on it.
· Click Change/Remove to remove the program from your system.
Note to network administrators on installing MPLAB IDE v7.30 and later in a secure environment:
MPLAB_X_YY.MST file is a Windows installer transform file, located in the full zipped installation of MPLAB IDE vX.YY. This file can be used by domain administrators with Microsoft Active Directory and group policies to assign the application for software deployment in a security environment (local machines do not have admin rights). Microsoft Active Directory can be used to assign the application to local workstations. It has not been tested for "assigning/publishing to users." If this is a first time install, you may need to install the isscript10.msi first. Apply the transform file to the MPLAB_X_YY.MSI installation file in the group policy object (GPO). All of the files in the MPLAB IDE vX.YY full download zip must be located on a shared network directory.
Versions of MPLAB IDE installed |
Multiple (as of v7.00) |
Instances of MPLAB IDE run |
1 (recommended) |
Number of debuggers and programmers that can run at the same time under MPLAB IDE |
Only 1 debugger or only 1 programmer (but not both) |
Tools from the Tools menu that can be run with a debugger or programmer under MPLAB IDE |
Any tool from the Tools menu |
Multiple versions of MPLAB IDE may be INSTALLED on the same PC.
Note: You still may not RUN multiple versions of MPLAB IDE at the same time, i.e., only one version will be registered on the PC.
If necessary, you may switch between installed MPLAB IDE versions (i.e., change which one is registered). In general, to switch versions you simply double-click on the MPLAB IDE icon for the version you wish to run. A program named mpswitch.exe will run automatically in the background. The mpswitch.exe may take several minutes to complete. For specific details on switching between versions, see the MPLAB IDE Help file.
Just as you can only run one VERSION of MPLAB IDE on your system, you should only run one INSTANCE of MPLAB IDE. And in that one instance, you can only use one debug/programmer tool at a time.
Tools under the Tools menu may be used with either a debug or programmer tool. Obviously you can only choose one language toolsuite at a time in the Select Language Toolsuite dialog.
For more on these topics, see the MPLAB IDE Help file.
· New device support.
MPLAB-1929: When using REAL ICE (also ICD3, PK3, and PK2) as a debugger, MPLAB IDE is not passing the DEBUG symbols for RAM to mplink.exe so it will not reserve the debug memory in shared RAM for PIC16F887.
MPLAB-1950: The structure address is shown incorrectly in the watch window with the v8.76
MPLAB-1942: Reserved resources information for the debuggers is incorrect in the Help file for PIC18F4685.
The following sections detail changes to checksum calculations per MPLAB IDE version.
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.
For PIC32MX devices, the checksum read in the IDE will not read as 0x0000 as it should if the device is code protected. This has been corrected in the IDE.
PIC16F946, PIC16F87, PIC16F887 – IDE shows incorrect User ID value when using "Unprotected Checksum" for MPLAB v8.40, v8.43, v8.46, and v8.50. This issue has been corrected under v8.53.
PIC12F509, PIC16F505, and PIC10F222 – Program memory region for Code-Protect Enabled has been changed to match Programming Specification DS41266G/DS41266C. Prior to MPLAB IDE v8.40 (including v8.40), it correctly defined program memory region for Code-Protect Enabled. MPLAB v8.43 and v8.46 have incorrect definition for memory protection region for code-protect enabled.
PIC18F14K22 – CONFIG4L’s default value and mask has been changed to match Programming Specification DS41357B. From MPLAB IDE v8.33 to 8.43, it has 0x8D and 0xC5 as its default value and mask value respectively. In v8.46, its default value is 0x85 with mask 0xCD.
PIC24FJ16GA002/004, PIC24FJ32GA002/004, PIC24FJ48GA002/004, PIC24FJ64GA002/004 – Program Specification DS39768 checksum calculation has changed. Revision D of the programming spec has added several configuration bits to CW2 (bits 11-14, Flash Configuration Word 2) that are now part of the checksum calculation. The new checksum calculation has been updated in this version of the MPLAB IDE.
PIC18F1230/1330 - Rev B to future silicon revisions will always set bit 3 of CONFIG4L (300006h) to a ‘0’. Therefore, the checksum configuration mask for this register will change from 0xF9 to 0xF1. The checksum calculation will no longer be adding this bit.
· PIC18F4585/2585 – Configuration mask for configuration words 0x300008, 0x30000A, 0x30000C has been changed to 0x07 from 0x0F. This will enable the checksum to revert back to the older checksum calculation (v7.62 and older), while maintaining bit 3 to be a 1.
· PIC32MX440F128L – Device ID has changed to 0x6D. Therefore, the blank checksum reference has changed to accommodate this value.
Linker script files are used by a linker to generate application code. You no longer need to add a device-specific linker script file to your project; the linker will find the appropriate file for you. Exceptions are:
· Projects using the MPLAB Assembler for PIC24 MCUs and dsPIC DSCs
· Projects where you want to specifically add an edited linker script file
See your language tool documentation for details.
For some language tools, MPLAB IDE provides an automated way to perform debug setup using the “Build Configuration” drop-down box on the Project Manager toolbar or the “Build Configuration” item on the Project menu.
To set up language tools for debug, select “Debug”. When your code is debugged and you are ready to release it (program the finished code into a device), select “Release”.
For more information, see MPLAB IDE Help, MPLAB IDE Features>Debug Features>Build Configuration.
For production images, set the tool as a Programmer, (e.g., Programmer>Select Programmer>REAL ICE), and export the file using the File>Export menu item.
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 IDE (hlpMPLABIDE.chm). Bolded prefix represents internal tracking numbers.
Problems launching MPLAB IDE.
This could be caused by a corrupted workspace file.
1. Exit MPLAB IDE.
2. Remove or rename the workspace file.
3. Run the executable in the C:\Program Files\Microchip\MPLAB IDE\Utilities\SetDefaultMPLABStartup folder.
4. Start MPLAB IDE.
Docked windows can be placed outside of the IDE program boundaries. Therefore, it may be difficult to locate these windows when switching to a different monitor. Here are some steps that will reset this information:
1. Exit MPLAB IDE.
2. Remove or rename the workspace file.
3. Run the executable in the C:\Program Files\Microchip\MPLAB IDE\Utilities\SetDefaultMPLABStartup folder.
4. Start MPLAB IDE.
The splash screen flashes, but MPLAB IDE will not launch
When you try to start MPLAB IDE, the splash screen flashes by, but the application does not launch.
(1) Applies to MPLAB IDE versions 7.01 and 7.10:
Occurs on PCs with non-administrator (user-only) privileges.
Note: Administrator rights are required to install, but should not be required to run.
The workaround is to modify the target path on the MPLAB IDE shortcut and append the option -noswitch:
mplab.exe -noswitch
You can reach the target path by selecting the MPLAB IDE icon on the desktop, right-clicking properties, and then selecting the shortcut tab.
(2) Applies to MPLAB IDE version 7.61a:
You will need to remove the following entry from the PC registry:
[-HKEY_CURRENT_USER\Software\Microchip\MPLAB IDE\DebugDisplays]
Select Start>Run, enter regedit or regedt32 after “Open”, and click OK to open the registry for editing.
MPLAB IDE used to work, but now it will not launch
Items to check are:
· Did you recently install another version of MPLAB IDE? Please see section 6 for information on switching between versions of MPLAB IDE.
· Did you recently install other software? If so, it may have overwritten a system DLL in such a way that other applications cannot use it. Consult the software documentation and the Windows OS documentation to determine how to repair or reinstall the correct system DLL.
· Did you recently edit your PC registry? MPLAB IDE uses the registry to find related files. Try reinstalling MPLAB IDE.
· Do you have virus protection software on your machine? Try other programs on your PC to see if they are functioning correctly. If not, you may have a virus.
· Once the program is installed and you attempt to run it, you might receive an error stating that a dll file failed to register. This is caused when the Windows OS does not allow the MPLAB IDE installation to register the file for some reason. You will need to select Start>Programs>Microchip>MPLAB IDE vx.xx>Setup MPLAB Tools and run Repair to install and register the file.
None.
IMPORTANT NOTICE: Beginning with MPLAB IDE v7.51, MPLAB IDE and most components will no longer be tested on Windows 98, Windows ME, or Windows NT. MPLAB IDE and its related components may continue to work under these operating systems, but their operation will no longer be verified through testing.
· On Windows 98/ME, for every open Editor window, a message box entitled "File Time warning" appears with the content, "The parameter is incorrect". This happens after a build or after minimizing and restoring the application's main window.
Fix: Close MPLAB IDE and run the batch file located, by default, at:
C:\Program Files\Microchip\MPLAB IDE\Core\Editor\Register Old Editor 9x.bat
Restart MPLAB IDE and select Help>About MPLAB IDE. Verify that MPEditor.dll, and not MPEditor4.dll, is registered. If the batch file fails, you may need to update your PATH to include the path to regsvr32.exe (wherever it is installed on your system.)
· "File not found" error on Windows NT systems, usually from an import or project manager build. This is a Windows NT v4.0 issue, not an MPLAB IDE issue. Update Windows NT v4.0 with service pack or set registry flag HK_CU\Network\DeferFlags = 1. For more information, see: http://support.microsoft.com/default.aspx?scid=kb;en-us;169138
SSR 21029: While most Windows NT users have been able to use the MPLAB IDE, a limited number of these users have reported being unable to run MPLAB IDE. Microchip Development Tools has determined that one cause of this problem is that Windows Desktop Update is not installed on the user's PC. See the Microsoft web site for more information about the Windows Desktop Update. Another cause of the problem may be due to a registration problem; the work-around: run register.bat in the dll subdirectory of the MPLAB IDE installation directory.
· MPLAB IDE v8.01 workspaces are incompatible with previous workspaces. Open the project file (.mcp) and reselect the device and other configuration settings before saving as a new workspace.
· When opening a workspace/project, MPLAB IDE crashes. The workspace/project file may be corrupt or from a previous version. Try opening a different workspace/project or MPLAB IDE alone as a test. If the workspace file (.mcw) is corrupt or from a previous version, delete it and then open the project file (.mcp). In this case, you may have to reselect the device and other configuration settings before saving as a new workspace. If the project file is corrupt (.mcp), you will have to rebuild the project.
· A Windows OS security vulnerability has been reported with .mcp files. While the exposure is believed to be small, MPLAB IDE v8.33 has addressed these issues. MPLAB IDE users should never accept or open .mcp files from unknown sources. These .mcp files can be inspected with a text editor for non-text string exploits.
· "Access Denied" message when trying to open a workspace. Make sure the workspace and related files have not been set to read-only, i.e., right-click on a file, select "Properties", and check that "Read-only" is NOT selected.
· Some language (build) tools may have problems if you use spaces, illegal characters or long file names for the file or project name. Consult the language tool documentation for details.
· If your language tools do not work correctly after installing this version of MPLAB IDE, go to our website or third party website to get the latest version of your language tool. If you have purchased the tool, contact your sales rep for an upgrade.
· If your HI-TECH C compilers do not work correctly with your debug tool, open the Project>Build Options>Project dialog and then close it to automatically set the correct debug tool.
· LCD Pixel View does not support these devices: PIC18F64J90, PIC18F65J90, PIC18F8393, PIC18F83J90, PIC18F8493, PIC18F84J90, and PIC18F85J90.
SSR 25806: [COFF] dsPIC disassembly listing shows address rather than Wreg number.
SSR 23550: While in Animate mode, if you select File>Exit, MPLAB IDE will crash.
Key |
Summary |
Device Affected |
MPLAB-1935 |
Dialog box with blank buttons for the production part/debug header pops up when connecting ICD3 as a debugger with 16F1827 |
PIC16F1827 and possibly others |
MPLAB-1924 |
Configuration bits window does not refresh |
|
MPLAB-1912 |
Functionality of menu item 'Package in .zip' inadvertently converts uppercase ASM '.S' file extensions to lowercase |
|
MPLAB-1911 |
ASM30: Disassembler output does not produce correct mnemonic for: TBLWTH.W (word mode) |
|
MPLAB-1862 |
Workspace becoming larger and larger. Attached one is 400+MB. |
|
MPLAB-1861 |
CLONE -Order of disassembly is lost when functions are implemented in a included file |
|
MPLAB-1676 |
Incorrect Checksums for Boot Block Code Protection for dsPIC33FJ256GP506 |
dsPIC33FJ256GP506 |
MPLAB-1637 |
Source level debug with C18 project does not work on specific directory structure and build directory policy |
PIC18 |
MPLAB-1632 |
In some cases, information of debug executable sections is not being passed to the linker. |
18F |
MPLAB-1949 |
In a PIC24/dsPIC project using C30 compiler, enum type values are shown only as 8 bits wide, instead of 16 bits wide, when added to the watch window |
All PIC24 and dsPIC devices |
MPLAB-1943 |
Under REAL ICE>Settings, ICD 3>Settings, PICkit 3 Settings, the Program Options section should not be grouped with the 'Manually select memories and ranges', since the Program Options are independent of this grouping.
|
|
MPLAB-1940 |
In the project.mcp file the ToolSettings gets a duplicate F5 option, the first on always stays the same, the second one changes with the printf setting. |
|
MPLAB-1939 |
A Warning message should be displayed when the user is attempting to program a device in DEBUG mode with the MCLR pin set as a Port input. |
PIC18F23K22, PIC16F887, and possibly others |
MPLAB-1919 |
"Parameter is incorrect" dialog box is displayed on building a program using a non-existant virtual memory location (out of the range) with the address() attribute. |
PIC32 Family |
MPLAB-1917 |
Memory usage gauge shows up all data memory as filled when an array is declared in the external data space. |
|
MPLAB-1916 |
IDE Installer failed to overwrite existing ..\MPLAB C32 Suite files |
|
MPLAB-1907 |
Make for header file changes (ELF output file format) builds all C files, even if that header file is not included in some C files. |
|
MPLAB-1905 |
[MPLAB C30] Array elements are displayed as Invalid array for a huge array |
|
MPLAB-1904 |
MPLAB 8.xx "Export Makefile" generates absolute paths for external libraries |
All devices |
MPLAB-1900 |
MPLAB IDE project wizard not changing the device in MPLAB IDE upon completion of the project wizard |
|
MPLAB-1897 |
The Structure members aren't updated correctly in the Watch Window; even though the values are assigned correctly |
|
MPLAB-1896 |
The setting of __IDLOC(9,xx) with the __CONFIG(FICD,xx) causes an MPLAB pop up message "The parameter is incorrect" |
|
MPLAB-1890 |
On some PIC24FJxxx devices, Freeze Peripheral bits, example T1CON<14>, are unimplemented and read as 0. These bits are under debugger control. If you read these in firmware you will read 0. However the Watch Window is showing this bit as 1 when “freeze peripherals” is enabled. Request for MPLAB IDE to mask these bits to 0 even if they are set. |
|
MPLAB-1872 |
Make file dependent on the MAP file in the output directory |
|
MPLAB-1852 |
MPLAB gives an application error if the "configuration bits conflict" window is closed after closing the project |
18F452 |
MPLAB-1835 |
Invalid argument path passed to the pic30-elf-ar.exe for the project |
|
MPLAB-1811 |
MPLAB won't open projects configured for version control systems if the current installation is not so configured. |
|
MPLAB-1801 |
The closing bracket of the function is missing in the Disassembly Listing of MPLAB IDE window for HI-TECH Compiler |
|
MPLAB-1731 |
Halt build on first failure does not work with HI-TECH compiler based project |
|
MPLAB-1701 |
Structure and pointer does not show the correct address |
24HJ128GP504 |
MPLAB-1675 |
MPLAB is not displaying version of the files after the filenames in the project tree in subversion. |
All |
MPLAB-1669 |
"Help" function does not work for "Custom Build" tab in Build Options. A help file exists for it however, if you manually search. |
|
MPLAB-1598 |
Build Options Optimization checkboxes don't get saved correctly |
|
MPLAB-1597 |
Project Wizard>Reconfigure Active Project - Make changes without saving doesn't function |
|
MPLAB-1596 |
Project Wizard>Reconfigure Active Project does not save to a new project |
|
MPLAB-1422 |
Remove "Section Information" (-ai) from PIC32 assembler listing options |
|
MPLAB-1345 |
[C32 build options] - The 'Exclude floating-point library' check-boxes available under 'MPLAB PIC32 C compiler' and 'MPLAB PIC32 Linker' should shadow each other. |
|
MPLAB-1300 |
There are times when a window loses focus and is frozen until a different window is selected and then the frozen window. |
|
MPLAB-1260 |
[MSK] - MPLAB Memory Starter Kit installer installs some unnecessary files in the SMSK folder in the MPLAB IDE subdirectory |
|
MPLAB-1200 |
[Project Subfolders] MPLAB IDE permits the user to create nameless project subfolders. |
|
MPLAB-1068 |
[Pickit2 as debugger] - When Pickit2 is selected as debugger opening the 'Hot Keys' tab of IDE setting (Configure>Settings), clicking OK , and then clicking RESET in debugger tool bar will not move green cursor to beginning of main() |
Not device specific |
MPLAB-1014 |
[ PIC18F8410 ] - The operational voltage of the device as shown by IDE's Pickit2 output window is wrong |
PIC18F8410 18F8490 18F8310 18F8390 18F6310 18F6410 18F6490 18F6390 |
MPLAB-736 |
Output Window (Resize & Move) : The Output Window Disappears on resizing the MPLAB IDE. |
|
MPLAB-677 |
[Dock] Opening the Project window shows a display issue |
|
MPLAB-563 |
After running simulator code coverage, setting source breakpoints shows hollow icon |
|
MPLAB-1921 |
Dialog box with blank buttons for the production part/debug header pops up when connecting PICkit3 as a debugger with 16F1937 |
16F1937 |
MPLAB-1906 |
MPLINK does not display the device database(resource file) version in the output window every time |
|
MPLAB-1879 |
MPLAB fails to build a project involving a mcp250xx devices |
mcp250xx |
MPLAB-1851 |
[Find in Files]Selecting constant and CTRL+SHIFT+F will put the variable into the "Find" box. If the constant is at the end of a very long string (260 chars) a blank "" is entered instead. |
All |
MPLAB-1839 |
If Project Manager window is undocked but in "dock" mode, switching between it and an undocked window creates a drawing problem. Win7-64bit. |
|
MPLAB-1749 |
Initial Update Column in the Watch Window does not account for the width of the diamonds |
|
MPLAB-1740 |
Icons in MPLAB IDE v 8.31 toolbar disappear following a project build |
|
MPLAB-1606 |
A watch window docked outside MPLAB should minimize along with MPLAB. |
|
MPLAB-1384 |
Focus to be released on a Tab, when Apply Button is clicked. |
|
MPLAB-1332 |
The autoupdate feature in MPLAB does not inform the user on newly available versions |
|
MPLAB-1216 |
Using DOS Abbreviated path name to add a file into project manager causes problems in tabbed editor. |
|
MPLAB-1070 |
The watch window does not stay minimized when saving it as minimized in the workspace |
|
MPLAB-965 |
On VISTA, the IDE's progress bar does not completely fill up. |
|
MPLAB-855 |
Symbol tab in the project window do not get updated when new project is added to the workspace |
All |
MPLAB-795 |
MPLAB IDE PIC32 enabled: Key board interaction for GOTO and Find function lost when first time memory window is docked for PIC32 devices |
PIC32MX |
MPLAB-740 |
Resize & Repaint on Output Window does not work appropriately. |
|
Key |
Summary |
Device(s) Affected |
Bit fields of SFR RPINR0 and RPINR2 of PIC24FxxxGBxxx does not match data sheet |
PIC24FJ256GB210 & PIC24FJ128GB210 |
|
UDBC-221 |
incorrect reset value of TRISA register for PIC16LF193x / PIC16F193x family of devices |
PIC16F1937, PIC16LF1937, PIC16F1936, PIC16LF1936, PIC16F1934, PIC16LF1934, PIC16F1933, PIC16LF1933 |
UDBC-202 |
Some of the Bits of TRISF are not according to Data sheet in the PIC24FJxxxGBxxx family |
PIC24FJ256GB108, PIC24FJ192GB108, PIC24FJ256GB110, PIC24FJ192GB110, PIC24FJ128GB108 |
UDBC-186 |
IFS3 and IEC3 should NOT exist for PIC24F16KA102 family |
PIC24F16KA102 family |
UDBC-154 |
Missing definition of BOREN_OFF & BOREN_ON |
dsPIC33FJ16GS504 |
UDBC-153 |
Add reference to bit fields in the 24FJ256GB110 include file |
PICJ256GB110 |
UDBC-147 |
Incorrect information on .h file for PIC24FJxxxGA1 devices (CW2 <11>). |
PIC24FJxxxGA1 devices |
UDBC-144 |
Default Config Bits Do Not Match Programming Spec (CONFIG1L and CONFIG1H) |
PIC18F6xKxx and PIC18xKxx FAMILY |
UDBC-133 |
Bits 14 & 15 of RCOUNT register should be marked unimplemented in the device files of PIC24FJ64GB004 family and PIC24FJ64GA104 family |
PIC24FJ32GA102/104, PIC24FJ64GA102/104, PIC24FJ64GB004/002, PIC24FJ32GB004/002 |
UDBC-125 |
PIC18F87J11 family is supposed to have F40-F59 unimplemented. PIC18F67J11 has these bits implemented. |
PIC18F87J11 |
UDBC-64 |
TRISA SFR Datasheet/Device mismatch. |
PIC18F14K22 |
UDBC-50 |
PIC24HJ128GP202 mouseover discrepancies |
PIC24HJ128GP202 |
SK-41: PIC32MX SK: When using DBPRINTF statement, any halt that happens to occur during the function call will prompt the user to RESET before continuing to run again.
SK-42: Request that PIC32MX SK freeze peripherals when stepping/halting.
MPLAB IDE supports a number of Microchip plug-ins under its Tools menu.
Microchip Tool |
Device Support |
Help File |
Data Monitor Control Interface |
N/A |
hlpDMCI.chm |
dsPIC Filter Design |
dsPIC30F/33F DSCs |
hlpdsPICFD.chm |
dsPIC30F SMPS Buck Converter |
dsPIC30F DSCs |
hlpSMPSDemo.chm |
dsPIC33F SMPS Buck/Boost Converter |
dsPIC33F DSCs |
hlpSMPSBuckBoost.chm |
KeeLoq Plug-in |
Secure Data Devices (HCS) |
hlpKEELOQ.chm |
Memory Starter Kit |
Memory devices (serial EEPROM) |
See included user’s guide (DS22087) |
MPLAB Macros |
N/A |
hlpMPLABIDE.chm |
mTouch Diagnostic Tool |
Devices with keypad I/O |
hlpmTouchGUI.chm |
RTOS Viewer* |
Same as RTOS used |
hlpMPLABIDE.chm |
Segmented Display Designer |
Devices that support LCD usage |
hlpSDDesigner.chm |
Graphical Display Designer |
Devices that are supported by the Microchip Graphics library |
hlpGDD.chm |
* The RTOS Viewer is part of MPLAB IDE. The actual RTOS is third party.
Third-Party Tools: See the Readme for Third Party Tools.htm for more on supported third-party tools.
Debuggers, Programmers and Starter Kits: See the individual tool Readme files or other documentation for more information on each tool.
In addition to MPLAB IDE, some hardware tools are supported by other software applications.
Hardware Tool |
Command Line Programmer |
Stand-Alone Utilities |
MPLAB REAL ICE In-Circuit Emulator |
REALICECMD |
No |
MPLAB ICD 3 In-Circuit Debugger |
ICD3CMD |
No |
PICkit 3 Programmer/Debug Express |
PK3CMD |
Coming soon |
PICkit 2 Programmer/Debug Express |
PK2CMD |
Yes* |
MPLAB PM3 Device Programmer |
PM3CMD |
Visual PROCMD |
* See the Microchip website.
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
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 in-circuit debugger, MPLAB ICD 2 in-circuit debugger, PICkit™ 3 debug express and PICkit 2 debug express.
· MPLAB IDE – This includes MPLAB IDE, the Windows® Integrated Development Environment for development systems tools, MPLAB 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.
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
Microchip’s license agreement accompanying the MPLAB IDE governs your use of the software. In addition, certain files or code accompanying this software are governed by third party licenses. You are responsible for complying with these license agreements. For your convenience, we have posted the third party licenses below.
Copyright (c) 1998 Todd C. Miller Todd.Miller@courtesan.com
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
5. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
6. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
7. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright (c) 1992 Henry Spencer.
Copyright (c) 1992, 1993
The Regents of the University of California. All rights reserved.
This code is derived from software contributed to Berkeley by Henry Spencer of the University of Toronto.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
4. This product includes software developed by the University of California, Berkeley and its contributors.
5. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
@(#)regex.h 8.2 (Berkeley) 1/3/94
=========================================================================
NOTICE file corresponding to section 4(d) of the Apache License,
Version 2.0, in this case for the Apache Xerces distribution.
=========================================================================
This product includes software developed by
The Apache Software Foundation (http://www.apache.org/).
Portions of this software were originally based on the
following:
- software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
DecisionSoft Open Source Software is copyrighted software available under the DecisionSoft Open Source License (see below), based on the BSD License (http://www.opensource.org/licenses/bsd-license.php).
Pathan 1 and Pathan 2 dynamically link against, and include a modified header file from Xerces-C by the Apache Software Foundation. Xerces-C is covered by the Apache Software License (see previous section.)
Pathan includes software developed by the Apache Software Foundation (http://www.apache.org/).
DecisionSoft Open Source License
DecisionSoft Open Source Software is copyrighted software available under the DecisionSoft Open Source License, based on the BSD License.
The DecisionSoft Open Source License
This license is based on the BSD License template.
Copyright (c) 2003, DecisionSoft Limited
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of DecisionSoft Limited nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE
/* zlib.h -- interface of the 'zlib' general purpose compression library
version 1.2.3, July 18th, 2005
Copyright (C) 1995-2005 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied
warranty. In no event will the authors be held liable for any damages
arising from the use of this software.
Permission is granted to anyone to use this software for any purpose,
including commercial applications, and to alter it and redistribute it
freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not
claim that you wrote the original software. If you use this software
in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
Jean-loup Gailly jloup@gzip.org
Mark Adler madler@alumni.caltech.edu
*/
Internal ID: 8_80_rc2