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. 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. 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

Trigger Settings

The maximum number of triggers available is 28. Please refer to the device specification for the usage of reserved triggers. The GUI will ensure that the maximum number of triggers is not exceeded and manage the usage of triggers across devices in a multiple PMIC application.

The trigger settings identify what triggers will move the PMIC operation from one state to another. In the context of the GUI, the arrows between states (or arrows looping back to the same state) must have at least one trigger definition. An example is used to outline the steps configuring the trigger settings. For this example, the IMMEDIATE_SHUTDOWN going high on any device will trigger all devices to execute a power down sequence and then transition to the SAFE state, which in turn will automatically transition all devices, without power sequence, to the hardware state SAFE_RECOVERY, to reset the devices. The following steps are how to setup this example.

  1. Select the transition between the STANDBY and SAFE states, by clicking on the transition in the diagram.
    Figure 8-23 Trigger: STANDBY to SAFE
  2. In the From States add ACTIVE, PFSM_START, and WAIT4ENABLE. (1)
  3. In the 'Add Devices' select Any, so that all devices appear in the window(1).
  4. From the Trigger Source drop-down menu, select IMMEDIATE_SHUTDOWN.
  5. From the Trigger Type drop-down menu, select HIGH.
  6. Select the Immediate check box. This means that the trigger can happen immediately and does not wait for the current sequence to finish.
    Figure 8-24 Trigger: STANDBY to SAFE (continued)
  7. Click ADD
  8. Now click on the transition between SAFE and SAFE_RECOVERY. No action is required as this trigger is populated automatically.
Note: Since SAFE_RECOVERY is a hardware state the trigger will not have an associated power sequence. This is indicated by the EXT attribute in the trigger description. Similarly, the RUNTIME_BIST will also have the EXT attribute.
Figure 8-25 Trigger: SAFE to SAFE_RECOVERY

At the bottom of the TRIGGER SETTINGS, highlighted in Figure 8-25, is a summary of the trigger(s) associated with a transition. A scroll bar is provided to see the bottom of the pane. The last step is to associate a power sequence with the transition. Since SAFE_RECOVERY is a hardware state, the EXTERNAL flag is set and no sequence is needed in the transition to SAFE_RECOVERY. The transitions to SAFE, however, do require a sequence. Making the association between the trigger and the sequence is listed in the following instructions.

  1. Click on the transition between STANDBY and SAFE (or ACTIVE and SAFE).
  2. Click the lightning bolt icon. A window displays showing all of the sequences which have the same destination or target state. In this case there is only one, any2safe.
    Figure 8-26 Mapping a Sequence to a Trigger
  3. Select the sequence and then click MAP TO TRIGGER. The Trigger Setting for the transition is now complete.
    Figure 8-27 Completed Trigger Settings

Once all of the transitions have been assigned triggers and all of the triggers have been associated with power sequences, then the default TRIGGER MASKS within the power sequences will be updated. Please note the various components and relationships discussed to this point:

  1. States

    The states are either hardware or mission states.

  2. Transitions

    Transitions have a source and target state. Transitions can have multiple triggers but require at least one. Transitions to the same target state can share the same trigger.

  3. Triggers

    Available triggers are defined in the device specification. Each trigger can have only one power sequence associated with it. Multiple triggers can share the same power sequence. In the special case that the transition target state is a hardware state, the trigger type is EXT and there is no power sequence.

  4. Power Sequences

    Power sequences are defined in terms of the target state and therefor can potentially be associated with multiple triggers or transitions. Within the power sequence is the trigger mask. The automatic trigger mask is defined by all transitions from the target state and the triggers defined in those transitions. Manual trigger masks can be used to create custom trigger masks. In the TRIG_MASK command there is an option to select either an automatic or a manual trigger mask.

The Reuse Trigger button is an alternative option. Step 2 is omitted. After step 7, the other transitions to the SAFE state are selected. At this point the 'Reuse Trigger' button is selected and then the same trigger used for the STANDBY to SAFE is selected.
While an example, Texas Instruments recommends that the IMMEDIATE_SHUTDOWN trigger be present in all devices. For other triggers, it is acceptable that the trigger is present in only one device.