Subject: Re: PIC16F877A
Date: Mon, 14 Oct 2002 15:36:15 -0400
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
"Mike Turco" wrote in message
> "dhrm77" wrote in message news:ao78h7$jnc5f$1@ID-
> > One works, not the other....
> > About the erratic behavior..
> > It seems that depending on WHERE the code is located in memory, the code
> > exhibit different malfunctions.
> What are the malfunctions?
I'm not the programmer on this project.. but as far as I understand, the
malfunction varies from one trial to the next.... for example if the result
of a group of 'C' instructions was wrong, and you add a printf somewhere in
this piece of code in an attempt to debug it, the problem will "move"
somewhere else.... i.e, that piece of code will work fine, but a different
piece of code will start giving wrong results...
This makes it very difficult to pin point using C... In assembly it wouldn't
be such a problem...
Note that the compiler that we are using is a "smart" compiler and will
locate subroutines at different places depending on a "best-fit" algorithm.
So from one compile to the next code is not guaranteed to stay
at the same place.
Elements beyond my control have made a decision to go back to the 877, and
let Microchip deal with it...