TPS25751: IC startup failure

Part Number: TPS25751
Other Parts Discussed in Thread: BQ25798

Hello,

I have received the following question from the customer regarding the subject above. Could you please help me respond to the customer?

Customer Situation

The customer reports that the TPS25751 mounted on their prototype board does not boot properly and is requesting guidance on the possible cause and corrective actions.

Observed Behavior

  • Mode Register (Offset = 03h): 0x50, 0x54, 0x43, 0x48 ("PTCH")
  • Boot Flags Register (Offset = 2Dh): 0xC1E2100000
  • The EEPROM capacity is sufficient, and the I2C address is configured as 0x50.
  • Clock stretching of approximately 100 ms to 500 ms or longer is observed between bytes during I2C communication.

System Configuration

  • The customer is using a BQ25798 in the system, however, it is not connected to the TPS25751.
  • The TPS25751 I2Cc interface is connected to the EEPROM, and the I2Ct interface is connected to the MCU.
  • The EEPROM has been programmed with the Full Flash Binary generated by the TI Customization Tool.

Information Confirmed by the Customer

  • The customer confirmed using an oscilloscope that I2Cc communication is occurring and that LowRegionStart and HighRegionStart are being read from the EEPROM.
  • The Boot Flags Register (Offset = 2Dh) value is 0xC1E2100000.
  • Patch Config Source = 7h.
  • Although communication with the EEPROM is taking place, I2C EEPROM Present = 0h is reported.

Could you please advise on the possible cause of this behavior and any recommended troubleshooting steps?

If additional information is required to further investigate the issue, please let me know. I will confirm it with the customer.

Thanks & Regards,
T.Imai

  • Hi Imai-san,

    Can you provide the schematic for TPS25751 and EEPROM? As well as the scope capture that was taken? 

    The mode register shows that PD controller is trying to load the patch file so that is correct.

    Decoding the Boot Flag Register, the state is "Boot in Progress" but as you mentioned I2C EEPROM Present is not set and Region 0 and Region1 are not showing "Attempted" or "Flash error"

    I tested an EVM with the EEPROM power disconnected and got different results for the register 0x2D Boot Flags

    EEPROM unpowered: Boot Flag (0x2D) - 0xC102600330

    Region0 and Region1 "Attempted" and "Flash Error"

    State 6 "BS_WAITING_FOREVER_BUNDLE_FROM_I2CHOST"