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.

TIDA-020047: PMIC not working

Part Number: TIDA-020047

Tool/software:

Hi,

We produced the TIDA-020047 reference design and we are facing issue related to PMIC which is not outputting the following voltages: 1.8V, 1.2V and 1.0V .

We checked the following test points and its OK:

  • 12V exists at TP9
  • 3.3V exists at TP42

But we didn't find voltages from PMIC output in J9 connector at:

  • 1.8V at pin 1/4 
  • 1.2V at pin 7/10
  • 1.0V at pin 25/28

We already pulled GPIO2 of PMIC to GND via 10K ohm resistor to trigger watchdog.

Could you help us to fix this issue is there any missing instructions that we should perform to make the PMIC outputting the needed voltages ?

Thanks.

Best regards.

  • Hello,

    The PMIC watchdog defaults to ON. So, it needs to be serviced or disabled for the power supply to remain ON.  This can be done with a pull down on PMIC_GPIO2, or by a SPI write to the PMIC.  This must be done within 500 ms from reset release.

    I understand you are opting to disable watchdog with 10k resistor.  What is the voltage at PMIC GPIO2?  Since R36 is 10k, I think your pull-down resistor will need to be stronger.  I would recommend 1k.  This will disable the PMIC watchdog.  

    Also, the TCAN1043A contains a TSW timer. If nSTBY and EN are not ON within 4 minutes, the transceiver goes to sleep and shuts down the pre-regulator.  So, in your software you need to ensure that these items are included:

    1. SoC to service PMIC Watchdog or Disable Watchdog over SPI within 500 ms from reset release. (unless using the 1k pulldown to disable watchdog)
    2. SoC to write SPI command to PMIC to cause PMIC_GPIO1 (CAN_nSTBY) to be high.
    3. SoC to enable TCAN by driving high CAN_EN (pin C17)
    4. Buck 4 needs to be enabled for 2-chip operation. This is the RF supply for FE2. 

    In addition, please:

    Check that R216 is not installed.

    Check that R218 is not installed.

    Regards,

    Brian

  • Hi Brian,

    Thanks for the  answer, it resolved my issue.