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

Creating a Custom Configuration

The NVM Configuration page does not require hardware to develop an NVM configuration. Connection with an actual device is needed only when attempting to upload to a target device.

There are three mechanisms available to start development. The first is to use the Open Configuration feature,below the File tab at the top of the screen, to open a configuration previously saved with the Save Configuration feature below the same File tab. Second, standard configurations are also provided as templates and can be selected below the Select a template to start with. Figure 8-1 shows the initial Select view with the upload and template mechanisms selected.

GUID-20200813-CA0I-QH0M-XT0J-FFKVRTKBZ0DK-low.png Figure 8-1 Open an Existing Configuration

Finally, device icons are provided on the left-hand-side which can be selected to create a single or multi-PMIC application, as shown in Figure 8-2. As devices are added the Device Name can be edited and the primary/secondary selection can be made. The GUI requires unique device names and only one primary.

GUID-6FBC95C6-8054-49A2-9C47-F86DADEFA18A-low.png Figure 8-2 Starting from a blank template

Once the configuration is uploaded or the devices for the application selected, the development flow will move through the Static Configuration and PFSM perspectives and then finally to the Program perspective as highlighted in Figure 8-3. Section Section 8.2.1 will describe how to program an existing NVM Configuration using the Skip to Programming option found at the bottom of Figure 8-3.

GUID-20200813-CA0I-72LD-7GK0-K2KXVVC15JQ4-low.png Figure 8-3 Configuration Development Flow
Note: It is not recommended to change or edit the selected devices of an existing configuration, with the exception of the device name. Doing so can break dependencies found in the PFSM. If during development it is discovered that the number or type of devices was defined in error, then a new configuration, restarted from a blank or existing template, is required.