• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 21 subscribers
  • Views 1143 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

problem about function calling in ISR

Carl Armstrong

I call some sub-routine in ISR. And I mark the ISR as "using 1". But I find out this will lead to the error of parameters passing from ISR to the sub-routine. How come?

Parents
  • 0 in reply to erik malund

    Erik,

    That is not the best way. Each function that has a using will save the PSW on the stack (which is a waste). Restoring the PSW from the stack destroys any return value of type bit. Using REGISTERBANK is simpler.

    For example:

    #pragma REGISTERBANK(1)

bit functionone(void)
{
    return( 1 );
}

void functiontwo( char c )
{
    ...
}

myISR interrupt n using 1
{
    if( functionone() ) functiontwo( 'c' );
}

Reply
  • 0 in reply to erik malund

    Erik,

    That is not the best way. Each function that has a using will save the PSW on the stack (which is a waste). Restoring the PSW from the stack destroys any return value of type bit. Using REGISTERBANK is simpler.

    For example:

    #pragma REGISTERBANK(1)

bit functionone(void)
{
    return( 1 );
}

void functiontwo( char c )
{
    ...
}

myISR interrupt n using 1
{
    if( functionone() ) functiontwo( 'c' );
}

Children