The ICE supports break-on-specific and trace history.  You're right, I should
have mentioned them too, as I use them a both a lot.

How is RAM "invalid" in a PIC?  They don't offer hardware-level protection.

The only problem with GPSIM is that it doesn't interface with the hardware too
well <G>

The other features would be neat (and possible) additions to the ICE I think.

Andy









Scott Dattalo <scott@DATTALO.COM> on 03/21/2000 01:20:37 PM

Please respond to pic microcontroller discussion list <PICLIST@MITVMA.MIT.EDU>








 To:      PICLIST@MITVMA.MIT.EDU

 cc:      (bcc: Andrew Kunz/TDI_NOTES)



 Subject: Re: MPLAB-ICD firmware version 2.04 and other
          problems








On Tue, 21 Mar 2000, James Newton wrote:

> <VBG> I've tickled somebody's "how much did I pay for this and he thinks its
> worthless" bone...
>
> Andy, you know I love you and your sharp wit, and yes, the ICE is a kick
> butt tool with all these whiz bang features, and I'll not even argue any of
> your points ('cause you got me on all of them, I think) and I would love to
> have one (Hint to Tech Tools: I'm possibly for sale <GRIN>) but it still
> isn't something that you can drop into every production device you ship.

Hey Andy,

gpsim can do all this stuff.

Also, I'm sure that trace dumps are useful too. Or how about break on read or
writes for specific values?  Or break when invalid ram is accessed? Or break
after certain amount of execution time? Or how about having the ability to
customize any kind of break condition that you need?

</GRIN>
</VBG>

Scott