<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!-- tidy -im -wrap 110 README.html -->

<html>
<head>
  <meta name="generator" content="HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org">
  <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
  <style type="text/css" media="all">
5px;border-collapse:collapse;}td.confluenceTd{border:1px solid
  4px;background:#f0f0f0;text-align:center;}.wiki-textarea,.wiki-textfield{width:100%;}.preformatted{border:1px
  dashed;font-size:11px;font-family:Courier;margin:10px;line-height:13px;}.preformattedHeader{background-color:#f0f0f0;border-bottom:1px
  dashed;padding:3px;text-align:center;}.preformattedContent{background-color:#f0f0f0;padding:3px;overflow:auto;}.panel{border:1px
  dashed;margin:14px;margin-top:0;}.panelHeader{background-color:#f0f0f0;border-bottom:1pxm
  dashed;padding:3px;text-align:center;}.panelContent{background-color:#f0f0f0;padding:12px;}.code{border:1px
  dashed;font-size:11px;font-family:Courier;margin:14px;line-height:13px;}.codeHeader{background-color:#f0f0f0;border-bottom:1px
  dashed;padding:3px;text-align:center;}.codeContent{text-align:left;background-color:#f0f0f0;padding:6px;overflow:auto;}.code-keyword{color:#000091;background-color:inherit;}.code-object{color:#910091;background-color:inherit;}.code-quote{color:#009100;background-color:inherit;}.code-comment{color:#808080;background-color:inherit;}.code-xml
  .code-keyword{color:inherit;font-weight:bold;}.code-tag{color:#000091;background-color:inherit;}.linkerror{background-color:#fcc;}ul#squaretab{margin-left:0;padding-left:0;white-space:nowrap;font:bold
  8px Verdana,sans-serif;}#squaretab
  li{display:inline;list-style-type:none;}#squaretab a{padding:2px
  6px;border:1px solid #999999;}#squaretab a:link,#squaretab
  a:visited{color:#fff;background-color:#999999;text-decoration:none;}#squaretab
  a:hover{color:#ffffff;background-color:#999999;border-color:#999999;text-decoration:none;}#squaretab
  li a#current{background:white;color:black;}.panel{border:1px
  dashed;margin:10px;margin-top:0;}.panelHeader{background-color:#f0f0f0;border-bottom:1px
  dashed;padding:3px;text-align:center;}.panelContent{background-color:#f0f0f0;padding:5px;}.minitab{padding:3px
  0 3px
  8px;margin-left:0;margin-top:1px;margin-bottom:0;border-bottom:1px
  solid #bbb;font:bold 9px
  Verdana,sans-serif;text-decoration:none;float:none;}
  </style>
  <style type="text/css">
span {
        font-family: Arial;
        color: #000000;
        background: #FFFFFF;
        font-size: 10pt;
  }
  pre {
        font-family: monospace;
        color: #000000;
        background: #FFFFFF;
        font-size: 10pt;
  }
  p.Heading0, li.Heading0, div.Heading0, span.Heading0 {
        font-size:14.0pt;
        font-family:Arial;
        font-weight:bold;
  }
  h1 {
        page-break-after:avoid;
        font-size:14.0pt;
        font-family:Arial;
  }
  h2 {
        page-break-after:avoid;
        font-size:12.0pt;
        font-family:Arial;
  }
  DL, DT, OL, UL, LI, DD {
    list-style-position: outside;
  }
  pre {
    font-family: monospace;
    font-size: 10pt;
  }
  table {
    font-size: 10pt;
  }
  </style>
  <style type="text/css">
ol.c10 {list-style-type: decimal;}
  dl.c9 {font-weight: normal; font-size: 10pt;}
  li.c8 {font-weight: bold;}
  span.c7 {font-style: italic;}
  span.c6 {font-weight: bold;}
  ul.c5 {font-weight: normal; font-size: 10pt; text-align: justify;}
  span.c4 {color: green; font-size: 120%}
  ol.c3 {font-weight: normal; font-size: 10pt; text-align: justify;}
  span.c2 {color: green}
  p.c1 {font-weight: normal; font-size: 10pt; text-align: justify;}
  </style>

  <title>MPLAB C Compiler for PIC32 v1.10(B), Release Notes</title>
</head>

<body>
  <script language="JavaScript" type="text/javascript">
function shoh(id) { 
        
        if (document.getElementById) { // DOM3 = IE5, NS6
                if (document.getElementById(id).style.display == "none"){
                        document.getElementById(id).style.display = 'block';
                } else {
                        document.getElementById(id).style.display = 'none';
                }       
        } else { 
                if (document.layers) {  
                        if (document.id.display == "none"){
                                document.id.display = 'block';
                        } else {
                                document.id.display = 'none';
                        }
                } else {
                        if (document.all.id.style.visibility == "none"){
                                document.all.id.style.display = 'block';
                        } else {
                                filter(("img"+id),'imgout');
                                document.all.id.style.display = 'none';
                        }
                }
        }
  }
  </script>

  <h1 class="formtitle">Release Notes for MPLAB<sup>&reg;</sup> C Compiler for PIC32 MCUs</h1>

  <h2>v1.10(B)<br>
  November 2009</h2>

  <h1 class="formtitle">Table of Contents</h1>

  <ol>
    <li><a href="#Overview">Overview</a></li>

    <li><a href="#GPL">GNU General Public License</a></li>

    <li><a href="#Devices">Devices Supported</a></li>

    <li><a href="#Install">Installation</a></li>

    <li><a href="#Document">Compiler Documentation</a></li>

    <li><strong><a href="#WhatsNew">What's New</a></strong></li>

    <li><a href="#Migration">Migration Issues</a></li>

    <li><a href="#DocUpdate">Documentation Updates</a></li>

    <li><a href="#Fixes">Fixed Issues</a></li>

    <li><a href="#Limits">Limitations</a></li>

    <li><a href="#FeatureLimited">Feature-Limited Editions and License Upgrades</a></li>

    <li><a href="#Support">Customer Support</a></li>
  </ol>
  <hr>
  <br>

  <ol class="c10">
    <li class="Heading0">
      <h1><a name="Overview" id="Overview">Overview</a></h1>

      <p class="c1">The 32-Bit language tools consist of a compiler (pic32-gcc.exe), an assembler
      (pic32-as.exe), a linker (pic32-ld.exe), and an archiver/ librarian (pic32-ar.exe). Additional tools
      distributed with this release include a binary to Intel[intl] Hex converter (pic32-bin2hex.exe) and
      miscellaneous binary utilities (pic32-strip.exe, pic32-strings.exe, pic32-readelf.exe, etc). In
      addition, the compiler utilizes a license manager (pic32-lm.exe) as part of the time-limited MPLAB C
      Compiler for PIC32 MCUs <a href="#FeatureLimited">Standard Evaluation edition</a>.</p>

      <p class="c1">As described in the user's guides, all of the language tools are sensitive to case on the
      command line, including the case of file names. In particular, the C compiler shell (pic32-gcc)
      requires that C source files be named on the command-line with a lower-case .c extension. If an
      upper-case .C filename extension is used, the compiler assumes that the file is a C++ file, which is
      not supported. Similarly, the compiler shell passes a file with an upper-case .S filename extension
      through the C preprocessor before passing it to the assembler, but it passes a file with a lower-case
      .s extension directly to the assembler.</p>
    </li>

    <li class="Heading0">
      <h1><a name="GPL" id="GPL">GNU General Public License</a></h1>

      <p class="c1">The <i>MPLAB<sup>&reg;</sup> C Compiler for PIC32 MCUs</i> tools are written and
      distributed under the GNU General Public License (GPL) which means that its source code is freely
      distributed and available to the public.</p>

      <p class="c1">The source for the tools under the GNU GPL may be downloaded separately from the
      Microchip WWW web page. You may read the GNU GPL in the file named COPYING located the docs
      subdirectory of your install directory. A general discussion of principles underlying the GPL may be
      found at <a href="http://www.gnu.org/copyleft" target="external">www.gnu.org/copyleft</a>.</p>

      <p class="c1">Support code provided for the header files, linker scripts, and runtime libraries are
      proprietary code and not covered under the GPL. See the full <i>MPLAB C Compiler for PIC32 MCUs</i>
      License Agreement for details.</p>
    </li>

    <li class="Heading0">
      <h1><a name="Devices" id="Devices">Devices Supported</a></h1>

      <p class="c1">The following <a href="http://www.microchip.com/pic32" target="external">PIC32MX</a>
      devices are supported:<br>
      <span class="c2">New items for v1.10 in green.</span></p>

      <table align="center" border="1" cellpadding="3" cellspacing="0" summary="Supported Devices">
        <tbody>
          <tr>
            <th>Part Number</th>

            <th>Part Number</th>
          </tr>

          <tr>
            <td align="center">PIC32MX320F032H</td>

            <td align="center">-</td>
          </tr>

          <tr>
            <td align="center">PIC32MX320F064H</td>

            <td align="center">-</td>
          </tr>

          <tr>
            <td align="center">PIC32MX320F128H</td>

            <td align="center">PIC32MX320F128L</td>
          </tr>

          <tr>
            <td align="center">PIC32MX340F128H</td>

            <td align="center">PIC32MX340F128L</td>
          </tr>

          <tr>
            <td align="center">PIC32MX340F256H</td>

            <td align="center">-</td>
          </tr>

          <tr>
            <td align="center">PIC32MX340F512H</td>

            <td align="center">-</td>
          </tr>

          <tr>
            <td align="center">-</td>

            <td align="center">PIC32MX360F256L</td>
          </tr>

          <tr>
            <td align="center">-</td>

            <td align="center">PIC32MX360F512L</td>
          </tr>
        </tbody>
      </table>

      <table align="center" border="1" cellpadding="3" cellspacing="0" summary="Supported Devices">
        <tbody>
          <tr>
            <th>Part Number</th>

            <th>Part Number</th>
          </tr>

          <tr>
            <td align="center">PIC32MX420F032H</td>

            <td align="center">-</td>
          </tr>

          <tr>
            <td align="center">PIC32MX440F128H</td>

            <td align="center">PIC32MX440F128L</td>
          </tr>

          <tr>
            <td align="center">PIC32MX440F256H</td>

            <td align="center">-</td>
          </tr>

          <tr>
            <td align="center">PIC32MX440F512H</td>

            <td align="center">-</td>
          </tr>

          <tr>
            <td align="center">-</td>

            <td align="center">PIC32MX460F256L</td>
          </tr>

          <tr>
            <td align="center">-</td>

            <td align="center">PIC32MX460F512L</td>
          </tr>
        </tbody>
      </table>

      <table align="center" border="1" cellpadding="3" cellspacing="0" summary="Supported Devices">
        <tbody>
          <tr>
            <th>Part Number</th>

            <th>Part Number</th>
          </tr>

          <tr>
            <td align="center"><span class="c2">PIC32MX575F256H</span></td>

            <td align="center"><span class="c2">PIC32MX575F256L</span></td>
          </tr>

          <tr>
            <td align="center"><span class="c2">PIC32MX575F512H</span></td>

            <td align="center"><span class="c2">PIC32MX575F512L</span></td>
          </tr>

          <tr>
            <td align="center"><span class="c2">PIC32MX675F512H</span></td>

            <td align="center"><span class="c2">PIC32MX675F512L</span></td>
          </tr>

          <tr>
            <td align="center"><span class="c2">PIC32MX695F512H</span></td>

            <td align="center"><span class="c2">PIC32MX695F512L</span></td>
          </tr>

          <tr>
            <td align="center"><span class="c2">PIC32MX795F512H</span></td>

            <td align="center"><span class="c2">PIC32MX795F512L</span></td>
          </tr>
        </tbody>
      </table>

      <p class="c1">The PIC32MXGENERIC device is, as its name implies, a non-specific target that can be used
      to represent a generic core device.</p><!--
      <p class="c1">(<a name="devicefootnote1" id="devicefootnote1">1</a>) The peripheral library is not yet
      fully supported for this device.</p> -->
    </li>

    <li class="Heading0">
      <h1><a name="Install" id="Install">Installation</a></h1>

      <p class="c1">If using <a href="http://www.microchip.com/mplabide" target="external">MPLAB IDE</a>, be
      sure to install MPLAB IDE v8.10 or later before installing these tools.</p>

      <p class="c1">To install the <i>MPLAB C Compiler for PIC32 MCUs</i> tools, perform the following
      steps:</p>

      <ol class="c3">
        <li>Locate the setup program on the 'MPLAB C Compiler for PIC32 MCUs' CD ROM.</li>

        <li>Run the setup program.</li>

        <li>Follow the directions on the screen. To install the standard evaluation edition, leave the
        license-key field blank when prompted. To install the full standard edition, enter your full license
        key.</li>

        <li>If the installation program indicates that it is necessary, reboot your computer to complete the
        installation.</li>

        <li>When the installation is complete, verify that the executable directory has been correctly added
        to your PATH (i.e., if you chose to install the tools in the default directory, c:\Program
        Files\Microchip\MPLAB C32, then ensure that c:\Program Files\Microchip\MPLAB C32\bin has been added
        to your PATH. On some systems, the default path is c:\Program Files\Microchip\MPLAB C32 Suite.).

          <p>From a Windows command prompt (cmd.exe), type: c:\&gt;PATH</p>
        </li>
      </ol>

      <p class="c1"><strong>To upgrade to a full standard-edition license</strong> from a lite or standard
      -evaluation edition license, follow the steps described in <a href="#FeatureLimited">this
      section</a>.</p>
    </li>

    <li class="Heading0">
      <h1><a name="Document" id="Document">Compiler Documentation</a></h1>

      <p class="c1">The following documents pertain to the MPLAB C Compiler for PIC32 MCUs. They may be
      installed in the compiler's doc subdirectory, but you should check <a href=
      "http://www.microchip.com/c32" target="external">Microchip's website</a> for the latest revisions.</p>

      <ul class="c5">
        <li><a href="http://bit.ly/MPLABC32Docs" target="doc"><cite>MPLAB<sup>&reg;</sup> C Compiler for
        PIC32 MCUs User's Guide</cite> (DS51686)</a></li>

        <li><a href="http://bit.ly/MPLABC32LibsDoc" target="doc"><cite>MPLAB<sup>&reg;</sup> 32-Bit Language
        Tools Libraries</cite> (DS51685)</a></li>

        <li>Microchip PIC32MX Peripheral Library - Compiled Help (chm)</li>

        <li><a href="http://bit.ly/ASM32Doc" target="doc">MPLAB<sup>&reg;</sup> MPLAB Assembler, Linker and
        Utilities for PIC32 MCUs User&rsquo;s Guide (DS51833)</a></li>
      </ul>

      <p class="c1">Additional documentation on the GNU Assembler and Linker is available on the <a href=
      "http://sourceware.org/binutils/docs-2.15/" target="external">GNU Binutils website</a>.</p>
    </li>

    <li class="Heading0">
      <h1><a name="WhatsNew" id="WhatsNew"></a>What's New</h1><a name="new106target" id="new106target"></a>

      <h2><a href="#new106target" onclick="shoh('new106');">New Features in v1.10</a></h2>

      <div style="display: block;" id="new106">
        <ul class="c5">
          <li>
            <p><strong>Compiler licenses renamed</strong> -- The feature-limited compiler licenses have been
            renamed. The academic version is now the <strong>MPLAB C Compiler for PIC32 MCUs Lite
            edition</strong>. The evaluation version is now the <strong>MPLAB C Compiler for PIC32 MCUs
            Standard Evaluation edition</strong>. The full version is now the <strong>MPLAB C Compiler for
            PIC32 MCUs Standard edition</strong> (Part Number: <a target="external" href=
            "http://www.microchipdirect.com/productsearch.aspx?Keywords=SW006015">SW006015</a>). This is a
            name change only. See <a href="#FeatureLimited">this section</a> for more information on the
            features available for each edition.</p>
          </li>

          <li>
            <strong>Smart I/O</strong> -- This release introduces a new
            <strong><tt>-msmart-io=[0|1|2]</tt></strong> command-line option. This feature attempts to
            statically analyze format strings passed to <tt>printf</tt>, <tt>scanf</tt>, and the 'f' and 'v'
            variations of these functions. Uses of non floating-point format arguments will be converted to
            use an integer-only variation of the library function. For many applications, this feature can
            reduce program-memory usage.

            <p><tt>-msmart-io=0</tt> disables this option, while <tt>-msmart-io=2</tt> causes the compiler to
            be optimistic and convert function calls with variable or unknown format arguments.
            <tt>-msmart-io=1</tt> is the safe default and will convert only when the compiler can prove that
            floating-point support is not required.</p>
          </li>

          <li>
            <strong><a name="ISR_Context_improvements" id="ISR_Context_improvements">Interrupt Context-Saving
            Improvements</a></strong> -- New PIC32 devices introduced in this release (5XX, 6XX, 7XX) allow
            us to select, via configuration fuses, which priority will use the shadow register set. (Refer to
            the device datasheet to determine if your PIC32 device supports this feature.) This means that we
            must specify which context-saving mechanism to use for each interrupt service routine. We specify
            the mechanism as part of the IPL specifier passed in the interrupt attribute,
            <strong><tt>__attribute__((interrupt([IPLn[AUTO|SOFT|SRS]])))</tt></strong>, where n is in the
            range of 0..7, inclusive.

            <p><strong>NOTE</strong>: An incorrect <tt>IPL<em>n</em></tt> value can cause incorrect nesting
            of interrupts, which could result in a stack overflow and eventually a bus-error exception. If
            you experience a bus-error exception related to an interrupt, double check that your
            <tt>IPL<em>n</em></tt> value matches the IPL value set for the interrupt source.</p>

            <p><a href="#ISR_Context_improvements" onclick="shoh('new106_IPL_READMORE');">Read
            More...</a></p>

            <div style="display: none;" id="new106_IPL_READMORE">
              <ul>
                <li>
                  <p><strong>IPL Specifiers</strong></p>

                  <ul>
                    <li>
                      <p><tt><strong>IPL<em>n</em>AUTO</strong></tt> -- The compiler supports an
                      <tt>IPL<em>n</em>AUTO</tt> IPL specifier that uses the runtime value in <tt>SRSCTL</tt>
                      to determine whether it should use software or SRS context saving. The interrupt
                      context-saving code generated for this specifier has a slightly higher latency,
                      compared to <tt>IPL<em>n</em>SOFT</tt> or <tt>IPL<em>n</em>SRS</tt>, due to the
                      instructions required to test the <tt>SRSCTL</tt> value. Example:<br>
                      <tt>void <strong>__attribute__((interrupt(IPL6AUTO), vector(1)))</strong> myISR (void))
                      { /* code */ }</tt></p>
                    </li>

                    <li>
                      <p><strong><tt>IPL<em>n</em>SOFT</tt></strong> -- The compiler will use software
                      context saving for the <tt>IPL<em>n</em>SOFT</tt> specifier. Application code is
                      responsible for applying the correct <em>n</em> interrupt-source priority value to the
                      matching handler routine. Example:<br>
                      <tt>void <strong>__attribute__((interrupt(IPL6SOFT), vector(1)))</strong> myISR (void))
                      { /* code */ }</tt></p>
                    </li>

                    <li>
                      <p><tt><strong>IPL<em>n</em>SRS</strong></tt> -- The compiler will generate interrupt
                      prologue and epilogue code utilizing shadow-register context saving for
                      <tt>IPL<em>n</em>SRS</tt>. This IPL specifier results in the shortest interrupt
                      context-saving latency. However, when using <tt>IPL<em>n</em>SRS</tt>, you must
                      configure the corresponding interrupt source to use a shadow register set. On some
                      devices, the shadow register set is tied to IPL7. On other devices, the shadow register
                      set is configurable in a device configuration register (DEVCFG). Example:<br>
                      <tt>void <strong>__attribute__((interrupt(IPL6SRS), vector(1)))</strong> myISR (void))
                      { /* code */ }</tt><br></p>
                    </li>

                    <li>
                      <p><strong><tt>single</tt></strong> -- For single-vector interrupt mode, use
                      <tt>single</tt> as the IPL parameter passed to the interrupt attribute. Example:<br>
                      <tt>void <strong>__attribute__((interrupt(single), vector(1)))</strong> myISR (void)) {
                      /* code */ }</tt></p>
                    </li>

                    <li>
                      <p><strong><em>Default</em></strong> -- The compiler defaults to selecting the IPL
                      value and shadow-register usage at runtime when the IPL specifier is omitted from the
                      interrupt() attribute. Omitting the IPL specifier results in slightly larger interrupt
                      context-saving latency. <em>For mult-vector interrupt mode where the requested IPL
                      value may change at runtime, use this default behavior</em>. Example:<br>
                      <tt>void <strong>__attribute__((interrupt(), vector(1)))</strong> myISR (void)) { /*
                      code */ }</tt></p>
                    </li>
                  </ul>
                </li>

                <li>
                  <p><strong>Updated __ISR Macro</strong> -- The IPL specifier argument to the
                  <tt>__ISR()</tt> macro, defined in <tt>&lt;sys/attribs.h&gt;</tt>, is now optional. With
                  the IPL specifier omitted, the compiler defaults to selecting the IPL value and
                  shadow-register usage at runtime.</p>

                  <ul>
                    <li>
                      <p><strong>Example 1</strong><br>
                      <tt>void <strong>__ISR(_CORE_SOFTWARE_0_VECTOR, IPL3SRS)</strong>
                      CoreSoftwareInt0Handler(void)</tt><br>
                      This example creates an interrupt handler function for the core software interrupt 0
                      that has an interrupt priority level of three. The compiler places a dispatch function
                      at the associated vector location. To reach this function, the core software interrupt
                      flag and enable bits must be set, and the interrupt priority should be set to a level
                      of three. The device configuration fuses must assign Shadow Register Set 1 to interrupt
                      priority level three. The compiler generates code that assumes that register context
                      will be saved in SRS1.</p>
                    </li>

                    <li>
                      <p><strong>Example 2</strong><br>
                      <tt>void <strong>__ISR(_CORE_SOFTWARE_0_VECTOR)</strong>
                      CoreSoftwareInt0Handler(void)</tt><br>
                      This example creates an interrupt handler function for the core software-interrupt 0
                      and uses the interrupt priority level from the runtime-requested IPL value. The
                      compiler generates code that determines, at runtime, whether context should be saved on
                      the stack by software or context was already saved in a shadow register set.</p>
                    </li>
                  </ul>
                </li>

                <li>
                  <p><strong>Latency improvements</strong> -- The interrupt context saving code has also been
                  modified to improve latency. For instance, the HI/LO register saving code, when required,
                  now appears later in the ISR prologue. This helps reduce stalls when an interrupt occurs
                  during a DIV (divide) instruction.</p>
                </li>
              </ul>
            </div>
          </li>

          <li>
            <strong><a name="APPIOReadMore" id="APPIOReadMore">APPIN/APPOUT Debugging Support</a></strong> --
            New PIC32 devices being introduced in v1.10 (5XX, 6XX, 7XX) support the APPIN/APPOUT debugging
            feature. This PIC32 feature allows the target application to write text or data to an MPLAB IDE
            window without halting the target device. Similarly, you may use the display window to send text
            or data back to the target PIC32 device. This feature requires an <a href=
            "http://www.microchip.com/realice" target="external">MPLAB REAL ICE</a> emulator or an <a href=
            "http://www.microchip.com/icd3" target="external">MPLAB ICD 3</a> debugger.<br>

            <p><a href="#APPIOReadMore" onclick="shoh('new106_APPIOReadMore');">Read More...</a></p>

            <div style="display: none;" id="new106_APPIOReadMore">
              <ul>
                <li><strong><tt>-mappio-debug</tt></strong> -- Use this command-line option to enable the
                APPIN/APPOUT debugging library functions for the ICD 3 debugger and REAL ICE emulator. This
                feature allows you to use the DBPRINTF and related functions and macros. Enable this option
                only when using a target PIC32 device that supports the APPIN/APPOUT feature.</li>

                <li>
                  <strong>Example Code</strong> --

                  <div class="code panel" style="border-width: 1px; margin: 2px;">
                    <div class="codeContent panelContent">
                      <pre class="codeContent">
