> I was able to take a new chip and verify that Microchip's PICSTART
leaves
> this value in place when erasing and programming, but after programming
> with the output of the Hitech compiler the 0x3FF value has changed.
Looks
> a lot like a HITECH compiler issue to me, that was the item I least
> expected on my list!

Did you make sure no real code can be placed at 3FFh.  The easiest way to
do this is to set up the linker sections so that 3FFh doesn't exist, or at
least is in a separate section flagged as PROTECTED.  A look at the link
map should tell you if anything got placed there.

> Now here comes another issue with Hitech compiler - Single Stepping
would
> be really nice if it actually worked.  When I single step through my
> program under MPLAB, The first 20-30 instructions are invisible.

That's why I keep saying to single step **in the program memory window**,
not in the source code.  That will (should) show you each instruction
regardless of where it came from.  I've never used MPLAB with a compiler,
but I would be very surprised if the program memory window goes away in
that case, or the ability to single step in that window.  Worst case,
create a new MPLAB project and tell it you are only using the assembler,
then import the raw HEX file.  That will definitely allow you to single
step each instruction.  Since there isn't any source code the startup code
came from directly, lack of a source window won't matter here.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body