• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 22 subscribers
  • Views 735 views
  • Users 0 members are here
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

Interrups Do not Trigger User Code ISR's

Jim Maidhof

I am running a piece of code that has ISR's (ie timer, serial)
When I generate interrupts.. say by writting to the SBUF register
I get the data in the SERIAL I/O window and it shows an interrupt occurred..
but my program does not vector to the ISR. What could be happening. I have all the interrupts enabled.

Parents
  • 0

    Without "piece of code" no ideas.

    Also, where you test ?
    - in dScope simulator ?
    - target board with MON251 ?
    - target board with ICE ?
    - target board with x251-chip ?


    If your code true (all interrupts enabled, etc...),
    there is only one reason why serial-ISR don't vectored:
    - your program stay (or clear RI/TI before RETI) in another higher-priority ISR.

Reply
  • 0

    Without "piece of code" no ideas.

    Also, where you test ?
    - in dScope simulator ?
    - target board with MON251 ?
    - target board with ICE ?
    - target board with x251-chip ?


    If your code true (all interrupts enabled, etc...),
    there is only one reason why serial-ISR don't vectored:
    - your program stay (or clear RI/TI before RETI) in another higher-priority ISR.

Children
No data