<tt>#include &lt;p32xxxx.h&gt;
int main (void)
{
    int num;
    char buf[256] ={0};
    DBINIT();

    while(1)
    {
      DBPRINTF ("Hello there!\n");
      DBPRINTF ("Enter a string\n");
#if defined(__APPIO_DEBUG)
      DBSCANF ("%s", &amp;buf[0]);
#elif defined(PIC32_STARTER_KIT)
      DBGETS  (&amp;buf[0],128);
#endif
      DBPRINTF ("Entered \"%s\"\n\n", &amp;buf[0]);
      
      printf ("Prints to UART2 by default or APPO when enabled\n");
    }
  return 0;
}</tt>
</pre>
                    </div>
                  </div>
                </li>
              </ul>
            </div>
          </li>

          <li>
            <strong><a name="SPLIMReadMore" id="SPLIMReadMore">Stack Limit symbol in built-in linker
            script</a></strong> -- The default linker script now provides an _SPLIM symbol that you can use
            from code to help detect a stack overflow at runtime. This symbol is associated with the lowest
            address of the space reserved for the stack.

            <p><a href="#SPLIMReadMore" onclick="shoh('new106_SPLIMReadMore');">Read More...</a></p>

            <div style="display: none;" id="new106_SPLIMReadMore">
              <ul>
                <li>
                  <strong>Example Code</strong> --

                  <div class="code panel" style="border-width: 1px; margin: 2px;">
                    <div class="codeContent panelContent">
                      <pre class="codeContent">
<tt>#include &lt;stddef.h&gt;
#define _STACK_DEBUG 1
#if (_STACK_DEBUG)
#define stackcheck() _stackcheck(__FILE__, __LINE__)

static inline __attribute__((always_inline))
ptrdiff_t _stackcheck(const char *filename, unsigned int linenum)
{
  extern void _SPLIM; /* From linker script */

  register void* stackptr __asm__("$sp");

  /* Compare the current stack pointer with the Stack Pointer Limit symbol, _SPLIM */
  if ((ptrdiff_t)stackptr &lt;= (ptrdiff_t)&amp;_SPLIM)
    {
        /* Handle stack overflow */
        while(1);
    }
  return ((ptrdiff_t)stackptr - (ptrdiff_t)&amp;_SPLIM);
}
#else
#define stackcheck() (void)0
#endif

unsigned char foo(unsigned char var);
volatile unsigned int testval;

int main (void)
{
    unsigned char array[0x7A50];
    testval = 0;

    array[0] = 1;
    foo (array[0]);

    testval = 1;
    while(1);
}
unsigned char
foo(unsigned char var)
{
    stackcheck();
    return var+1;
}</tt>
</pre>
                    </div>
                  </div>
                </li>
              </ul>
            </div>
          </li>

          <li>
            <strong><a name="FeatureSetMacro" id="FeatureSetMacro">Predefined macro for Feature
            Set</a></strong> -- The compiler predefines a macro based on the features available for the
            selected device. These macros are intended to be used when writing code to take advantage of
            features available on newer devices while maintaining compatibility with older devices.

            <p><a href="#FeatureSetMacro" onclick="shoh('new106_FeatureSetMacroReadMore');">Read
            More...</a></p>

            <div style="display: none;" id="new106_FeatureSetMacroReadMore">
              <ul>
                <li><strong>Examples</strong><br>
                PIC32MX<strong>795</strong>F512L would use <tt>__PIC32_FEATURE_SET__ == 795</tt>, and<br>
                PIC32MX<strong>340</strong>F128H would use <tt>__PIC32_FEATURE_SET__ == 340</tt>.<br>
                <br></li>

                <li>
                  <strong>Example Code</strong> --

                  <div class="code panel" style="border-width: 1px; margin: 2px;">
                    <div class="codeContent panelContent">
                      <pre class="codeContent">
