TPS6594-Q1: PMIC unstable connection to computer through GUI, after connector succeed occaslonally, burning NVM code by GUI, reporting EEPROOM unlock fault, unable to perform flashing

The SCH of TPS65941213 and TPS65941111 as fllow：

Question 2 was asked on another post. The answer can be found here:

https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1311850/tps6594-q1-pfsm-error

Does anyone help me to  solve  the "EEPROOM unlock failed" problem ? This error still exist. Thanks.

Hello Chenggang,

chenggang said:

Question 1:

Through the debugging board of MSP432E401Y MCU Launchpad, the TPS6594 chip is connected through GUI. The output connection is unstable, sometimes good and sometimes bad, and the I2C pull-up resistor is 1.5K. It can connect to the MSP432 board, but cannot connect to the chip. The latest GUI version used is 4.0.

I'm assuming you using the Launchpad to connect directly to already developed board, if you could take a picture of your setup?

The second question is, this setup, looking at the part numbers I see TPS659413 & TPS659411, is this correct?

If yes, the GUI currently only handles 2nd revision silicon after adding improvements, the previously mentioned part numbers are for 1st revision silicon and you will need to use an older GUI in order to communicate properly with it.

Try it with version 2.0.0, use it with the following link and click the TPS6594x-1.0: (click me for link)

chenggang said:

Question 3: Occasionally, after successfully connecting the TPS6594 chip, the quick start button automatically recognizes only one chip during device operation. The address of the chip is 0X4C. The other chip cannot automatically recognize.

Again since this is older silicon and the current GUI doesn't handle it. Could you try again with the linked above GUI

chenggang said:

Question 4:  After successfully connecting one chip, the template configuration of J721e was burned, and it could not be burned. A fault was reported that EPROOM  unlock failed. A multimeter was used to test the actual output of the chip, but the actual voltage of the chip was not displayed, so NVM was not burned successfully.

Same as above.

Awaiting your reply & BR,

Nicholas

Thanks Nicholas, The TPS6594 is not Tps659413 of SCH view , it havs change to the TPS65941213 and TPS65941111.

Hello Nicholas,

The system setup pictures are shou that as follows. I2C is used PB2 and PB3 pin, the firmware version is 1.0.3.6.

.

The TPS6954 system configuration is as follows：

1、It's use the tps65941213 and tps65941111.

2、I have the same result of "eeproom unlock failed" when the enable pin pulled down and pulled up.

3、The watchdog is disable , GPIO8 pin of tps65941213 is pulled up.

4、The VCC and VIO_IN、VSYS_SENSE pin is 3.3V.

5、All of the output pin is zero except the VSYS_IO_3V3 pin, it's have 0.17V voltage.

6、The GUI Vsion is 4.0  and configuration template is J721E.

7、The VOUT_LDOVINT and VOUT_LDOVRTC pin is 1.8V output.

All of the registers is not empty when the first power up and connect success. I can read and write the USER_EE_CTRL_1 registers.  Order write 0x00.0x98,0xB8,0x13 ,0x7D than the USER_EE_CTRL_2 is not change to 0XC0, it‘s still 0x80.

After I  down load the program ,all of the registers change to zero .

w

Hello Chenggang,

Thanks for reaching out. The device expert is out of office due to public holiday in US. Please expect delay in response by tomorrow. 

Best regards,

Ishtiaque Panhwar

 As shown in register USER_EE_CTRL_2 of the picture, the NVM of the chip is locked ,prohibited programming? 

How to solve the problem of Unable to connect to Page0？

Hello Chenggang,

Where are you getting your instructions on how to connect this launchpad to your development board?

I want us to be on the same page.

chenggang said:

 As shown in register USER_EE_CTRL_2 of the picture, the NVM of the chip is locked ,prohibited programming? 

This is correct as you need to do a series of writes which the GUI will do for you, once it's able to connect.

You said the GUI connected, but the connection is spotty, have you been able to probe the lines with a logic analyzer?

BR,

Nicholas

HI, Nicholas

This is our new project  not TI‘s development board.

I get the debug and connect information from E2E design support and technical documentation.

