SPRUIY2 November 2024 F29H850TU , F29H859TU-Q1
There are certain CPU pipeline conditions that cause an uninteruptible boundary for the CPU. These conditions prevent entry of interrupts until the conditions are over, effectively blocking interrupts during the hold time. Table 3-2 explains these situations:
Condition Description | INT Blocked | RTINT Blocked | NMI Blocked |
---|---|---|---|
Conditional instructions in packet not all completed | Yes | ||
Discontinuity instruction delay slot not completed | |||
Multicycle instructions like branch, call, return not completed | |||
For CALL.PROT instruction: first instruction at the call destination not executed | |||
For RET.PROT instruction: first instruction of the return address not executed | |||
The first instruction of the previous asserted interrupt has entered the D2 stage | |||
CPU "pipeline ready" not asserted | |||
CPU pipeline stalled due to memory RD/WR access | |||
CPU pipeline stalled due to no instruction in the instruction buffer | |||
Instruction packet stalled in D2 phase of pipeline due to pipeline hazard, but the packet is not ready to move to R1 phase of pipeline. | |||
LP Interrupt is disabled in DSTS.INTE | Yes | NO | |
ATOMIC instruction counter not completed | Yes | NO |