Unexpected PIC reset (probably when byte variable overflows)

[HenrikOlsson]

Turning off the watchdog makes it work so that's what's resetting it for sure...

The original code, where I notices it is like this:

Main:
  i = i + 1
  Gosub GetValue
  PortB = Out
Goto Main

Then the subroutine GetValue is a lookuptable with 255 entries returning the value in Out. It too restarts when the dog is unleashed. However, if I add IF i = 255 then i = 0 at the end it works. I then tried to boil that down to the minimum, which is what I posted above.

So, is this an oversight on my behalf or an unwated side effect of a "tight" (it's not THAT tight) program?

In any case, thanks Bruce!
/Henrik.

[mister_e]

How your lookup table looks like?

I could be wrong but probably the generated asm for the IF/THEN have some CLRWDT while the lookup don't?

[Bruce]

It sounds to me like PBP does not reset WDT for all instances. I.E. if you have only a simple loop, incrementing or decrementing a variable, with no PBP commands in the loop, you have a WDT reset.

PBP will reset WDT in most command routines, but with something so simple, without any PBP library routines invoked, it may not be resetting WDT!

And - why the heck did this reply end up as the 1st post magically? It was posted after post #6?