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

Hardware Platform Not Recognized

GUID-FAED4302-873D-42A5-BDD8-EA9DDFE2734D-low.png Figure 12-1 Hardware Platform Error

The GUI will automatically connect to the AEVM (micro controller with the analog evm controller firmware) and then to the PMIC. Typically, if the GUI cannot find the hardware platform this is due to either a faulty USB connection or the GUI is attempting to connect to the wrong communication (COM) port. The hardware platform will enumerate as three devices; two CDC classes and one DFU class. From another program, like the device manager in windows, the user can verify which COM port is the ACCtrl and which is the ACCtrl Console. From the GUI option, the user should select the COM port number of the ACCtrl and not the ACCtrl Console. The AEVM supports a baud rate of 115200.

Other devices connected to the PC, may also enumerate at CDC class devices and the GUI may attempt to communicate with these devices. If no response is made from the device, then it is possible that the GUI will not attempt to connect to other devices until the current device responds.

Only one AEVM should be connected to a host (MAC of PC) at one time. The GUI does not support the ability to handle and respond to multiple AEVM devices connected to the host.