Microchip Technology AC162096 数据表
Processor Extension Pak and Header Specification
DS51292U-page 26
2006-2012 Microchip Technology Inc.
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.
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 exces-
sive current due to the higher voltage used on a target board designed for HV devices
and damage the device mounted on the header.
target board designed for a shunt regulator (HV) device, the device may draw exces-
sive 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 IDE or 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.
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 IDE or 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 http://support.microchip.com.
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 http://support.microchip.com.
Header Limitations
See the “Limitations” section in your debug tool online Help file for details.