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

Program an Existing NVM Configuration

The NVM Configuration page can also be used to program a device with an existing NVM Configuration in the assembly or binary format. The process is simply to start at the beginning of the page and choose which type of device to program by clicking the device icon, as shown in Figure 8-31. Once a device is chosen, click the Skip to Programming button to go directly to the programming page.

GUID-6FBC95C6-8054-49A2-9C47-F86DADEFA18A-low.png Figure 8-31 Skip to Programming with an existing NVM Configuration

The programming perspective has changed slightly from what was described in Section 8.2. As shown in Figure 8-32, only the Uploaded Program File tab is available, the save options are disabled, and the Select Device reflects the device selection at the beginning. The interface selection should match the device being programmed. If the interface is not setup correctly the connection indicator at the bottom of the screen will reflect that the Hardware not Connected. Failed to connect and any attempt to Verify Connection will fail. Once the correct(1) device is connected and the file to program selected, click Verify Connection and then Program Device.

GUID-77774B7E-63E1-4710-961E-F06603673AC5-low.png Figure 8-32 Program with an Existing Configuration
When multiple devices are connected to the AEVM, ensure that for I2C that the address is that of the device to be programmed. In the case of SPI, make sure that the chip select is connected to the device to be programmed.