MPLAB IDE Release Notes

Release Notes for MPLAB® IDE v8.92

Includes MPLAB Editor v4.56

July 8, 2013

Table of Contents

1 Operating System Support

2 Minimum Required Configuration

3 Common C Interface Support

4 Documentation Support

5 Installing/Uninstalling MPLAB IDE

6 Network Administrator Information

7 Administrator vs User Privileges

8 Multiple Installations, Instances and Tool Usage

9 What's New in v8.92

10 Repairs and Enhancements Made in v8.92

11 Checksum Changes

12 Linker Script Usage in MPLAB IDE Projects

13 Known Problems

14 Microchip Plug-In Tools

15 Microchip Command-Line and Utility Support

16 Customer Support

17 License Agreements

# 1 Operating System 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.

## 1.1 32-Bit Windows OS Support

This tool has been tested under:

· Microsoft Windows XP Professional SP3

· Windows 7 Professional

· Windows 8 Professional

## 1.2 64-Bit Windows OS Support

This tool has been tested under:

· Microsoft Windows XP Professional SP3

· Windows 7 Professional

· Windows 8 Professional

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

# 3 Common C Interface Support

MPLAB XC C Compilers have an option for a common C interface (CCI) activated by an option switch and described in the user’s guides of each compiler. If you wish to use this feature with MPLAB IDE, please do the following:

· Build the project on the command line using the option –cci for MPLAB XC8 and –mcci for MPLAB XC16 and MPLAB XC32.

· Import the project into MPLAB IDE for debugging.

# 4 Documentation Support

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:

- Web Seminars (Webinars) Link

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

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

# 7 Administrator vs User Privileges

Administrator rights are required to install MPLAB IDE but should not be required to run the program.

The Administrator must grant the User permissions to read, execute, and list folder contents for:

· All of the MPLAB IDE directories and all of its subdirectories.

· All language-tool suite directories and subdirectories.

The User also needs full control for the registry permissions.

On occasion, Users will still have difficulty running the IDE. If the problem persists, have the Administrator export the MPLAB IDE registry as follows:

· Click on Start > Run

· Type REGEDIT

· Select OK

· In the registry editor go to directory: HKEY_CURRENT_USER\Software\Microchip\MPLAB IDE

· Export the folder by File > Export

· Select a location available to your users

· Pick a name

· Select Save

· Have each user log-on to their account

· Have each user double-click the exported registry file, which will import the file and add the attributes

These instructions apply specifically to Windows XP OS.

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

# 9 What's New in v8.92

· New Device Support.

# 10 Repairs and Enhancements Made in v8.92

None.

# 11 Checksum Changes

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

## 11.1 Checksum Changes in v8.85

PIC16F1783 - Config2 Checksum Mask has been changed to 0x3F33 from 0x3F23 due to a change in Programming Spec DS41457.

dsPIC33EPxxxGU/GP and 24EPxxxGU/GP devices - Checksum is incorrect when Code-protection mode is enabled in v8.84. This has been corrected in the IDE.

## 11.2 Checksum Changes in v8.84

PIC16F1783 - Config2 Checksum Mask has been changed to 0x3F13 from 0x3F33 due to a change in Programming Spec DS41457.

Checksum support has been added for all 16-bit devices that supports boot and secure segment.

## 11.3 Checksum Changes in v8.63

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

## 11.4 Checksum Changes in v8.60

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.

## 11.5 Checksum Changes in v8.53

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.

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

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

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

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

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

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

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

· Starter Kit Issues

## 13.1 Launch Issues

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

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

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

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

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

## 13.3 IDE Issues

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

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

· LCD Pixel View does not support these devices: PIC18F64J90, PIC18F65J90, PIC18F8393, PIC18F83J90, PIC18F8493, PIC18F84J90, and PIC18F85J90.

### 13.3.1 Language Tool Related Issues

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

· If you open a project using a HI-TECH or MPLAB C Compiler and switch to an MPLAB XC Compiler, you will have to reset all of your compiler options.

· Uninstall of MPLAB IDE v8.86: Compiler plug-ins disappear on uninstall of this version of MPLAB IDE. Please re-install your compiler after you install a new version of MPLAB IDE. If you still have issues, contact technical support through the web site at: http://support.microchip.com

### 13.3.2 IDE SSRs

The following are enumerated issues for the MPLAB IDE. SSR is an abbreviation for System Service Request.

