• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 295 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.

TPS65313-Q1: Could the PMIC device be configured to operate in the diagnostic state and work properly

khaled Mohamed
Prodigy 50 points
Part Number: TPS65313-Q1

Could the PMIC device be configured to operate in the diagnostic state instead of the active state and work properly without any limitation?
And if there are some limitations or features that are supported only in the Active state, what are theses features?

  • 0
    TI__Mastermind 19700 points

    Hi Khaled,

    as stated in data sheet section 11.13.5 DIAGNOSTIC State all the monitoring and protection functions stay enabled in the DIAGNOSTIC state. The primary purpose of DIAGNOSTIC state is for the system MCU to perform the device and system-level diagnostics. The DIAGNOSTIC state is not intended for the PMIC to stay at for long and thus the tDIAG_STATE_TO timeout is implemented. This can be masked to stay in the DIAGNOSTIC state indefinitely but this is not the intended use-case. In the DIAGNOSTIC state all the configuration registers stay open so that the MCU can write to them. In ACTIVE state these are locked so that the MCU wouldn't change any of these registers by accident causing potential misbehavior in the system which could be safety violation.

    regards,

    Niko

  • 0 in reply to Niko Alatalo
    Prodigy 50 points

    Hi Niko,

    Thanks for the clarification.

    The reason behind staying at the Diagnostic state is to be able to reconfigure the PMIC WDT window at the shutdown sequence by increasing the window size because the servicing of WDT at the shutdown sequence is different from servicing the WDT at runtime (where Tasks are scheduled).

    Is this concept valid or there are different approaches that can be taken to handle this case?

    Thanks,

    Khaled

  • 0 in reply to khaled Mohamed
    TI__Mastermind 19700 points

    Hi Khaled,

    thanks for the additional information. By shutdown sequence do you mean the shutdown of the MCU but not the PMIC and is the WAKE pin of the PMIC pulled low at some point? Would it be possible to use the same watchdog window for both runtime and shutdown or is the shutdown watchdog window too long for the runtime? Have you considered letting the PMIC to go to SAFE state at the shutdown sequence?

    regards,

    Niko

  • 0 in reply to Niko Alatalo
    Prodigy 50 points

    Hi Niko,
    Thanks for your proposals and clarification.

    Yes, by the shutdown sequence I mean the shutdown of the MCU (but not the PMIC) when the application decides that MCU should go to sleep or off.

    Yes, having the same window for both runtime and shutdown will lead to a very big window for runtime.

    Letting the PMIC to go to SAFE state at the shutdown sequence will not help the PMIC to perform automatic reaction if during the shutdown sequence the MCU has a serious error (WDT error for example).

    Regards,

    Khaled

  • 0 in reply to khaled Mohamed
    TI__Mastermind 19700 points

    Hi Khaled,

    thanks for the clarification. You could first induce a watchdog error or CRC error which would take you to SAFE state from which you get to DIAGNOSTIC state and you can reconfigure the watchdog. After this go back to ACTIVE state for the shutdown sequence. If you want to go to SAFE state with WD error you have to make sure to have WD_RST_EN = 0x0 because if its 0x1 it will take you to RESET.

    regards,

    Niko 

  • +1 in reply to Niko Alatalo
    Prodigy 50 points

    Hi Niko,

    Thanks for your reply and for your suggestions. I will consider your suggestions according to the project needs.

    Regards,

    Khaled