-----Original Message-----
From: pic microcontroller discussion list
[mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of John Hansen
Sent: Thursday, July 15, 1999 9:58 AM
To: PICLIST@MITVMA.MIT.EDU
Subject: Re: Strange MPLAB-ICD behavior


At 10:21 PM 7/14/99 -0400, you wrote:
>I received my (first) mplab icd today (have two more systems coming so I'll
>get a chance to compare them later) and was both impressed and slightly
>irritated because of things not working all that well.


AMEN


>Features that I cannot get working:
>*verify

I think the problem with verify is that it verifies your .hex code against
the code in the chip.  But when the debug feature is turned on, it loads a
slightly different code to support debug.  I found that verify never works
if debug is turned on, but if you turn the debug off, it does verify fine.

Since you have this system up and running let me ask you a couple of
questions:

After the chip is programmed (with debug off) are you actually able to run
it in the prototype module without the ICD connected?  I've not been able
to do so.

I can  get the demo program to run independently, It is not enough to
uncheck the debug mode , the chip has to be programmed after this.. then I
can unplug the cable and after pressing reset or powering off and back up ,
it runs

When you run the code with the ICD module connected in debug mode but have
no breakpoint set, do the LED's flash on your unit or are they solidly on?

I can get this same behavior by not setting the program "configuration bits"
but with the "erase all before program" on I suspect ...but did not check
yet that the watchdog might be the problem

when I program config bits it is ok


Thanks,

John Hansen