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.

TPS65982 Using SRDO in intrusive mode

Other Parts Discussed in Thread: TPS65982

Hi,

I can not use SRDO command to send the RDO data from sink to source to change the delivery power.

After the SRDO 4CC command is sent, I use the Data1(0x09) to read two byte data and it get 0x40 0x03 always such that I cannot send the RDO data by Data1(0x09) command. From the Python Script example, the data send by Data1 command seem to make sure the two byte data read of Data1(0x09) is 0x40 0x00.

Please give me the flow or condition to use the SRDO command.

Best Regards

Philip Jou 

 

  • Hi Philip,

    Could you provide some details on the use-case where SRDO in intrusive mode support would be required?

    Regards,
    Atiq
  • Hi Phillip,

    What is the 32-bit RDO programmed in Data1 register before issuing SRDO command?

    You mentioned that after issuing SRDO you read back Dtaa1 and it was 0x4003. The LSB value of 0x03 indicates that the SRDO command was rejected. Following are the reasons for the SRDO command to be rejected:
    (i) The port is not in Sink role [OR]
    (ii) If PDOIntrusiveMode bit in Control Configuration register (address: 0x29) is 0 [OR]
    (iii) Invalid value of object position field in the 32-bit RDO that was programmed in Data1 register

    So please check that you are meeting these conditions.

    Shafi

  • Hi Shafi,

    Thanks for your kindly response. I change the control flow and do not use the SRDO command in my current program. However, your information is valuable for me in future program development.

    Best Regards
    Philip Jou
  • Hi Shafi,

    I have an intrusive mode problem which is for the Apple Macbook linking to ask you.

    In the application, the TPS65982 is source role and Macbook is sink role. They link with 5V power initially.   The intrusive mode is used to negotiate new source capability. From the CC monitor, I saw that as the TPS65982 send a WAIT command to Macbook and it will cause a HARD_RESET immediately. The negotiation is fail. In the same flow, It do not happen in the Dell XPS13 Notebook. Do you know why?  

    Best Regards

    Philip Jou