Timer1 usage in PIC18F252

[EShatara]

Been diviing into the description of the use of the interrupts for the 18F252 device and want to test out my understanding relative to the relationship between the prescaler and 8/16 bit registers of the timer.

If I'm using a 4Mhz oscillator and an internal clock for the Timer then my effective frequency going to the 8 or 16 bit counter is either:

1 Mhz for a Prescale value of 1
500 Khz for a prscale value of 2
etc....

Then this frequency is fed into the counter and when it overflows an interrupt is generated.

Correct?

So if I want an interrupt every 0.5 seconds I could use a prescale of 8 giving me a frequency of 125khz (8us period) and preload the 16bit register with 3036 (decimal)

I reached this figure by dividing 0.5 sec by 8 us and getting 62500 pulses required to overflow the 16bit counter. With no preload, the counter would take 65,536 counts to overflow so I would preload it with 65536-62500

Correct?

The other thing I'm not sure about is the ability to configure the timer for 16 bit reads and writes. I still need to read TMR1L and TMR1H separately... don't I?

I'm sure I'll have more questions when I attempt to program this later on this weekend.

thanks...Chris

[Charles Linquis]

Your math is correct, but be sure you write to any 16bit timer in the order: highbyte, lowbyte. The datasheet explains this.

[EShatara]

I'm also assuming that I will need to reload the TMR1H/L register as I exit the interrupt service routine. Correct?

[Charles Linquis]

Generally no. If you are interrupt driven, and you need an interrupt every 'x' seconds then your ISR would reload the registers with the appropriate values as soon as possible (to insure correct timing). There is no need to reload them upon exit.

In PBP, I normally run in "pseudo-interrupt" mode. I sit in a tight loop polling PIR1.0 until it goes true, clear that bit, reload TMR1H and TMR1L then enter my main routine. After the routine, I go back to the polling mode.

I put all my high-priority items (such as checking the serial port interrupt bit) in the tight loop, and all the normal stuff in the main program. I avoid pauses whenever possible and instead rely on the timer to provide timing information.

[EShatara]

>Generally no. If you are interrupt driven, and you need an interrupt every 'x' >seconds then your ISR would reload the registers with the appropriate >values as soon as possible (to insure correct timing). There is no need to >reload them upon exit.

That's what I meant...thank you

>In PBP, I normally run in "pseudo-interrupt" mode. I sit in a tight loop >polling PIR1.0 until it goes true, clear that bit, reload TMR1H and TMR1L >then enter my main routine. After the routine, I go back to the polling >mode.

I already have a tight loop polling my serial port looking for a charaacter. Are you saying I can use the timer without having it generate an interrupt?

Hadn't thought about that....That could be quite easy to implement in my code.

Thanks .... chris

[Charles Linquis]

Yes, here is a quick code example:


FastLoop:
IF PIR1.0 = 1 THEN
PIR1.0 = 0
TMR1H = TimerPreloadValue.Highbyte
TMR1L = TimerPreloadValue.Lowbyte
GOSUB MainProgram
ENDIF
IF PIR1.5 = 1 THEN
Gosub KeyboardInputRoutine ' HSERIN clears PIR1.5
ENDIF

GOTO FastLoop

MainProgram:

'Do something here every time the timer rolls over

RETURN




' This works perfectly as long as your 'Main Program' never takes as long as the timer period. The code sits in the FastLoop waiting for either a keyboard input or a timer timeout. When the timer timeout occurs, then the MainProgram is executed. If you output data in your MainProgram, that data will be output at a regular interval regarless of the length of your program.
Just remember - stay away from PAUSEs in your main program whenever possible!

[EShatara]

Thanks Charles...you've been most helpful....Chris