• State TI Thinks Resolved
  • Locked Locked
  • Replies 62 replies
  • Answers 28 answers
  • Subscribers 34 subscribers
  • Views 7434 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.

TPS65987D: Workflow or example code to use as PD3.0 source

DH
Intellectual 310 points
Part Number: TPS65987D
Other Parts Discussed in Thread: TPS65987, , TPD6S300A

Currently we are wondering if there is an example code, config file or a description of a workflow to use the TPS65987 as a power source for a mobile device. We are checking different combinations of the poorly described registers but even after a few hours we see no success. 

We would be glad about any hint to configure the IC as a power source to provide our MCU all information to configure the external power source.

  • 0 in reply to Christian Wern56
    TI__Mastermind 36756 points
    Hi Christian,

    It is included with the TPS6598x application customization tool which can be downloaded here: www.ti.com/.../tps6598x-config

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    Prodigy 190 points

    Hi Eric,

    is there a way to test this quick and easy? The way I see it I have to implement the whole process in my firmware without even knowing if it is solving the problem. Do you have an example project based on SLVA972? Or is there some tool I can use to patch the TPS?

  • 0 in reply to Christian Wern56
    TI__Mastermind 36756 points

    Hi Christian,

    The other method is to add a SPI-Flash onto your board to hold the patch and configuration. The TPS65987D would read from the flash during boot up.

    Thank you,
    Eric

  • 0 in reply to Eric Beljaars
    Intellectual 310 points

    Hi,

    we use the SWD interface in most of our products and it looks like the TPS65987 provides this interface as well. May this be an option, too?

    As you can imagine, we will need again several days to implement the update functionality from the scratch without knowing if this solves our issue. What's TIs official statement at this point. Will this update fix the issue? Have you seen similar problems with the firmware version we are using?

    Please allow me to repeat Christian, we need an urgent and deep support. We are wasting a lot of time and money. For me, the situation is very simple. We implement the IC as described in your datasheet but this datasheet had a mistake related to the recommended connection. This generated a lot of extra costs and we loose time. More than that, we tried several ways and options and use the IC as specified in the USB specification without any success. I would highly appreciate if there could be a more detailed support instead of using this forum and loosing one day upon the other doing trial and error...

    In the past, application engineers had visited and directly supported customers. Is this forum the new way to help customers with problems where TI is not completely uninvolved in?

    Please excuse my hard words, but I believe that we can not go ahead like this. 

  • 0 in reply to DH
    TI__Mastermind 36756 points
    Hi DH,

    The SWD interface is not available for use by customers and is disabled by HW. We have not seen any other customer with the issues you are reporting. With all the hardware changes you have made to your PCB, I cannot determine what is causing this failure.
    Additionally, other customers have a means for loading a patch onto the TPS65987D which it seems was not implemented in this case. Hence my suggestion.

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    TI__Intellectual 1165 points

    Hi Eric,

    customer implemented the patch and configuration load through MCU and got successful results. Downside is the time to load all the data which takes several seconds even with 400kHz I2C. Any way to improve this?

    Could you please also help by sharing more detailed release notes than the ones from the application customization tool which only list known bugs?

    BR
    Cevin

  • 0 in reply to Cevin
    TI__Mastermind 36756 points
    Hi Cevin,

    Unfortunately, we do not have more detailed release notes than the ones provided with the application customization tool. Is the customer having more success with the patch loading through MCU?

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    TI__Intellectual 1165 points
    Hi Eric,

    that was fast.

    Yes, the customer has more success with loaded patch. Downside is the long load time of several seconds. Any way to improve this?

    Can you please work with your team that future release notes will get more accurate?

    BR
    Cevin
  • 0 in reply to Cevin
    TI__Mastermind 36756 points
    Hi Cevin,

    We are working on improving the boot time in future releases. The estimated time with 400kHz I2C is about 1.3 seconds currently.

    We will work to improve the release notes as well.

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    TI__Mastermind 36756 points

    Hello,

    I have not heard back from you in a while.

    If I answered your question, PLEASE select This resolved my issue

    Thank you,
    Eric

  • 0 in reply to Eric Beljaars
    Prodigy 190 points

    Hi Eric,

    as Cevin already said we have had success in downloading the patch, which finally made the system work.

    However when trying to implement the PD3.0 specific features like "battery status message" etc I have had no success once again. In the application customization tool I get errors when trying to select "Support Battery Status Message" (Exception Encountered during Checkbox Update: <type 'exceptions.AssertionError'>).

    Is there any trick I need to do to get it working?

    Thanks,

    Christian

  • 0 in reply to Christian Wern56
    TI__Mastermind 36756 points

    Hi Christian,

    I do not see this error when using the TPS65987EVM. The issue you are seeing could be related to the FTDI. I would suggest exiting debug mode and re-entering it when you encounter this. The FTDI is relatively slow and can time-out after a certain amount of reads/writes.

    This thread has been open for 3 months now. PLEASE open a new thread if you have further questions.

    If this answers your question, PLEASE select This resolved my issue

    Thank you,
    Eric