• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 422 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TPS65987EVM: Can't receive power supply ID

TPS65987EVM: Registers readable via EVM -> USB-C -> EVM -> USB-Micro-B -> PC ?

Franz Schellhase
Expert 3605 points

Part Number: TPS65987EVM

Hi guys,

my customer is evaluating the following use case setup:

Power Supply <=> EVM1 <=> USB-C <=> EVM2 <=> USB-Micro-B <=> PC

On the EVMs they have written VIDs and PIDs (Registers 0x73 and 0x77). They want to read those via the Application Customization Tool.

  1. When reading from each EVM individually via a direct connection through USB-Micro B to the PC they get back the IDs.
  2. When reading the EVM IDs from the use case setup from register 0x71 (pointed out by you before here) they only get back zeros.

Is it possible to read the IDs with this use case setup? If yes how can it be done?

Thank you,

Franz

  • 0
    TI__Mastermind 30000 points

    Hello Franz,

    Do you have a PD analyzer that you can use the read the PD communication being sent between the two devices? You want to make sure that the Get_manufacturer_Info and Manufacturer_Info messages are sent between the two devices. Also, another register that will contain the manufacturer info is 0x7E.

    If these messages are not being sent, or you still do not see anything in register 0x7E, you can issue the 'GMfl' command (Get Manufacturer Info). This is done by going into to debug mode, clicking Device 1 port 0, click commands, and scroll to the bottom for Get Manufacturer Info. Then click "execute GMfl" and the Get_Manufacturer_Info message is sent from the PD controller that is currently in debug mode.

     

  • 0 in reply to Adam Mc Gaffin
    Prodigy 20 points

    Hello Adam,

    unfortunately we do not have a PD analyzer.

    I also already read the register 0x7E, with all zeros too.

    (The GMfI command says, when I connect two Boards, "ABORT_CMD" or "REJECT_CMD".)

    Edit: Now on the powering board it shows "SUCCESS_CMD", too but reading the registers still shows zeros.

    When one Board is connected to a power supply which has written IDs, GMfI says "SUCCESS_CMD" but the registers 0x71 and 0x7E are still all zero.

    If you need the files I loaded onto the devices or anything let me know.

    Regards,

    Daniel Stürmer

  • 0 in reply to Daniel Stürmer
    TI__Mastermind 30000 points

    Hello Daniel,

    One reason why you are seeing the REJECT_CMD is that the PD controller sending this message must be the one providing VCONN.

    As far as why register 0x71 is not being updated, I think I figured it out. You'll need to update the configuration of both devices to where the manufacturer info message is supported within register 0x41. Just tested this on my end, and after enabling this bit, sending the GMfl command, register 0x71 is successfully updated.

  • 0 in reply to Adam Mc Gaffin
    Prodigy 20 points

    Hello Adam,

    Thank you, now everything works just as it should!

    Regards,

    Daniel Stürmer

  • 0 in reply to Daniel Stürmer
    TI__Mastermind 30000 points

    Daniel,

    Great to hear! One final thing though is that I would strongly suggest you and your team investing into a PD analyzer. It will make debugging a lot easier because it allows for you to read the messaging sent between the two devices. We typically recommend the Total Phase PD analyzer because its affordable, and has everything you need for debugging PD messaging