• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 65 subscribers
  • Views 313 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

TPS6594-Q1: No correct STARTUP_DEST trigger detected in the Validate PFSM

TPS6594-Q1: A working JSON file for the TPS65941111EVM

Nimrod Tenne
Prodigy 200 points
Part Number: TPS6594-Q1

Hello,

I have the TPS65941111EVM

I configured the static configuration but I cant get the standard template for the PFSM to pass validation

Can I please get a JSON file for the TPS65941111EVM that pass validation so I can see how all the states triggers sequences on the EVM are configures

The main error I see is "No correct STARTUP_DEST trigger detected"

Thanks

  • 0 in reply to Chris Sterzik
    Prodigy 200 points

    Hello,

    I only need a JSON so I can see how to set the PFSM, I will start with the configuration that is used buy the EVM,

    I will use the EVM and add stages to power the BUCKs and LDO in  the correct order but I need a JSON so pass verification then I can start adding stages and triggers.

    I don`t see where the connection is form "STARTUP_DEST" to the PFSM is made

    Thanks

  • +1 in reply to Nimrod Tenne
    TI__Guru 64141 points

    Hello,

    Please find the attached file. https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/sample_5F00_template.json

    The connection has three main components.

    (1) The On Request event.  In this case it is the ENABLE pin on the device.  If 'None' is selected this results in what is called first supply detect 'FSD'.

     the associated interrupt should also be unmasked.

    (2) The link between the PFSM and the static settings is through the STARTUP_DEST.  In this case the on_request results in the SU_ACTIVE trigger.  Other options are SU_STANDBY and SU_MCU_ONLY.

    (3) In the PFSM the SU_ACTIVE trigger is used to transition between states.  In this example the FORCE_STANDBY=HIGH, means that the ENABLE pin is low.  What is unique about SU_ACTIVE is that this value is 'latched' in the ENABLE_INT, meaning SU_ACTIVE will always be 'HIGH' until the ENABLE_INT is cleared.  FORCE_STANDBY is the direct representation of the ENABLE pin.  There is an additional 'self-terminating' trigger of FORCE_STANDBY=HIGH in the STANDBY state and the FORCE_STANDBY=HIGH trigger is higher priority.  This combination keeps the PMIC in the standby state until the enable pin goes low.  There are a number of alternative implementations, but generally this is recommended and provides the ability to expand the implementation and take advantage of some of the other modes like MCU_ONLY and Retention (deepsleep).

    Regards,

    Chris