<tt>#if ((__PIC32_FEATURE_SET__ &gt;= 500) &amp;&amp; 
     (__PIC32_FEATURE_SET__ &lt;= 799))
   { /* do stuff for 5XX, 6XX, 7XX families */ }
#elif ((__PIC32_FEATURE_SET__ &gt;= 300) &amp;&amp; 
       (__PIC32_FEATURE_SET__ &lt;= 499))
   { /* do stuff for 3XX, 4XX families */ }
#elif ((__PIC32_FEATURE_SET__ &gt;= 800) &amp;&amp;
       (__PIC32_FEATURE_SET__ &lt; 1000))
   { /* do stuff for some future family */ }
#endif
</tt>
</pre>
                    </div>
                  </div><br>
                  <br>
                </li>
              </ul>
            </div>
          </li>
        </ul>
      </div>

      <h2><a href="#new105" onclick="shoh('new105');">New Features in v1.05</a></h2>

      <div style="display: none;" id="new105">
        <ul class="c5">
          <li><strong>Student Edition renamed Evaluation Version</strong> -- The student edition has been
          renamed the evaluation version. This release also introduces a new academic version. For more
          information on the feature-limited version, see <a href="#FeatureLimited">this section.</a>
          <font color="red">(Note that the licenses have been renamed again for the v1.10
          release.)</font></li>

          <li><strong>Improved 16- and 32-bit FFT functions in the DSP Library</strong> -- The FFT functions
          have been significantly improved and optimized for the PIC32 instruction set. See the 32-bit
          Language Tools Libraries document (DS51685) for more information. Please visit <a href=
          "http://www.microchip.com/c32">Microchip's website</a> for the revision C of this document
          (DS51685C).</li>

          <li><strong>Binary Constants</strong> -- A sequence of binary digits preceded by 0b or 0B (the
          numeral '0' followed by the letter 'b' or 'B') is taken to be a binary integer. The binary digits
          consist of the numerals '0' and '1'. Note that this binary-constant syntax may not be accepted by
          other C compilers.</li>

          <li>
            <strong>Linker Memory-Usage Report</strong> -- This optional, informational report allows you to
            easily determine the program- and data-memory usage of your application. It allows you to see how
            much space is used by the project being linked and how much space is available on the target
            device. The memory-usage report appears on stdout and in the optional map file.

            <ul>
              <li>Using this feature with <strong>MPLAB IDE 8.30 and earlier</strong> -- On the linker's tab
              of the project build options, select to <strong>Use Alternate Settings</strong>. Add the
              <strong><tt>--report-mem</tt></strong> option to the Alternate Settings field. The memory-usage
              report will appear in the output window after a project build. (This option will appear as a
              checkbox in later MPLAB IDE releases.)</li>

              <li>Using this feature on the <strong>command prompt</strong> -- Add the <tt>--report-mem</tt>
              option to the linker's command line. If you are calling the linker via the compilation driver,
              use the driver's <tt>-Wl</tt> option to pass the <tt>--report-mem</tt> option to the linker.
              The memory-usage report will appear on stdout.</li>
            </ul>
          </li>

          <li>
            <strong>Improved malloc implementation</strong> -- This release contains a new
            malloc/free/realloc implementation based on the implementation written by Doug Lea and released
            to the public domain.

            <ul>
              <li>This is not the fastest, most space-conserving, most portable, or most tunable malloc ever
              written. However it is among the fastest while also being among the most space-conserving,
              portable and tunable. Consistent balance across these factors results in a good general-purpose
              allocator.</li>

              <li>For a high-level description, see <a href=
              "http://g.oswego.edu/dl/html/malloc.html">http://g.oswego.edu/dl/html/malloc.html</a></li>

              <li>This implementation is also provided with the <a href=
              "http://sourceware.org/newlib/">Newlib</a> C Library.</li>
            </ul>
          </li>

          <li><strong>Instruction Macros</strong> -- The p32xxxx.h include file now contains a Nop() macro
          that issues a superscalar SSNOP instruction.</li>

          <li><strong><tt>gettimeofday()</tt> weak stub</strong> -- The time.h <tt>clock()</tt> and
          <tt>time()</tt> functions require a user-provided <tt>gettimeofday()</tt> helper function. The
          compiler's library now provides a weak stub implementation that allows the project link to complete
          without error, but you should provide your own implementation appropriate for your
          application.</li>

          <li><strong>Microchip DSP Compatibility Wrapper functions</strong> -- This release provides new DSP
          wrapper functions intended to ease the migration from the Microchip DSP library for dsPIC DSCs to
          the general DSP library for PIC32 MCUs. See the 32-Bit Language Tools Libraries (DS51685C) document
          for more information on these new wrapper functions.</li>

          <li><strong>Updated peripheral-library documentation</strong> -- The 32-bit peripheral library
          document is now distributed as a compiled help file (*.chm) rather than a PDF file.</li>

          <li><strong>Support for PWP configuration bits</strong> -- The config pragma now supports enabling
          the Program Write Protect bits. See the <em>PIC32MX Config Settings</em> help file for information
          on the setting name and available values for each device.</li>
        </ul>
      </div>
    </li>

    <li style="list-style: none; display: inline">
      <h2><a href="#new104" onclick="shoh('new104');">New Features in v1.04</a></h2>

      <div style="display: none;" id="new104">
        <ul class="c5">
          <li>
            <strong>General DSP Library</strong> -- The DSP Library supports a variety of signal processing
            functions that have applicability in speech compression, echo cancellation, noise cancellation,
            channel equalization, audio decoding, and many other DSP and media applications. The library is
            highly optimized for the PIC32 MCU instruction set.

            <ul>
              <li>The DSP Library expects Q-type fixed-point arguments and produces Q-type results. The MPLAB
              C Compiler for PIC32 MCUs does not currently support converting float or double types to
              Q-types.</li>

              <li>See the 32-Bit Language Tools Libraries (DS51685) for documentation on the DSP Library
              functions.</li>

              <li>In the near future, a "dsPIC DSC DSP Algorithm Library" compatibility layer will be
              available. This compatibility layer makes the PIC32 DSP Library backwards compatible with the
              existing dsPIC DSC DSP Algorithm Library.</li>
            </ul>
          </li>

          <li>
            <strong>Vector attribute accepts parenthesized list of vector numbers</strong> -- The interrupt
            vector attribute now accepts a parenthesized list of one or more interrupt vector numbers. This
            means that you can now more easily generate multiple dispatch functions that target a single
            interrupt service routine as shown in the example below.

            <div class="code panel" style="border-width: 1px; margin: 10px;">
              <div class="codeContent panelContent">
                <tt>#include &lt;p32xxxx.h&gt;<br>
                #include &lt;sys/attribs.h&gt;<br>
                void __ISR((_TIMER_1_VECTOR,_TIMER_2_VECTOR,_TIMER_3_VECTOR),ipl6) TimerISR(void);</tt>
              </div>
            </div>
          </li>

          <li><strong>Interrupt service routines forced to nomips16</strong> -- The compiler will now force
          functions marked with the interrupt attribute to be nomips16. The compiler will emit a warning if
          it overrides the mips16 attribute or command-line default. Previous compiler releases stopped
          compilation with an error and required users to manually add the nomips16 attribute. Note that you
          should use the __ISR macro from the sys/attribs.h header rather than manually specify the interrupt
          attribute.</li>

          <li><strong>Trigonometric function refactorization</strong> -- A few trigonometric functions have
          been refactored for a smaller code-size footprint.</li>
        </ul>
      </div>

      <h2><a href="#new103" onclick="shoh('new103');">New Features in v1.03</a></h2>

      <div style="display: none;" id="new103">
        <ul class="c5">
          <li><strong>Optimized math library</strong> -- The floating-point math library provided with the
          compiler has been significantly optimized to take full advantage of the PIC32MCU instruction set.
          The improved library provides the greatest benefit for the more complex operations, offering a
          greater than 5x performance improvement over the 1.02 library for many operations and an even more
          significant improvement for some operations. In addition, single-precision math library functions
          are now available, giving users a choice between double- and single-precision operations. See
          math.h for more information.</li>
        </ul>

        <ul class="c5">
          <li><strong>Time-Limited Evaluation Version</strong> -- The new evaluation version provides
          <strong>full functionality for 60 days</strong>. After the evaluation version has expired, the
          compiler becomes feature limited. See <a href="#FeatureLimited">this section</a> for further
          details. <font color="red">(Note that this license has been renamed to the "Standard Evaluation
          Edition" for the v1.10 release.)</font></li>
        </ul>

        <ul class="c5">
          <li><strong><tt>__C32_VERSION__</tt> predefined macro</strong> -- The C compiler defines the
          constant <tt>__C32_VERSION__</tt>, giving a numeric value to the version identifier. This macro can
          be used to construct applications that take advantage of new compiler features while still
          remaining backward compatible with older versions. The value is based upon the major and minor
          version numbers of the current release. For example, release version 1.03 will have a
          <tt>__C32_VERSION__</tt> definition of 103. This macro can be used, in conjunction with standard
          preprocessor comparison statements, to conditionally include/exclude various code constructs.</li>
        </ul>

        <ul class="c5">
          <li>
            <strong><tt>__ISR_SINGLE__</tt> and <tt>__ISR_SINGLE_AT_VECTOR__</tt> convenience macros</strong>
            -- The sys/attribs.h header file now provides two new macros intended to simplify the use of the
            single-vector interrupt mechanism. See the sys/attribs.h header file for more information.

            <ul>
              <li>The <tt>__ISR_SINGLE__</tt> macro specifies a function as an interrupt-service routine in
              single-vector mode. This will place a jump at the single-vector location to the interrupt
              handler.</li>

              <li>The <tt>__ISR_SINGLE_AT_VECTOR__</tt> macro places the entire single-vector interrupt
              handler at the vector 0 location. The user is responsible for ensuring that the vector spacing
              is set to accommodate the size of the handler.</li>
            </ul>
          </li>
        </ul>
      </div>
    </li>

    <li class="Heading0">
      <h1><a name="Migration" id="Migration"></a>Migration Issues</h1>

      <p class="c1">The following changes may affect migration from older versions of the compiler.</p>

      <h2><a href="#migrate105" onclick="shoh('migrate106');">Migrating to Version v1.10</a></h2>

      <div style="display: block;" id="migrate106">
        <ul class="c5">
          <li class="c8">Interrupt context saving

            <ul class="c5">
              <li>
                <strong>IPL specifier</strong> -- In prior compiler releases, the interrupt service-routine
                prologue code determined the IPL value from the runtime RIPL value. This meant that the IPL
                specifier value in the interrupt attribute or interrupt pragma did not have to exactly match
                the actual IPL value for the interrupt source. The interrupt service routine worked
                correctly, even when there was a discrepancy in the IPL value.

                <p>The interrupt prologue code generated by this release of the compiler uses the IPL value
                as specified in the interrupt attribute or interrupt pragma. An incorrect IPLn value can
                cause incorrect nesting of interrupts, which could result in a stack overflow and eventually
                a bus-error exception. If you experience a bus-error exception related to an interrupt,
                double check that your IPLn value matches the IPL value set for the interrupt source.</p>

                <p>Some applications may require an interrupt priority that changes at runtime. In this case,
                omit the IPL specifier from the interrupt attribute as shown in the examples below. e.g.<br>
                <tt>&nbsp;&nbsp;void __attribute__((interrupt(), vector(1))) myISR1 (void)) { /* code */
                }</tt><br>
                <tt>&nbsp;&nbsp;void __ISR(_CORE_SOFTWARE_0_VECTOR) CoreSoftwareInt0Handler(void) { /* code
                */ }</tt></p>

                <p>Currently, the interrupt pragma does not support interrupt priority levels that change at
                runtime. In this case, convert the interrupt pragma to an interrupt attribute as described
                above. For instance:</p>

                <div class="code panel" style="border-width: 1px; margin: 2px;">
                  <div class="codeContent panelContent">
                    <pre class="codeContent">
<tt>#pragma interrupt foo ipl3 vector 4
void foo (void) { /* code */ }</tt>
</pre>
                  </div>
                </div>becomes

                <div class="code panel" style="border-width: 1px; margin: 2px;">
                  <div class="codeContent panelContent">
                    <pre class="codeContent">
<tt>void __attribute__((interrupt(), vector(4))) foo (void) { /* code */ }</tt>
</pre>
                  </div>
                </div>
              </li>
            </ul>
          </li>

          <li class="c8">STDIO

            <ul class="c5">
              <li><strong>BUFSIZ</strong> -- The input buffer size has been reduced from 1024 to 64 bytes.
              Use the setvbuf() function to specify another buffer if your application requires a buffer of
              another size.</li>

              <li><strong>STDOUT_BUFSIZ</strong> -- The stdout default-buffer size has been reduced from 128
              bytes to 32 bytes. Use the setvbuf() function to specify another buffer if your application
              requires a buffer of another size.</li>
            </ul>
          </li>

          <li class="c8">Device support

            <ul class="c5">
              <li><strong>PIC32MX4xx devices</strong> -- The UPLLIDIV configuration fuse settings were
              incorrectly named DIV_7 and DIV_8 for several PIC32MX4XX devices. They are now correctly named
              DIV_10 and DIV_12, respectively. Code using the older names will fail to compile. Update your
              code to use the new setting names.</li>
            </ul>
          </li>

          <li class="c8">Documentation

            <ul class="c5">
              <li><strong>Peripheral Library documentation now provided as a help file</strong> -- The
              peripheral library documentation is now provided as a CHM file rather than a PDF file. Older
              versions of the compiler installer added a link to the PDF file in MPLAB IDE's online help. To
              remove this outdated link, run the uninstall facility in Windows Add/Remove Programs to
              completely uninstall the compiler. Then re-run the v1.10 compiler installer.</li>
            </ul>
          </li>
        </ul>
      </div>

      <h2><a href="#migrate105" onclick="shoh('migrate105');">Migrating to Version v1.05</a></h2>

      <div style="display: none;" id="migrate105">
        <ul class="c5">
          <li class="c8">DSP Library

            <ul class="c5">
              <li><strong>FFT setup functions</strong> -- The FFT setup functions, mips_fft16_setup() and
              mips_fft32_setup(), are now deprecated. The FFT functions now load precalculated coefficients
              so these setup functions are no longer required. Please visit <a href=
              "http://www.microchip.com/c32">Microchip's website</a> for the revision C of the 32-bit
              Libraries document (DS51685C).</li>
            </ul>
          </li>
        </ul>
      </div>

      <h2><a href="#migrate104" onclick="shoh('migrate104');">Migrating to Version v1.04</a></h2>

      <div style="display: none;" id="migrate104">
        <ul class="c5">
          <li class="c8">Device-support files

            <ul class="c5">
              <li><strong>Device specific IRQ macro definitions</strong> -- The IRQ macro definitions, such
              as <tt>_CORE_TIMER_IRQ</tt>, have moved from the ppic32mx.h header file to the device-specific
              header file (e.g. proc/p32mx460f512l.h). This change should not affect most applications
              because they should include the generic p32xxxx.h file.</li>
            </ul>
          </li>
        </ul>
      </div>

      <h2><a href="#migrate103" onclick="shoh('migrate103');">Migrating to Version v1.03</a></h2>

      <div style="display: none;" id="migrate103">
        <ul class="c5">
          <li class="c8">Peripheral Library

            <ul class="c5">
              <li>Modified SYSTEMConfigXXX functions to use revised flash speed of 30 MHz. If you are
              currently using a SYSTEMConfigXXX function, your application will automatically use the new
              flash-speed specification.</li>
            </ul>
          </li>

          <li class="c8">Examples

            <ul class="c5">
              <li>Modified all plib_examples to use SYSTEMConfig() function. This function allows users to
              selectively configure certain parameters only.</li>
            </ul>
          </li>
        </ul>
      </div>

      <h2><a href="#migrate102" onclick="shoh('migrate102');">Migrating to Version v1.02</a></h2>

      <div style="display: none;" id="migrate102">
        <ul class="c5">
          <li>
            <span class="c6">Processor Header files</span>

            <ul>
              <li>Removed Extended Mode (XM bit) in DMA controller</li>
            </ul>
          </li>

          <li class="c8">Peripheral Library - See the <span class="c7">Microchip PIC32MX Peripheral
          Library</span> compiled help (*.chm) for details<br>

            <ul class="c5">
              <li>DMA Extended mode is removed. The maximum transfer length is now 256 bytes, even for memory
              copy and CRC functions.</li>

              <li>Symbols DMA_OPEN_NORM and DMA_OPEN_EXT used in the DmaChnOpen() call were removed. A new
              symbol, DMA_OPEN_DEFAULT was added.<br></li>

              <li>A new function, DmaGetMaxTcferSize() was added, to return the maximum supported size of a
              transfer, variant dependent. Right now, only 256 bytes transfer size supported.<br></li>

              <li>DmaChnSetExtTxfer() was removed, no longer relevant.<br></li>

              <li>DMA_CTL_EXT_EN was removed from the low level access routines</li>

              <li>SYSTEMConfig() function was added to enable user-specified configuration for a given system
              frequency.</li>
            </ul>
          </li>
        </ul>
      </div>
    </li>

    <li class="Heading0">
      <h1><a name="DocUpdate" id="DocUpdate"></a>Documentation Updates</h1>

      <h2>Library documentation updates</h2>

      <p class="c1">This section describes pending updates to the <cite>MPLAB<sup>&reg;</sup> 32-Bit Language
      Tools Libraries</cite> documentation. These changes will be incorporated into the next full revision of
      the documents.</p>

      <ul class="c5">
        <li><strong>BUFSIZ</strong> -- The BUFSIZ definition in stdio.h has been reduced to 64.</li>
      </ul>

      <h2>Compiler documentation updates</h2>

      <p class="c1">This section describes pending updates to the <em>MPLAB C Compiler for PIC32</em>
      documentation. These changes will be incorporated into the next full revision of the documents.</p>

      <ul class="c5">
        <li><strong>Binary Constants</strong> -- A sequence of binary digits preceded by <tt>0b</tt> or
        <tt>0B</tt> (the numeral '0' followed by the letter 'b' or 'B') is taken to be a binary integer. The
        binary digits consist of the numerals '0' and '1'. For example, the (decimal) number 255 can be
        written as <tt>0b11111111</tt>. Like other integer constants, a binary constant may be suffixed by
        the letter 'u' or 'U', to specify that it is unsigned. A binary constant may also be suffixed by the
        letter 'l' or 'L', to specify that it is long. Similarly, the suffix 'll' or 'LL' denotes a long long
        binary constant. Note that this binary-constant syntax may not be accepted by other C compilers.</li>

        <li><strong><tt>__VERSION__</tt> predefined macro</strong> -- The <tt>__VERSION__</tt> macro expands
        to a string constant describing the compiler in use. Do not rely on its contents having any
        particular form, but it should contain at least the release number. Use the <tt>__C32_VERSION__</tt>
        macro for a numeric version number.</li>

        <li><strong>Interrupt-vector macros</strong> -- Each processor-support header file (e.g.
        \pic32mx\include\proc\p32mx360f512l.h) provides a macro for each interrupt-vector number. When used
        in conjunction with the <tt>__ISR()</tt> macro provided by the sys\attribs.h header file, these
        macros help make an interrupt service routine easier to write and maintain. Example: <tt>void __ISR
        (<em>_TIMER_1_VECTOR</em>, ipl7) Timer1Handler (void);</tt></li>
      </ul>
    </li>

    <li class="Heading0">
      <h1><a name="Fixes" id="Fixes">Fixed Issues</a></h1>

      <p class="c1">The following issues have been resolved in this release</p>

      <h2><a href="#fixed110" onclick="shoh('fixed110');">Fixed in v1.10</a></h2>

      <div style="display: block;" id="fixed110">
        <dl class="c9">
          <dt>C32-267:</dt>

          <dd>The '0' (zero-fill) flag for the output-format conversion specifiers (used with the printf
          functions), now properly causes zero filling when used with floating-point conversions. (e.g.
          <tt>printf("%010.2f",foo);</tt> )</dd>

          <dt>C32-266:</dt>

          <dd>A 'naked' attributed function containing a function call no longer causes a compiler crash when
          building with optimizations enabled.</dd>

          <dt>C32-252:</dt>

          <dd>The SoftReset() peripheral library function now works correctly on devices that do not use DMA,
          such as the PIC32MX320F032H.</dd>

          <dt>C32-224:</dt>

          <dd>In stdlib.h, MB_CUR_MAX is now correctly defined as 1.</dd>

          <dt>DAYHLD-10:</dt>

          <dd>The UPLLIDIV configuration fuse settings were incorrectly named DIV_7 and DIV_8 for several
          PIC32MX4XX devices. They are now correctly named DIV_10 and DIV_12, respectively.</dd>
        </dl>
      </div>

      <h2><a href="#fixed105" onclick="shoh('fixed105');">Fixed in v1.05</a></h2>

      <div style="display: none;" id="fixed105">
        <dl class="c9">
          <dt>C32-064:</dt>

          <dd>Code generated using -Os -mips16 and a very large number of common subexpressions now compiles
          correctly.</dd>

          <dt>C32-232:</dt>

          <dd>Interrupt context-saving code now preserves the assembler temporary ($at) register. While the
          compiler does not use this register for standard C code, the general DSP library or the optimized
          math library use this register.</dd>

          <dt>Peripheral Library:</dt>

          <dd>
            The peripheral-library source files listed below contain fixes and improvements. See the updated
            peripheral-library documentation for further details.

            <ul>
              <li>pic32mx/include/peripheral/int.h</li>

              <li>pic32mx/include/peripheral/incap.h</li>

              <li>pic32mx/include/peripheral/nvm.h</li>

              <li>pic32mx/include/peripheral/dma.h</li>

              <li>pic32mx/include/peripheral/ports.h</li>

              <li>pic32mx/include/peripheral/uart.h</li>

              <li>pic32mx/include/peripheral/i2c.h</li>

              <li>pic32mx/include/peripheral/outcompare.h</li>

              <li>pic32mx/include/peripheral/cmp.h</li>

              <li>pic32mx/include/peripheral/timer.h</li>

              <li>pic32mx/include/peripheral/reset.h</li>

              <li>pic32mx/include/peripheral/pcache.h</li>

              <li>pic32mx/include/peripheral/system.h</li>

              <li>pic32mx/include/peripheral/bmx.h</li>

              <li>pic32-libs/peripheral/nvm/source/nvm_operation_lib.c</li>

              <li>pic32-libs/peripheral/i2c/source/idle_i2c2_lib.c</li>
            </ul>
          </dd>

          <dt>C32-42:</dt>

          <dd>The compiler now emits a more useful diagnostic message when multiple -mprocessor options
          appear on the command line.</dd>
        </dl>
      </div>

      <h2><a href="#fixed104" onclick="shoh('fixed104');">Fixed in v1.04</a></h2>

      <div style="display: none;" id="fixed104">
        <dl class="c9">
          <dd>No significant fixed issues for this release</dd>
        </dl>
      </div>

      <h2><a href="#fixed103" onclick="shoh('fixed103');">Fixed in v1.03</a></h2>

      <div style="display: none;" id="fixed103">
        <dl class="c9">
          <dt>BIN32-30:</dt>

          <dd>Assertion statements in the linker scripts now correctly compare the size of an exception
          vector to the vector spacing.</dd>

          <dt>C32-179:</dt>

          <dd>The gmtime() library function now links without error. In previous releases, the linker would
          complain about an undefined reference to 'offtime_r'</dd>

          <dt>C32-172:</dt>

          <dd>The config pragma now defaults the DEVCFG0 MSb to zero.</dd>

          <dt>C32-171:</dt>

          <dd>The first call to getchar() now calls _mon_getc(). The previous implementation treated the
          initial STDIN character as an ungetc() pushed-back character.</dd>

          <dt>C32-164:</dt>

          <dd>The device-specific header files now use '__asm__' rather than 'asm' when mapping each SFR
          struct to it's symbol name. Previous versions of these files did not compile when building with the
          compiler's -ansi option.</dd>

          <dt>C32-147:</dt>

          <dd>The interrupt attribute now properly accepts an uppercase IPLx value. Earlier compiler versions
          could reject the uppercase IPLx with an internal error.</dd>
        </dl>
      </div>

      <h2><a href="#fixed102" onclick="shoh('fixed102');">Fixed in v1.02</a></h2>

      <div style="display: none;" id="fixed102">
        <dl class="c9">
          <dt>C32-119:</dt>

          <dd>Removed pipeline interlock in ISR handling</dd>

          <dt>C32-141:</dt>

          <dd>Large <tt>malloc()</tt> calls no longer generate a general exception vector instead of
          returning a NULL pointer.</dd>

          <dt>C32-144:</dt>

          <dd>Interrupt macro now sets <tt>nomips16</tt></dd>

          <dt>C32-145:</dt>

          <dd>Include C startup code source is now provided in the standard distribution</dd>

          <dt>C32-151:</dt>

          <dd>IPL7 prologue code now sets incorrect bits in status register</dd>
        </dl>
      </div>
    </li>

    <li class="Heading0">
      <h1><a name="Limits" id="Limits">Limitations</a></h1>

      <p class="c1">The current limitations are as follows.</p>

      <h2>Compiler</h2>

      <p class="c1">No significant issues reported.</p><!--
      <dl class="c9">
        <dt>SSR:</dt>

        <dd>description</dd>
      </dl>
