*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 with USB Converter*	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

1.3 Windows 98/ME/NT OS Support

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.

2 Reference Documents

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 MPLAB IDE

· Introduction to Microchip’s Development Tools

3 Minimum Required Configuration

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

4 Installing/Uninstalling MPLAB IDE

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.

5 Network Administrator Information

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.

6 Multiple Installations, Instances and Tool Usage

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.

7 What's New in v8.56

mTouch CVD Board support.
New device support.

8 Repairs and Enhancements Made in v8.56

MPLAB-1857: MPLAB IDE shows more than 1 breakpoint for the PIC16F1828 device, but the device supports only 1.

MPLAB-1856: "Package in ZIP" feature in IDE truncated *.lib Content and Extracted *.lib file became unusable.

MPLAB-1865: Using CTRL+M on an #ifdef where a commented out #ifdef is nested within, causes MPLAB IDE to crash.

MPLAB-1812: ID memory programming option is grayed out under the PICkit 3 program options for the PIC32MX devices.

MPLAB-1066: Both the "Include Search Path" and "Assembler Include Search Path" passed as assembler include paths when building a .S file.

MPLAB-1863: ASM32 instructions are not colored in blue.

UDBC-235: PIC18F65k22/85K22 bank 15 should be unimplemented.

UDBC-227: Incorrect Checksum Protection Region Definition for PIC18Fx6K22 and PIC18LFx6K22.

UDBC-223: DCH3CON, DCH3ECON, DCH3INT, DCH3SSA, DCH3DSA .etc SFR's are redefined in the DEV files for PIC32MX5xx, PIC32MX6xx and PIC32MX7xx devices. This is making stimulus controller unusable.

UDBC-175: The support files of PIC24FxxxxDA Devices have ambiguities in the *.h / *.inc file C.

UDBC-160: Ambiguities in .INC file for PIC24F16KAxxx and PIC24F8KAxxx family of devices.

UDBC-74: Reset values of BMXPFMSZ, BMXBOOTSZ, BMXDRMSZ, and BMXCON registers are incorrect in MPLAB IDE for PIC32MX devices.

UDBC-176: UTXISEL1 bit of U2BMODE SFR is incorrectly named as TXISEL0 in PIC32MXxx5Fxxx device header files.

UDBC-161: Ambiguities in .INC file for PIC24F04KA20x family of devices.

UDBC-159: Ambiguities in .h file for PIC24F04KA2xx family of devices.

UDBC-158: Ambiguities in .h file for PIC24F16KAxxx and PIC24F8KAxxx family of devices.

9 Checksum Changes in v8.53

PIC16F946, PIC16F87 – 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.

9.1 Checksum Changes in v8.50

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.

9.2 Checksum Changes in v8.46

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.

9.3 Checksum Changes in v8.30

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.

9.4 Checksum Changes in v8.20

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.

9.5 Checksum Changes in v8.14

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

10 Linker Script Usage in MPLAB IDE Projects

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.

11 Debug/Release Selection for Language Tools

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.

12 Known Problems

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.

· Launch Issues

· Operating System Issues

· IDE Issues

· PICC Issues

· Starter Kit Issues

12.1 Launch Issues

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.

12.2 Operating System Issues

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

12.2.1 Windows Vista, Windows 7 OSs

None.

12.2.2 Windows 98, Windows ME, Windows NT OSs

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.

12.3 IDE Issues

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

