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.

TPS389006-Q1: I2C communication related problems

Part Number: TPS389006-Q1
Other Parts Discussed in Thread: TPS389006, TDA4VH

Hello Team,

There is a debugging problem that needs help.

1.Does the Tps389006 enable the i2c crc verification mechanism? If so, I want to know the specific crc calculation method. Here are my experiments:

(7bit address and 1bit read/write bit,the 7bit address we use is 0x30)
 Read 0x0 register
 Read 0x1 register
 Read 0x2 register
 Continuously read the 0x0 address and find that the second byte read is not the data of the 0x1 address
 Continuously read the 0x1 address and find that the second byte read is not the data of the 0x2 address

2.Questions about unknown devices of I2C bus:

       In our debugging, we found that a device with an address of 0x0 will appear on the I2C bus of WKUP_I2C0 (this device has an answer). After checking one by one, we found that the existence of this device is related to whether the I2C of TPS389006 is connected. If TPS389006 is attached to this bus, the device with an address of 0x0 will appear. If the I2C of TPS389006 is disconnected, the device will disappear.At the same time, we also tested the VH demo board we just received, WKUP_I2C0 will also read the device with 0x0 address. To verify,MCU_I2C0 is also read, and no device with 0x0 address is found.( Is 0x0 address of WKUP_I2C0 used as broadcast address?)

 
                                                   WKUP_I2C0                                                              MCU_I2C0

Best regards,

Kevin

  • Hello Kevin, 

    I have brought this query to the attention of the team, will respond with an update by tomorrow 12/8/22 2:00PM PT. 

    Regards,

    Oscar Ambriz

  • Hello Kevin, 

    After speaking with the team I believe this issue is due to PEC being enabled. Additionally, I believe this issue has been brought to the attention of the our systems engineer and is being handled over email. if this is the case I will go ahead and close this thread.

    Regards, 

    Oscar Ambriz 

  • Hello,

    I have received feedback on the problem of crc and resolved it. However, for the problem of 0x0 device address conflict, I need your help to follow up the Q2. (We have verified on the demo board of TDA4vh. The 0 address on the wkup_i2c0 will respond. The same is true in our own development board. However, we removed the TPS389006 on our development board, and then accessed the 0 address device through the i2c bus. At this time, there is no response.)

    Best regards,

    Kevin

  • Hi Kevin, 

    I understand, I will reach out to our team and return with a update by Monday 12/12/22 2:00 PM PT. We appreciate your patience. 

    Regards, 

    Oscar Ambriz

  • Hello Kevin,

    It is my current understanding that a 0x00 I2C address is not an available option. Could I ask what I2C ADDR resistor is currently being used?

    Regards, 

    Oscar Ambriz

  • Hello,

    At present, the 0x0 address of this I2C bus is used by us to debug the power supply device. When the NVM is not programmed for this device, the default address is 0x0. After the debugging is successful, the default address will be modified through the OTA, but it is currently in the debugging stage, So we need to continue to use the 0 address (we also found that the 0x0 address on the I2C will be coupled with the tps389006 in the use, and the same is true on the demo board of the TDA4VH. Does the tps389006 use the 0 address for broadcasting?), Please ask your team to help follow up.

    Best regards,

    Kevin

  • Hello Kevin, 

    Thank you for the information, I will bring this to the attention of the team. I will provide an update by tomorrow 12/14 at 2:00 PM PT. We appreciate your patience. 

    Regards, 

    Oscar Ambriz

  • Hello Kevin, 

    I am still waiting to hear back from our expert. Thank you for your patience, I will provide an update by tomorrow 12/16 at 2:00 PM PT. 

    Regards, 

    Oscar Ambriz

  • Hello Kevin, 

    After speaking with our expert it is my understanding that this matter will be handled over email. You can expect a member of the team to reach out shortly. I will close this thread for now. 

    Regards, 

    Oscar Ambriz