[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] How to handle interrupt vectors ?

From: Charalampos Alexopoulos
Subject: Re: [avr-gcc-list] How to handle interrupt vectors ?
Date: Wed, 29 Oct 2008 20:12:00 +0200
User-agent: Thunderbird (X11/20080421)

Joerg Wunsch wrote:
> Charalampos Alexopoulos <address@hidden> wrote:
>> An ISR is used with a vector as a parameter, ...
> Did you ever look into what the ISR macro actually resolves to?  It's
> just a couple of ``extern "C"'' declarations, and the parameter of
> that macro is used as the function name to declare it to.  The ISR
> macro itself doesn't check anything there, but the expected value (by
> the C run-time startup code) for that parameter is to be of the form
> __vector_N (with N being a number ranging from 1 through the number of
> interrupt vector slots of that AVR).
> It should be pretty obvious that a name like foo::mumble can never
> match that __vector_N requirement, so the linker will never be able to
> put your interrupt handler into place.
I was asking for information about interrupt vector's not for ISR. Yes i
have seen the code for the ISR and i have no understanding of the
mechanism because i don't know what that vector is. It is very obvious
that foo::mumble is not working, thats why i am asking for help.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]