<html>

<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=Generator content="Microsoft Word 11 (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:"MS Shell Dlg";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"NKMNCA+TimesNewRoman\,Bold";}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* 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;}
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;
	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;
	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:13.0pt;
	font-family:Arial;
	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:14.0pt;
	font-family:"Times New Roman";
	font-weight:bold;}
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;
	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";
	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";}
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";
	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;}
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;}
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;}
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;}
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;}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:5.0pt;
	margin-left:.25in;
	text-indent:-.25in;
	font-size:10.0pt;
	font-family:Arial;}
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;}
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;}
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;}
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;}
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;}
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;}
p.Heading0, li.Heading0, div.Heading0
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:14.0pt;
	font-family:Arial;
	font-weight:bold;}
p.Computer, li.Computer, div.Computer
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.NormalNoSpace, li.NormalNoSpace, div.NormalNoSpace
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Arial;}
p.DeviceList, li.DeviceList, div.DeviceList
	{margin-top:2.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Arial;}
p.Default, li.Default, div.Default
	{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
	{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;}
p.ListBulletNoSpace, li.ListBulletNoSpace, div.ListBulletNoSpace
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Arial;}
span.ComputerChar
	{font-family:"Courier New";}
@page Section1
	{size:8.5in 11.0in;
	margin:.75in .75in .75in .75in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

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

<div class=Section1>

<p class=Heading0>Release Notes for MPLAB<sup></sup> REAL ICE In-Circuit
Emulator</p>

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

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>MPLAB REAL ICE DLL
v6.01</p>

<p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'>MPLAB REAL ICE
Suite (OS, FW) v1.23</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'>March
25, 2009</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="#_Toc225678218">1<span style='font-size:12.0pt;font-family:"Times New Roman";
color:windowtext;text-decoration:none'> </span>Device Support</a></p>

<p class=MsoToc1><a href="#_Toc225678219">2<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Operating
System Support</a></p>

<p class=MsoToc1><a href="#_Toc225678220">3<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Reference
Documents</a></p>

<p class=MsoToc1><a href="#_Toc225678221">4<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>What's
New in v8.30</a></p>

<p class=MsoToc1><a href="#_Toc225678222">5<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Repairs
and Enhancements Made in v8.30</a></p>

<p class=MsoToc1><a href="#_Toc225678223">6<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>USB
Port Setup</a></p>

<p class=MsoToc1><a href="#_Toc225678224">7<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Powering
the Emulator and Target Board</a></p>

<p class=MsoToc1><a href="#_Toc225678225">8<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Setting
Up the Emulator and Target Board</a></p>

<p class=MsoToc1><a href="#_Toc225678226">9<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Device
Programming Considerations</a></p>

<p class=MsoToc1><a href="#_Toc225678227">10<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Known
Problems</a></p>

<p class=MsoToc1><a href="#_Toc225678228">11<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Important
Notes</a></p>

<p class=MsoToc1><a href="#_Toc225678229">12<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Reserved
Resources</a></p>

<p class=MsoToc1><a href="#_Toc225678230">13<span style='font-size:12.0pt;
font-family:"Times New Roman";color:windowtext;text-decoration:none'> </span>Number
of Hardware Breakpoints Per Device</a></p>

<p class=MsoToc1><a href="#_Toc225678231">14<span style='font-size:12.0pt;
font-family:"Times New Roman";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;&nbsp;&nbsp;&nbsp;
</span><a name="_Toc225678218">Device Support</a></h1>

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

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><a href="Device%20Support.htm">Device Support List</a></p>

<p class=MsoNormal>For device family feature support, 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;&nbsp;&nbsp;
</span>Programming Considerations</h2>

<p class=NormalNoSpace>See section 8 for special device programming considerations
to avoid damage these devices:</p>

<table class=MsoTableGrid 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>PIC24F/H </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>
</table>

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

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

<table class=MsoTableGrid 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=MsoTableGrid 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=MsoTableGrid 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=MsoTableGrid 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=MsoTableGrid 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;&nbsp;&nbsp;
</span>Debugging Considerations</h2>

<p class=MsoNormal>For low pin-count devices (8 to 28 pins), a <b>Header board</b>
is usually required. See the <i>Header Board 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>Header
board</b> may be available, but is not required. See the <i>Header Board Specification</i>
(DS51292) or Header help file (hlpHeader.chm) for a list of available headers
by device.</p>

<h1><a name="_Toc225678219">2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&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>Windows<sup><span style='font-size:12.0pt'></span></sup>
2000 SP4, Windows XP SP2, and Windows Vista OSs</p>

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

<h1><a name="_Toc225678220">3<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&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="_Toc225678221">4<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span>What's New in v8.30</a></h1>

<p class=MsoNormal>New device support.</p>

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

<p class=MsoNormal><b>Peripherals not starting after a halt</b>  A firmware
issue was found where certain peripherals were not restarting after a halt had
occurred during a debug session. This affected 16-bit devices (PIC24 MCUs/dsPIC
DSCs).</p>

<p class=MsoNormal><b>Intermittent programming for PIC24FGA/GB devices</b>  A
firmware issue was corrected where some members of the PIC24FGA/GB families
were reporting programming failures.</p>

<p class=MsoNormal><b>Programming failure when Software Breakpoints enabled</b>
 A programming problem has been found when Software Breakpoints are enabled
and the device is programmed. This happens on PIC18F MCUs, except for PIC18FxxJ
devices. The failure signature is the Debug Executive will fail to program.</p>

<p class=MsoNormal><b>RI-141:</b> Help file shows the wrong locations for File
Registers Used for the PIC18F83J11 Family.</p>

<p class=MsoNormal><b>RI-150:</b> Verify occasionally fails for REAL ICE as programmer
with PIC18F6628.</p>

<p class=MsoNormal><b>RI-206:</b> On PIC18F4620, SPI Trace after a Reset gives
'RIErr0051 Unrecognized trace data format received.' Early versions of this
device have a silicon issue with SPI. Please check the errata.</p>

<p class=MsoNormal><b>RI-266:</b> Emulator as a debugger fails to program a
PIC24HJ256GP610 reporting RIErr0009: Failed while reading configuration memory
with a second message that a memory object is missing.</p>

<p class=MsoNormal><b>RI-298:</b> After debugging with REAL ICE on a
PIC18F4320, attempting to use REAL ICE as a programmer resulted in blank check
failures and mismatched IDs.</p>

<p class=MsoNormal><b>RI-304:</b> Using the option, 'Run after successful
program', with REAL ICE and a PIC18F device results in the debugger running but
no halt button available. The work around on the REAL ICE is to click on the
Reset button on the REAL ICE which will halt the debugger.</p>

<p class=MsoNormal><b>RI-355:</b> Using tab to progress through the REAL ICE
Settings Program Memory tab is not quite as expected.</p>

<p class=MsoNormal><b>RI-357:</b> Using MPLAB REAL ICE emulator as a debugger
for a PIC24FJ128GA010 PIM on the Explorer 16 board with its demo code, if the
user selects Halt and then Run, the RTCC stops but does not restart.</p>

<p class=MsoNormal><b>RI-359:</b> Write to IO remapping control registers do
not change the content of the register for dsPIC33FJ16GS502.</p>

<p class=MsoNormal><b>RI-360:</b> Programming failed when software break point
is enabled for devices such as PIC18F8722/6722 or PIC18F4620.</p>

<h1><a name="_Toc225678223">6<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></a>USB Port Setup</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>

<ul style='margin-top:0in' type=disc>
 <li class=MsoNormal>USB 2.0 is recommended for use with these drivers. USB 1.1
     may be used but may result in reduced performance.</li>
 <li class=MsoNormal>If you change emulator units or PC USB ports, you will
     need to reinstall the drivers.</li>
 <li class=MsoNormal>If you use a USB hub, it needs to be powered.</li>
</ul>

<p class=MsoNormal><b>Win 2000/XP</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>

<ol style='margin-top:0in' start=1 type=1>
 <li class=MsoNormal>Install MPLAB IDE v7.43 or higher.</li>
 <li class=MsoNormal>Insert a communication board (standard or high-speed) into
     the MPLAB REAL ICE pod.</li>
 <li class=MsoNormal>Connect the MPLAB REAL ICE pod to a PC USB port using a
     USB cable.</li>
 <li class=MsoNormal>Follow the Found New Hardware Wizard to install the
     drivers (software) automatically.</li>
</ol>

<p class=MsoNormal><b>Win XP 64/Vista/Vista 64</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<br>
</span>or for Win XP 64 only:<br>
<span style='font-family:"Courier New"'>C:\Program Files\Microchip\MPLAB IDE\VistaXP64\ddxp64.htm</span></p>

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

<ol style='margin-top:0in' start=1 type=1>
 <li class=MsoNormal>Install MPLAB IDE v7.43 or higher for Win Vista or 8.14 or
     higher for Win XP/Vista 64.</li>
 <li class=MsoNormal>Insert a communication board (standard or high-speed) into
     the MPLAB REAL ICE pod.</li>
 <li class=MsoNormal>Connect the MPLAB REAL ICE pod to a PC USB port using a
     USB cable.</li>
 <li class=MsoNormal>Follow the Found New Hardware Wizard to install the
     drivers (software) manually.<br>
     <span style='color:#FF6600'>32-bit drivers:</span> <span style='font-family:
     "Courier New"'>C:\Program Files\Microchip\MPLAB IDE\REAL ICE\Drivers</span><br>
     <span style='color:#FF6600'>64-bit drivers:</span> <span style='font-family:
     "Courier New"'>C:\Program Files\Microchip\MPLAB IDE\VistaXP64</span></li>
</ol>

<h1><a name="_Toc225678224">7<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&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="_Toc225678225">8<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&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;&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;&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;&nbsp;&nbsp;
</span>Power the target.</p>

<p class=MsoListNumber>4.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&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;&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;&nbsp;&nbsp;
</span>The emulator will now be ready for use.</p>

<h1><a name="_Toc225678226"></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;&nbsp;&nbsp;&nbsp;
</span>Device Programming Considerations</a></h1>

<p class=MsoNormal><u>For CodeGuard Security Devices</u></p>

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

<p class=MsoNormal><u>For Non-CodeGuard Security Devices</u></p>

<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="_Toc225678227">10<span style='font:7.0pt "Times New Roman"'>&nbsp;&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>

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

<p class=MsoListBullet><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><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>10.2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span>General
Issues</h2>

<p class=MsoListBullet><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><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=MsoNormal><b>SSR 29271:</b> Sometimes the source code is not being
updated with the id values from the <a name="OLE_LINK2"></a><a name="OLE_LINK1">__</a>LOG
and/or __TRACE. The work-around is to close and reopen the source file.</p>

<p class=MsoNormal><b>ICD3-55:</b> Above 16MHz, in EC mode, a Reset executes
the first few instructions instead of only 1 instruction. Workaround is to add
3 NOPs at the reset vector.</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>

<p class=MsoNormal><b>RI-291:</b> With the option to Program after a Successful
Build selected, if the user selects Run (which is active) while the device is
being programmed, the IDE hangs.</p>

<h3>10.2.1<span style='font:7.0pt "Times New Roman"'> </span>PIC16F Devices</h3>

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Freeze Peripherals for PIC16F devices are not supported at this
time.</p>

<p class=MsoNormal><b>RI-332:</b> PIC16F616-ICD header (part #AC162083) does
not debug user code somewhere above 11 MHz in 'EC' oscillator mode. The
following devices are supported by this header: PIC12F609, PIC12F615,
PIC16F610, PIC16F616, PIC12HV609, PIC12HV615, PIC16HV610, and PIC16HV616 (These
devices do not have debug capability by themselves, so the header must be used
to debug user code.)</p>

<h3>10.2.2<span style='font:7.0pt "Times New Roman"'> </span>PIC18F Devices</h3>

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Watch window  It will take 1 cycle for the watch window to
update properly for PORTx registers. Use an instruction that reads the port
such as MOVFF PORTx, PORTx_copy before the breakpoint is reached. This
affects the following devices:</p>

<table class=MsoTableGrid border=0 cellspacing=0 cellpadding=0
 style='margin-left:25.4pt;border-collapse:collapse'>
 <tr>
  <td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F4620</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F84J90</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F65J11</p>
  </td>
 </tr>
 <tr>
  <td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F63J90</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F84J95</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F83J11</p>
  </td>
 </tr>
 <tr>
  <td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F64J90</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F85J90</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F84J11</p>
  </td>
 </tr>
 <tr>
  <td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F64J95</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F63J11</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F84J16</p>
  </td>
 </tr>
 <tr>
  <td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F65J95</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F64J11</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F85J11</p>
  </td>
 </tr>
 <tr>
  <td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F83J90</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F64J16</p>
  </td>
  <td width=127 valign=top style='width:95.0pt;padding:0in 5.4pt 0in 5.4pt'>
  <p class=NormalNoSpace>PIC18F8722</p>
  </td>
 </tr>
</table>

<p class=MsoListBullet><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 PIC18F14K22 family, MPLAB IDE debug/programming tools
will not work below 1.9v. The work-around is to run the device above 1.9v.</p>

<p class=MsoNormal><b>RI-354:</b> Using REAL ICE as a debugger for the
PIC18F46J50 (or PIC18F46J11) the SPI Trace is not functioning as expected.</p>

<p class=MsoNormal><b>RI-371:</b> Programming fails on PIC18F13K50/18F14K50
with SW breakpoints enabled.</p>

<p class=MsoNormal><b>RI-373:</b> Unable to use data capture/real time watch
for more than one SFR in the watch window even when the device has 3 HW
breakpoints for the PIC18F46J50 family of devices.</p>

<h3>10.2.3<span style='font:7.0pt "Times New Roman"'> </span>PIC24F/H Devices</h3>

<p class=MsoNormal><b>SSR 29399:</b> PIC24F devices can start to run after
programming but before verification. This can result in a verification failure
if the code performs self-write to either program memory or Data EE.</p>

<p class=MsoNormal><b>ICD2-81:</b> 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>

<p class=MsoNormal><b>RI-266:</b> REAL ICE as a debugger fails to program a
PIC24H device reporting RIErr0009: Failed while reading configuration memory
with a second message that a memory object is missing. This can happen if the
device was programmed with a previous version of MPLAB IDE. The workaround is
to switch to REAL ICE as a programmer, erase the device, switch back to the
debugger and then program.</p>

<h3>10.2.4<span style='font:7.0pt "Times New Roman"'> </span>dsPIC30F Devices</h3>

<p class=MsoNormal><b>RI-335:</b> Attempting to connect REAL ICE to a
dsPIC30F6015 target results in Device Mismatch when using LVDS (10 ft).</p>

<h3>10.2.5<span style='font:7.0pt "Times New Roman"'> </span>PIC32MX Devices</h3>

<p class=MsoNormal><b>RI-319:</b> Sometimes a spurious halt occurs while using
REAL ICE and triggers on a PIC32MX340F512H.</p>

<p class=MsoNormal><b>RI-348:</b> [PIC32 Trace] PIC32 instruction trace does
not match disassembly when instruction in branch delay slot is other than NOP.</p>

<p class=MsoNormal><b>RI-350:</b> [PIC32 Trace] Instructions in the trace
window have incorrect addresses when compared with the actual memory contents
for PIC32 devices.</p>

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

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>When using I/O Port trace, make sure multiplexed device port pins
are set as I/O pins.</p>

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Make sure that table reads/writes are not code protected.</p>

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>At low Vdd, bulk erase will not erase code protect bits.</p>

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

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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>11.2<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span>16-Bit
Devices</h2>

<p class=MsoListNumber>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&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;&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;&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;&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;&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;&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;&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;&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;&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;&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;&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;&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;&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>11.3<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span>32-Bit
Devices</h2>

<p class=MsoListBullet><span style='font-family:Symbol'><span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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="_Toc225678229">12<span style='font:7.0pt "Times New Roman"'>&nbsp;&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="_Toc225678230">13<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;
</span>Number of Hardware Breakpoints Per Device</a></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 Device Debug
Resource toolbar. For more on this toolbar, see MPLAB IDE on-line help.</p>

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

<p class=ListBulletNoSpace>PIC18F devices  1 breakpoint</p>

<p class=ListBulletNoSpace>PIC18F Enhanced devices  3 breakpoints</p>

<p class=ListBulletNoSpace>PIC18FXXJ devices  3 or 5 breakpoints<span
style='color:blue'>*</span></p>

<p class=ListBulletNoSpace>dsPIC30F devices  2 breakpoints</p>

<p class=ListBulletNoSpace>dsPIC33F/PIC24 devices  4 breakpoints</p>

<p class=ListBulletNoSpace>PIC32MX devices  6 breakpoints</p>

<p class=MsoNormal><span style='color:blue'>*</span> There is a limitation for
these devices that only 1 data capture is available.</p>

<h1><a name="_Toc225678231">14<span style='font:7.0pt "Times New Roman"'>&nbsp;&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>
