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.

TPS65917-Q1: TPS65917 PMIC

Part Number: TPS65917-Q1
Other Parts Discussed in Thread: USB2ANY, , TIDA-01480, TPS65023-Q1, TPS65023, TPS62067, TPS56C215, TPS568215, TPS65400, LP5912

I've made a Eval-Board  of TPS65917; but it occours some problem:

1:When I appield 5V to the Eval-Board, it seems no current goes through,LDOVRTC_OUT pin is  1.8V.

but when I push the KEY1 down, there is about 1~2A inrush  current ;

and then the TPS65917 goes very hot, while, all the DCDC seems dosen't working yet.

Is there any errors in my SCH?

2:Also I have a USB2ANY box(works correctly with FPD-LINK chips)and TPS6591x EVM GUI,But the USB2ANY box dosen't work correctly with the TPS6591x EVM GUI;

How can I connect the TPS65917 with the TPS6591x EVM GUI software?

TPS65917.pdf

  • Hi,

    This current seems quite high. With no load, the input current of the device usually sits around 50mA. Have you checked for shorts on the outputs? Can you measure the resistance from each output to ground?

    Also, which TPS65917 part number are you using?

    For I2C communication with the PMIC, the device will need to startup correctly with no interrupts and RESET_OUT going high before it can communicate with the GUI. Likely, if the device is not starting up correctly, you will not be able to use the GUI yet.

    Thanks,

    Nastasha

  • Thanks!

    I found when I press down the K1, PIN11 SMPS3_SW will output a 5V, and this phenomenon cause the PIN11 damaged, then the chip goes very hot; 

    And now , I  removed L3, there is only 27mA current after I press down the K1;  

    My TPS65917 marked "OTP 52  1.1";  I was also confused which part should choose, since there are so many Device Markings in the datasheet.

    I2C communication still jammed; My USB2ANY didn't output any signal, seem  my GUI dosen't  work correctly; 

    Can you give us an exactly download link of LabVIEW, since there are many errors about xxx.lvlib xxx.vi,

    and I'm using WIN7-64.

  • Hi,

    It looks like you may be shorting SMPS3 to your VCC3.3 domain. SMPS3 has a 1.8V output. There is a conflict here.

    To pick which part number you are using, see our user guides. This is the user guide for 0x52 OTP: http://www.ti.com/lit/ug/slvuas4e/slvuas4e.pdf

    The I2C will not work if there is a short. You can probe your interrupt pin. If the interrupt is set during startup, you will not be able to communicate through I2C.

    You should only need the executable files that can be downloaded online for the GUI to work: http://www.ti.com/lit/zip/slvc670

    Thanks,

    Nastasha

  • We are intend to use TPS65917 to power XILINX MPSOC, which need  0.85V core voltage; 

    TPS65917 seems  has a default voltage after powerd up, such as1.06V 1.15V; 

    Do TPS65917  got the ability for us to change the default output voltage before SMT?

  • Hi,

    Which version of Xilinx processor are you using?

    TPS65917-Q1 is programmed through OTP (one-time programmable). Once programmed in the TI factory, you cannot change the default voltages and sequences. You can only change the voltages after startup through I2C.

    We do have some PMIC solutions for Xilinx processors, however, it would be helpful to know which variant you are using.

    Thanks,

    Nastasha

  • Thanks a lot!

    We are using XAZU3EG and  XAZU5EV for ADAS, both automotive grade.

    we have read all TI PMICs nearly, and compare many other vender's; TPS65917 might be the best solution.

    One piece TPS65917 for XAZU3EG, and two piece for XAZU5EV. enought current, automotive grade, no external LDOs need and proper price.

    But the OTP default voltages makes it unsuitable for MPSOC~~oh no~~

    Is there any possibility for us to ask TI factory to make another OTP verison specially for XILINX MPSOC?

    Or, can the OTP operation left for the customers to do?

  • Hi,

    The OTP for TPS65917-Q1 cannot be done by the customer, only in the TI factory. If you are interested in a custom OTP there are minimum volume requirements, you would need to reach out to your local sales representative.

    I am looping in our expert for Xilinx attached power solutions for recommendations on ZU3EG and ZU5EV.

    Thanks,

    Nastasha

  • Hello,

    It appears you need an automotive qualified solution for Xilinx XAZU3EG and XAZU5EV.

    There is a TI Reference Design that covers ZU3EG and ZU5EV applications, TIDA-01480.

    The TIDA-01480 reference design does not use automotive grade components, but there are some recommendations for swapping out components. For example, you can use TPS65023-Q1 instead of TPS65023. You can use the TPS62069-Q1 instead of the TPS62069 (which is an improved version of the TPS62067).

    The TPS56C215 and TPS568215 do not have -Q1 versions because they are hysteretic converters. Any fixed-frequency converter with a -Q1 variant can be used instead of these devices.

    The philosophy of using these building blocks and selecting different components as needed is explained in this Webinar we hosted with Xilinx in 2018.

  • Thanks!

    This discretely solution mainly increased our board area, and we prefer TPS65400+LP5912.

  • Hi Nastasha:

        There ara about 8 OTP  verision in TPS65917's datasheet, where can I find all those 8 OTP default powerd up volutage?

    Just in case there is any one 0.85V default.

    And we are contacting ARROW to know about custom OTP and MOQ.

  • Hi,

    The OTP settings for TPS65917-Q1 can be found in the user guides:

    http://www.ti.com/lit/pdf/slvuas4

    http://www.ti.com/lit/pdf/slvuaj1

    http://www.ti.com/lit/pdf/slvuax9

    http://www.ti.com/lit/pdf/slvubc8

    Please note, this device cannot be reprogrammed. Custom OTPs are only supported in house for this device, not through third parties. (There are volume minimums, you would need to contact your local TI representative to inquire.) I recommend checking out TIDA-01480 for a Xilinx solution.

    Thanks,

    Nastasha