SSR | Description | Device(s)
MPLAB-2029 | MPLAB IDE shows incorrect 'DEBUGDATASTART=0xcf6' address when selecting PICkit 3 as a debug tool. However when you open the file registers in the view menu, you can see that the R part of the memory already starts at 0xcf4. | PIC18F4682
MPLAB-2028 | Get the error "Unable to send freeze peripheral information" when debugging dsPIC33EP512MU810 with MPLAB REAL ICE in-circuit emulator and software breakpoints. | dsPIC33EP512MU810
MPLAB-2025 | Project>Clean does not clean all the files viz. .obj, .pre, .d and funclist. | PIC18F
MPLAB-2024 | MPLAB IDE locks up when code coverage is outputting to a file and a call instruction is used. | PIC16F716
MPLAB-2023 | This is a known issue of the MPASM assembler to do with the support file information. Please refer to issue MPASM-409. |
MPLAB-2015 | MCCP Peripheral Freeze checkbox missing from REAL ICE Settings>Freeze on Halt tab |
MPLAB-2014 | Memory Usage Gauge for dsPIC33EP devices containing Aux memory incorrectly counts the unimplemented space between the User Program Memory and the Aux Flash Memory. | dsPIC33EP devices with Aux memory.
MPLAB-2013 | The Watch Window sometimes shows an incorrect value for an object, whether it is an unsigned or a signed char, when using MPLAB XC8 1.11 and before. The debug information is COF and has some missing data. This will be fixed by moving to ELF and MPLAB X IDE. |
MPLAB-2010 | On newer 8-bit devices like the PIC16F1459, the Revision ID has been moved to a new address. This is not supported under MPLAB IDE v8, so it shows as zero. |
MPLAB-2001 | Some float values get corrupted occassionally in the watch window using HI-TECH PICC Pro v9.83. |
MPLAB-1999 | Opening a project file (.MCP) without the compilers installed can crash MPLAB IDE. |
MPLAB-1998 | White spaces in the string entered are not displayed on the output of 'Application Input/ Output' window. | PIC32MX795F512L
MPLAB-1996 | Trace is not available for MPLAB ICD 3. However, the trace menus are available (not grayed out.) | dsPIC33FJ16MC104, PIC24FJ16MC101
MPLAB-1995 | Voltage Caution pop-up: Buttons <OK> <CANCEL> overlap text | PIC16F1459, PIC16LF1459
MPLAB-1984 | --fill does not work with the debug output set to COF. Please use ELF debug output. | dsPIC33EP512MU810
MPLAB-1954 | Window 7 OS x64: PIC16F88 may not erase. | PIC16F88
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-1924 | Configuration bits window does not refresh when the address column is not shown in the window. |

MPLAB-1916

If you are using the 'MPLAB C Compiler for PIC32 MCUs' for your project, install MPLAB IDE v8.83 first. Once the MPLAB IDE installation is complete, re-install the MPLAB C32 compiler using the standalone installer downloaded from: http://www.microchip.com/c32.

When installing, make a note of the install directory and verify that your MPLAB IDE projects are built using the compiler from that location. You can set the location under Project>Set Language Tool Locations> Microchip PIC32 C-Compiler Toolsuite> Executables. After building your project, you should see this path in the Output window.

PIC32 Family

MPLAB-1912 | Functionality of menu item 'Package in .zip' inadvertently converts uppercase ASM '.S' file extensions to lowercase |
MPLAB-1911 | Disassembler output does not produce correct mnemonic for: TBLWTH.W (word mode) |
MPLAB-1907 | Reforming 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 when using COFF debug files instead of ELF. |
MPLAB-1904 | MPLAB 8.xx "Export Makefile" generates absolute paths for external libraries. |
MPLAB-1900 | Sometimes MPLAB IDE project wizard does not change the device in MPLAB IDE upon completion of the project wizard. |

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.

PIC24FJxxx

