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

Static Configuration

The Static Configuration perspective provides a similar interface as to what is found in the Quick-start page. The recommended flow is to start with the System Info tab on the far left, updating each block within the System Info tab and then proceeding to the next configuration tab. In a multi-device system, simply select the device to be configured from the Select a device to configure drop-down menu at the top left of the page.

Within each block are a list of registers and fields which directly match the device register and field names. It is recommended to use the data sheet specification to understand and properly set the field values for a given application. Within the BUCK blocks there is an additional graphical selection tool, see Figure 8-4, to abstract the register settings into the use cases also described in the device data sheet. The graphical selection tool will appear in the far right column of the display, providing the Configuration Use case name as well as the recommended inductor value.

GUID-20200813-CA0I-THT4-V8PH-QPWC0C91QN3V-low.png Figure 8-4 BUCK Static Configuration
Note: Only one device is visible at a time. Be sure that all devices in the application are defined.

Within the Static Configuration perspective, the GUI is monitoring the validity of the configuration. Specifically, for multi-device solutions the GUI is making sure that both the power (VCCA and nPWRON) and interface selections match. By clicking on the Validation Failed text at the bottom of the perspective a pop-up window, as shown in Figure 8-5, will describe all of the issues which are invalid and preventing the next stage of the development.

GUID-20200813-CA0I-0B3C-FVQ3-SM1NVL80KXSP-low.png Figure 8-5 Static Configuration, Failed Verification

In this example, all three devices have the same I2C address(es). After updating each device to a unique address, the GUI now shows Validation Success and the Define PFSM button is now active.

GUID-20200813-CA0I-JSZP-GNVT-ZN6KJDLNNMMT-low.png Figure 8-6 Static Configuration, Passing Verification

In addition to the check of the static settings, in devices which support functional safety, there is an additional check of the safety related features. By clicking on the Functional Safety Assumptions not met text, a pop-up window, as shown in Figure 8-7, displays. The window lists the parameters related to the device’s functional safety assumptions. Refer to the device's functional safety manual and the application’s functional safety goals, to confirm that the selected settings meet their functional safety target.

GUID-AEDBA26B-AAA1-4E6F-BC2B-29F46DB7CC5F-low.png Figure 8-7 Function Safety Assumptions Check

When transitioning to the PFSM perspective from the static settings if any values were not updated, then a warning message will appear. Values that are not updated will appear with a yellow highlight around the value. In this example, only the I2C addresses have been updated. Texas Instruments recommends reviewing and confirming all settings that are highlighted as unchanged.

GUID-20200813-CA0I-HTBX-SJQH-FDZHWCGG6HMW-low.png Figure 8-8 Example of non-updated Static Configuration Values
Note: The GUI does not provide an auto-save feature. Save often using the Save Configurations below the File tab shown in Figure 8-9.
GUID-20200813-CA0I-D9LM-SMNF-DKTQTV2DBF2J-low.png Figure 8-9 Save Often