Right now I'm using codewarrior to program a hsc12 microcontroller using C. I want to figure out how to write ISRs (Interrupt Service Routines). The include file that comes with codewarrior has names associated with each address of the ISR such as:
#define vrti 0x0000FFF0
....
However I'm not quite sure on how to actually write the ISR itself. If anybody has experience with this any kind of help would be appreciated.
Have you searched for microcontroller interrupt programming? Because I get a whole bunch of matches in random-popular-search-engine.
Quzah.
Hope is the first step on the road to disappointment.
Well actually more specifically I want to know how to build a interrupt vector table.
That would consist of:
1. Figuring out what the interrupt vector table looks like.
2. Then figure out how you actually put stuff in there from C.
I have built vector tables (or modified entries at least) for x86, 68K, 29K.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Well I know what the vector table for the hsc12 looks like. However I'm not quite sure how to build the actual table. This is what I have now.
so for the interrupts that I want to ignore I put a 0. So my question is basically what am I supposed to put for entires in the vector table I want to ignore. Also how do I actually write the interrupt service routine for say "rti_isr".Code:typedef void (*near tIsrFunc)(void); const tIsrFunc _InterruptVectorTable[] @0xFF80 = { 0, 0, ... rti_isr ... };
I have no idea how to write rti_isr - what is rti?
You probably can't just put zero in the vector table unless you know for sure that interrupt will absolutely never happen (including by programmer error). It is better to have a dummy-interrupt handler that deals with unknown interrupts [and possibly reports that in some way, e.g. count up a counter or write a message to the console or some such, so that you know that is happening].
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
