Alan B Pearce wrote:
>> Jason White wrote:
>>     
>>> I got your code I couldn't really get it to work. but with a whole
>>> bunch a clrwdt commands I got around the restart problem in my code.
>>>       
>> Hmm.  That could mean two things:
>>
>> 1 - You had the watchdog enabled despite your claim to the contrary, and
>> kicking the dog regularly keeps it from biting.
>>
>> 2 - The CLRWDT instruction don't do anything useful, but move things 
>> around
>> so that the address-related bug no trashes something harmless or causes a
>> symptom you haven't noticed yet.
>>
>> You should do a global edit and replace all CLRWDT instructions with NOP 
>> and
>> see what happens.  If it now fails the problem was #1 and you need to fix
>> your config settings for real.  If it still works, you've got a much more
>> subtle but nasty bug lurking, and it's got nothing to do with the 
>> watchdog.
>>     
>
> And he probably needs to get an understanding of this before attempting to 
> move onto another processor, which if he uses an 18F series one as seems to 
> be the intent in another thread, has more methods of biting him in manners 
> he doesn't understand. 
>
>   
Moving from 16F877 to 18F4550 was "interesting" on the Fuses front, as 
was then moving same code onward to 18F67J50

I actually had to read the datasheet :)
Having a 1600 line screen saves on printing PDFs though, even though 
it's 8 years old.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist