<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=Generator content="Microsoft Word 12 (filtered)">
<title>MPLAB REAL ICE Emulator Release Notes</title>

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helv;
	panose-1:2 11 6 4 2 2 2 3 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"MS Shell Dlg";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"NKMNCA+TimesNewRoman\,Bold";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	font-size:14.0pt;
	font-family:"Arial","sans-serif";
	font-weight:bold;}
h2
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.4in;
	text-indent:-.4in;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Arial","sans-serif";
	font-weight:bold;
	font-style:italic;}
h3
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.5in;
	text-indent:-.5in;
	page-break-after:avoid;
	font-size:11.0pt;
	font-family:"Arial","sans-serif";
	font-weight:bold;}
h4
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.6in;
	text-indent:-.6in;
	page-break-after:avoid;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";
	font-weight:bold;
	font-style:italic;}
h5
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.7in;
	text-indent:-.7in;
	font-size:13.0pt;
	font-family:"Arial","sans-serif";
	font-weight:bold;
	font-style:italic;}
h6
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.8in;
	text-indent:-.8in;
	font-size:11.0pt;
	font-family:"Times New Roman","serif";
	font-weight:bold;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.9in;
	text-indent:-.9in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:1.0in;
	text-indent:-1.0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	font-style:italic;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:1.1in;
	text-indent:-1.1in;
	font-size:11.0pt;
	font-family:"Arial","sans-serif";}
