avr-gcc-list
[Top][All Lists]
Advanced

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

RE: [avr-gcc-list] Handling High Speed Interrupts


From: Douglas Dotson
Subject: RE: [avr-gcc-list] Handling High Speed Interrupts
Date: Wed, 22 Sep 2004 05:42:40 -0700 (PDT)

I don;t believe that will help. As I understand it,
the only difference between INTERRUPT and SIGNAL is
that INTERRUPT keep interrupts enabled while
processing an interrupt while SIGNAL disables
interrupts for the duration of the handler.

Doug

--- Bernard_Fouche <address@hidden> wrote:

> >From what I've understood, use:
> 
> INTERRUPT(<vector name>)
> 
> instead of :
> 
> SIGNAL (<vector name>)
> 
> (I use only the later at the moment)
> 
>       Bernard
> 
> -----Message d'origine-----
> De : address@hidden
> [mailto:address@hidden la part de
> Ramkumar Rengaswamy
> Envoye : mercredi 22 septembre 2004 09:09
> A : address@hidden
> Objet : [avr-gcc-list] Handling High Speed
> Interrupts
> 
> 
> Hi,
>    I have an application that needs to generate a
> Timer Output Compare
> Interrput every 10 uS. I have an ATMega128L clocked
> at 7.329 MHz. This
> means that I have 74 clock cycles to handle the
> interrupt routine and
> currently most of the clock cycles are wasted in
> pushing and popping
> things off the stack. Is there anyway in avr-gcc to
> avoid all this
> overhead and utilize all the cycles for my
> processing only ?
> 
> Thanks,
> -Ram
> 
> 
> 
> _______________________________________________
> avr-gcc-list mailing list
> address@hidden
> http://www.avr1.org/mailman/listinfo/avr-gcc-list
> 
> _______________________________________________
> avr-gcc-list mailing list
> address@hidden
> http://www.avr1.org/mailman/listinfo/avr-gcc-list
> 



reply via email to

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