Header Identification

The AC number is used for ordering the Processor Extension Pak, which contains the debug header. However, this number is not on the header, as the board may be used for multiple headers by inserting different -ICE/-ICD devices. To identify these headers, use the following information.

AC Number -ICE/-ICD Device Board Assembly Number
AC162083 PIC16F616-ICD 02-01976

Header Setup and Operation

BoardZap.jpg CAUTION
Header Damage.
Incorrect rotary switch (see "Header Dimensions" figure) settings may irreparably damage the header.
Ensure rotary switch settings are correct (see table below) before powering or connecting the header.
Do not change the rotary switch setting while the header is powered or connected to a debug tool.
Do not power shunt regulator (HV) devices from the debug tool.

Test points are available on this header to check the following: Ground (TP1), Vdd (TP2), ICD Clock (TP3), ICD Data (TP4) and ICD MCLR/Vpp (TP5).

Switch Position Device Switch Position Device
0 PIC12HV609 8 PIC12F609
1 PIC12HV615 9 PIC12F615
2 Reserved HV A PIC12F617
3 PIC16HV610 B PIC16F610
4 PIC16HV616 C PIC16F616
5 Reserved HV D Reserved F
6 Reserved HV E Reserved F
7 Reserved HV F Reserved F

Also see the AC162083 Insert (DS51693).

Potential Issues

HV device selected instead of F device

If you inadvertently select a shunt regulator (HV) device and attempt to use it in a target board designed for a non-shunt regulator (F) device, the shunt may draw excessive current due to the lack of current-limiting circuitry on the target board and damage the device mounted on the header.

F device selected instead of HV device

If you inadvertently select a non-shunt regulator (F) device and attempt to use it in a target board designed for a shunt regulator (HV) device, the device may draw excessive current due to the higher voltage used on a target board designed for HV devices and damage the device mounted on the header.

HV devices cannot be powered from debug tool

Do not select in MPLAB® X IDE to power the target (debug header) from the debug tool (if it supports powering the target) when using shunt regulator (HV) devices since this will also cause the shunt to draw excessive current.

Determining Damage

A damaged header will cause MPLAB® X IDE to report a device ID of 0. However, there are other issues that can cause the device ID to report as 0. Please consult your debug tool documentation on troubleshooting to identify the problem. If you believe you have a damaged header, please contact Microchip technical support at

Header Limitations

Sometimes a header device (-ICE/-ICD) has operational issues or errata. To determine if a device on a header has limitations, see your hardware tool documentation.

Header Dimensions

The figure below lists the dimensions for the debug header. Dimensions are design values in inches.

If the length and/or width of the debug header is too large a footprint for the target board, consider using stand-offs, transition sockets or other extenders in the header connection socket to raise the header above the target.

Figure: Dimensions – AC162083

20th Annual
Microchip MASTERs Conference 2016
Register now - Deadline: July 29

JW Marriott Desert Ridge Resort-Phoenix, AZ

© 2016 Microchip Technology, Inc.
Information contained on this site regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION, INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights.