SLVUCI5 april   2023 AM6526 , AM6528 , AM6548 , TPS6594-Q1

 

  1.   PDN-0C User's Guide for Powering AM65x with the TPS6594-Q1 PMIC
  2.   Trademarks
  3. 1Introduction
  4. 2Device Versions
  5. 3Processor Connections
    1. 3.1 Power Mapping
    2. 3.2 Control Mapping
  6. 4Supporting Functional Safety Systems
  7. 5Static NVM Settings
    1. 5.1  Application-Based Configuration Settings
    2. 5.2  Device Identification Settings
    3. 5.3  BUCK Settings
    4. 5.4  LDO Settings
    5. 5.5  VCCA Settings
    6. 5.6  GPIO Settings
    7. 5.7  Finite State Machine (FSM) Settings
    8. 5.8  Interrupt Settings
    9. 5.9  POWERGOOD Settings
    10. 5.10 Miscellaneous Settings
    11. 5.11 Interface Settings
    12. 5.12 Watchdog Settings
  8. 6Pre-Configurable Finite State Machine (PFSM) Settings
    1. 6.1 Configured States
    2. 6.2 PFSM Triggers
    3. 6.3 Power Sequences
      1. 6.3.1 TO_SAFE_SEVERE and TO_SAFE
      2. 6.3.2 TO_SAFE_ORDERLY and TO_STANDBY
      3. 6.3.3 ACTIVE_TO_WARM
      4. 6.3.4 ESM_SOC_ERROR
      5. 6.3.5 PWR_SOC_ERROR
      6. 6.3.6 MCU_TO_WARM
      7. 6.3.7 TO_MCU
      8. 6.3.8 TO_ACTIVE
      9. 6.3.9 TO_RETENTION
  9. 7Application Examples
    1. 7.1 Moving Between States; ACTIVE, MCU ONLY, and RETENTION
      1. 7.1.1 ACTIVE
      2. 7.1.2 MCU ONLY
      3. 7.1.3 RETENTION
    2. 7.2 Entering and Exiting Standby
    3. 7.3 Entering and Existing LP_STANDBY
    4. 7.4 Runtime Customization
  10. 8References

PFSM Triggers

As shown in Figure 6-1, there are various triggers that can enable a state transition between configured states. Table 6-1 describes each trigger and its associated state transition from highest priority (Immediate Shutdown) to lowest priority (I2C_3). Active triggers of higher priority block triggers of lower priority and the associated sequence.

Table 6-1 State Transition Triggers
TriggerPriority (ID)Immediate (IMM)REENTERANTPFSM Current StatePFSM Destination StatePower Sequence or Function Executed
Immediate Shutdown0TrueFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMSAFE(1)TO_SAFE_SEVERE
MCU Power Error1TrueFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMSAFE(1)TO_SAFE
Orderly Shutdown2TrueFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMSAFE(1)TO_SAFE_ORDERLY
OFF Request4(9)FalseFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMSTANDBY(2)TO_STANDBY
WDOG Error5FalseTrueACTIVEACTIVEACTIVE_TO_WARM
ESM MCU Error6FalseTrueACTIVEACTIVE
ESM SOC Error7FalseTrueACTIVEPwr SOC ErrorESM_SOC_ERROR
WDOG Error8FalseTrueMCU ONLYMCU ONLYMCU_TO_WARM
ESM MCU Error9FalseTrueMCU ONLYMCU ONLY
SOC Power Error10FalseFalseACTIVEMCU ONLYPWR_SOC_ERR
I2C_1 bit is high(3)11FalseTrueACTIVE, MCU ONLYNo State ChangeExecute RUNTIME BIST
I2C_2 bit is high(3)12FalseTrueACTIVE, MCU ONLYNo State ChangeEnable I2C CRC on I2C1 and I2C2 on all devices.(4)
ON Request13FalseFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMACTIVETO_ACTIVE
WKUP1 goes high14FalseFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMACTIVE
NSLEEP1 and NSLEEP2 are high(5)15FalseFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMACTIVE
MCU ON Request16FalseFalseSTANDBY, ACTIVE(7), MCU ONLY, Suspend-to-RAMMCU ONLYTO_MCU
WKUP2 goes high17FalseFalseSTANDBY, ACTIVE, MCU ONLY, Suspend-to-RAMMCU ONLY
NSLEEP1 goes low and NSLEEP2 goes high(5)18FalseFalseACTIVE, MCU ONLY, Suspend-to-RAMMCU ONLY
NSLEEP1 goes low and NSLEEP2 goes low(5)19FalseFalseACTIVE, MCU ONLYSuspend-to-RAMTO_RETENTION
NSLEEP1 goes high and NSLEEP2 goes low(5)20FalseFalseACTIVE, MCU ONLYSuspend-to-RAM
I2C_0 bit goes high(3)21(8)FalseFalseSTANDBY, ACTIVE, MCU ONLYLP_STANDBY(2)TO_STANDBY
I2C_3 bit goes high(3)22(8)FalseFalseACTIVE, MCU ONLYNo State ChangeDevices are prepared for OTA NVM update.(6)
From the SAFE state, the PFSM automatically transitions to the hardware FSM state of SAFE_RECOVERY. From the SAFE_RECOVERY state, the recovery counter is incremented and compared to the recovery count threshold (see RECOV_CNT_REG_2, in Table 5-10). If the recovery count threshold is reached, then the PMICs halt recovery attempts and require a power cycle. Refer to the data sheet for more details.
If the LP_STANDBY_SEL bit is set (see RTC_CTRL_2, in Table 5-10), then the PFSM transitions to the hardware FSM state of LP_STANDBY. When LP_STANDBY is entered, then please use the appropriate mechanism to wakeup the device as determined by the means of entering LP_STANDBY. Refer to the data sheet for more details.
I2C_0, I2C_1, I2C_2 and I2C_3 are self-clearing triggers.
Enabling the I2C CRC, enables the CRC on both I2C1 and I2C2, however, the I2C2 is disabled for 2ms after the CRC is enabled. Be aware when using the watchdog Q&A before enabling I2C CRC. The recommendation is to enable the I2C CRC first, and then after 2ms, start the watchdog Q&A.
NSLEEP1 and NSLEEP2 of the primary PMIC can be accessed through the GPIO pin or through a register bit. If either the register bit or the GPIO pin is pulled high, the NSLEEPx value is read as a high logic level.
After completion of an OTA update, the processor is required to initiate a reset of the PMICs to apply the new NVM settings.
When in the ACTIVE mode, the ON Request to MCU ONLY trigger cannot be accessed while other higher priority triggers, like NSLEEP1=NSLEEP2=HIGH, are still active.
Trigger IDs 21 and 22 are not available until the NSLEEP bits are masked: NSLEEP2_MASK=NSLEEP1_MASK=1.
Trigger IDs 3, 23, and 24 are enabled and activated by the power sequences and are not shown. These triggers are used to manage the transition between the PFSM and the FSM.