When powered on for the first time,  the GUI maybe could not be connected. I need to repeat power on.If the connection is successful and the state is stable. 

The urgent problem now is that I cannot “unlock the EEPROM" and "anable to connect to the page0". Can you help me as soon as possible？Thanks.

Hello Chenggang,

I understand this is urgent, I'm trying to recreate your steps in order to best help out.

Could you link the specific thread in which you are following the instructions. As I've been trying to connect to the GUI myself with firmware 1.0.3.6 and I'm unable to connect, we have not released any official documentation regarding the launchpad as a means for evaluation.

The reason the unlock is not happening is that it is following the same set of 4 register writes to 0xA2 that are detailed out in this guide. (click link here for guide section 4)

Normally the GUI does this for us.

BR,

Nicholas

Hi, Nicholas

 1、please see the technical documentation of slvubt8b, it's show that of  use the  MSP432E401Y SimpleLink to do the debug.

2、Download the GUI Composer Runtime and install the program.

3、When I first setup a connection with the GUI through MSP432E401Y on my computer，The GUI will automatically prompt "Please update firmware”1.0.3.6“. I find this firmware in the Installation Path of GUI. C:\Users\Lucky\guicomposer\runtime\gcruntime.v12\Scalable_PMICs_GUI\app\fw

I can't connect to TPS6594 now.  If i set of 4 register writes to 0xA2 still don't unlock the EEPROM.

If my connection is incorrect ,Can you tell me the correct connection method?

Thanks.

Hi, Nicholas

Do you have any method to debug TPS6594?

BR,

Gang

Hello Chenggang,

I got my board to connect now with a boosterpack, but in order for the connection to work I had to flash via the GUI with a known good firmware installed via the GUI, not uploading one provided by myself.

Please make sure you install the UNIFLASH tool as the GUI will do this for and will make the correct firmware is installed when asked to be updated:

(click here for UNIFLASH installer download)

Please make sure you're connecting via ACCtrl, not ACCtrl Console when inside the GUI.

As for the I2C lines on the launchpad:

PB2 is for I2C1_SCL1

PB3 is for I2C1_SDA1

Note the launchpad itself doesn't have pullups for these lines and will need to have them populated, if they haven't please make sure there is power on these rails along with having VIO & VCCA powered.

chenggang said:

I can't connect to TPS6594 now.  If i set of 4 register writes to 0xA2 still don't unlock the EEPROM.

Because when the GUI tries to do it from the user register GUI page, it performs the write and then immediately does a readback of the register to show the most up to date version on the GUI. When it tries to program it, the GUI does not perform these writes.

As it says in the NVM update guide it needs to do these writes as four single back to back commands with no other read or writes inbetween.

Can you confirm you are getting a NACK, can you please a logic analyzer on the I2C lines?

BR,

Nicholas

Hi, Nicholas

Thanks for your details introduction. But the connection of TPS65941312 still has issues.

 1、My connecting via ACCtrl, not ACCtrl Console when inside the GUI.

2、I used PB2 is for I2C1_SCL1 ，PB3 is for I2C1_SDA1  and I2C's pullup res is 3.3K, but the 3.3K res is used R13 and R14 of MSP432 Launchpad

3、I have install Uniflash on my computer, the frimware version has automatically updated to visversion is 1.0.3.6 via the GUI.

4、All the states are correct when I connect to TPS65941111 via 0x4c address，I can capture the waveform of  I2C on the oscilloscope when I verify Connection via GUI .

5、It's show that of  "PMIC I2C RESET " and "unable to connect pgae0"  when I connect to TPS65941213 via 0x48 address，I don't capture any waveform of  I2C on the oscilloscope when I verify Connection via GUI . It's show that of "Operation failed. Status = 4294959999" when i read the rigister.

6、 I measured a voltage of 0.08V at location FB_3 pin  and 0.065V at location LDO4 output， Does this voltgae will  affect the connection to the GUI？

Hello Chenggang,

chenggang said:

2、I used PB2 is for I2C1_SCL1 ，PB3 is for I2C1_SDA1  and I2C's pullup res is 3.3K, but the 3.3K res is used R13 and R14 of MSP432 Launchpad