-->

      <h2>Assembler</h2>

      <p class="c1">No significant issues reported.</p>
    </li>

    <li class="Heading0">
      <h1><a name="FeatureLimited" id="FeatureLimited">Feature-Limited Editions and License Upgrades</a></h1>

      <h2>Time-Limited Standard Evaluation Edition</h2>

      <p class="c1"><strong>Feature Limitations</strong> - Microchip provides a <em>free</em> time-limited
      Standard Evaluation edition of the <strong><em>MPLAB C Compiler for PIC32 MCUs</em></strong>. The
      standard evaluation edition of the compiler provides <strong>full functionality for 60 days</strong>.
      After the evaluation period has expired, the compiler becomes feature limited, and optimization
      features associated with levels -O2, -O3, and -Os are disabled. In addition, MIPS16 code generation is
      disabled. The compiler continues to accept the -O1 and -O0 optimization levels indefinitely.</p>

      <p class="c1"><strong>Installing the standard evaluation edition</strong> - To install the time-limited
      standard evaluation edition of the compiler, run the standard evaluation-edition installer and follow
      the on-screen instructions. If the installer asks for a license key, leave the field blank and
      continue.</p>

      <p class="c1"><strong>Upgrading to a standard-edition license</strong> - For applications requiring
      additional code efficiency, as well as full support via <a target="external" href=
      "http://support.microchip.com">http://support.microchip.com</a>, users are encouraged to upgrade to a
      full standard-edition compiler license. For further information on upgrading to a full standard-edition
      license (Part Number: SW006015), visit <a target="external" href=
      "http://www.microchipdirect.com/productsearch.aspx?Keywords=SW006015">http://www.microchipdirect.com</a>
      or contact your preferred Microchip distributor.</p>

      <p class="c1">Once you've obtained a standard-edition license key, run the Upgrader tool
      (pic32-upgrader\upgrader.exe) as a Windows administrator. After you enter your license key and press
      the Upgrade button, the license manager should then report the license upgrade status.</p>

      <h2>Lite Edition</h2>

      <p class="c1"><strong>Feature Limitations</strong> - Microchip provides a <em>free</em> Lite edition of
      the <strong><em>MPLAB C Compiler for PIC32 MCUs</em></strong> intended for use in projects where code
      efficiency is not critical. This edition of the compiler does not support optimization features
      associated with levels -O2, -O3, and -Os. In addition, this edition does not support MIPS16 code
      generation.</p>

      <p class="c1"><strong>Upgrading to the standard edition or standard evaluation edition</strong> - To
      take advantage of the advanced optimization and MIPS16 code generation features, you can upgrade to a
      standard edition or a 60-day standard evaluation edition. To upgrade to a full or 60-day standard
      evaluation edition, uninstall the lite edition using the normal Windows Add/Remove Programs feature.
      Next, install the standard edition or the standard evaluation edition by running the appropriate
      installer and following the on-screen instructions.</p>
    </li>

    <li class="Heading0">
      <h1><a name="Support" id="Support">Customer Support</a></h1>

      <p class="c1">Microchip provides online support via our home page at:<br>
      <a target="external" href="http://www.microchip.com">http://www.microchip.com</a></p>

      <p class="c1">Technical support is available through the web site at:<br>
      <a target="external" href="http://support.microchip.com">http://support.microchip.com</a></p>

      <p class="c1">A forum for discussion of Microchip products and tools is available at:<br>
      <a target="external" href="http://forum.microchip.com">http://forum.microchip.com</a></p>

      <p class="c1">Microchip PIC32 documentation and product info is available at:<br>
      <a target="external" href="http://www.microchip.com/pic32">http://www.microchip.com/pic32</a></p>

      <p class="c1">MPLAB<sup>&reg;</sup> C Compiler for PIC32 MCUs updates and information are available
      at:<br>
      <a target="external" href="http://www.microchip.com/c32">http://www.microchip.com/c32</a></p>
    </li>
  </ol>
</body>
</html>
