Datasheet

ManualsBrandsMICROCHIP TECHNOLOGY ManualsDev KitsPCB design board

MPLAB

ICD 2

Header Specification

INTRODUCTION

This document contains information about MPLAB

ICD 2 headers, which provide

in-circuit debugging capabilities for specific Microchip devices.

A special ICD/ICE device is connected to a header board to be used with MPLAB ICD 2.

This device is mounted on the top of a header and its signals are routed to the

MPLAB ICD 2 connector (Figure 1). On the bottom of the header is a socket that is

used to connect to the target board.

FIGURE 1: MPLAB

ICD 2 MODULE CONNECTION WITH PDIP HEADER

Special ICD/ICE versions of selected devices are needed to provide one or more of the

following:

• the built-in debug circuitry that a device may lack

• additional pins for the clock, data and MCLR

functions required for ICD

• dedicated program/data memory for ICD

ICD versions are labeled with an ICD suffix (Device-ICD). For some devices, ICE

versions are available (Device-ICE) and may be used with MPLAB ICD 2 as ICD

devices.

MPLAB

ICD 2

Power In

Target Application

Target Socket

MPLAB ICD 2 Header

Stand-off Connector

-ICD Device*

Jumpers

*Number of pins is determined

by -ICD device used.

**Number of stand-off pins is

determined by MPLAB ICD 2

Header used.

Module

Summary of content (12 pages)

PAGE 1
MPLAB® ICD 2 Header Specification INTRODUCTION This document contains information about MPLAB® ICD 2 headers, which provide in-circuit debugging capabilities for specific Microchip devices. A special ICD/ICE device is connected to a header board to be used with MPLAB ICD 2. This device is mounted on the top of a header and its signals are routed to the MPLAB ICD 2 connector (Figure 1). On the bottom of the header is a socket that is used to connect to the target board.
PAGE 2
MPLAB® ICD 2 HEADERS FOR ICD DEVICES Some devices have no built-in debug circuitry. Therefore, special ICD versions of these devices are required for MPLAB ICD 2 operation. Other devices have built-in debug circuitry and do not require a header to use MPLAB ICD 2. However, some pins and memory must be used to support the ICD function. Therefore, for some of these devices, special ICD versions offering additional pins (and sometimes memory) are available to provide more transparent debugging capabilities.
PAGE 3
Header Specification HEADERS FOR ICE DEVICES Devices that have built-in debug circuitry do not require a header to use MPLAB ICD 2. However, some pins and memory must be used to support the ICD function. Special ICE versions offering additional pins, memory and emulator functions can be used to provide superior debugging capabilities. Currently-available headers and their associated ICE devices/supported devices are shown in Table 2.
PAGE 4
MPLAB® ICD 2 18-PIN HEADERS For these headers, there are no jumpers/switches. The device with the most program memory is always selected. If PIC16F627A or PIC16F628A devices are selected for MPLAB ICD 2 development in MPLAB IDE, the warning “ICDWarn0020: Invalid target device id” may be received in the build window and as a dialog. The reason is the PIC16F648A-ICD device supports PIC16F648A, PIC16F627A and PIC16F628A, but only reports the device ID for the PIC16F648A.
PAGE 5
Header Specification TABLE 3: S1 SWITCH SETTINGS Switches Device ADC 4kPFM USART SSP ECCP PIC16F631 0 0* 0 0 0 PIC16F677 1 0** 0 1 0 0 1 1 1 1 0 0 1 PIC16F685 1 1 0 PIC16F687 1 0** 1 PIC16F689 1 1 1 PIC16F690 1 1 1 Legend: 1 = Enabled 0 = Disabled * = 1k PFM ** = 2k PFM 64/80-PIN HEADERS For these headers, there are no jumpers/switches. MPLAB IDE will use its selected device to choose the correct device to emulate.
PAGE 6
MPLAB® ICD 2 PROGRAMMING NON-ICD DEVICES The MPLAB ICD 2 header can only program the -ICD device, not the regular device. To program non-ICD devices with the MPLAB ICD 2, use the Universal Programming Module (AC162049) or design a modular interface connector on the target. See the appropriate specification for connections. For the most up-to-date device programming specifications, see the Microchip website (www.microchip.com).
PAGE 7
Header Specification FIGURE 3: 8/14/18-PIN HEADERS VDD 1 2 3 1 3 2 JP1 ENABLE 14 ICDCLK 13 ICDMCLR ICDDATA VDD 12 Vss 4 11 5 10 6 9 7 8 NC ICD 8-Pin Header To MPLAB® ICD 2 Connector VDD 1 3 1 2 JP1 14-Pin Header 20 ENABLE ICDCLK 2 ICDMCLR ICDDATA 19 3 18 Vss VDD 4 17 5 16 6 15 7 14 8 13 9 12 10 ICD NC 11 To MPLAB® ICD 2 Connector 1 28 2 27 3 26 4 25 6 VDD 24 23 7 22 8 21 9 20 10 19 11 18 12 17 5 Vss 13 ICDMCLR 14 ICD 18-Pin Header ICDCL
PAGE 8
MPLAB® ICD 2 FIGURE 4: 20-PIN HEADERS 1 20 ICDCLK 2 ICDMCLR ICDDATA 19 3 VDD Vss 18 4 17 JP3 VDD 5 16 6 15 7 14 8 13 9 12 10 NC ICD PIC16F639 11 3 1 To MPLAB® ICD 2 Connector 2 VDD 1 3 1 2 JP2 PIC16F785 2 3 SHNTREG ICDCLK ICDMCLR ICDDATA VDD Vss 28 27 26 4 25 5 24 6 23 7 22 8 21 9 20 10 19 11 18 12 17 13 ICD 14 NC NC 16 NC 15 VDD ICDMCLR ICDCLK ICDDATA Vss To MPLAB® ICD 2 Connector 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 Vss 28 27 26 25 24
PAGE 9
Header Specification 128 VDD ICDT Vss 64/80-PIN HEADERS ICCK FIGURE 5: 116 115 111 109 97 96 1 Vss 19 VDDcore 21 VDD Max = 3.6V ENICPORT 85 Vss 84 79 VDD 70 ICRST 32 65 64 VDD 45 47 Vss 33 To MPLAB® ICD 2 Connector © 2005 Microchip Technology Inc.
PAGE 11
Note the following details of the code protection feature on Microchip devices: • Microchip products meet the specification contained in their particular Microchip Data Sheet. • Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the intended manner and under normal conditions. • There are dishonest and possibly illegal methods used to breach the code protection feature.
PAGE 12
WORLDWIDE SALES AND SERVICE AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPE Corporate Office 2355 West Chandler Blvd. Chandler, AZ 85224-6199 Tel: 480-792-7200 Fax: 480-792-7277 Technical Support: http://support.microchip.com Web Address: www.microchip.