MPLAB-1879 | MPLAB IDE fails to build a project involving a MCP250xx device. However, the device code can be built using QuickBuild. | MCP250xx
MPLAB-1872 | Make file dependent on the MAP file in the output directory |
MPLAB-1862 | Sometimes a workspace will become larger and larger, greater than 400MB. Discard workspace and create a new one. |
MPLAB-1861 | Order of disassembly is lost when functions are implemented in an included file. |
MPLAB-1852 | MPLAB IDE gives an application error if the "configuration bits conflict" window is closed after closing the project. | PIC18F452
MPLAB-1834 | The value of the structure members isn't appended when the chosen compiler is HI-TECH, works fine with the MPLAB C30. |
MPLAB-1813 | On Windows(R) 7 and Windows Vista(R) x64 OSs, 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-1804 | Import of hex file does not properly set the configuration bits. This hex file has proper configuration information in it, but during import, it does not make it into the MPLAB IDE Configuration bits area. This hex file is not in a standard MPLAB IDE format. It is a raw compiler generated hex file. | PIC18F24J10 and others in the family
MPLAB-1803 | MPLAB IDE disappears if the Vpp clamper message is ignored with MPLAB ICD 2. | PIC16(L)F707
MPLAB-1743 | [HI-TECH PICC] Configuration bit information from hex file is not being imported into MPLAB IDE. | PIC18F67J10
MPLAB-1734 | Import of hex file does not import the User ID information due to User ID info in the same block as the Program Memory section. |
MPLAB-1731 | Halt build on first failure does not work with HI-TECH compiler based project. | 16-Bit Devices
MPLAB-1722 | Freeze Peripherals on Halt textbox does not show up if the IDE is viewed on the 2nd monitor |
MPLAB-1632 | Information of debug executable sections may not be passed to the linker correctly under PICkit 2. | PIC18F MCUs
MPLAB-1631 | Bit field display is incorrect in watch and local window when using Union for PIC32 Devices | PIC32MX Family
MPLAB-1517 | [Call Stack] Call Stack window displaying function parameters value incorrectly for PIC32 devices. | PIC32MX Family
MPLAB-1345 | [C32 build options] - The 'Exclude floating-point library' checkboxes available under the Build Options 'MPLAB PIC32 C compiler' and 'MPLAB PIC32 Linker' tabs should shadow each other. Currently, the checkbox on the compiler tab does not work, but the checkbox on the linker tab does. |
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. The workaround is to edit the linker script, restart MPLAB IDE and rebuild the project. | PIC32MX Family
MPLAB-1295 | Selection of 2 folders for comparison through browsing is not possible using External DIFF tool in MPLAB IDE. But if you provide the folder information by typing in directly, then the External DIFF tool will compare both the files. |
MPLAB-1216 | Using DOS Abbreviated path name to add a file into project manager causes problems in tabbed editor. |
MPLAB-855 | Symbol tab in the project window does not get updated when new project is added to the workspace | All
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. When you open the Project window from an older project, you will see a refresh issue. The work-around is to resize the window smaller than what is shown and then size it to what is needed. |

MPLAB-572

Error messages are not properly centered when using dual monitors.

To move any window that may be in focus which you cannot 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.

- Another choice is select windows from the menu item and select cascade. This puts all windows within the frame.

MPLAB-563 | After running the simulator's code coverage, which sets checkmarks in the gutter, the editor will place only hollow (disabled) breakpoint icons in the gutter when setting breakpoints. The breakpoints work correctly, but they show the wrong icon in the gutter. |

### 13.3.3 UDBC SSRs

The following are enumerated issues for the device data base incorporated into MPLAB IDE. SSR is an abbreviation for System Service Request.

SSR | Description | Device(s)
UDBC-704 | Values of config 1 and config 2 options in p12f1822.inc are of 16-bit wide, but should be 14-bit wide. | PIC12f1822
UDBC-701 | TCS bit of T2CON , T3CON, T4COn and T5CON SFR's is implemented as r/w bit for PIC32MX3xx/4xx-64 pin devices |
UDBC-695 | When using the PIC33FJ128MC804 device, the PWM signal continues on the PWM pin when an MPLAB ICD 3 operation is halted, regardless of the settings on the Freeze-on-Halt tab. | PIC33FJ128MC804
UDBC-692 | MCP19114: PMADRH width not defined correctly |
UDBC-691 | OSCIOFNC_ON and OSCIOFNC_OFF should be OSCIOFCN_ON and OSCIOFCN_OFF respectively | PIC24FJ128GA310
UDBC-690 | "18V" is not a valid config value for BORV in XC16 v1.11. I get an error when I assign "18V" to BORV in code for PIC24F04KA200 | PIC24F04KA200
UDBC-683 | Device ID mismatch error seen with PIC32MX440F128H in MPLAB X IDE. | PIC32MX440F128F
UDBC-682 | [PIC16] Alias DACCON0 and DACCON1 SFR and bit definition removed from devices PIC16L/F1789/88 | 4 devices PIC16L/F1789/88
UDBC-681 | TRIGSEL bits in ADCON2 SFR are 3 bits wide but the data sheet in Table 3-6 (DS41674B ) incorrectly shows them to be 4 bits wide. | PIC12LF1552
UDBC-670 | PMMODE- Bit16 (Busy) is implemented as r/w bit for PIC32MX devices. | PIC32MX Family
UDBC-669 | SPI2CON- Bit16 implementation does not match the datasheet for PIC32MX3xx/4xx devices | PIC32MX3xx/4xx
UDBC-664 | Not enough FUID macros, highest byte not handled by FUID macros. |
UDBC-654 | CM bit of RCON register is absent in C include files of PIC18FxxJ60 family. |
UDBC-652 | Memory region [0x100:0x104] should be marked as reserved for dsPIC33FJ32MC101. Missing such information caused incorrect checksum value in MPLAB X IDE. | dsPIC33FJ32MC101
UDBC-648 | MPLAB XC8 compiler register definition LCDSE3 missing for the device PIC16LF1902 header files. | PIC16LF1902
UDBC-647 | The Internal RC Frequency select (IRCF) bits are improperly labeled as IRFC in PIC16F88X MPLAB XC8 header files. | PIC16F88x family
UDBC-634 | List of issues observed with the device support files provided with XC32 v1.11 for 32MX430F064L, 32MX330F064L, 32MX430F064H & 32MX430F064L devices. | PIC32MX430F064L, PIC32MX330F064L, PIC32MX430F064H & PIC32MX430F064L
UDBC-629 | [PIC18] Default config value for CONFIG4L incorrect for devices | PIC18(L)F24/5K50
UDBC-613 | PIC24FJ32MC101/102/104 header files contain IC and OC modules but block definitions are missing. For example, Input Capture block needs to be defined: extern volatile IC IC1 attribute((sfr)); : extern volatile IC IC5 attribute((sfr)); | PIC24FJ32MC1xx
UDBC-608 | Missing certain PORTB bits declaration for PIC18F14K22LIN. | PIC18F14K22LIN
UDBC-589 | Corrected issue with configuration word bit for CP. | PIC12F529T39A, PIC12F529T48A
UDBC-587 | Incorrect values for flash_write field in .ini file for PIC16L/F1938/39 devices. | PIC16F1938, PIC16F1939 , PIC16LF1938, PIC16LF1939
UDBC-546 | IC9-IC16 and OC9-OC16 register blocks missing in dsPIC33EP512GP/MC806 MPLAB XC16 header files. | dsPIC33EP512GP/MC806
UDBC-517 | Data sheet is incorrect for PIC10(L)F320 A1 revision, which were only released as engineering samples. Production was released at revision A2 which has the correct memory mapping per the data sheet. | PIC10(L)F320
UDBC-515 | Configuration bit name is PLL_96MHZ_ON, should be PLL96MHZ_ON | PIC24FJ128GB106, PIC24FJ128GB108, PIC24FJ128GB110, PIC24FJ192GB106, PIC24FJ192GB108, PIC24FJ192GB110, PIC24FJ256GB106, PIC24FJ256GB108, PIC24FJ256GB110, PIC24FJ64GB106, PIC24FJ64GB108, PIC24FJ64GB110
UDBC-479 | MPASM PIC16F648A include file config bit typo: DATA_CP macros should be _DATA_CP. | PIC16F648A
UDBC-44 | Several devices from DS70286A (including the dsPIC33FJ256GP710) show ~60 shadow variables but they should only have 16 shadow variables. | dsPIC33FJ256GP710, dsPIC33FJ128GP710, dsPIC33FJ128GP708, dsPIC33FJ128GP706, dsPIC33FJ64GP710, dsPIC33FJ64GP708, dsPIC33FJ64GP706
UDBC-43 | Four devices from data sheet DS70287A do not have the correct shadow registers displayed in the SFR window. | dsPIC33FJ256MC710, dsPIC33FJ128MC710, dsPIC33FJ128MC708, and dsPIC33FJ64MC710

### 13.3.4 Other SSRs

The following are additional enumerated issues relating to MPLAB IDE.SSR is an abbreviation for System Service Request.

SSR | Description
25806 | [COFF] dsPIC disassembly listing shows address rather than Wreg number.
23550 | While in Animate mode, if you select File>Exit, MPLAB IDE will crash.

## 13.4 Starter Kit Issues

The following apply to starter kit issues.

SSR | Description
MPLAB-1260 | [MSK] - MPLAB Memory Starter Kit installer installs some unnecessary files in the SMSK folder in the MPLAB IDE subdirectory.
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.
SK-48 | PIC32SK doesn't update variables correctly. Right Click to "refresh" the window and values become correct.

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

# 15 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 | Yes*
PICkit 2 Programmer/Debug Express | PK2CMD | Yes*
MPLAB PM3 Device Programmer | PM3CMD | Visual PROCMD

* See the Microchip website.

# 16 Customer Support

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

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

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

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

## 17.1 Copyright notice for strlcpy() and strlcat()

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.

## 17.2 Copyright notice for Henry Spencer's implementation of regex

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

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

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

2. 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.
3. 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.
4. 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:

1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
2. You must cause any modified files to carry prominent notices stating that You changed the files; and
3. 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
4. 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.

5. 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.
6. 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.
7. 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.
8. 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.
9. 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.

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.

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

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

## 17.5 zlib License

/* 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_92_RC4