Assertion: interrupt | /r/HasProperty | serviced
Facets:
Source sentences:
text: The system has authority to decide which conditions are allowed to interrupt the CPU, while some other interrupt is being serviced.
text: The most that an interrupt (service) routine might do would be to remember that the red button was pressed.
text: Every ISR should clear the interrupt flag (clear the appropriate bit of IFSx to zero), indicating that the interrupt has been serviced.
text: Therefore the time for an interrupt to be serviced would be extended by the length of time interrupts were turned off.
text: Let’s suppose that none of the three cases holds, so the interrupt has to be serviced.
text: wait for the interrupt to be serviced if more data needs to be send
text: The CPU is now free to work on another piece of software but can return to what it was doing after the interrupt has been serviced because it has saved where it was.
text: you probably clear the interrupt bit as first thing: if the level stays low the hardware immediately triggers another interrupt that will be serviced just when you are finished with this.
text: Therefore the time for an interrupt to be serviced would be extended by the length of time interrupts were turned off.
text: Interrupts have priority over normal code found in the main loop function, but what happens when another interrupt is detected while an interrupt is being serviced?