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.

TPS65987DDJ: Sink PDO Negotiated Trigger Event not triggering to send I2C command to BQ25703A

Part Number: TPS65987DDJ
Other Parts Discussed in Thread: TPS65987, BQ25703A,

Hello,

I'm working on a new design, based on TIDA-01627.  I have the new board connected to a PD adapter (RAVPower RP-PC112).  I'm using a "firmware" image for the TPS65987 that is based on a file I found in this E2E post:  https://e2e.ti.com/support/tools/sim-hw-system-design/f/234/p/865318/3202009?tisearch=e2e-sitesearch&keymatch=TIDA-01627#3202009
And, I'm monitoring the PD messages using a PD protocol analyzer.

The problem I'm having is that when a PD contract is negotiated, the TPS65987 is not sending the I2C message to the BQ25703A that sets the charge current for the connected battery, and thus the battery doesn't charge.  Some screen shots below show the problem.  First shot shows the active PDO, which matches Sink PDO 5 shown in 2nd picture.  3rd picture shows that this PDO being negotiated should trigger the sending of the I2C message to set the current on the BQ25703A.  I have the "App Config Binary Data Indices" Port 1 I2C Record Number of Indices set to the correct value (15), since that's all I have.  Other I2C messages based on other event triggers are being sent properly, so I know everything else is working the way it should.  I did try one experiment to set the Event Trigger to the closing of the PP Switch...when I did this, the message was correctly sent, and the battery charged.

The problem, as I see it, is that the TPS65987 is for some reason not recognizing that PDO 5 is being negotiated/used, and is therefore not generating the event to send the I2C message.  How do I fix this?

After doing some additional reading on the E2E, I see that the "DDJ" parts are really meant for Intel-based systems, and perhaps I should be using a different part since I'm not designing a PC.  But I think this should still work?  Firmware Base Image is:  TPS65987_88_F707_10_08.bin            I'm using GUI 6.1.1             My program is using 958 of the 1536 Allocated Bytes

Thanks!

Ted

  • Hi Ted,

    The post you are referring to seems to have just a project configuration file. Can you share the below information / files?

    1. Your current project configuration
    2. Firmware patch version. Refer screenshot below:

    3. Your current GUI version. You can get that from Help->About in the GUI tool.

    Regards,
    Kedar

  • Hello Kedar,

    Sure thing.  Here are a couple more screenshots with the requested info, and I've attached my project.  Please let me know if there's any other information I can provide.



     TPS65987DDJ Updated For PSB.pjt

  • Hello Ted,

    It looks like you are using the binary meant for TPS65987DDH on TPS65987DDJ.

    Please change your firmware to F708_12_3x and try your tests again.

    Regards,
    Kedar

  • Hello Kedar,

    I feel like I'm missing something.  The version of the Application Customization Tool that I'm using is version:  6.1.1

    This seems like the most recent version that I can find:  http://www.ti.com/tool/TPS6598X-CONFIG

    However, in other forum posts, I see people referencing what look like later/newer versions (in this post someone mentions version 6.2.3:  https://e2e.ti.com/support/interface/f/138/p/871010/3226850?tisearch=e2e-sitesearch&keymatch=TPS65987DDJ%20firmware#3226850)

    In the 6.1.1 version, when I click on the "Change File" button under "Firmware Base Image", the only options I see are shown below.  How do I find the firmware version you mention above (F708_12_3x)?

    Thanks!

    Ted

  • Hi Ted,

    My apologies. I seem to have misquoted the version number as F708_12_3x, instead of F807_12_3x. The title of this E2E issue mentions "TPS65987DDJ", but the GUI tool version you are mentioning supports TPS65987DDH. 

    Can you confirm the device version of the board you are using? 

    If you are using TPS65987DDH, then the GUI application version and the binary being used are correct.

    If it is a TPS65987DDJ board you have, may I know where you sourced it from?

    Also, It appears that the project configuration is missing the I2C Master Event configuration.

    Did you get a chance to look at our application note at http://www.ti.com/lit/an/slvae18/slvae18.pdf. This has detailed steps on setting up the device for I2C Master.

    Let me know if you face any issues with this.

    Regards,
    Kedar

  • Hello Kedar,

    The board I've built has a TPS65987DDJ device populated on it.  These parts were sourced from Digi-Key.  I should have purchased TPS65987DDH, but at the time I didn't realize what the difference was.  I have since ordered DDH version, and will replace the DDJ with the DDH on my board, and test again from there.

    Even with the incorrect binary running on the DDJ version, I'm still able to get some I2C messages sent from TPS65987DDJ to the BQ25703A, however, I was just never able to see the "PDO 1 Event" get triggered.  I'm now guessing that I never saw this event because I'm running the DDH version of binary on a DDJ device.  Hopefully running this same code on the DDH will produce the proper results.

    Thanks,

    Ted

  • Hello Kedar,

    Just to follow up...I was finally able to swap out the DDJ part for the DDH part, and of course it's working correctly now!

    Thanks,

    Ted