TPS6593-Q1: TPS6593/4x-socket EVM board

Hello Raj,

After trying to recreate your situation, I'm unable to recrate the issue of not being to connect via the GUI.

My setup is was made to mimic yours with the exception of GUI version, it appears you are not using the latest, I was using GUI version 4.0.0 (can be found here)

Please try the following:

• Make sure the VSYS to 3V3 jumper is set and the base I2C address is set to 0x48
• Before connecting the board to PC via the USB C cable, hold down S1 while it attempts to make a connection.
  • This is due to the way your configuration tries to do a power attempt as soon as power is applied
  • Wait until 10 seconds after the USB C is connected and you see traffic on the bottom left corner of the screen

My questions to you are the following:

1. Has the TPS65931211 been able to connect ever?
2. Have the units been reprogrammed to your knowledge, as the topside marking in the photo doesn't indicate this as a production TPS65931211 device?

As for the device recognition on the PC, the fact it shows you attempting to connect means the evaluation board is recognized by the PC correctly. The connection failing is between the microcontroller on the board and the PMIC.

Best Regards,

Nicholas McNamara

Hi Nicholas,

Thank you for your reply.

Following your suggestion, I've updated to the latest GUI version (4.0) and attempted to connect my PMIC. Unfortunately, the issue persists.

Here's a confirmation of the settings:

VSYS to 3V3 jumper: Properly connected
I2C address: Set to 0x48 (screenshot attached for reference)
I've also held down the S1 switch before connecting the board to my PC, trying multiple times. While the connection seems to initiate, it fails to establish after a couple of minutes.

Answers to Your Questions:

1.Has the TPS65931211 been able to connect ever?
Yes, we were initially able to connect and program our PMIC.

2.Have the units been reprogrammed to your knowledge, as the topside marking in the photo doesn't indicate this as a production TPS65931211 device?
Yes, we have reprogrammed our PMIC. Additionally, our board has been validated. However, this issue is occurring when attempting to program the PMIC for the next batch assembly.

This issue is critical for our progress, so any assistance you can provide would be greatly appreciated.

Thank you
Raj Bhuvanesh

Hello Raj,

Raj Bhuvanesh said:

1.Has the TPS65931211 been able to connect ever?
Yes, we were initially able to connect and program our PMIC.

So the device is not a TPS65931211, but a different NVM was programmed onto the unit, may I ask for the .json or assembly file to see what changes where made?

The ask is from a place of trying to replicate your results to see what can be done to work with your setup, have their been any other changes to the board. As it stands the device will immediately start reacting to the enable being high due to the hardware configuration done.

BR,

Nicholas McNamara

Hi Nicholas,

I'm happy to report that I've identified the root cause of the PMIC communication issue. I suspected a problem with the I2C lines and upon probing, discovered that the U9 - SN74GTL2003PWR I2C_SPI_Level Shifter was causing the issue.

Resolution for PMIC Communication:

*Removed U9 (SN74GTL2003PWR) I2C_SPI_Level Shifter.
*Shorted the I2C lines (schematics screenshot attached).
*Confirmed voltage levels on both sides of the shorted connection are the same.

With these changes, I can now successfully connect the PMIC to the GUI and program it.

New Issue During NVM Validation:

However, I've encountered a new issue during the NVM validation page. When attempting to compare the programmed code with my .bin file, I receive a notification stating "unlocking EEPROM." Despite waiting for several minutes, the comparison doesn't proceed.

Could you please advise on how to troubleshoot this "unlocking EEPROM" issue and complete the NVM validation process?

Additionally, I'd appreciate your feedback on the I2C wiring modification. Is it likely to be causing the NVM validation issue, or is it a separate problem?

Thank you
Raj bhuvanesh

Hello Raj,

I'm glad that you've been able to reprogram the units. Although we do not recommend changing hardware on the EVM.

Raj Bhuvanesh said:

Could you please advise on how to troubleshoot this "unlocking EEPROM" issue and complete the NVM validation process?

Several modifications have been made to the board already, please can you get a logic capture of the I2C1 lines when attempting this validation process, this will be the most helpful thing during this time.

Raj Bhuvanesh said:

Additionally, I'd appreciate your feedback on the I2C wiring modification. Is it likely to be causing the NVM validation issue, or is it a separate problem?

In terms of SPI and changing voltage levels, the device has now been pulled up to VIO & MCUVCC, again please take a logic capture.

The unlocking EEPROM performs an unlock to the device, a certain set of writes need to occur in order as for the hang, I can not say at this moment without seeing the traffic on the lines.

BR,

Nicholas McNamara

Thank you for working with us on this Raj.

Just to give you awareness on these boards, they're only used for the purpose of programming loose units and are not meant for power evaluation.

Best Regards,

Nicholas McNamara