• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 166 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TPS6594-Q1: Device not detecting

Kaushal C
Intellectual 350 points
Part Number: TPS6594-Q1

Dear team,

I've connected the pre-programmed TPS65941515RWERQ1 to EVM to slightly modify the PMIC register, but when connected to PC through USB type-C it shows hardware connected but no device detected. Can you please explain why is that?

Also when programming it shows EEPROM locked. Can you explain this as well

Regards,
Kaushal

  • 0
    TI__Genius 14382 points

    Hello Kaushal,

    This following behavior is typical when it fails to receive an ACK from the various pages on the PMIC. It may be able to connect to some pages but not all.

    By chance did you change the I2C address of the TPS65941515 or were you only changes the registers via a separate PMIC EVM?

    Either way please if you can use a logic analyzer or oscilloscope to capture the traffic on the I2C lines to get an acknowledgement [or lack thereof] and share here.

    BR,

    Nicholas

  • 0 in reply to Nicholas McNamara
    Intellectual 350 points

    Hi Nicholas,

    Actually according to TPS65941515RWERQ1 PMIC GPIO 1&2 are SDA2/SCL2, but in my bin file I'm changing it to GPIO for my use case. Once i program that Bin file to my PMIC it gets locked. Do you think this maybe the issue for PMIC EEPROM getting locked?

    Regards,
    Kaushal

  • 0 in reply to Kaushal C
    TI__Genius 14382 points

    Kaushal,

    Can you please give me more details, like the TPS65941515, is it on a non EVM board?

    Kaushal C said:
    Do you think this maybe the issue for PMIC EEPROM getting locked?

    The EEPROM is locked by default and is done so to prevent destroying the device. In the event of unlocking the device if any of the necessary steps are not done properly the GUI returns this error.

    Now when trying to reprogram, have you been previously successful in programming?

    According to our programming guide these are the pieces of hardware necessary in order to program the devices.

    VCCA, VIO_IN, pull ups to I2C_[SDA/SCL]. The guide that details this out is here: CLICK HERE FOR LINK

    Now if any of these rails go down then you will not be able to program the device.

    There can be a time where the GUI will say connected but the PMIC is not or "connected", the connection is done by a series of reads and if it passes the GUI will then say connected, it will not "disconnect" until there's a detection change by either a removal of the MSP432 controller to the PC or a readback of the register failing.

    When the PMIC is being programmed the above rails still need to be on, but when the process begins to program the new EEPROM the PMIC rails go down. So if the output rail of one of the BUCKs or LDOs power the VIO or the pull up resistors on the I2C, these will go down and the programming of the PMIC is not possible as the requirements are not met.

    BR,

    Nicholas

  • 0 in reply to Nicholas McNamara
    Intellectual 350 points
    Nicholas McNamara said:

    Can you please give me more details, like the TPS65941515, is it on a non EVM board?

    No, My PMIC is inserted to TPS6594 socket EVM board and tried to re-program the PMIC.

    Nicholas McNamara said:

    Now when trying to reprogram, have you been previously successful in programming?

    Yes, it showed programmed successfully, but when tried to compare the program with my .bin file it is showing EEPROM locked.

    Nicholas McNamara said:

    According to our programming guide these are the pieces of hardware necessary in order to program the devices.

    VCCA, VIO_IN, pull ups to I2C_[SDA/SCL].

    All these should be proper as I'm using EVM for programming.

    Can you please suggest how to unlock the current EEPROM in re-programmed PMIC

    Regards,
    Kaushal

  • 0 in reply to Kaushal C
    TI__Genius 14382 points

    Hello Kaushal,

    Thank you for letting me know the context of how you're programming the board.

    The SKT EVM is currently not for public release.

    So in order to help you best, could you either privately message me or email (n-mcnamara@ti.com) the following?

    1. The binary file you flashed.

    2. The one you compared

    3. A picture of SKT board configuration (if you can)

    Kaushal C said:

    Can you please suggest how to unlock the current EEPROM in re-programmed PMIC

    Please probe the I2C lines and see what I2C address is not receiving a NACK, this is what typically causes this error.

    BR,

    Nicholas

  • 0 in reply to Nicholas McNamara
    Intellectual 350 points
    Nicholas McNamara said:

    1. The binary file you flashed.

     I extracted the .bin file from pre-programmed PMIC TPS65941515  and change few register set values

    Nicholas McNamara said:

    2. The one you compared

    Then compared the programmed PMIC IC with the same .bin file which then showed comparison failed due to EEPROM locked

  • 0 in reply to Kaushal C
    Intellectual 350 points
    Nicholas McNamara said:

    Please probe the I2C lines and see what I2C address is not receiving a NACK, this is what typically causes this error.

  • +1 in reply to Kaushal C
    TI__Genius 14382 points

    Hello Kaushal,

    So this shows that a readback is about to occur on the 0x48 address, but often when this error occurs it is the other pages that refuse to have a ACK, 0x49, 0x4B, & 0x4C.

    We offer a way for people to do self validation as the GUI just implements the already available instructions from our NVM update guide.

    GUIDE HERE FOR NVM UPDATE

    If any of these steps fail, you will get the error you see before you when doing validation.

    Note when the PFSM halts, the PMIC will not have any of the power rails on and outputting.

    BR,

    Nicholas