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

Keil 8051 interrupt ISR

I'm having problems with 8051 based ISRs. The problem occures when:

1- Interrupt A is being serviced.
2- Interrupt B occures and is serviced (in the middle of ISR A execution.
3- Sometimes ISR A fails to complete.

I'm using the C ISRs used in C51 without any register set defined ("using xx"). My understanding is that the ISRs should get entered and serviced mutually exclusive from one another without corrupting one another's stack. Is this not the case?

Parents Reply Children
  • "Interrupts DO work."

    What a particularly strange statement.

    An interrupt definitely does NOT necessarily work AS REQUIRED if the coder has done something incorrect.

  • "Interrupts DO work."

    What a particularly strange statement.

    blabbering the above which is, by no means 'strange' or 'incorrect' would be something like "in the particular case you describe, the interrupts are generated correctly by the compiler/linker and thus the reason for your problem would have to be in your code."

    So, instead of typing a ton of blabber, I state the fact "interrupts DO work." and say "show your code"

    If whoever is hiding behind "John Malund" can not handle "short and concise" and want everything to be blabber, then I suggest she writes the blabber herself instead of having a cow about "short and concise".

    Erik

  • I've no problem with short and concise.

    However, additions of meaningless and superfluous baggage like your "Interrupts DO work." cannot be considered conducive to short or concise.

    You might as well say, "keyboards DO works", and "kettles DO works" and "wheels DO turn"; they'd be just as valid!

    Blabber is as blabber does.