On 7/1/2014 3:37 PM, Peter Dufault wrote:
> On Jun 30, 2014, at 14:41 , Joel Sherrill wrote:
>
>> Is your "struct handler_arguments" declared on the stack (e.g. an
>> automatic variable)? If so, then the memory is likely clobbered by
>> the time the ISR runs.
> Not necessarily. A common method wo
On Jun 30, 2014, at 14:41 , Joel Sherrill wrote:
> Is your "struct handler_arguments" declared on the stack (e.g. an
> automatic variable)? If so, then the memory is likely clobbered by
> the time the ISR runs.
Not necessarily. A common method would be:
thread_to_process_something() {
lva
> Cc: devel@rtems.org
> Subject: Re: Function pointer within isr
>
> On 06/30/14 18:07, Gedare Bloom wrote:
> > On Mon, Jun 30, 2014 at 12:52 PM, Wendell Silva
> wrote:
> >> André,
> >>
> >> Technically, you should be able to call functions (d
On 6/30/2014 1:08 PM, Andre Marques wrote:
On 06/30/14 18:07, Gedare Bloom wrote:
On Mon, Jun 30, 2014 at 12:52 PM, Wendell Silva wrote:
André,
Technically, you should be able to call functions (directly or indirectly)
in any point of your program. AFAIK, there are only a subset of RTEMS
dire
On 06/30/14 18:07, Gedare Bloom wrote:
On Mon, Jun 30, 2014 at 12:52 PM, Wendell Silva wrote:
André,
Technically, you should be able to call functions (directly or indirectly)
in any point of your program. AFAIK, there are only a subset of RTEMS
directives you shouldn't call from an ISR.
If t
On Mon, Jun 30, 2014 at 12:52 PM, Wendell Silva wrote:
> André,
>
> Technically, you should be able to call functions (directly or indirectly)
> in any point of your program. AFAIK, there are only a subset of RTEMS
> directives you shouldn't call from an ISR.
If the function does not 'sleep' it sh
André,
Technically, you should be able to call functions (directly or indirectly)
in any point of your program. AFAIK, there are only a subset of RTEMS
directives you shouldn't call from an ISR.
What kind of error have you got? BSP?
--Wendell.
2014-06-30 13:47 GMT-03:00 Andre Marques :
> Hell
