Timer0 Match Interrupt

[danlee58]

I have a SuperPro. I have set up Timer0 to Interrupt on Match 0xFFFFFF. This takes a few seconds after a reset for the Interrupt procedure to run and print some text to the terminal. Once the procedure begins to run, it will run continuously. I expect it to take a few more seconds to Match 0xFFFFFF again.

This is the code to reset Timer0.

T0_TCR = 2; //Reset Timer 0
T0_TCR = 1; //Enable Timer 0

[olzeke51]

there was some timer changes recently - Apr???
http://www.coridiumcorp.com/forum/viewt ... tick#p2471
is my search -- check your kernel versions/dates
'
what is your clock source/freq for the Timer0??
'
are you getting the first INT message but not the 2nd??

[danlee58]

The clock source is PCLK. I have Timer0 clocking at full rate (Prescale = 0). I get the first interrupt message, but then it seems to repeat, as if Timer0 interrupt was not cleared or the timer was not reset.

There should be dead time between messages. It's to be used as a watchdog timer to keep another operation from rollover.

[danlee58]

I think that it's working now. I used this code:

T0_IR = 0x1; //Reset Channel 0 Interrupt.
T0_TCR = 2; //Reset Timer 0
T0_TCR = 1; //Enable Timer 0

However, I don't get a message from the Main Program in between the Timer0 Interrupt messages.

[basicchip]

Take a look at the TIMER1 interrupt example in BASIC, same general operations have to be done

Code: Select all

INTERRUPT SUB TIMER1IRQ
  T1_IR = 1	      ' Clear interrupt
ENDSUB

SUB ON_TIMER ( msec, dothis )
   TIMER1_ISR   = dothis + 1              'in C you don't need to do this if the vector already points to dothis
   VICIntEnable or= (1<<2)  'Enable interrupt
  T1_MR0 = msec-1 ' set up match number of ms
  T1_MCR = 3      ' Interrupt and Reset on MR0
  T1_IR  = 1      ' clear interrupt
  T1_TC  = 0      ' clear timer counter
  T1_TCR = 1      ' TIMER1 Enable
ENDSUB

main:
  ON_TIMER(2000, ADDRESSOF TIMER1IRQ)

[danlee58]

It appears that the Main loop stops executing, once the Timer0 Interrupt runs. Timer0 continues to run, however.

[danlee58]

I caught this message on y Terminal Program;

FaultISR 0xFFFFFFF1 SCB->CFSR=0x00020000

Any idea what this means?

[olzeke51]

this thread might shed some light on it..
http://www.coridiumcorp.com/forum/viewt ... t=244#p628