Changing the way you learn

ICT2104 Chapter 4: Interrupts

CPU Processing Stages
1. RESET State: CPU and internal peripheral modules are initialised and stopped
2. Exception-Processing State: Transient state that occurs when CPU alters normal processing flow due to exception source
3. Program Execution State; CPU executes program instructions in sequence
4. Bus-Released State: Occurs when bus has been released in response to bus request from a bus master; CPU halts operations
5. Program Stop State: Power-down state which CPU stops operating
Reset and Interrupts
1. Program Execution
  1. PC: Points to next instruction to be executed
  2. SR: Subsequent instruction make use of altered values of SR to carry out branch condition
  3. SP: Storing of information that cannot be over-written within ISR
2. RESET: Allows fetching the first instruction to be executed after a power-up
  1. Other Reset Triggers
    1. Only triggers when button is released
  2. Power-On Reset
    1. Is a NMI
    2. Reset Signal must be active for at least 2us
IVT and Priority
1. Reset Address
  1. Fixed Vector
  2. Auto-Vectored
MSP430 port interrupt registers
1. Types
  1. NMI: Cannot be disabled by GIE; Used for high priority events
  2. MI: GIE must be set, can be switched off by software
2. Interruptible Ports: Port 1 & Port 2
  1. PxIFG: Interrupt Flag
    1. Bit 1: Interrupt pending
    2. Bit 0: No interrupt pending
  2. PxIE: Interrupt Enable
    1. Bit 1: Interrupt enabled
    2. Bit 0: Interrupt disabled
  3. PxIES: Interrupt Edge Select
    1. Bit 1: Falling Edge
    2. Bit 0: Rising Edge
3. #pragma vector = PORTx_VECTOR
4. During interrupt event
  1. PC points to next instruction and is pushed with SR to stack
  2. SR is cleared (except SCG0) and GIE flag
  3. RETI returns to original program flow, pops SR and PC
5. ISR processing time should be < interrupt's request time interval
  1. To avoid stack overflow, collapsing program
6. Interrupt Latency: Time between event beginning and ISR execution
Interrupt identification and priority determination
1. Identification Methods
  1. Non-vectored
    1. Unable to identify which device directly
    2. CPU has to check which device within ISR
  2. Vectored-Based
    1. Auto-Vectored
      1. Vector number is predefined by assigning an interrupt to a vector number
      2. Generated internally by CPU
      3. Only one IRQ line, no acknowledgement
      4. Only 1 interrupt / IRQ line
    2. Full-Vectored
      1. Can be supplied by device itself
      2. Provided by device
      3. IRQ + IACK lines: Handshake logic
      4. Flexible as device can send different #
      5. Can have > 1 IRQ line
    3. Each interrupt is uniquely identified with a different vector number
    4. More flexible in providing priority and masking of bits
    5. Requires a lot of hardware resources to resolve additional issues (i.e. masking)
2. Priority Handling
  1. Daisy Chain
    1. The closer it is to CPU, the higher the priority
    2. Hardwired, difficult to balance services among devices
  2. Interrupt Controller
    1. Programmable support peripheral, allows handling of requests from multiple devices
    2. Flexible in terms of priority management
Interrupt processing stages and latency
1. Stages
  1. 1. Complete any currently executing instructions
  2. 2. Push PC to stack
  3. 3. Push SR to stack
  4. 4. Select highest priority interrupt if multiple interrupts occured
  5. 5. IFG resets automatically on single-source flag. Otherwise, IFG remain set.
  6. 6. Clear all bits of SR (except SCG0) and GIE.
  7. 7. Load content of interrupt vector into PC; continues ISR.
2. Latency
  1. At least 6 clock cycles before ISR executes (see stages)
  2. RETI requires 5 cycles
    1. 1. Pop SR and GIE from stack
    2. 2. Pop PC from stack and continues execution from where it was interrupted
Interrupt driven I/O
1. Maximum interrupt handler execution time permitted: Time between each interrupt
Multiple interrupts and interrupt nesting

Next up

ICT2104 Chapter 4: Interrupts

Description

Resource summary

Similar

	Created by Meixi Lim about 9 years ago