This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============24651712752406407== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C48F57.22B8EB8C" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C48F57.22B8EB8C Content-Type: text/plain; charset="ISO-8859-1" Ed Browne wrote: > Phil, > If you can find no rational reason for the problems, then check your > grounding and shield your board while debugging. I suppose I should have checked that first. But no, ground appears good. passes continuity check at least. There are separate analog and digital grounds. The grounds are connected via a ferrite bead (panasonic EXCELSA35) > Check all of your > bypass caps and pull-ups to make sure they're sized correctly. I > found the ICD2 much more susceptible than the old debugger. Good > hunting. anything special about the reset pullup? I'm using a 10K from Vpp to Vdd. No caps on the pin. ------_=_NextPart_001_01C48F57.22B8EB8C Content-Type: text/html; charset="ISO-8859-1"
Ed Browne wrote:
> Phil,
> If you can find no rational reason for the problems, then check your
> grounding and shield your board while debugging.
I suppose I should have checked that first. But no, ground appears
good. passes continuity check at least.
There are separate analog and digital grounds. The grounds are
connected via a ferrite bead (panasonic EXCELSA35)
> Check all of your
> bypass caps and pull-ups to make sure they're sized correctly. I
> found the ICD2 much more susceptible than the old debugger. Good
> hunting.
anything special about the reset pullup? I'm using a 10K from Vpp
to Vdd. No caps on the pin.