Number	Description	Device(s) Affected
MPLAB-1852	MPLAB gives an application error if the "configuration bits conflict" window is closed after closing the project	PIC18F452
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-1847	Import/Export table feature for watch windows corrupts values when using HI-TECH compiler with PIC18F6622
MPLAB-1839	If Project Manager window is undocked but in "dock" mode, switching between it and an undocked window creates a drawing problem. Windows 7, 64-bit.
MPLAB-1837	Value for the SPICON register does not update in the watch window for PIC2416KA101	PIC24F16KA101
MPLAB-1834	The value of the structure members isn't appended when the chosen compiler is HI-TECH, works fine with the 16-bit C compiler.
MPLAB-1813	In the Save As dialog box, if selecting 'No' to replacing a file with an identical name, it will still replace that file.
MPLAB-1811	MPLAB IDE won't open projects configured for version control systems if the current installation is not so configured.
MPLAB-1809	Debugger Information is Missing after a Build when using HI-TECH Compilers. Workaround: 1. Go to Project>Build Options>Project. Click on Linker tab and then click OK. 2. Rebuild project. Now "--debugger=icd2" will be part of the command line options and codes are placed in different addresses (disassembly_listing_after.txt).
MPLAB-1803	MPLAB IDE disappears if the Vpp clamper message is ignored with MPLAB ICD 2.	PIC16F707, PIC16LF707
MPLAB-1801	The closing bracket of the function is missing in the Disassembly Listing of MPLAB IDE window for HI-TECH Compiler
MPLAB-1749	Initial Update Column in the Watch Window does not account for the width of the diamonds
MPLAB-1731	Halt build on first failure does not work with HI-TECH project
MPLAB-1743	Configuration bit information from hex file is not being imported if not in proper section.
MPLAB-1723	Animate Debug function does not halt the execution when it hits advanced breakpoints.
MPLAB-1722	Freeze Peripherals on Halt textbox does not show up if the IDE is viewed on the 2nd monitor
MPLAB-1701	When the instance of a structure and a pointer to the instance are included for the first time in the watch window, the fields below the pointer do not show the correct addresses. Second time onwards (after processor reset and run) the correct addresses are displayed.	PIC24HJ128GP504
MPLAB-1676	Incorrect Checksums for Boot Block Code Protection.	dsPIC33FJ256GP506
MPLAB-1675	MPLAB IDE is not displaying version of the files after the filenames in the project tree in subversion. The files show (null) next to the file names.	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-1637	Source level debug with C18 project does not work on specific directory structure and build directory policy when 1.Source file added to project are in different folders AND 2.Build directory is set to "Assemble/Compile/Link in project directory AND 3.Output Directory is set to path other than project directory.	PIC18F MCUs
MPLAB-1632	PICkit 2 - Information of debug executable sections is not being passed to the linker. As a result of this no error is generated when the code overlaps the debug executables section of the program memory for PIC18 devices.	PIC18F MCUs
MPLAB-1631	Bit field display is incorrect in watch and local window when using Union for PIC32 Devices	PIC32MX Family
MPLAB-1606	A watch window docked outside MPLAB IDE should minimize along with MPLAB IDE.
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-1517	[Call Stack] Call Stack window displaying function parameters value incorrectly for PIC32 devices	PIC32MX Family
MPLAB-1460	Using dual screens, with MPLAB IDE moved to a second screen, watch window mouseovers will appear on the first screen. Dual monitor systems depend on the configuration of the video display cards. Typically, the setting that provides correct mouseover positions is: “Extend my desktop onto this monitor”.
MPLAB-1422	Remove "Section Information" (-ai) from PIC32 assembler listing options	PIC32MX Family
MPLAB-1353	When files generated by the build are placed into the ‘Others’ folder in the Project window, a plug-in exception occurs.
MPLAB-1345	[PIC32 build options] - The 'Exclude floating-point library' check-boxes available under 'MPLAB PIC32 C compiler' and 'MPLAB PIC32 Linker' should shadow each other.	PIC32MX Family
MPLAB-1332	The autoupdate feature in MPLAB IDE does not inform the user on newly available versions
MPLAB-1302	[KUSEG] Virtual address column of Memory window does not refresh correctly when there is an overlap due to incorrect linker. Even after correcting linker script, it shows old value	PIC32MX Family
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-1272	Build / Make icons in the toolbar jumbled up for a MPASM assembler project
MPLAB-1216	Using DOS Abbreviated path name to add a file into project manager causes problems in tabbed editor.
MPLAB-1200	[Project Subfolders] MPLAB IDE permits the user to create nameless project subfolders.
MPLAB-1070	The watch window does not stay minimized when saving it as minimized in the workspace
MPLAB-1068	[PICkit 2 as debugger] - When PICkit 2 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-1066	Both the "Include Search Path" and "Assembler Include Search Path" passed as assembler include paths when building a .S file
MPLAB-1014	[ PIC18F8410 ] - The operational voltage of the device as shown by IDE's PICkit 2 output window is wrong	PIC18F8410, PIC18F8490, PIC18F8310, PIC18F8390, PIC18F6310, PIC18F6410, PIC18F6490, PIC18F6390
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 MCUs
MPLAB-736	Output Window (Resize & Move): The Output Window Disappears on resizing the MPLAB IDE.
MPLAB-661	Call Stack Window: Simulator can hang when stepping through ‘MPLAB C compiler for 16-bit devices’ optimized code with the Call Stack window open.
MPLAB-572	Error messages are not properly centered when using dual monitors. To move any window that may be in focus which you can not see: Pressing Alt+<space> brings up the top left icon menu of the dialog followed by M to move the display then you can use the left or right, up or down arrows to move the display.
MPLAB-563	After running simulator code coverage, setting source breakpoints shows hollow icon

Number	Description	Device(s) Affected
UDBC-244	RC bit in FOSC setting is defined twice in PIC18LF45K22.PIC	PIC18LF45K22
UDBC-242	PIC18F87J50 IOFS bit defined, but should not be.	PIC18F87J50 Family of microcontrollers
UDBC-238	Incorrect Reset value for SSP1ADD SFR in PIC18F87J11	PIC18F87J11
UDBC-228	RPINRxx are set to MCLR value of 0x00. According to the datasheet the reset value should be 0x1F	PIC18F65J50, PIC18F45J50; possibly the entire family.
UDBC-224	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-206	Pop up message occurs during the Checksum test indicating that the WPFP configuration bits are invalid for the PIC24FJ192/128/64GB110/GA110 device families.	PIC24FJ192/128GA110, PIC24FJ192/128GA108, PIC24FJ192/128GA106 , PIC24FJ192/128/64GB110, PIC24FJ192/128/64GB108 and PIC24FJ192/128/64GB106
UDBC-202	Some of the Bits of TRISF are not according to Data sheet in the PIC24FJxxxGBxxx family	PIC24FJ256GB108, PIC24FJ192GB108, PIC24FJ256GB110, PIC24FJ192GB110, PIC24FJ128GB108
UDBC-196	Status bits in the include file are not brought out.	PIC12F617
UDBC-189	SFR INTTREG is missing in the support files.	PIC24FJ256GA110 family
UDBC-186	IFS3 and IEC3 should NOT exist for PIC24F16KA102 family	PIC24F16KA102 family
UDBC-179	Missing FICD CONFIG register info	PIC24F04KA201 and PIC24F16KA201 Family.
UDBC-166	Some of the SFR bit information in MPLAB IDE does not match datasheet	PIC32MX795F512L family
UDBC-164	PIC16F723 PMADRH R/W properties are not set to match the datasheet.	PIC16F723
UDBC-154	Missing definition of BOREN_OFF & BOREN_ON	dsPIC33FJ16GS504
UDBC-153	Add reference to bit fields in the 24FJ256GB110 include file	PICJ256GB110
UDBC-150	No reference of AD1CHS & AD1PCFGLbits in the support file PIC24FJ256GB110.h	PIC24FJ256GB110 Family
UDBC-147	Incorrect information on .h file for PIC24FJxxxGA1 devices (CW2 <11>).	PIC24FJxxxGA1 devices
UDBC-144	Default Confi Bits Do Not Match Programming Spec (CONFIG1L and CONFIG1H)	PIC18F6xKxx and PIC18xKxx FAMILY
UDBC-135	Bit implementation of IFS3 and IEC3 registers is incorrect for PIC24F08KA10x and PIC24F16KA10x	PIC24F08KA101, PIC24F08KA102, PIC24F16KA101, PIC24F16KA102
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

12.4 Starter Kit Issues

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.

13 Microchip Plug-In Tools

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

14 Microchip Command-Line and Utility Support

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.

15 Customer Support

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

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

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

16 License Agreements

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.

16.1 Copyright notice for strlcpy() and strlcat()

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.

16.2 Copyright notice for Henry Spencer's implementation of regex

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

16.3 License notice for Apache Xerces

=========================================================================

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

Definitions.

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

Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

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.

Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

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.

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.

16.4 Pathan Open Source 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.

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

16.5 zlib License

/* zlib.h -- interface of the 'zlib' general purpose compression library

version 1.2.3, July 18th, 2005

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