SOLVED - PIC seems to RESET unless I add a PAUSE in Mainloop

[HenrikOlsson]

PBP does handle it in, dare I say, >99% of cases. Here's one, fairly unrealstic case, where it doesn't.
I don't think PBP analyses the code in the details and determine exactly where to insert CLRWDT, I think it's more in line with what Richard says that the macros used by the various PBP statements either included a CLRWDT or they don't. When they get combined into a larger assembly listing it's "sprinkled" with CLRWDT instructions.

In this case the code resulted in assembly listing without any CLRWDT inserted. During >20 years of use I've never had that problem. That doesn't mean no one else have - apparently.

I mean, if you REALLY wanted to squeeze the most out of the PIC you'd turn off the WDT anyway in order to not waste time clearing it.

Out of curiosity, can you post an example of such a tight, endless loop, that you've used?

[Ioannis]

If compiler does not analyze this case then it is a problem. I really cannot remember having such a problem over my 25+ years of using PBP.

Will try to find that tight loop I tried many years ago when discussed it with Darrel and maybe it was on a F628 chip.

Will need time for this as it was long time ago...

Ioannis

[tumbleweed]

I may want (and have needed in the past) very fast loops. It is the responsibility of the compiler to add that @clrwdt in between. Not mine.

I disagree. If the compiler adds a CLRWDT in between every single instruction then there's no point in having it in the first place.
It's not going to detect a "fast loop" you make in your code.

[Ioannis]

I do understand fully. But also think there is a way compiler can detect that when needed. Sure it should not fill all over the place the CLRWDT!

Ioannis