p.MsoToc1, li.MsoToc1, div.MsoToc1
	{margin-top:2.0pt;
	margin-right:0in;
	margin-bottom:2.0pt;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoToc2, li.MsoToc2, div.MsoToc2
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:10.0pt;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoNormalIndent, li.MsoNormalIndent, div.MsoNormalIndent
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:.5in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoList, li.MsoList, div.MsoList
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:.25in;
	text-indent:-.25in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoListNumber, li.MsoListNumber, div.MsoListNumber
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:.25in;
	text-indent:-.25in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoListBullet2, li.MsoListBullet2, div.MsoListBullet2
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:.25in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoListBullet3, li.MsoListBullet3, div.MsoListBullet3
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:.75in;
	text-indent:-.25in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoListNumber2, li.MsoListNumber2, div.MsoListNumber2
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:.5in;
	text-indent:-.25in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.MsoDate, li.MsoDate, div.MsoDate
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:0in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.Heading0, li.Heading0, div.Heading0
	{mso-style-name:"Heading 0";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:14.0pt;
	font-family:"Arial","sans-serif";
	font-weight:bold;}
p.Computer, li.Computer, div.Computer
	{mso-style-name:Computer;
	mso-style-link:"Computer Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.NormalNoSpace, li.NormalNoSpace, div.NormalNoSpace
	{mso-style-name:NormalNoSpace;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.DeviceList, li.DeviceList, div.DeviceList
	{mso-style-name:"Device List";
	margin-top:2.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.Default, li.Default, div.Default
	{mso-style-name:Default;
	mso-style-link:"Default Char";
	margin:0in;
	margin-bottom:.0001pt;
	text-autospace:none;
	font-size:12.0pt;
	font-family:"NKMNCA+TimesNewRoman\,Bold";
	color:black;}
p.ListBullet2NoSpace, li.ListBullet2NoSpace, div.ListBullet2NoSpace
	{mso-style-name:"List Bullet 2 NoSpace";
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	text-indent:-.25in;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
p.ListBulletNoSpace, li.ListBulletNoSpace, div.ListBulletNoSpace
	{mso-style-name:"List Bullet No Space";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Arial","sans-serif";}
span.ComputerChar
	{mso-style-name:"Computer Char";
	mso-style-link:Computer;
	font-family:"Courier New";}
span.DefaultChar
	{mso-style-name:"Default Char";
	mso-style-link:Default;
	font-family:"NKMNCA+TimesNewRoman\,Bold";
	color:black;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:.75in .75in .75in .75in;}
div.WordSection1
	{page:WordSection1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=WordSection1>

<p class=Heading0>Release Notes for MPLAB<sup></sup> REAL ICE In-Circuit
Emulator &amp;<br>
Device (Production) Programmer</p>

<p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt'>MPLAB<sup><span
style='font-size:12.0pt'></span></sup> IDE v8.91</p>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><p style='font-size:10.0pt;font-family:Arial;font-weight:bold;'>DLL and Firmware versions:</p><table style='font-size:10.0pt;font-family:Arial;font-weight:normal;' border=0 cellspacing=2 cellpadding=0><tr><td>&nbsp;MPRealICE.dll&nbsp;</td><td>&nbsp;&nbsp;v6.0.8.13</td><td>&nbsp;&nbsp;</td></tr><tr><td>&nbsp;MPLAB REAL ICE Suite (OS, FW)&nbsp;</td><td>&nbsp;&nbsp;v1.28.75</td><td>&nbsp;&nbsp;(RIFW_012875.jam)</td></tr></table></p>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;text-autospace:none'>&nbsp;</p>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;text-autospace:none'>April 30, 2013</p>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt;text-autospace:none'>&nbsp;</p>

<p class=Heading0>Table of Contents</p>

<p class=MsoToc1><a name="_Ref123024713"></a><a
href="#_Toc354648483">1<span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:windowtext;text-decoration:none'> </span>Device Support</a></p>

<p class=MsoToc1><a href="#_Toc354648484">2<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Operating
System Support</a></p>

<p class=MsoToc1><a href="#_Toc354648485">3<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Reference
Documents</a></p>

<p class=MsoToc1><a href="#_Toc354648486">4<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>What's
New in v8.91</a></p>

<p class=MsoToc1><a href="#_Toc354648487">5<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Repairs
and Enhancements Made in v8.91</a></p>

<p class=MsoToc1><a href="#_Toc354648488">6<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>USB
Port Setup</a></p>

<p class=MsoToc1><a href="#_Toc354648489">7<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Powering
the Emulator and Target Board</a></p>

<p class=MsoToc1><a href="#_Toc354648490">8<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Setting
Up the Emulator and Target Board</a></p>

<p class=MsoToc1><a href="#_Toc354648491">9<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Device
Programming Considerations</a></p>

<p class=MsoToc1><a href="#_Toc354648492">10<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Command-Line
Programming</a></p>

<p class=MsoToc1><a href="#_Toc354648493">11<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Known
Problems</a></p>

<p class=MsoToc1><a href="#_Toc354648494">12<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Important
Notes</a></p>

<p class=MsoToc1><a href="#_Toc354648495">13<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Reserved
Resources</a></p>

<p class=MsoToc1><a href="#_Toc354648496">14<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Number
of Hardware Breakpoints per Device</a></p>

<p class=MsoToc1><a href="#_Toc354648497">15<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:windowtext;text-decoration:none'> </span>Durability/Insertion
Life Cycle of the Card Guide</a></p>

<h1>1<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><a
name="_Toc354648483">Device Support</a></h1>

<p class=MsoNormal>Click the link below to see <b>device support</b> for REAL
ICE Debugging (RID) and REAL ICE Programming (RIP).</p>

<p class=MsoListBullet><a href="Device%20Support.htm">Device Support List</a></p>

<p class=MsoNormal>For <b>feature support</b> by device family, see the
emulator on-line help file, Device and Feature Support.</p>

<h2>1.1<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Programming Considerations</h2>

<p class=NormalNoSpace>For PIC24F/H and dsPIC33F devices, see section 9 for special device programming considerations.</p>

<p class=MsoNormal>For PIC16F1xxx devices: </p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>For the LVP configuration bit set to &quot;Low-voltage
programming enabled&quot;, you may program in either high-voltage (default) or
low-voltage (select Programmer&gt;Settings and check the &quot;Enable Low
Voltage Programming&quot; checkbox.)</p>

<p class=MsoNormal style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>For the LVP configuration bit set to &quot;High-voltage on
MCLR/Vpp must be used for programming&quot;, you may only program in
high-voltage.</p>

<h2>1.2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Trace Considerations</h2>

<p class=MsoNormal><b>No</b> Native trace available for these devices:</p>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0
 style='margin-left:15.4pt;border-collapse:collapse'>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC10F/12F/16F</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F (2)</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F (1)</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX (3)</p>
  </td>
 </tr>
</table>

<p class=MsoNormal style='margin-left:15.0pt'>(1) Except for PIC18FXXJXX
devices<br>
(2) Except for dsPIC30F SMPS devices (dsPIC30F1010/2020/2023)<br>
(3) These devices use PIC32 instruction trace, if available (see below)</p>

<p class=MsoNormal><b>No</b> real-time data capture available for these
devices:</p>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0
 style='margin-left:15.4pt;border-collapse:collapse'>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC10F/12F/16F</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F (2)</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F (1)</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
</table>

<p class=MsoNormal style='margin-left:15.0pt'>(1) Except for PIC18FXXJXX
devices<br>
(2) Except for dsPIC30F SMPS devices (dsPIC30F1010/2020/2023)</p>

<p class=MsoNormal><b>No</b> SPI trace is available for these devices:</p>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0
 style='margin-left:15.4pt;border-collapse:collapse'>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F1010</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3010</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F4012</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2010</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3011</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F4013</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2011</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3012</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC33F</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2012</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3013</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC24F/H</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2020</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3014</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2023</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F4011</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
</table>

<p class=MsoNormal><b>No</b> I/O Port trace is available for these devices:</p>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0
 style='margin-left:15.4pt;border-collapse:collapse'>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F1010</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3010</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F5015</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2010</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3011</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F6010</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2011</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3012</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC33F</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2012</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F3013</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC24F/H</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2020</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F4011</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F2023</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F4012</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
</table>

<p class=MsoNormal>The following devices <b>cannot</b> perform data capture,
runtime watches, and Native trace at 40 MIPS, or use trace on Ports C and D:</p>

<p class=NormalNoSpace style='margin-left:15.0pt'>dsPIC33F RevA1 DSCs</p>

<p class=MsoNormal>PIC32 instruction trace <b>is available</b> for these
devices:</p>

<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0
 style='margin-left:15.4pt;border-collapse:collapse'>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX360F256L</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX460F256L</p>
  </td>
 </tr>
 <tr>
  <td width=153 valign=top style='width:115.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX360F512L</p>
  </td>
  <td width=160 valign=top style='width:120.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX460F512L</p>
  </td>
 </tr>
</table>

<h2>1.3<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Debugging Considerations</h2>

<p class=MsoNormal>For low pin-count devices (8 to 28 pins), a <b>Processor
Extension Pak</b> or <b>Header</b> is usually required. See the <i>Processor
Extension Pak and</i> <i>Header Specification</i> (DS51292) or Header help file
(hlpHeader.chm) for a list of available headers by device.</p>

<p class=MsoNormal>For high pin-count devices (40 to 100 pins), a <b>Processor
Extension Pak</b> or <b>Header</b> may be available, but is not required. See
the <i>Processor Extension Pak and</i> <i>Header Specification</i> (DS51292) or
Header help file (hlpHeader.chm) for a list of available headers by device.</p>

<p class=MsoListBullet>For enhanced mid-range devices (PIC12F/16F1xxx), performing
a read during debug may take some time.</p>

<h1><a name="_Toc354648484">2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Operating System Support</a></h1>

<p class=MsoNormal>This tool has been tested using the following operating
systems:</p>

<p class=MsoNormal><b>32-Bit</b>: Windows<sup><span style='font-size:12.0pt'></span></sup>
2000 SP4, Windows XP SP2, Windows Vista and Windows 7 OSs</p>

<p class=MsoNormal><b>64-Bit</b>: Windows XP 64, Windows Vista 64 and Windows 7
64 OSs</p>

<p class=MsoNormal><b>NOTE:</b> <span style='font-family:"Helv","sans-serif";
color:black'>Windows NT</span><sup><span style='font-size:12.0pt'></span></sup><span
style='font-family:"Helv","sans-serif";color:black'> and Windows 98/ME OSs are
NOT supported.</span></p>

<h1><a name="_Toc354648485">3<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Reference Documents</a></h1>

<p class=MsoNormal>The following documents may be found on our website or MPLAB
IDE CD-ROM:</p>

<p class=NormalNoSpace style='margin-left:.5in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>MPLAB REAL ICE In-Circuit Emulator Setup (DS51615)</p>

<p class=NormalNoSpace style='margin-left:.5in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>MPLAB REAL ICE In-Circuit Emulator User's Guide (DS51616)</p>

<p class=NormalNoSpace style='margin-left:.5in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Header Board Specification (DS51292)</p>

<p class=NormalNoSpace style='margin-left:.5in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Transition Socket Specification (DS51194)</p>

<p class=MsoNormal>On-line help (<i><u>Help&gt;Topics</u></i>) is also
available for this tool:</p>

<p class=NormalNoSpace style='margin-left:.5in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Debuggers&gt;MPLAB REAL ICE</p>

<p class=MsoNormal>The default location of the Help file is:</p>

<p class=NormalNoSpace style='margin-left:.5in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>C:\Program Files\Microchip\MPLAB IDE\REAL ICE\hlpMPLABREALICE.chm</p>

<h1><a name="_Toc354648486">4<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>What's New in v8.91</a></h1>

<p class=MsoListBullet>New Device Support.</p>

<h1><a name="_Toc354648487">5<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Repairs and Enhancements Made in v8.91</a></h1>

<p class=MsoNormal>None.</p>

<h1><a name="_Toc354648488">6<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>USB Port Setup</a></h1>

<p class=MsoNormal>Installation and setup instructions are dependent on your
operating system. Open the appropriate file for your OS in a web browser and
follow the instructions to install the driver(s).</p>

<p class=MsoNormal><b>Notes:</b></p>

<p class=MsoListBullet>USB 2.0 is recommended for use with these drivers. USB
1.1 may be used but may result in reduced performance.</p>

<p class=MsoListBullet>If you change emulator units or PC USB ports, you will
need to reinstall the drivers.</p>

<p class=MsoListBullet>If you use a USB hub, it needs to be powered.</p>

<p class=MsoNormal><b>Win 2000/Win XP/Win Vista/Win 7</b></p>

<p class=MsoNormal>Find detailed instructions at:<br>
<span style='font-family:"Courier New"'>C:\Program Files\Microchip\MPLAB
IDE\REAL ICE\Drivers\ddri.htm</span></p>

<p class=MsoNormal>Basic instructions are as follows:</p>

<p class=MsoListNumber>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Install MPLAB IDE v7.43 or higher (for Win 2000/XP/Vista) or v8.40 or
higher (for Win 7).</p>

<p class=MsoListNumber>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Insert a communication board (standard or high-speed) into the MPLAB
REAL ICE pod.</p>

<p class=MsoListNumber>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Connect the MPLAB REAL ICE pod to a PC USB port using a USB cable.</p>

<p class=MsoListNumber>4.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Follow the Found New Hardware Wizard to install the drivers
(software):</p>

<ol style='margin-top:0in' start=1 type=a>
 <li class=MsoNormal>Automatically for Win 2000/XP.</li>
 <li class=MsoNormal>Manually for Win Vista and Win 7. The drivers are located
     in:<br>
     <span style='font-family:"Courier New"'>C:\Program Files\Microchip\MPLAB
     IDE\REAL ICE\Drivers</span></li>
</ol>

<p class=MsoNormal><b>Win XP 64/Win Vista 64/Win 7 64</b></p>

<p class=MsoNormal>Find detailed instructions for Win XP 64 at:<br>
<span style='font-family:"Courier New"'>C:\Program Files (x86)\Microchip\MPLAB
IDE\Drivers64\XP64\ddxp64.htm <br>
</span>or for Win Vista 64:<br>
<span style='font-family:"Courier New"'>C:\Program Files (x86)\Microchip\MPLAB
IDE\Drivers64\Vista64\ddvista64.htm<br>
</span>or for Win 7 64:<br>
<span style='font-family:"Courier New"'>C:\Program Files (x86)\Microchip\MPLAB
IDE\Drivers64\Win7_64\ddwin764.htm</span></p>

<p class=MsoNormal>Basic instructions are as follows:</p>

<p class=MsoListNumber>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Install MPLAB IDE v 8.14 or higher (for Win XP/Vista 64) or v8.43 or
higher (for Win 7 64).</p>

<p class=MsoListNumber>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Insert a communication board (standard or high-speed) into the MPLAB
REAL ICE pod.</p>

<p class=MsoListNumber>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Connect the MPLAB REAL ICE pod to a PC USB port using a USB cable.</p>

<p class=MsoListNumber>4.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Follow the Found New Hardware Wizard to install the drivers (software)
manually. The drivers are located in:<br>
<span style='font-family:"Courier New"'>C:\Program Files (x86)\Microchip\MPLAB
IDE\Drivers64</span></p>

<h1><a name="_Toc354648489">7<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Powering the Emulator and Target Board</a></h1>

<p class=MsoNormal>The MPLAB REAL ICE emulator is powered through its USB
connection to the PC.</p>

<p class=MsoNormal>The target board is powered from its own supply. The
emulator cannot provide power to the target board.</p>

<h1><a name="_Toc354648490">8<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Setting Up the Emulator and Target Board</a></h1>

<p class=MsoListNumber>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Install the USB drivers on your PC, as discussed above (USB Port Setup).
When this is complete, MPLAB REAL ICE emulator should be plugged into a USB
port of the PC.</p>

<p class=MsoListNumber>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>If you have not already done so, connect to a target, either directly or
through a header board. See on-line help or the user's guide for ways to
connect the emulator to a target board.</p>

<p class=MsoListNumber>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Power the target.</p>

<p class=MsoListNumber>4.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Start MPLAB IDE.</p>

<p class=MsoListNumber>5.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>In MPLAB IDE, select either <i><u>Debugger&gt;Select Tool&gt;REAL ICE</u></i>
or <i><u>Programmer&gt;Select Programmer&gt;REAL ICE</u></i>. The emulator will
automatically connect. Also, the emulator can automatically detect if it has
been disconnected/reconnected and if the target has been
disconnected/reconnected.</p>

<p class=MsoListNumber>6.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>The emulator will now be ready for use.</p>

<h1><a name="_Toc354648491"></a><a name="_Ref123024726"></a><a
name="_Ref123024690"></a><a name="_Ref123024677"></a><a name="_Ref123024671"></a><a
name="_Ref123024626">9<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Device Programming Considerations</a></h1>

<h2>9.1<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>CodeGuard Security Devices</h2>

<p class=MsoNormal>Several 16-bit devices allow customers to define up to 3
programming segments: Boot, Secure and General. The purpose is to allow a
customer to place proprietary data (libraries, IP address, etc.) into a
protected boot or secure segment. That customer may then transfer these
preprogrammed devices to another customer who would use the unprotected general
segments.</p>

<p class=MsoNormal>For more details on <a
href="http://www.microchip.com/codeguard">CodeGuard Security</a> functionality,
please refer to the CodeGuard Security reference manual for 16-bit devices
(DS70180) and dsPIC33F/PIC24H and dsPIC30F device programming specifications
found on our website.</p>

<p class=MsoNormal>To program the preprogrammed devices, MPLAB IDE v8.00 and
above provides a Secure Segment tab on the Settings dialog, accessed under
either the Programmer or Debugger menu. This tab contains the following
options:</p>

<p class=MsoListNumber><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Full Chip Erase/Program</p>

<p class=MsoListNumber><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Segment Programming</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Boot, Secure &amp; General Segments</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Secure, General Segments</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>General Segment.</p>

<p class=MsoNormal>The programming function of this tool is now capable of
identifying various device segments and their sizes upon connecting the device.
Hence, these options allow you to selectively program the program memory
segments and thus avoid accidental eraser of preprogrammed proprietary data
(Libraries, IP, etc.)</p>

<h2>9.2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>Non-CodeGuard Security Devices</h2>

<p class=MsoNormal>When programming these devices, bulk erase commands should
be issued between successive programming operations, i.e., erase, then program,
then erase, then program, etc. Therefore, Microchip advises against
multiple-stage programming sessions which may fail to verify. For example, you
should NOT do the following sequence with these devices:</p>

<ol style='margin-top:0in' start=1 type=1>
 <li class=MsoNormal style='margin-top:0in;margin-bottom:0in;margin-bottom:
     .0001pt'>load and program a particular hex file</li>
 <li class=MsoNormal style='margin-top:0in;margin-bottom:0in;margin-bottom:
     .0001pt'>load a second hex file</li>
 <li class=MsoNormal style='margin-top:0in;margin-bottom:0in;margin-bottom:
     .0001pt'>disable erase-all-before-programming</li>
 <li class=MsoNormal style='margin-top:0in;margin-bottom:0in;margin-bottom:
     .0001pt'>specify an address sub-range</li>
 <li class=MsoNormal style='margin-top:0in;margin-bottom:0in;margin-bottom:
     .0001pt'>program the device</li>
</ol>

<h1><a name="_Toc354648492">10<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>Command-Line Programming</a></h1>

<p class=MsoNormal>You may use the emulator as a production programmer
controlled via the command line by using RealICECMD found in the Programmer
Utilities directory of the MPLAB IDE installation directory. The Readme for
this tool is Readme for RealICECMD_ICD3CMD.txt.</p>

<p class=MsoNormal><span style='font-family:"Helv","sans-serif";color:black'>See
also Known Problems for </span>RealICECMD<span style='font-family:"Helv","sans-serif";
color:black'> support.</span></p>

<h1><a name="_Toc354648493">11<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>Known Problems</a></h1>

<p class=MsoNormal>The following is a list of known problems. For information
on <b>common problems</b>, <b>error messages</b> and <b>limitations</b> please
see Troubleshooting in the online help file for the MPLAB REAL ICE emulator
(hlpMPLABREALICE.chm). Bolded prefix represents internal tracking numbers.</p>

<p class=MsoListBullet><a href="#_Communication_Issues">Communication Issues</a></p>

<p class=MsoListBullet><a href="#_General_Issues">General Issues</a></p>

<p class=MsoListBullet><a href="#_Emulator_SSRs">Emulator SSRs</a></p>

<p class=MsoListBullet><a href="#_Other_SSRs">Other SSRs</a></p>

<p class=MsoListBullet><a href="#_Engineering_Technical_Notes">Engineering
Technical Notes (ETNs)</a></p>

<h2><a name="_Communication_Issues"></a>11.1<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>Communication Issues</h2>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Do not connect to more than one MPLAB REAL ICE unit at a time or
attempt to connect two MPLAB IDE sessions to the MPLAB REAL ICE emulator.</p>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>If you do not use the included cables, make sure the cables you
do use are: (1) not longer than 6 inches for standard communications or errors
could result and (2) USB 2.0 compliant if you will be using USB 2.0
communications.</p>

<h2><a name="_General_Issues"></a>11.2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>General Issues</h2>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Using the USB connection on a laptop PC with suspend mode enabled
will lock up the emulator if suspend mode is entered. Unplug the USB cable from
the MPLAB REAL ICE emulator and then plug the cable back in to resume
debugging. You may want to disable suspend mode while using the emulator. From
Control Panel, select &quot;Power Options&quot; and disable suspend mode.</p>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Running a data capture at greater than 16 MIPS may result in a
bad header error. At higher speeds decrease the number of data capture points
or the frequency of the capture. For example create a trigger on a temporary
variable that gets changed ever nth cycle.</p>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Virus protection software can interfere with USB driver
installation. If your development tool is not operational and you have tried
reinstalling the USB drivers, consider disabling your virus protection software
and reinstalling the USB drivers again.</p>

<p class=MsoNormal><b>RI-38:</b> If the target voltage is changed while the
MPLAB REAL ICE emulator is connected, the emulators Vdd may be out of range.</p>

<h3><a name="_PIC12F/16F_Devices"></a><a name="_PIC18F_Devices"></a><a
name="_dsPIC30F/33F_and_PIC24H/F"></a><a name="_PIC32MX_Devices"></a><a
name="_dsPIC33EP/PIC24EP_Devices"></a>11.2.1<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>dsPIC33EP/PIC24EP Devices</h3>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>The breakpoint dialog doesnt accept Auxiliary memory addresses.
The only way to set breakpoints in Aux memory is via double clicking.</p>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>If there is a Software breakpoint on a function call to a
function that is in Auxiliary memory, single stepping over that breakpoint will
not work properly. </p>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Verifying Auxiliary Memory sometimes will proceed even when
verifying Program memory has failed.</p>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>When programming in Debugger mode, a message may come up that
protection bits need to be turned off even though they show as being turned off
in the Configuration Bits window.</p>

<p class=MsoListBullet style='margin-left:.25in;text-indent:-.25in'><span
style='font-family:Symbol'><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>The UART does not freeze when in debug mode for
PIC24EPxxxGU/dsPIC33EPxxxMU devices.</p>

<h2><a name="_Emulator_SSRs"></a>11.3<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>Emulator SSRs 8</h2>

<table class=MsoNormalTable border=1 cellspacing=0 cellpadding=0
 style='border-collapse:collapse;border:none'>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;padding:
  0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>SSR</b></p>
  </td>
  <td width=358 style='width:268.45pt;border:solid windowtext 1.0pt;border-left:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Description</b></p>
  </td>
  <td width=229 style='width:171.6pt;border:solid windowtext 1.0pt;border-left:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Device(s)</b></p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-567</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Flash program memory is not written when a 24 bit flash
  write is performed in the user code when the code is &quot;run&quot; for the
  device dsPIC33EP512MU810.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP512MU810</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-566</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Code cannot run past the first software breakpoint when
  two or more contiguous software breakpoints are set in assembly language
  code.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP64MC502, dsPIC33EP512GM710</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-560</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Run time watch uses a lot of RAM and takes CPU usage to
  100%. Problem is seen with WIN XP system. [MPLAB IDE v8 only].</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18F47J13</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-556</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>For PIC18F97J94 device family MPLAB IDE seems to enable
  only 3 runtime watches when the device has 5 breakpoint/data capture
  resources</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18F97J94 device family</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-552</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Not halting on data breakpoints on the STKPTR register.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18F8720</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-542</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Debugging issue: Program Counter does not reset at Fosc =
  32 kHz but will at higher Fosc frequencies - (frequency-dependent issue).</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18F45K50 44-pin rev A0 using dedicated ICSP channel
  (ICPORT), PIC18F46K22, PIC18F14K22</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-541</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Register 'PCLATU' cannot be cleared to 0x00 (value is
  stuck at 0x20).</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18F45K50</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-533</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Runtime read/update of watch window variables doesn't take
  effect on dsPIC33EP/PIC24EP devices.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP, PIC24EP</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-527</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>The option to program the Auxiliary memory is missing from
  the command line utilities.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP/PIC24EP devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-526</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>High speed (~40 MIPS) runtime watch seems to cause data
  corruption.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33FJ245GP710A</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-524</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Cannot preserve Auxiliary memory on dsPIC33EP and PIC24EP
  devices</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP and PIC24EP devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-517</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>When using Data Capture on a PIC32, an incorrect symbol
  (_persist_begin) appears in the variable list. In general, the first
  initialized global variable will be replaced.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>All PIC32MX devices that support data capture such as the
  PIC32MX795F512L</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-506</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>The error &quot;NMMR register read failed
  (RIErr0018)&quot; is occasionally seen on dsPIC33EP and PIC32 parts when
  using the emulator as a debugger. </p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC32MX, dsPIC33EP</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-503</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>For PIC18F devices, Trace and Log macros within tight
  loops do not work when using IO PORT Trace. The workaround is to use NOP
  instructions within the loop.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18F devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-489</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Runtime Watch &amp; Data Capture have a silicon errata
  limitation which prevents these features from working up to the maximum Fosc
  frequency of 32 MHz for Enhanced Midrange devices.</p>
  <p class=MsoNormal>Work-around: In order to ensure reliable Runtime Watch
  &amp; Data Capture operation it is recommended to keep the maximum Fosc at or
  below 3 MHz during the debugging phase of product development.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC16F1xxx devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-481</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Runtime watch does not work for arrays defined in a struct
  for PIC32MX devices.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC32MX devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-476</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Add Breakpoint Dialog box does not accept Auxiliary memory
  addresses.</p>
  <p class=MsoNormal>Work-around: One can go into the program memory window and
  set the breakpoint. </p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP512MU810 family</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-475</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>[MPLAB 8 only] Watch window variable address may change
  momentarily on single step using dsPIC33FJ16GP102 family devices.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33FJ16GP102 and others devices in the family</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-464</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Occasionally receiving the &quot;RIErr0028: The MPLAB REAL
  ICE is missing its Device Database&quot;. </p>
  <p class=MsoNormal>Work-around: Perform a manual update of the firmware. See
  emulator help in the IDE for further solutions.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-449</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Step-over will cause code to run if the statement
  following the step-over is part of a sequenced breakpoint. Stepping over a
  function works by setting a breakpoint right after the function and issuing a
  Run. However if the next statement has a breakpoint already, the IDE will not
  set a breakpoint assuming that the existing breakpoint will suffice. But if
  that existing breakpoint is part of a sequence, MPLAB IDE will still not
  issue a breakpoint even though that execution isn't guaranteed to stop at the
  following statement (since the whole sequence has to be followed first before
  the program halts).</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33FJ256GP710, dsPIC33EP512MU814, probably other devices
  that supports sequenced breakpoints</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-409</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>MPLAB IDE v8.xx - For PIC32 devices, single stepping
  becomes very slow and apparently code runs if single stepping is started from
  within the middle of the assembly instructions required to do a variable update.
  These instructions are:</p>
  <p class=MsoNormal>lw<br>
  addiu<br>
  sw<br>
  beq</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC32MX devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-391</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Performing Build All will disable runtime watch for some
  of the array elements. This happens when array elements manually enabled for
  run time watch.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC32MX devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-354</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Using REAL ICE as a debugger for the PIC18F46J50 (or
  PIC18F46J11), the SPI Trace is not functioning as expected.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18F46J50 &amp; PIC18F46J11, possibly others.</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-350</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>[PIC32 REAL ICE Trace] Instructions in the trace window
  have incorrect addresses when compared with the actual memory contents for
  PIC32 devices in some cases.</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC32MX devices</p>
  </td>
 </tr>
 <tr>
  <td width=100 style='width:74.75pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RI-348</p>
  </td>
  <td width=358 style='width:268.45pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>[PIC32 Trace] PIC32 instruction trace does not match disassembly
  when instruction in branch delay slot is other than NOP</p>
  </td>
  <td width=229 style='width:171.6pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC32MX family</p>
  </td>
 </tr>
</table>

<h2><a name="_Engineering_Technical_Notes"></a><a name="_Other_SSRs"></a>11.4<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span>Other SSRs</h2>

<table class=MsoNormalTable border=1 cellspacing=0 cellpadding=0
 style='border-collapse:collapse;border:none'>
 <tr>
  <td width=79 style='width:59.4pt;border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>SSR</b></p>
  </td>
  <td width=414 style='width:310.5pt;border:solid windowtext 1.0pt;border-left:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Description</b></p>
  </td>
  <td width=193 style='width:144.9pt;border:solid windowtext 1.0pt;border-left:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal><b>Device(s)</b></p>
  </td>
 </tr>
 <tr>
  <td width=79 style='width:59.4pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>ICD3-335</p>
  </td>
  <td width=414 style='width:310.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>Software breakpoints do not work on the PIC16(L)F1459
  family of devices. This is a silicon issue.</p>
  </td>
  <td width=193 style='width:144.9pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC16(L)F1459 family</p>
  </td>
 </tr>
 <tr>
  <td width=79 style='width:59.4pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>ICD3-301</p>
  </td>
  <td width=414 style='width:310.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>MPLAB IDE passes the incorrect DEBUG symbols for reserving
  RAM to MPLINK linker when using REALICE as a debugger with PIC18F8722.</p>
  </td>
  <td width=193 style='width:144.9pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC18 MCUs</p>
  </td>
 </tr>
 <tr>
  <td width=79 style='width:59.4pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>ICD3-243</p>
  </td>
  <td width=414 style='width:310.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>RealICECMD, ICD3CMD and PK3CMD do not always work for
  64-bit Operating Systems. You might see failures connecting to the device
  when switching firmware using the command line utility. The workaround is to
  try to connect to the device, switch the firmware using MPLAB IDE and then
  use the command line utility to connect to the device.</p>
  </td>
  <td width=193 style='width:144.9pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=79 style='width:59.4pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>ICD2-81</p>
  </td>
  <td width=414 style='width:310.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>For PIC24F devices during a programming/verify operation
  (or subsequent verification operation) of user code that performs self-writes
  and/or self-erases to program space, a verify sequence may fail if the code
  execution occurs within the first execution cycles following reset.</p>
  <p class=MsoNormal>Workaround:</p>
  <p class=MsoNormal>Place a delay in your code before the code section that
  performs the self-write and/or self-erase. The specific delay value may need
  to be adjusted, but 100 ms would be a conservative value to start out with.
  Here is a C language example that illustrates the workaround:</p>
  <p class=Computer>int main (void)</p>
  <p class=Computer>{</p>
  <p class=Computer> // Place 100 ms delay here before any
  self-write/self-erase code</p>
  <p class=Computer> : : :</p>
  <p class=Computer>}</p>
  </td>
  <td width=193 style='width:144.9pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>PIC24F devices</p>
  </td>
 </tr>
 <tr>
  <td width=79 style='width:59.4pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>SPI001-113</p>
  </td>
  <td width=414 style='width:310.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>SPI misses SDI input when single stepping with freeze in
  debug enabled.</p>
  </td>
  <td width=193 style='width:144.9pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP/PIC24EP</p>
  </td>
 </tr>
 <tr>
  <td width=79 style='width:59.4pt;border:solid windowtext 1.0pt;border-top:
  none;padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>TBAA0-199</p>
  </td>
  <td width=414 style='width:310.5pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>When reading a device with a programmer, code or write
  protection applied to either the General or Auxiliary Segment is being
  applied to both; therefore all flash memory will read back as zero. Only
  devices with no code or write protection applied can be successfully read
  using a programmer. This limitation applies to revision B1 (0x4002) of the following
  devices:</p>
  <p class=ListBulletNoSpace>PIC24EP512GU814</p>
  <p class=ListBulletNoSpace>PIC24EP512GU810</p>
  <p class=ListBulletNoSpace>PIC24EP256GU814</p>
  <p class=ListBulletNoSpace>PIC24EP256GU810</p>
  <p class=ListBulletNoSpace>dsPIC33EP512MU814</p>
  <p class=ListBulletNoSpace>dsPIC33EP512MU810</p>
  <p class=ListBulletNoSpace>dsPIC33EP256MU814</p>
  <p class=ListBulletNoSpace>dsPIC33EP256MU810</p>
  <p class=ListBulletNoSpace>dsPIC33EP256MU806</p>
  <p class=ListBulletNoSpace>PIC24EP512GP806 </p>
  <p class=ListBulletNoSpace>dsPIC33EP512GP806</p>
  <p class=ListBulletNoSpace>dsPIC33EP512MC806</p>
  </td>
  <td width=193 style='width:144.9pt;border-top:none;border-left:none;
  border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=MsoNormal>dsPIC33EP/PIC24EP</p>
  </td>
 </tr>
</table>

<h2>11.5<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span>Engineering
Technical Notes (ETNs)</h2>

<p class=MsoNormal>The following ETNs are related to the MPLAB REAL ICE
in-circuit emulator. Please see the product webpage for details.</p>

<p class=MsoListBullet><b>ETN-30</b>: Applies to Assembly #10-00401-R1 or below.</p>

<h1><a name="_Toc354648494">12<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>Important Notes</a></h1>

<p class=MsoListBullet>When using real-time data capture trigger or Capture
trace, standard communication can only provide a data rate of 15 MIPS. For
speeds up to 40 MIPS, high-speed communication will be required, via the
Performance Pak.</p>

<p class=MsoListBullet>When using I/O Port trace, make sure multiplexed device
port pins are set as I/O pins.</p>

<p class=MsoListBullet>When adding/removing Capture or I/O Port trace points, you must rebuild the project (Build All) and reprogram the device. When
switching the Build Configuration (Debug/Release), you must rebuild the project
and reprogram the device.</p>

<p class=MsoListBullet>When running in debug mode, selecting <i><u>Debugger&gt;Reset</u></i>
resets the program, goes to the zero location, and halts. The program does not
automatically re-run.</p>

<p class=MsoListBullet>If porting an existing project using MPLAB ICD 2 to the
MPLAB REAL ICE emulator, you must do the following:</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Select <i><u>Project&gt;Build Options&gt;Project</u></i>. When
the dialog opens, click <b>OK</b>. This is necessary to save new Build Options
in the project. Previously there had been a checkbox option for &quot;Link for
ICD2&quot; on the <b>MPLAB LINK30</b> tab. This is now gone and has been
replaced by a Build Configurations selection (see below.)</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>On the Project Manager toolbar select &quot;Debug&quot; from the
Build Configurations drop-down list, or from the Project menu select Build
Configurations and then Debug.</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Rebuild the project (Build All).</p>

<p class=MsoListBullet>Make sure that table reads/writes are not code
protected.</p>

<p class=MsoListBullet>At low Vdd, bulk erase will not erase code protect bits.</p>

<h2>12.1<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span>PIC18
Devices</h2>

<p class=MsoListBullet>Before setting the Stopwatch between any 2 Software
breakpoints, ensure that the total number of Hardware breakpoints being used is
always 2 less than the Maximum number of Hardware breakpoints available for the
device.</p>

<h2>12.2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span>16-Bit
Devices</h2>

<p class=MsoListNumber>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>RB0 and RB1 pins:<br>
If the MPLAB REAL ICE emulator is selected as a debugger, it initializes all
the A/D input pins - AN0 (RB0) through AN15 (RB15) pins - as
&quot;digital&quot; pins, by setting all 16 bits in the ADPCFG register.</p>

<ol style='margin-top:0in' start=1 type=a>
 <li class=MsoNormal>If you have selected a pair of &quot;debug pins&quot;
     (EMUD/EMUC, EMUD1/EMUC1, EMUD2/EMUC2 or EMUD3/EMUC3) that are multiplexed
     with A/D input pin functions on the particular dsPIC30f device being used,
     then you must never clear the bits in the ADPCFG register that correspond
     to those A/D pins. </li>
</ol>

<p class=MsoNormal style='margin-left:.5in'>For example, if EMUD3 and EMUC3 are
used as the debug pins on a dsPIC30F2010 device, then bits 0 and 1 of the
ADPCFG register must remain set at all times. Similarly, if EMUD and EMUC are
used as the debug pins on a dsPIC30F5011 device, then bits 6 and 7 of the
ADPCFG register must remain set at all times. In such cases, you must also take
proper precaution to isolate the application circuitry from the corresponding
A/D pins during debugging.</p>

<ol style='margin-top:0in' start=2 type=a>
 <li class=MsoNormal>If your application needs to use certain A/D pins as
     analog input pins, then your code must clear the corresponding bits in the
     ADPCFG register during A/D module initialization.</li>
</ol>

<p class=MsoNormal style='margin-left:.5in'>For example, if AN4 and AN5 are
required as analog input pins, then bits 4 and 5 of the ADPCFG register must be
cleared.</p>

<p class=MsoListNumber>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>SLEEP, IDLE, WDT, Clock Switching:<br>
For dsPIC devices, debug operations can be executed on programs which use SLEEP
or IDLE mode, Watchdog Timer, and/or Clock Switching. </p>

<p class=MsoListNumber>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Debug during SLEEP or IDLE Mode:<br>
When the device is in SLEEP and IDLE mode and a Halt command is issued, the
MPLAB REAL ICE emulator will wake up the device and halt execution on the
instruction immediately following the PWRSAV instruction.</p>

<p class=MsoListNumber>4.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Interrupts:</p>

<ol style='margin-top:0in' start=1 type=a>
 <li class=MsoNormal>In general, single-stepping an instruction will not
     generate an interrupt or trap, because the corresponding interrupt/trap
     status flag bit would not get set. Essentially, the interrupt or trap
     condition would be ignored.</li>
 <li class=MsoNormal>However, if the user has explicitly set an interrupt/trap
     flag bit, either in the user program or by modifying the status flag
     values in the MPLAB Watch, SFR or File Registers window, then the
     interrupt/trap would get generated, and the user would be able to
     single-step into the Interrupt or Trap Service Routine.</li>
</ol>

<p class=MsoListNumber>5.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Break Point Behavior:<br>
If a break point is set on an instruction that follows a taken branch, the
Breakpoint will be triggered even though the branch went elsewhere.</p>

<p class=MsoListNumber>6.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>Break Point Behavior and Skidding:<br>
It is possible that a breakpoint halt will exhibit program memory skidding in
that the execution stops N instructions after reaching the breakpoint. The
following definitions are provided and referred to:</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>One skid - A breakpoint occurs AFTER the instructions is
executed (PC+2)</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Two skid - A break point occurs AFTER the NEXT instruction
(PC+4) </p>

<p class=MsoNormal style='margin-left:.25in'>Break Point Behavior:</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>If a Non-Program-Flow, modifying, Single-Word, Two-Cycle
instruction (such as Table or PSV) precedes a break point instruction, then the
breakpoint occurs BEFORE the instruction at the breakpoint address is executed
(ONE SKID).</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>All other instructions have a &quot;TWO SKID&quot;, which means
the break occurs AFTER the NEXT instruction is executed.</p>

<p class=MsoListNumber>7.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>The CAN module, unlike the other peripherals, does not get frozen in the
following situations:</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>during a Halt </p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>during a stop on a Breakpoint</p>

<p class=ListBullet2NoSpace><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>after a Single-Step </p>

<p class=MsoNormal style='margin-left:.25in'>For example, if you set a
Breakpoint and run to it, the CAN module continues to run in the background,
and it may seem that data transmissions and receptions have completed
immediately.</p>

<p class=MsoListNumber>8.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>DISICNT register:<br>
In five dsPIC30F devices (dsPIC30F6010, dsPIC30F6011, dsPIC30F6012,
dsPIC30F6013 and dsPIC30F6014), since the DISICNT register continues to
decrement even when the device is halted by the debugger, the DISICNT value
will always be seen as 0x0000 in the Watch, SFR and File Registers windows. To
monitor the DISICNT value, add code to copy the DISICNT register contents to a
W register or memory location and monitor the value of the corresponding W
register or memory location in the Watch, SFR or File Registers window.</p>

<p class=MsoListNumber>9.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;
</span>ADCMD bit in PMD1 register:<br>
The user application must not set the ADCMD bit (bit 0 of PMD1 register). This
would lead to incorrect ICE operation.</p>

<p class=MsoListNumber>10.<span style='font:7.0pt "Times New Roman"'>&nbsp; </span>SPLIM
register:<br>
When using the MPLAB REAL ICE emulator as a Debugger, your software must
initialize the Stack Pointer Limit register (SPLIM) before using the stack
(device errata).</p>

<p class=MsoListNumber>11.<span style='font:7.0pt "Times New Roman"'>&nbsp; </span>Single-stepping
a DO loop:<br>
In five dsPIC30F devices (dsPIC30F6010, dsPIC30F6011, dsPIC30F6012,
dsPIC30F6013 and dsPIC30F6014), single-stepping through a DO loop in dsPIC30F
assembly code results in the loop getting executed one less time than expected.</p>

<p class=MsoListNumber>12.<span style='font:7.0pt "Times New Roman"'>&nbsp; </span>Pass
Counter feature in Advanced Breakpoints:<br>
For a specified Pass count of 'N', the code will break after 'N+1' occurrences
of the breakpoint instead of 'N' occurrences.</p>

<p class=MsoListNumber>13.<span style='font:7.0pt "Times New Roman"'>&nbsp; </span>If
you need to use the Fail-Safe Clock Monitor feature on a dsPIC device when
using the MPLAB REAL ICE emulator for debugging your application, a Watchdog
Timer Device Reset will occur, even if the Watchdog Timer has not been
explicitly enabled in the application. To work around this issue, use the
&quot;CLRWDT&quot; instruction in the main loop of your application code. This
will ensure that the Watchdog Timer gets cleared before it causes the device to
reset.</p>

<h2>12.3<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span>32-Bit
Devices</h2>

<p class=MsoListBullet>Instruction Trace: When using the trace functionality
ensure TROEN bit on DDPCON register is not modified in your code. Refer to the
data sheet for more information.</p>

<h1><a name="_Toc354648495">13<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>Reserved Resources</a></h1>

<p class=MsoNormal>Due to the built-in in-circuit debugging capability of ICE
devices, and the ICSP function offered by the emulator, the MPLAB REAL ICE in-circuit
emulator uses on-chip resources when debugging, i.e., some device resources are
reserved for use by the emulator.</p>

<p class=MsoNormal>Refer to the on-line help for the most up-to-date list of
resources used by the emulator.</p>

<h1><a name="_Toc354648496"></a><a name="_Number_of_Hardware_Breakpoints Per "></a>14<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp; </span>Number of Hardware
Breakpoints per Device</h1>

<p class=MsoNormal>To see the number of breakpoints supported for your device
and the number of breakpoints used in your project, use the <b>Device Debug
Resource</b> toolbar. For more on this toolbar, see MPLAB IDE on-line help.</p>

<p class=MsoNormal>Breakpoint support per device is as follows:</p>

<table class=MsoNormalTable border=1 cellspacing=0 cellpadding=0
 style='margin-left:5.4pt;border-collapse:collapse;border:none'>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:solid black 1.5pt;
  border-left:none;border-bottom:solid black 1.5pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace><b><i>Devices</i></b></p>
  </td>
  <td width=264 valign=top style='width:2.75in;border-top:solid black 1.5pt;
  border-left:none;border-bottom:solid black 1.5pt;border-right:none;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace><b><i>Number of Hardware Breakpoints</i></b></p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border-top:solid black 1.5pt;
  border-left:none;border-bottom:solid black 1.5pt;border-right:none;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace><b><i>Notes</i></b></p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC12F/16F</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>1</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC16F1xxx enhanced</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>1 to 3</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>(1)</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>1</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F enhanced</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>3</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18FxxJ</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>3 or 5</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>(2)</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC30F</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>2</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC33F/PIC24H/F</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>4</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>dsPIC33EP/PIC24EP</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>2</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
 <tr>
  <td width=168 valign=top style='width:1.75in;border-top:none;border-left:
  none;border-bottom:solid black 1.5pt;border-right:solid black 1.0pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC32MX</p>
  </td>
  <td width=264 valign=top style='width:2.75in;border:none;border-bottom:solid black 1.5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>6</p>
  </td>
  <td width=115 valign=top style='width:86.0pt;border:none;border-bottom:solid black 1.5pt;
  padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>&nbsp;</p>
  </td>
 </tr>
</table>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in'>Note 1: Refer to
the Development Tools Selector (DTS) on microchip.com to select your device and
determine the number of available breakpoints for the device and its related
processor extension pak or debug header.</p>

<p class=MsoNormal style='margin-left:.5in;text-indent:-.5in'>Note 2: There is
a limitation for these devices that only 1 data capture is available.</p>

<h1><a name="_Toc354648497">15<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;
</span>Durability/Insertion Life Cycle of the Card Guide</a></h1>

<p class=MsoNormal>The card guide is the part of the emulator pod where the
communications board (either standard or high-speed) is inserted into the pod.</p>

<p class=NormalNoSpace align=center style='text-align:center'><b>SAMTEC</b></p>

<p class=NormalNoSpace align=center style='text-align:center'><b>Durability
Summary Report</b></p>

<p class=NormalNoSpace align=center style='text-align:center'><b>PART
DESCRIPTION</b></p>

<p class=NormalNoSpace align=center style='text-align:center'><b>MB1-130-01-S-S-02-A1-N</b></p>

<p class=NormalNoSpace align=center style='text-align:center'><b>&amp;</b></p>

<p class=NormalNoSpace align=center style='text-align:center'><b>MB1-130-01-H-S-02-A1-N</b></p>

<p class=NormalNoSpace align=center style='text-align:center'><b>(The -H 50u
thick Au Plating is currently non-standard.)</b></p>

<p class=MsoNormal>&nbsp;</p>

<p class=MsoNormal><b>SCOPE: </b>To perform the following tests: Durability up
to 10,000 cycles. </p>

<p class=MsoNormal>For the complete report, see:</p>

<p class=MsoNormal><a
href="http://www.samtec.com/technical_specifications/test.asp?series=MB1&amp;menu=STANDARD_PRODUCTS">http://www.samtec.com/technical_specifications/test.asp?series=MB1&amp;menu=STANDARD_PRODUCTS</a></p>

</div>

</body>

</html>
