user defined vector

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

user defined vector

2,770 Views
Poornima
Contributor I
Does anyone know what user defined vector #118 is?
The code warrior help has no documentation for this exception.
I am using MC5485 with coldfire and trying to generate a slice timer interrupt. My timer count gets to 0 but the interrupt is not raised.Instead I get this exception.
Labels (1)
0 Kudos
5 Replies

529 Views
CrasyCat
Specialist III
Hello
 
According to the ColdFire CF4e Core User's Manual specifies that interrupt 64-255 are user defined interrupt.
So interrupt 118 is a user defined interrupt that you have somehow enabled and that you need to handle.
 
I would recommend you to look at your source code and the way you initialize your timer interrupt.
 
CrasyCat
0 Kudos

529 Views
Poornima
Contributor I
Thankyou, I figured out the reason for that. I configured a timer to generate an interrupt and created the condition to invoke the interrupt. But, the timer interrupt I am using is system defined and has a vector no of 54. I cannot understand why it is being generated as that of 118(64+54=118).
0 Kudos

529 Views
CrasyCat
Specialist III
Hello
 
  How did you initialize /define the interrupt?
  More specifically How did you initialize the entry in the vector table?
 
CrasyCat
 
0 Kudos

529 Views
Poornima
Contributor I
Hi,

The vector table in the vector.s file has "asm_exception_handler" as the entry for all the interrupts. This exception handler is defined in int_handlers.c with a switch case statement, with cases for all the interrupts. My slice timer interrupt is falling down to the default case, which is supposed to be the case for the user defined vectors. That is where the no 118 is coming from. When I add a case for 118, the routine that I call in that case is getting invoked when my interrupt occurs.

--Poornima
0 Kudos

529 Views
CrasyCat
Specialist III
Hello
 
So that means you have configured your application to get an interrupt on vector 118 and you get it there.
I will assume the problem is fixed now.
 
CrasyCat
0 Kudos