ATmega32 AVR单片机如何扩展中断引脚？能否转普通引脚为中断？

Hey there, let's break down your question about getting more interrupts out of the ATmega32—since the built-in INT0, INT1, INT2 aren't enough, we've got a few solid options to explore.

Can you convert any general-purpose pin to an interrupt pin? #

Short answer: Not exactly "any pin" as a dedicated external interrupt, but you can use Pin Change Interrupts (PCINT) to get interrupt functionality from most GPIO pins. Here's how it works:

• The ATmega32 has three PCINT groups: PCINT0 (PORTA pins), PCINT1 (PORTB pins), PCINT2 (PORTC pins). Each group triggers an interrupt when any pin in the group changes state (rising or falling edge, depending on your setup).
• You'll need to configure the relevant registers:
  • Enable the PCINT group via PCICR (e.g., set PCIE0 to enable PORTA's pin change interrupts).
  • Use PCMSK0/PCMSK1/PCMSK2 to mask specific pins in the group (so only the pins you care about trigger the interrupt).
• In the interrupt service routine (ISR), you'll have to read the port's pin state to figure out which specific pin caused the interrupt.

Example snippet to enable PCINT on PORTA pin 0:

#include <avr/interrupt.h>

void setup_pcint() {
  PCICR |= (1 << PCIE0);    // Enable PCINT0 group (PORTA)
  PCMSK0 |= (1 << PCINT0);  // Enable interrupt on PORTA pin 0
  sei();                    // Enable global interrupts
}

ISR(PCINT0_vect) {
  if (PINA & (1 << PA0)) {
    // Handle rising edge or high state on PA0
  } else {
    // Handle falling edge or low state on PA0
  }
}

Note: PCINTs are level-change triggered by default—you'll need to handle edge detection manually in the ISR if that's what your project requires.

Other ways to expand interrupt count #

If PCINTs don't meet your needs (e.g., you need edge-specific triggers without manual handling, or more independent interrupts), try these methods:

• Timer Input Capture: The ATmega32's Timer1 has an input capture pin (ICR1, PB1). This can be used to detect rising/falling edges on that pin as an interrupt, adding one more dedicated interrupt source for pulse-based signals.
• External Interrupt Expanders: Use chips like the 74HC148 (priority encoder) to multiplex up to 8 input signals into 3 output lines that feed into your existing INT0-INT2 pins. In the interrupt, you read the encoder's output to identify which input triggered the interrupt. For more flexibility, I2C/SPI GPIO expanders (like PCF8574 or MCP23017) can add dozens of GPIO pins, and most have an interrupt output that alerts the ATmega32 when any pin state changes—you then read the expander's register to find the source.
• Software Polling: If real-time response isn't critical, you can periodically scan your general-purpose pins for state changes. This isn't true interrupt-driven, but it's a low-cost workaround for non-time-sensitive applications.

Should you switch to a different AVR MCU? #

If all the above workarounds are too limiting (e.g., you need multiple independent, low-latency edge-triggered interrupts), it might be time to upgrade. Consider these AVRs:

• ATmega128: Offers 4 external interrupts (INT0-INT3) plus more PCINT groups, giving you more dedicated interrupt pins.
• ATmega2560: Has 6 external interrupts (INT0-INT5) and a massive number of GPIO pins, along with more advanced peripherals—great for projects needing lots of interrupts and I/O.

内容的提问来源于stack exchange，提问作者Mohamed Emad