• State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 20 subscribers
  • Views 4852 views
  • Users 0 members are here
Options
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

Switch Statement in ISR

Jeremy Brookley

Hello everyone,

I am using the PGA400 from Texas Instruments (an 8051W processor) with uVision V4.02 and have traced an issue back to using a switch statement in the commBuff ISR. It appears to either have corrupted or overflowed some sort of variable (this might not be the case but that's what it appears to have done). I've replaced it from:

        switch (CommandState)
        {
                case (0):
// random code here
                break;
        }

to:

        if(CommandState==0)
        {
// random code here
        }

This seems to have fixed my problem for whatever reason. Is it a common practice to avoid using switch statements in an ISR or is this a Keil related issue? Any help you can give me would be appreciated. Thanks a lot!

0