STDA066 November   2026 DRA821U , DRA821U-Q1 , TDA4AEN-Q1 , TDA4VEN-Q1 , TDA4VH-Q1 , TDA4VL-Q1 , TDA4VM , TDA4VM-Q1 , TDA4VP-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 GPIO in Automotive Applications
    2. 1.2 The J7 GPIO Virtualization Solution
  5. 2GPIO Hardware Architecture
    1. 2.1 GPIO Module Structure
    2. 2.2 GPIO Instances Across J7 Devices
  6. 3GPIO Interrupt Modes
    1. 3.1 Bank Interrupt Mode
    2. 3.2 Line (Per-Pin) Interrupt Mode
    3. 3.3 The BINTEN Register — A Critical Hardware Constraint
    4. 3.4 Interrupt Mode Comparison
  7. 4GPIO Virtualization Architecture
    1. 4.1 The Virtual GPIO Concept
    2. 4.2 The PADCONFIG VGPIO_SEL Field
  8. 5Interrupt Routing Architecture
    1. 5.1 The GPIO Interrupt Router
  9. 6Multi-Core GPIO Virtualization — Validated Scenario
    1. 6.1 Test Configuration
    2. 6.2 Observed Results
  10. 7Conclusion
  11. 8References

The Virtual GPIO Concept

All GPIO module instances within the same power domain — for example WKUP_GPIO0 and WKUP_GPIO1 in the WKUP domain — are mapped to the same physical I/O pins. The silicon does not dedicate different pins to different instances. Instead, a per-pin selector in the PADCONFIG register determines which interrupt path of an instance is active for each individual pin.

This is the GPIO virtualization mechanism and enables:

  • Isolation: Core A uses WKUP_GPIO0 to monitor Pin 6; Core B uses WKUP_GPIO1 to monitor Pin 3. Each core interacts with a separate module instance and receives independent interrupts.
  • Freedom from interference: The hardware mux prevents the interrupt traffic of one instance from polluting the interrupt path of another instance.
  • Independent software ownership: Each GPIO module instance has a register space, a TISCI device ID, and interrupt router connections.