Can you explain how? We did once offer an expansion for this particular EVM but we never used pullups located on the MSP432?

I am just trying to make sure that the pullups being used have a stable connect, because at times I did have the pullups physically on the board and would get a connection but after looking an oscilloscope the connection was not reliable and when programming this could lead to errors.

chenggang said:

3、I have install Uniflash on my computer, the frimware version has automatically updated to visversion is 1.0.3.6 via the GUI.

Wonderful! Glad to see that we're working with the same firmware from the same location.

chenggang said:

5、It's show that of  "PMIC I2C RESET " and "unable to connect pgae0"  when I connect to TPS65941213 via 0x48 address，I don't capture any waveform of  I2C on the oscilloscope when I verify Connection via GUI . It's show that of "Operation failed. Status = 4294959999" when i read the rigister.

I know it may be difficult but please try, I understand you tried to program the PMICs, I would like to not think that the unstable connection might have done something wrong. I'm just looking for a ACK or NACK on I2C address 0x48 which would indicate that you could at least communicate with the PMIC therefor having a chance to reprogram.

The 9999 ending of the code just means it can't communicate *VIA* the GUI, not that it's not programmable, again if the pullups aren't stable then no chance to connect relatiably.

chenggang said:

6、 I measured a voltage of 0.08V at location FB_3 pin  and 0.065V at location LDO4 output， Does this voltgae will  affect the connection to the GUI？

It shouldn't looks like it's just discharging from a power up attempt. No, but if you could make sure the enable PIN is low while VCCA is powered when you try to communicate with it that would be best.

BR,

Nicholas

Hi, Nicholas

 1、I added a  pullup resistors for 3.6k,4.7k,6.8K on the test board ,but the problem of "unable to connect pgae0" is still exists.

2、 The enable PIN is allways low while VCCA is powered。

 What I don't understand is that the I2C wiring of tps6594111  is longer than tps65941213 from debugging port  on the PCB board, but 6594111 is connection very good and 65941213 is failed.

 What can i do something？

Thanks.

Hello Chenggang,

I am trying my best, but I need more information from you.

So to understand that currently this is a Jacinto 7 EVM, correct, could you give me the specific part number?

If you are able to connect to the TPS65941111, can you paste a screenshot of the registers of 0x5A to 0x6C, these interrupts will help me understand.

I expect a SPMI error if the TPS65941213 is unable to be powered on, are any of the power rails from TPS65941213 on?

What is voltage on the input after the FET for TPS65941213?

Have you made any hardware or software changes on the board since you've started, I understand you tried to flash the PMICs, but any other changes?

chenggang said:

 What I don't understand is that the I2C wiring of tps6594111  is longer than tps65941213 from debugging port  on the PCB board, but 6594111 is connection very good and 65941213 is failed.

This shouldn't affect communication to either, I suspect the TPS65941213 is not receiving the correct, inputs, but I need to know the specific EVM.

BR,

Nicholas

Hi, Nicholas

 1、The screenshot of  registers 0X5A and 0x6C is as follow.

2. The input voltage after the FET for TPS65941213 is 3.3V, it's same to TPS65941111.

3. Is there a default configuration for TPS65941213 and 1111 before leaving the factory? If i don't connect to GUI and pullup the enable PIN to 3.3V ，the chips is a automation work，the buck and LDO is output 0.8V,0.85V,1.8V and so on.

4.I don't understand What does this passage  description，do I have to change the address of I2C after successful burning.

5.  This new design  EVM version is refence to the part of  Jacinto 7 EVM's power and TDA4 SCH and has nothing change, only add some test circuit  unrelated to 6594.

Hi, Nicholas

I try to burn in 6594111 through GUI, it's show that of  successful ，but it cann't to connect through I2C adress 0x4C  than the GUI shows "hardware not connected" when power up again.

The 65941213 also can connect via GUI with the IC2 adress 0x48.

Best,

Gang

Hello Chenggang,

So to understand that you have never been able to connect to the TPS65941213 via 0x48. But now after a flash of the TPS65941111 you are able to connect to TPS65941213?

The EVM should have not needed any flashing on any of the PMICs.

When you flashed did you make sure to select the proper the PMIC?

As it's possible to flash your secondary PMIC (TPS65941111) as a TPS65941213, which is what I fear has happened. You may have connected to the 0x4C device and flashed it now as 0x48 device.

If there are two functioning devices with the same address we can no longer tell what device is reacting to the commands.

For a solution, you may need to replace a or both PMICs now.

BR,

Nicholas

Hi, Nicholas

1. I have changed three boards and they have same state,I connect to the TPS65941213 via 0x48 is  successful，the GUI show that "Hardware connected ", the TPS65941111 via 0x4c is connect successful too, but TPS65941213 show of that  "unable to connect pgae0" and TPS65941111 Verify Connection is OK. 

I have chosen the correct address when i burn in the chip，I know that the address of 95641213 is 0x48 and the address of 65941111d is 0x4c.

 After i  burned in the 65941111, it can't connect via 0x4c,  but the state of  65941213 is same to befor burn in 1111chip, it's connected successful but don't connected to the PAGE0.

Hello Chengang,

So to understand you've had three J7 EVMs, but they all have the same issue?

Look before I can assist you further I do need the EVM for the J7 board, without it I can't help you much other than to say that you will not be able to unlock the NVM unless you can connect to page0.

And please if you do get another board do not flash the PMIC.

There is a chance that you can still connect successfully with old silicon to the GUI, while the GUI does a wonderful job, it can not detect the change in Silicon.

BR,

Nicholas

Hi, Nicholas

Thank you very much for your so super support.

Yes, i have three board and they all heve the same issue.

I'll try again and find any other way to connect to Pag0.

Best,

Gang

Chenggang,

I have gotten a hold of a J7 board, not necessarily the one you have I'll try to replicate your setup.

But can you do me a favor and try to connect to I2C address 0x49 or 0x4A, just do a read and see if you can get an acknowledgement, this would signify that the device is on and is working, but clearly I2C isn't behaving like we expect. I just don't want you to have to go through the trouble of replacing the part.

BR,

Nicholas

Hi, Nicholas

1. How can I connect to the I2C address of 0x49,0x4a?  There is don't have this two IC address selection in the GUI，and the I2C address cannot be manually entered in the GUI.

2. I can only read the information of the two register addresses of 0x49 and 0x4a, shown it in the screens as below.

Best,

Gang

Hello Chenggang,

My apologies on that, using the GUI interface there isn't a direct way in order to connect to the I2C addresses of 0x49, 0x4A, or 0x4B due to the way the GUI hides the connection.

If you have access to a logic analyzer, please probe the I2C1 bus and read the lines

Upon trying to connect to address 0x48, the GUI will ask for a register read on address 0x49, as shown for successful connection.

We are looking for a 

For a unsuccessful connection you will see the first connection for page1 (0x49) in red and

followed by two attempts to connect to page 0 in yellow.

If there isn't an acknowledgement after two attempts, the connection will fail and drop it. Please confirm that there is an acknowledgement in the red for the first I2C read.

BR,

Nicholas

Hi, Nicholas

Thanks very much for your sharing, i will find a logic analyzer to test I2C1 but I need some time to find .

Best,

Gang

HI, Nicholas

1. It's  the I2C information as follw for 0x48 address , this stats  is don't connect to GUI.

2. It's  the I2C information as follw for 0x4c address , this stats  is don't connect to GUI.

Gang,

Firstly thank you for doing all of these test and I'm sorry to say if you're not receiving a ACK from the first device and it never responds. I'm going to say after the first flashing attempt the EEPROM may have been incorrectly written to with an unstable connection.

Now if you can provide the specific part number for the Jacinto7 EVM we can see what to do from here.

BR,

Nicholas

Hi, Nicholas

 Is that of  template "J721e_TPS6594" in the GUI correct?  Is it  really  can be uased ?

 I reference the design package of  "PROC078E8C_RP" and  "PROC079E3D_RP" .

PROC079E3D(001)_SCH.pdfPROC078E8C(001)_SCH.pdf

Best,

Gang