Other Parts Discussed in Thread: TPS65987
note:MCU and PD are connected via I2C2 (I2C2_SCL/I2C2_SDA/I2C2_IRQ)
1.4CC CMD 'VDMs'
a. Write UVDM data (0x08 0x09 0x02 0x03 0x00 0x76 0x2B 0x00 0x00 0x00 0x00 0x01) to 0x09 DATA1,
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.
note:MCU and PD are connected via I2C2 (I2C2_SCL/I2C2_SDA/I2C2_IRQ)
1.4CC CMD 'VDMs'
a. Write UVDM data (0x08 0x09 0x02 0x03 0x00 0x76 0x2B 0x00 0x00 0x00 0x00 0x01) to 0x09 DATA1,
Hi,
Thank you for reaching out!
Write UVDM data (0x08 0x09 0x02 0x03 0x00 0x76 0x2B 0x00 0x00 0x00 0x00 0x01) to 0x09 DATA1,
It seems the data length is 10 but you are telling it to write 9 bytes. Also, you would need to write the data to 0x09 so the first byte should be "0x09" instead of "0x08".
Write the 'VDMs' -pd send VDM command to 0x08(0x08 0x04 0x56 0x44 0x4D 0x73)4CC CMD
This looks correct!
Please see this guide on how to use 4CC commands along with an example.
2262.Using 4CC Commands (3).pdf
Best Regards,
Aya Khedr
Hi,
Thank you for providing more information.
Could you please help identify where the EC is sending the 4CC command in the PD logs? Is the "Not Supported" message below the point of failure?
Also, see below for reasons as to why the command could be rejected:
Best Regards,
Aya Khedr
HI,
Unsupported Old vendor id(0x12d1) is not supported, this does not trigger enter mode, so it is normal,
As shown in the figure, enter mode has been triggered for vendor id(0x2B76), and the first time we send UVDM(0x2b7601fb 0x7d01) is successful,
But when we receive UVDM(0x2b760002) sent by the object, then our MCU will send UVDM(0x2b76) to write PD 0x09data via IC2, PD does not have any CC log printed out.
The IIC operates as follows:
At this time, the PD status register 0x08 is read, and it is found that the execution is not according to spec.