[PIC] Watchdog timer don't work on PIC18f67J94

[brankobr]

I configured PIC18F67J94-I/PT as in pictures in attachment, nowhere in code put CLRWDT instruction, and I expect that PIC reset after some time, but reset never happens.
Can someone help me, please?

 

[KlausST]

Hi,

How do you know RESET never happens?
What is your exact test mode, HW, SW, measurement devices...?

Klaus

 

[brankobr]

Hi,

How do you know RESET never happens?
What is your exact test mode, HW, SW, measurement devices...?

Klaus

I have GLCD display that changes view, and buzzer that makes sound on reset, also relays that turns off. So I'm sure that RESET never happens because device is working without any change.

 

[KlausST]

Hi,

It's very unlikely that the watchdog system in a PIC does not work.
Thus I see just some possible reasons for your problem
* the watchdog setup is not properly programmed into the circuit
* wrong code
* wrong test method

Your given informations are too vague for us to validate.

If you don't want to show us your code, then I recommend to use just a minimal code containing:
* port setup
* testpin = output, Low
* wait 10ms
* testpin = output, High
* infinite loop

Then use a digital scope at the testpin with proper trigger detection.

Calculate the expected watchdog timeout.

Klaus

 

[brankobr]

Hi,

It's very unlikely that the watchdog system in a PIC does not work.
Thus I see just some possible reasons for your problem
* the watchdog setup is not properly programmed into the circuit
* wrong code
* wrong test method

Your given informations are too vague for us to validate.

If you don't want to show us your code, then I recommend to use just a minimal code containing:
* port setup
* testpin = output, Low
* wait 10ms
* testpin = output, High
* infinite loop

Then use a digital scope at the testpin with proper trigger detection.

Calculate the expected watchdog timeout.

Klaus

Thanks a lot! I will try this!
It's not problem to show you code if you can help me.

 

[betwixt]

What language is your code written in?
Unless you are coding in pure assembly language it is quite likely that the compiler has inserted watchdog resets in the code by itself or it has included a library that incorporates them.

Brian.

 

[brankobr]

What language is your code written in?
Unless you are coding in pure assembly language it is quite likely that the compiler has inserted watchdog resets in the code by itself or it has included a library that incorporates them.

Brian.

I use mikroC pro for PIC compiler, C language.
I also think that problem may be in compiler.
Do you have idea how to solve this.

 

[FvM]

The usual way to trigger a watchdog reset is to disable all interrupts and perform an endless loop e.g.

INTCON.GIE = 0;
while (1);

 

[brankobr]

The usual way to trigger a watchdog reset is to disable all interrupts and perform an endless loop e.g. while (1);

If timer 1, and timer 2 interrupts are enabled, can WDT reset PIC? I think that it should.

 

[KlausST]

Hi,

WDT does not depend on timer and interrupts.

It just depends on WDT setup and WDT RESET...(at least I can´t remember anything else)

****
Are you aware that a "RESET" may be a very short event? It maybe just takes 10us (depending on your code). So it surely is possible that you don´t even see the tinyiest flicker on an GLCD. Thus I don´t think a GLCD is a proper test method.

But as long as you don´t give informations like schematic, code, clear test methods, feedback on recommended test routines.... it´s impossible for me to further assist you.

***
If you "think" it´s a compiler problem... then have a look at the compiler output files. I expect a file that contains the assembler code. Please understand, we don´t have this file .... so you have to check it on your own.

Klaus

 

[FvM]

If timer 1, and timer 2 interrupts are enabled, can WDT reset PIC? I think that it should.

Yes, if you are sure that the interrupt functions don't indirectly perform a WDT clear. mikroC documentation doesn't seem to tell anything about internal CLRWDT usage, but it can be expected at least for built-in software delay instructions. Inspecting the generated code maybe the only way to find out.

--- Updated Dec 23, 2021 ---

You didn't tell much about your code layout. In which state of code execution are you expecting the watchdog reset to occur?

 

[brankobr]

I found solution for this problem. Compiler mikroC pro for PIC, has a bug, and when you select in the wizard Watchdog timer enabled, it writes wrong value in .cfg file. I have edited values in .cfg file by myself, and now WDT works as expected.