Josh Koffman wrote:

> What I'd really like is to be able to make a variant of a breakpoint
> for when I'm using my ICD2. If I want the values in my watch window to
> update, I can either set a breakpoint (which halts everything
> completely), press the pause button, or enter "Jog" mode which updates
> the watch after each step, leading to slow execution. What I'd really
> like is to set a position in my program where every time execution
> passes that point, the watch window is updated. That would allow me to
> do tests on my large switch matrix and watch which registers change.
> Is that even feasible?

The breakpoint assertions I discussed applied only to the simulator (and 
specifically to my simulator). The ICD is a different beast. One way to 
achieve this watch window feature is with a simple serial port debugging 
tool. I usually instrument my programs with a little RS232 debugging 
routine so that I can monitor certain state variables or whatever. This 
is similar to the "jog" feature of the ICD, but I have control when 
things are updated.

If you're willing to stay in simulation land, then you may consider 
building a gpsim switch matrix module and simulating a portion of your 
system. I just checked in a patch the other day from a user who 
introduced switch capacitance to the switch module (there already was a 
concept of switch resistance), so you could model capacitive loading 
(which may or may not be important to you). In my opinion, it may be 
more effort than it's worth to build a model, but if this is a project 
that you think will have a long life span and used as the basis for 
other projects, then it may be worth it.

Scott
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist