• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 63 subscribers
  • Views 207 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:

TPS65219: Reprogramming the TPS65219

TPS65219: Issues programming NVM after RV

Justin Loundagin
Prodigy 30 points
Part Number: TPS65219
Other Parts Discussed in Thread: AM623

Tool/software:

I am using the TPS6521901 and there is an RV that occurs on BUCK2. BUCK2 is programmed to be 3.3v, however it drops to 2.6V after 20ms.

The device is not in a valid state and seems to be stuck in a "transition state" when I read register 0x35.

I need to reprogram the NVM over I2C however it seems that changes are not sticking to memory after power cycle. I assume this is because the device is not in a valid state. Is there a way to force the TPS6521901 to not power up on FSD without programming the NVM? I know that the EN is ignored on power on, but is there any other work around?

Any ideas on how program the NVM while the device is stuck in this "transition" state?

Thanks

  • 0
    TI__Mastermind 22156 points

    Hi,

    Thanks for reaching out. If FSD is enabled by default, the device ignores the state of the EN/PB/VSENSE pin until the power-up sequence is complete (until nRSTOUT is released). To re-program a custom NVM, we recommend using the TPS6521905 (user-programmable). 

    What SoC or processor are you powering with our PMIC? We can provide technical support for a PMIC schematic review and help create a NVM configuration file.  

    Thanks,

    Brenda

  • 0 in reply to Brenda Diaz
    Prodigy 30 points

    We are using the PMIC to power the AM623. The issue is that the power up was intermittent, and would sometimes fail. The PMIC is connected to another processor over I2C. On a successful power up I reprogrammed the PMICs BUCK2_SEQUENCE to use slot 1 instead of 0. After doing so, the power up fails every time, and I cannot reprogram the PMIC due to its invalid state.

    I am trying to determine if there is a work around to allow me to reprogram the BUCK2_SEQUENCE back to slot 0, or if the PMIC is "bricked" and it needs to be replaced.

    Thanks

  • 0 in reply to Justin Loundagin
    TI__Mastermind 22156 points

    I would like to understand a little more about the expected PMIC behavior with the targeted NVM programming. How does changing the Buck2 sequence fixes the application issue? Could you share the PMIC schematic?

    Thanks,

    Brenda