• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 64 subscribers
  • Views 109 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: TPS6594-Q1 EEPROM locked problem

yong zhang
Prodigy 10 points
Part Number: TPS6594-Q1

Tool/software:

Hello,
I need help about TPS6594-Q1 EEPROM locked problem.

I use Scalable PMICs GUI(4.0.0) to program TPS6494-Q1 (TPS65941111EVM),
when I operate "Step 4 Program Device",some error occured(some message about program failed(I have not noticed,)but not EEPROM locked failed info ),the step is not yet to click lock eeprom or not option screen.
when I reprogram Device, the "eeproom unlock failed"  error message is displayed.
I checked USER_EE_CTRL_1 register,the bit 7 is 0,eeprom is locked.

I would like to know,what kind of error can cause eeprom to lock?
e.g.,I2C is unstable?


Thanks

Yong.Zhang

  • 0
    Prodigy 10 points

    Hello,
    Update some information about this error.
    I can connect to Device, but cannot detected device,and cannot read all register.
    In the previous post, I explained that USER_EE_CTRL_1 reads bit 7 as 0, probably because all registers are unreadable.

    Thanks
    Yong.Zhang

  • 0 in reply to yong zhang
    TI__Mastermind 19247 points

    Hello Yong,

    Can you take a screenshot of the register page after you connect to the TPS65941111EVM as the device's address by default is not 0x28, but 0x4C.

    Click the pencil on the let side of the screen below the shield with the check mark.

    Was this the first time programming the device?

    Can you share the .json file that you were trying to program the device with?

    Common issues that could cause the EEPROM to fail at this step is an incorrect voltage applied to the device after flashing.

    BR,

    Nicholas

  • 0 in reply to Nicholas McNamara
    Prodigy 10 points

    Dear Nicholas,
    Thank you for your reply,

    *********
    Was this the first time programming the device?

    ----------
    Not the first time,I have programed several times,and all successful before
    is there any limit on the number of programming times?
    *********


    *********
    Can you share the .json file that you were trying to program the device with?
    ______

    I used a sample template json,and change some params about BUCK initial Voltage ,VCCA Voltage(From 5V to 3.3V)

    Moreover, the configuration this time is not much different from the previous one.(I have successfully use this sample template many times)
    The only problem that comes to my mind is that the default voltage of VCCA was originally set to 5V, and this time it was set to 3.3V.
    When I programming, I used 5V (because VCCA requires 5V power supply before program complete).
    Is it possible that the VCCA monitoring exceeded the 3.3V(Target Voltage) threshold at the moment of programming, resulting in failure of programming?

    Sorry I can't seem to successfully submit the json file in the forum.
    *********

    *********
    Can you take a screenshot of the register page after you connect to the TPS65941111EVM as the device's address by default is not 0x28, but 0x4C.
    ______
    Sorry,I've already replace with a new chip and cannot read the register table of broken chip,
    but I am worried that the new chip will be burned, so I hope to find out the reason.
    ********



    Thanks
    Yong

  • 0 in reply to yong zhang
    TI__Guru 74866 points

    Hi Yong,

    It sounds like you are having trouble attaching the .json file. Are you using this method? 

    In any case, if you encounter the issue again, I would recommend trying the method listed in the Scalable PMIC NVM Update Guide www.ti.com/lit/pdf/slvaf93 section 2 where it says: 

    "The initial PMIC state must also be understood before attempting to configure the NVM. Generally, the PMIC must be in a static or idle state. In some NVM configurations, the PMIC does not power up until the ENABLE pin is activated. Simply holding the ENABLE pin low can be an effective means to hold the PMIC in a known static state."

    Can you try holding Enable pin low? 

    Regards,

    Katie