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

 

  1.   Scalable PMIC's GUI User’s Guide
  2.   Trademarks
  3. 1 Introduction
  4. 2 Supported Features
  5. 3 Revisions
  6. 4 Overview
  7. 5 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. 6 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. 7 Register Map Page
  10. 8 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. 8.1.2.1 Creating a State Diagram
        2. 8.1.2.2 Global Settings
        3. 8.1.2.3 Power Sequence
          1. 8.1.2.3.1 Power Sequence Resources and Commands
          2. 8.1.2.3.2 Sub-sequences
          3. 8.1.2.3.3 Power Sequence Editing Tools
        4. 8.1.2.4 Trigger Settings
        5. 8.1.2.5 Trigger Priority List
        6. 8.1.2.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. 9 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
8.1.2.3.2 Sub-sequences

Sub-sequences are groups of commands within the power sequence and are associated with the JUMP or WAIT instructions. Functionally, the sub-sequence is simply a destination label for the JUMP or the WAIT statements to jump to. Graphically, the sub-sequence can be used to group commands and then the entire group can be moved within the power sequence. In Figure 8-19, the WAIT instruction is used to test GPIO1, if GPIO1 is high, then the timeout occurs and the execution jumps to the SKIPBUCK5 label and continues execution. Specifically, if GPIO1 is low then BUCK5 is enabled, if GPIO1 is high, then the regulator is not enabled. Figure 8-20 shows that there are no instructions within the sub-sequence. Instructions placed within or after the sub-sequence will be chronologically equivalent. Again, the main benefit of placing instructions within the sub-sequence is to logically group the commands and then to move them as a group when needed.

GUID-20200813-CA0I-RDL2-KX8H-MXPKFGN49WBV-low.png Figure 8-19 WAIT Command Action
GUID-20200813-CA0I-LTNW-FQ99-LGQFPJ2CXVMK-low.png Figure 8-20 Empty Sub-Sequence
Note: WAIT and JUMP statements can only jump forwards in the sequence of commands. The destination can never be placed before the JUMP or WAIT statement.