Re:

>I've read some things that make me think that its possible to use the MPLAB
>source debugging features (stepping/tracing, watches, breakpoints, etc)
>with C code generated by the Hitech PIC C Lite compiler, but haven't seen
>any examples of how to do so (seems that that's what the 'fake' option is
>for?)  Is this the case?  Has anyone done this?  If it can be done, do you
>actually step through the C code or through the generated assembler
>code?  Any tips on setting this up would be most helpful.

I run HPDPIC, MPLAB and my editor in separate windows under Win98.  How
MPLAB steps through my code is dependent on whether the Program Memory
window or a C sourcee window is topmost in the MPLAB IDE.

I create an MPLAB project (.pjt) in the same directory as my PIC C project
(.prj). I use "Source level debug info" and "Fake local symbols" under Map
and Symbol File Options

I have never bothered to "integrate" PIC C into the MPLAB IDE, as I find it
much easier to manage a PIC C project than change all the compile- and
link-time settings in MPLAB.

So my sequence to test new code is:

1) Edit in CodeWarrior, and save.
2) Make Project in HPDPIC.
3) Assuming no errors, in MPLAB I Import->Download to Memory the project's
.hex file.

Note that I don't edit anything in MPLAB -- hence I don't normally have a
source file window open.  So, in order to step through (multiple) source
files in C, I usually open the project's main.c file, reset the PICMASTER,
and go / step. It works very nicely, even picks up source code from modules
I have linked to in HPDPIC, and you can switch back and forth between C and
assembly by selecting the appropriate window.



 ______________________________________
  Andrew E. Kalman, Ph.D.   aek@netcom.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.