TPS65987D: Fail with i2c address after SPI-Flash is program

Hans Nilsson

Prodigy 70 points

Part Number: TPS65987D
Other Parts Discussed in Thread: TUSB1146, TUSB1146EVM

Hello

Design USB-C Alternate Mode.

Used IC is :

Power Device TPS65987D
Linear Re-driver Crosspoint Switch TUSB1146

Electrical diagram is copy of eluviation board TUSB1146EVM.

Before SPI-Flash program I can scan 2pc i2c-addresser.

TPS65987D 0x20
TUSB1146 0x44

PD-ic can be debug and configuration with i2c 0x20.

If it take a copy of SPI-Flash eluviation board TUSB1146EVM, then program the SPI-Flash on my design. After programming, full working function on USB-C Alternate Mode.

BUT !

TPS65987D i2c-address cannot be scan and debugging cannot be performed, after SPI-Flash is program with eluviation board SPI-Flash copy.

Note! Eluviation board TUSB1146EVM IC TPS65987D i2c address is not available (TUSB1146 is available).

How I do access TPS65987D i2c address on my design or eluviation board?

over 2 years ago

0 Ghouse Mohiuddin23 over 2 years ago

TI__Expert 8280 points

The I2C address should not have changed. Can you probe on I2C signals and see what is the state? When you scan do you get NAK on address 0x20.

0 Hans Nilsson over 2 years ago in reply to Ghouse Mohiuddin23

Prodigy 70 points

We use dongle USB to SPI/I2C model Aardvark from Totalphase. Regardless of which PC program (TI or Totalphase) is used, the same result is obtained.

Picture below show i2c address 0x20, this can be compare with answer from i2c-address 0x44 which works correctly.

(I think is clock stretch on Master with i2c address 0x20).

0 Field Tolson over 2 years ago in reply to Hans Nilsson

TI__Genius 10772 points

Hi Hans,

I am unfamiliar with this issue and device, and don't quite believe I understand what is going on, so please expect some delay in my response.

To help me understand, the 0x20 device address works, and then after flashing it doesn't?

I am wondering if you are changing the I2C address when you flash. Are using this as the master? Are you writing to register 0x64? Is this single or dual port?

Thanks,
Field

0 Hans Nilsson over 2 years ago in reply to Field Tolson

Prodigy 70 points

Yes it is correct that i2c address 0x20 works before SPI-Flash is programmed with a SPI-Flash copy from the development kit TUSB1146EVM.

If SPI-Flash erases and HW-resets the device, i2c address 0x20 works as normal again (and TI GUI program can use for at readout register and debug).

Would need a full list register setup for TPS65987D used on TUSB1146EVM. Support which registry affects i2c when TPS65987D boot up from SPI-Flash.

0 Field Tolson over 2 years ago in reply to Hans Nilsson

TI__Genius 10772 points

Hi Hans,

Are you cycling power on the EVM after flashing? Could you try using 0x38 as the address and see if this gets a response?

Additionally what may help is if you are using the Application Customization Tool, or if not this can be found at the TI website linked here, you could you try sweeping for the I2C address? Can be done via the following: Adapter tab -> Configure I2C/SPI Adapter Settings -> (since/if you are using the aardvark, please select this from the list of options in the configurations drop down menu) -> Sweep I2C address range for device response. This can also be seen in the following screenshots.

Thanks,
Field

0 Hans Nilsson over 2 years ago in reply to Field Tolson

Prodigy 70 points

Hi Field.

Update GUI program from revision 6.1.3 to 6.1.4.

Same problem, can only sweep 0x44 i2c address to Switch TUSB1146 on board TUSB1146EVM.

If tried to use 0x20 or 0x38, response is no answer on i2c.

/Hans

0 Eric Beljaars over 2 years ago in reply to Hans Nilsson

TI__Mastermind 36756 points

Hans,

It appears the issue you are reporting is related to the questions being asked in this thread: https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1261990/tps65987d-discrepancies-between-datasheet-and-tusb1146evm-implementation/4776606#4776606

Based on the issue description, I assume you are reading the I2C address on I2C1 which when the TPS65987D is in PTCH mode (no configuration loaded) will act as an I2C target. Then, when the configuration for the TUSB1146EVM is loaded, the I2C1 port is configured to be an I2C controller and thus you can't see the 0x20 I2C address on I2C1 anymore.

If you need to read from the I2C port on the TPS65987D, I would suggest connecting to the I2C2 port since it will always be an I2C target port.

Thank you,
Eric

0 Hans Nilsson over 2 years ago in reply to Eric Beljaars

Prodigy 70 points

Okej. I2C1 change permanent from Slave to Master.

Read in manual and understand, but not why development card is configuration for no debugging.

8.3.9 Digital Interfaces
The TPS65987D contains several different digital interfaces which may be used for communicating with other
devices. The available interfaces include three I

2C ports (I2C1 is a Master/Slave, I2C2 is a Slave, and I2C3 is a
Master), one SPI controller, and 12 additional GPIOs.

0 Ghouse Mohiuddin23 over 2 years ago in reply to Hans Nilsson

TI__Expert 8280 points

Nilsson, Do you have TPS65987D EVM to try your FW image?

0 Hans Nilsson over 2 years ago in reply to Ghouse Mohiuddin23

Prodigy 70 points

No, use TUSB1146EVM for eluviation USB-C with Alternate Mode (DisplayPort). There TPS65987D imported component for right configuration.

0 Eric Beljaars over 2 years ago in reply to Hans Nilsson

TI__Mastermind 36756 points

Hi Hans,

If you'd like to test the full functionality of all debug interfaces on the TPS65987D, I would suggest testing with the TPS65987DEVM. The TUSB1146EVM is intended to highlight more functionality of the TUSB1146. Not all features of the TPS65987D will be exposed on that EVM.

Thank you,
Eric

Power management

Power management forum

TPS65987D: Fail with i2c address after SPI-Flash is program