TPS65185: i am getting the issue on the PMIC

Hi, 

Is it possible to share a higher resolution image of the schematic for review? For example, attached the full PDF file.

Thanks,

Gerard

https://gitlab.com/Vinodh9/test/-/raw/main/IT8951E_DriverBoard_V1.3.pdf?inline=false

can you plese find the file link for my schematics 

Hi,

Thank you for the attachment.

Comments on the schematic:

• VIN_P pin does not have a PMIC_PWR power port. Can you confirm the pin is connected on the PCB?
• 10 uF decoupling is recommended close to the VIN_P pin.

Additionally:

1. Is the device responsive to I2C? You can try the REVID register (address 0x10). If it is responsive, please collect and share the full register dump.

Thanks,

Gerard

Hello Gerard,

Thank you for your response,

As you mentioned the points,

1. Yes, I connected the PMIC_PWR to VIN_P by using the external bus because I misplace the trace while designing.
2. I used the decoupling cap of 0.1uF and 4.7uF, but those are litter far away from the VIN_P PIN. (can I change it to 10uF), please find the attachment.

https://gitlab.com/Vinodh9/test/-/raw/main/MicrosoftTeams-image__1_.png?inline=false

1. While debugging the board, I got the response on the logs, for your reference, I am attaching the screenshot.

I got the default I2C Address as 0xC0, there are 2 I2C slaves in the circuit. (one is PMIC and another one is MAX7500MS)

 https://gitlab.com/Vinodh9/test/-/raw/main/MicrosoftTeams-image.png?inline=false

But I don’t know which address is this, I have only the .bin file which ITE has provided.

If you need any input from my side please let me know.  

Hi,

Tejash Kumar said:

Yes, I connected the PMIC_PWR to VIN_P by using the external bus because I misplace the trace while designing.

Could you expand on this - how are you connecting the VIN_P pin to PMIC_PWR? An external wire?

Tejash Kumar said:

I got the default I2C Address as 0xC0, there are 2 I2C slaves in the circuit. (one is PMIC and another one is MAX7500MS)

The I2C address for the PMIC is not configurable - it should be 0x68 (7-bit):

Thanks,

Gerard

Hello Gerard,

i was connected the 24th pin(VIN_P) with the inductor led wire to cap26 which that cap connected to PMIC_PWR

https://gitlab.com/tejashkumar/tejash_kumar/-/raw/main/IMG20220916141655.jpg?inline=false

How should configure the I2C with the 0x68? can you plese help me out.

Hello Tejash,

Unfortunately Gerard our device expert on the TPS65185 is out of office today. Therefore please expect a delayed response early next week. Thank you for your patience.

Best Regards,

Garrett 

Hi,

VIN_P is the input pin for the inverting buck-boost converter. These converters have high slew-rate input currents, so the placement of the input capacitor close to the pin is critical. See the EVM layout of this converter for reference: 

5381.TPS65185_EVM_Sch_Layout.pdf

As for changing the I2C address, I'm not exactly sure since this is a customer firmware. You can try entering it when prompted for the input address (highlighted below). 

You may also be able to increase the input length to 0x11 to ensure all TPS65185 registers are read. 

Alternatively, if you have a USB2ANY available you can connect it to the PCB and use USB2ANY explorer to communicate with the PMIC:

USB2ANY Evaluation board | TI.com

Thanks,

Gerard

Hi Gerard,

I placed the capacitor near the VIN_P.

This is custom firmware which ITE has given to us.

which input address has to be given through.

we don't have the USB2ANY to check the PMIC, is there any other way to check.

i am sending the new log of my board please find the screenshot, 

in the log we seen the PWR_GOOD is showing the Timeout! but the rest of the pins are got HIGH, and nINT was also not high

https://gitlab.com/tejashkumar/tejash_kumar/-/raw/main/Screenshot_2022-09-23_new.png?inline=false

Hi,

It seems this firmware has limitations so an external I2C controller like USB2ANY or Aardvark is the most direct way to read the PMIC registers. Do you have anything like that available?

Another way to debug is to check the outputs on the scope when enabling the rails (options highlighted below). Please check VIN, buck-boost output, and boost output first. 

Thanks,

Gerard