Stopping and re-starting a timer

[kgng97ccs]

The PIC18LF46K22 datasheet has this paragraph in Section 12.5.1 (READING AND WRITING TIMER1/3/5 IN ASYNCHRONOUS COUNTER MODE):
"Reading TMRxH or TMRxL while the timer is running from an external asynchronous clock will ensure a valid read (taken care of in hardware). However, the user should keep in mind that reading the 16-bit timer in two 8-bit values itself, poses certain problems, since the timer may overflow between the reads. For writes, it is recommended that the user simply stop the timer and write the desired values. A write contention may occur by writing to the timer registers, while the register is incrementing. This may produce an unpredictable value in the TMRxH:TMRxL register pair."

Questions:
1. How does one stop and re-start Timer1, or for that matter, any other timer, without accessing the register directly and without affecting the other settings of the timer?
2. Is it correct that if we use the get_timer1() function, which returns a 16-bit integer, the above read problem will never happen?
3. Similarly, is it correct that if we use the set_timer1() function to write a value to Timer1, the above write problem will never happen?

[PCM programmer]

For question #1, see the #int_timer1 routine in this post:
http://www.ccsinfo.com/forum/viewtopic.php?t=45458&start=5

[PCM programmer]

For question #2:

[Ttelmah]

And, on '1', this depends on the timer, and what you actually 'mean'.
For example if you look at Timer3, there is an 'on' bit, but it makes the
comment (for off), "Clears Timer1/3/5 Gate flip-flop". So turning this
'off' (which will stop the timer), also clears this flip-flop. Means you cannot
stop it without this changing.
Timer0, does not have this problem, and this has a T0_OFF setting.
Generally, you don't stop timers. Just reset them, read and write them.
If you want to stop their 'effect', just disable the interrupt from them.

[kgng97ccs]

Thank you, PCM Programmer, for the link and for directing me to the assembly code. I am not familiar with assembly language but will make an effort to understand the code.

Thank you, Ttelmah, for your advice regarding stopping a timer and for highlighting its effect on the Timer1/3/5 gate flip-flop. I have taken note of that.

If you know of any good resources for learning assembly language relevant to PIC MCU programming, please do let me know. Thank you.

[kgng97ccs]

We are using the PIC18LF46K22, CCS C compiler v5.078, and MPLAB IDE v8.92.

[Ttelmah]

Honestly enormously easier just to use one timer.....

If you need separate handling, just have a flag set to say which routine
to use inside the ISR.

[kgng97ccs]

Thank you, Ttelmah, for your suggestion.

Actually, the interrupt periods for both Timers are different.

Timer1 has an interrupt period of 125 ms (with a preload). I have several short PWM signal bursts that run at intervals ranging from 250 ms to 1 second (= 2 to 4 Timer1 interrupt periods). The int_timer1 ISR only sets some flags (no time-consuming tasks).

Timer3 has a much longer interrupt period of 2 seconds (no preload). I have one long PWM signal burst that runs for 60 seconds (= 30 Timer3 interrupt periods). The int_timer3 ISR only counts the number of Timer3 interrupts (no other tasks). Once the count reaches 30, I stop the long PWM signal burst.

As I do not wish for the long PWM signal burst to be distorted too much by the MCU having to take time off to execute an ISR, and also to save power, I thought I would do this:
(a) Minimize the number of Timer3 interrupts during the 60-second period, by choosing the longest interrupt period (2 seconds) that can be provided by Timer3 and the SOSC.
(b) During the 60-second period, turn ON Timer3; and turn OFF Timer1 so that the MCU will not need to execute any Timer1 ISR, and also to save power.
(c) When the 60-second period is over, turn OFF Timer3 and turn ON Timer1; I would turn ON Timer3 again only when needed.

For a similar reason, when sending the short PWM signal bursts, I would ensure that Timer3 is OFF.

If I use just one timer (in this case, it has to be Timer1), there will be 480 interrupts (480 x 125 ms = 60 seconds) during the 60-second period when I am sending the long PWM signal burst. By using a separate timer (Timer3) for the long PWM signal burst, the number of interrupts is reduced to only 30.

Does this approach sound reasonable?

[Ttelmah]

Point is the timer setups are the same. It is only the preload you are changing.
So:

[kgng97ccs]

Thank you, Ttelmah, for your explanation and advice.

Your illustration code gave me several ideas on how to manage timing with one timer.