SLVUBT8B November   2020  – June 2022 LP8764-Q1 , TPS6594-Q1


  1.   Scalable PMIC's GUI User’s Guide
  2.   Trademarks
  3. Introduction
  4. Supported Features
  5. Revisions
  6. Overview
  7. Getting Started
    1. 5.1 Finding the GUI
    2. 5.2 Downloading the Required Software
    3. 5.3 Launching the GUI
    4. 5.4 Connecting to a PMIC
  8. Quick-start Page
    1. 6.1 Device Scan Results
    2. 6.2 Configuration and Monitoring
      1. 6.2.1 System Info
      2. 6.2.2 BUCK
      3. 6.2.3 LDO
      4. 6.2.4 GPIO
      5. 6.2.5 Interrupts
      6. 6.2.6 Miscellaneous Settings
      7. 6.2.7 Advanced
  9. Register Map Page
  10. NVM Configuration Page
    1. 8.1 Creating a Custom Configuration
      1. 8.1.1 Static Configuration
      2. 8.1.2 Pre-Configurable Mission States (PFSM)
        1. Creating a State Diagram
        2. Global Settings
        3. Power Sequence
          1. Power Sequence Resources and Commands
          2. Sub-sequences
          3. Power Sequence Editing Tools
        4. Trigger Settings
        5. Trigger Priority List
        6. PFSM Validation
    2. 8.2 Program
      1. 8.2.1 Program an Existing NVM Configuration
      2. 8.2.2 NVM Configuration Special Use Case: Changing the Communication Interface
      3. 8.2.3 Lock Option During NVM Programming
  11. NVM Validation Page
  12. 10Watchdog Page
  13. 11Additional Resources
  14. 12Appendix A: Troubleshooting
    1. 12.1 Hardware Platform Not Recognized
    2. 12.2 PMIC Device Not Found
    3. 12.3 I2C2 is configured but not connected
  15. 13Appendix B: Advanced Topics
    1. 13.1 Scripting Window
  16. 14Appendix C: Known Limitations
  17. 15Appendix D: Migration Topics
    1. 15.1 Migrating from LP8764-Q1 PG1.0 to PG2.0
    2. 15.2 Update the PFSM to Include the PFSM_START State
    3. 15.3 Update Timing Delays
    4. 15.4 Update Trigger Priority and Settings
  18. 16Revision History

Power Sequence

Power sequences are dependent upon the target state definition, and therefore it is required to define the state in the global settings before creating a power sequence. Most sequences apply to the transition to a specific state. Some sequences can be made target state agnostic, so that the same sequence can be reused in multiple states. These sequences require that the target state selected be 'ANY' and mapped only to transitions which are self terminating as shown in Figure 8-15 and Figure 8-16.

GUID-20220601-SS0I-HK2B-0JBS-LPP45RGD7CBG-low.png Figure 8-15 Target State set to ANY
GUID-20220601-SS0I-LCTQ-BW0V-ZST13WZDFKLT-low.png Figure 8-16 Self-Terminating Transition and Trigger Association

In addition to the target state, there are options to select the sequence type. The sequence types Power Up, Power Down, and Reset come pre-populated with ACTIVATE and or DEACTIVATE commands based upon the sequence type. The Power Down and Reset types are not recommended for use in multi-PMIC applications. Please see the DEACTIVATE descirption, 16, for a discussion on how to properly power down multiple PMICs. All sequence types have the TRIG_MASK pre-populated. These commands are described in Section

The To Safe sequence type is a new means to identify which sequences lead to the SAFE_RECOVERY state. Functionally this selection has no impact, but it does alert the PFSM validation routine to inspect the sequence for required instructions before entering SAFE_RECOVERY.

Once a new sequence has been created, then the sequence name is added to the list of sequences (see Figure 8-17), and the sequence can be edited (lightning bolt), updated (pencil), or deleted (‘X’). The update simply allows the name of the sequence to be updated as well as the target state. Using the edit icon will open a new window as shown in Figure 8-18.

Figure 8-17 How to Add a Sequence
GUID-20200813-CA0I-F5XN-JNSH-KZLPLP78WNJH-low.png Figure 8-18 Power Sequence Command Window

From this window, commands for each PMIC can be added and the timing relationship between each command is represented. Arrows are provided to move commands within the sequence.

Note: Delays in the ADD ACTION or UPDATE ACTION windows are relative to the previous action. Delays shown in the Power Sequence Commands list are relative to the start of the sequence.

There is a distinction between commands which have Rail Connections and commands which do not. The commands with Rail Connections are typically representative of physical outputs from the device and voltage monitors. The Rail Connections are what will appear in the power sequence diagram as described in section Section The names of the Rail Connections are editable and can be updated to more meaningful names related to the application.

Initially, the trigger masks for each device are provided. As additional commands are added, they will always be placed above the trigger masks. The trigger masks can be moved in the sequence order, but typically these are the last commands in the sequence. The trigger mask at the end of the power sequence is automatically generated based upon the available triggers of the destination state. This mask can be edited to mask triggers from triggering a power sequence and a state change. Before editing the mask. it is recommended to define the triggers as described in the Section