3.3. Power Management

• 3.3.1. Power Management Overview
• 3.3.2. CPUIdle
• 3.3.3. Low Power Modes
  • 3.3.3.1. Overview
  • 3.3.3.2. RTC Only Plus DDR
  • 3.3.3.3. DeepSleep
  • 3.3.3.4. Memory Usage
• 3.3.4. Wakeup Sources
  • 3.3.4.1. Real-Time Clock (RTC)
  • 3.3.4.2. MCU GPIO
  • 3.3.4.3. WKUP GPIO
  • 3.3.4.4. Main I/O Daisy Chain
    • 3.3.4.4.1. Main UART
    • 3.3.4.4.2. Main GPIO
  • 3.3.4.5. WKUP UART
  • 3.3.4.6. USB Wakeup methods
    • 3.3.4.6.1. Host Mode Wakeup Events
      • 3.3.4.6.1.1. Wakeup via a device connect event
      • 3.3.4.6.1.2. Wakeup via a device disconnect event
      • 3.3.4.6.1.3. Via Remote wakeup event
    • 3.3.4.6.2. Device Mode Wakeup Events
      • 3.3.4.6.2.1. Wakeup via connect event
  • 3.3.4.7. MCU IPC based Wakeup
  • 3.3.4.8. CAN UART I/O Daisy Chain
  • 3.3.4.9. RTC Ext Pin
  • 3.3.4.10. Confirming the Wakeup event type
• 3.3.5. Debug Information
  • 3.3.5.1. Low Power Modes
    • 3.3.5.1.1. Overview
    • 3.3.5.1.2. Prerequisites
    • 3.3.5.1.3. Step 1: Enable Low Power Logs in Board Configuration
    • 3.3.5.1.4. Step 2: Remove I/O Isolation and Enable Logging in TF-A
    • 3.3.5.1.5. Generating logs and running the parser script
      • 3.3.5.1.5.1. Step 1: Prepare the EVM terminal
      • 3.3.5.1.5.2. Step 2: Set up the parser script on host
      • 3.3.5.1.5.3. Step 3: Run and capture logs
      • 3.3.5.1.5.4. Alternative: Direct terminal output
    • 3.3.5.1.6. Troubleshooting: Parser errors
    • 3.3.5.1.7. Interpreting the logs
    • 3.3.5.1.8. Additional information: Decoding driver failures during suspend