TMR0 stops working

[shahidali55]

16F628A has been running stable for 10 days now.(Tried doing all sorts of things to make it reset, but its immunity is really good).
So i guess the only solution is to stick with the 16F628A . . .

[shahidali55]

My problem is still very much alive.
I had turned off the clock for over a month.
Now the clock "locks up" within 48 hours.
It has locked up twice at 7 hours , 14 minutes (7:14).
The mux routine works fine but the ISR just stops updating timing registers.
(The varibles that handle this are bres_hi ,bres_mid ,bres_lo.)
(uC is 16F628A and TMR0 used ot keep time)

[Darrel Taylor]

I'm still thinking it's related to voltage.

The device is being powered by 3.6V
But the 16F84A is only specified to work down to 4.5V

In post #3 you said the datasheet specifies 2.0V
But that's only for the 16LF84A

Edit: Doh! You're using the 628 now. Nevermind.
<br>

[Darrel Taylor]

shahidali55,

Do you have an updated program?
I tried to compile the program from post#1, but it has too many errors.

It also has the pushbuttons on the same pins as the segments, and ASM opcodes in column 1.
<br>

[shahidali55]

Hello Darrel,
As you suggested in post 2, the battery now charges from output from the 5v regulator (through a diode and a 2.2k resistor). The voltage at the PIC never rises above 4.6v. I tested this system with a 20v DC supply and the voltage at the pic pins is still at 4.63 volts (after 48 hours of running).

I have attached a copy of the file with the required include (Instant interrupts) as a zip archive.
The pushbuttons are not a concern now since the primary function of the device itself
(i.e. keeping time) is not met.

Is ASM opcodes in column 1 bad ?

[Darrel Taylor]

I have attached a copy of the file with the required include (Instant interrupts) as a zip archive.

I don't understand why you've modified DT_INTS-14 like that. There's no need.
I also don't like modified versions being posted on the Internet. Somebody will download it, it won't work, and then they'll blame me.

Is ASM opcodes in column 1 bad ?

Yes! Very BAD!
ONLY Labels can go in the first column of ASM code.
This applies to lines using the @ sign too. There must be a space after the @. (unless it's a label)

With opcodes in column 1, the program won't compile. So that can't be the program you are currently running in the chip.

DT

[shahidali55]

Strange . . .
Compiles fine for me.
I have corrected the OPCODE in column 1 errors and attached another copy of the file.
Sorry for modifying DT_INTS-14 , it it your work and i respect that. I modified it in my frustating attempts to correct the resetting and locking up of the chip.
(still getting 3 warnings though)