• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 33 subscribers
  • Views 1061 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.

TPS65982: Problem with Version 4.03 of the App Customization Tool

WST
Expert 1005 points
Part Number: TPS65982
Other Parts Discussed in Thread: HD3SS460

I pulled an older project into the 4.03 version of the tool. It now flags an error in red on the 'Transmit Source Capabilities' option. I have the number of source PDOs set to 0, since my board is only operating as a SINK.

If I temporarily change the Source PDOs to 1, I see that the Switch Source Field has a red ?, and if I click on this I get the following message:
Consistency check failed while attempting to set field: Switch Source in register: Transmit Source Capabilities (0x32)
Warning Message:
"Setting Transmit Source Capabilities PDO switch source to PP_5V requires that this switch be configures as an output in the System Configuration register. Currently it is configures as: PP_5V0 switch not used (disabled)"

Why is this an error??? If I don't have any Source PDOs, why would I want the PP_5V0 switch turned on as an output?? I'm assuming that the TPS65982 won't turn on the switch if the PDO = 0 even if it is enabled as an output but wanted to make sure. I have no source on the TPS65982 on my board that could provide 5V when I am a sink.

If I 'fix' this, then it also complains about the 'PP_HV' switch. If I make them both outputs, then Why do I have a bad setting if the PDO=0?

Warren

  • 0
    Expert 1005 points
    More Info... When I created the original images, I used the "TPS6598x Snapshot 3_05' version of the software and it didn't flag an error. However, I just checked with the 3.08 software and it flags the problem also. It looks like there have been other versions since then also.
    I don't see this as a real problem if I leave the switch(es) in the disabled more if the TPS65982 is in a power input / sink configuration. It just has a red error in the setup. Also if the Source PDO number always == 0, then having the switches set as source shouldn't be a problem if they are never connected [this gets rid of the 'error'] but it makes me nervous.
    I noticed that I can write out the binary file with the conflict. A binary compare of my old file with the 4.03 version file shows many differences, but I guess that is to be expected. I noticed that the 4.03 version wants to change the images to 0x2000 and 0x12000, the old one had them at 0x2000 and 0x20000 which is what I wrote out to do the compare.
  • 0
    TI__Mastermind 24075 points
    Hi WST,
    When you change Source PDO to 1, the default transmit source capability would be for a 5V 3A contract. You will see the Switch Source Field red, as the original PP5V configuration in System configuration (0x28) would not be configured to support this contract. (PP_5V disabled needs to be changed to PP5V configured for output). If you have 0 Source PDO and PP5V disabled this will not be an issue.
    As you are only using TPS65982 as a sink, what are the configurations for PP5V, PPHV, and PP_EXT, along with what your specified sink PDOs are? These must be consistent with your sink PDOs.
  • 0 in reply to Kedar Manishankar
    TI__Mastermind 24075 points
    Following up on your update, the switches cannot be disabled if they are actively being used. If you are sourcing, then switch should be configured for output, and if you are sinking then switch should be configured for input. Example: If you are only using 5V, you can configure the PP5V accordingly, and all other switch paths can be disabled.
  • 0 in reply to Kedar Manishankar
    Expert 1005 points
    In my configuration when I'm in SINK mode I have the PP_HVE switch enabled as an input, the two internal ones are turned off. However, my question was EVEN WITH the source PDO = 0, I get the error from the 4.03 tool about the PP_5V0 and PP_HV switches being disabled. The tool doesn't like them being disabled. Why is the 'Transmit Source Capabilities' field RED when the Source PDO = 0? The tools requires both the PP_5V0 and PP_HV set to OUTPUTS even with no source PDOs. This wasn't true with the 3.05 version of the tool.
    I did find out that the binary file could be written even with these set 'incorrectly' to disabled.
  • 0 in reply to WST
    Expert 1005 points
    By the way, thanks so much for the quick response!
    Warren
  • 0 in reply to WST
    TI__Mastermind 24075 points
    Hi Warren,
    I do not see this issue when I have the other switches disabled with 4.03 version of the Customization Tool. I will check with our firmware team to see if they have any inputs. In the meantime, can you create a new TPS65982 project and try configuring just the source or sink PDO with the appropriate switch configuration, and see if this issue still persists?
  • 0 in reply to Kedar Manishankar
    Expert 1005 points
    Hmm... I loaded in the following to start with TPS65982_HD3SS460_DRP_Host_Advanced_v4_03.tpl and then tried to get it to fail. I couldn't either. If I load my .prj file into the 4.03 tool it shows the failure. I then proceeded to try to match the register settings from my failing file using the 4.03 version of the tool for both. I even looked at the 'RAW view' the best I could with the naked eye. They looked the same, but I can't get rid of the error if I start with my 3.05 project. I played with the Transmit Source Capabilities and the System Configuration on both files, but still couldn't cause the problem with the new file and couldn't get rid of the problem with mine. The output binaries don't match, and the 'Application Configuration used:' is 0x32a with the new file, and with my file is it 0x3c1.
    There is some difference that I can't clear by changing the above registers. Since there are other changes with the 4.03 version of the tool(using 0x12000 instead of 0x20000) for the upper address I'm hesitant to start from scratch. I could send you my project file, but I don't want to upload it here. I guess there is just a bug that can't be cleared up by setting the Src PDO = 0 in my file without starting from scratch.
    Warren
  • 0 in reply to WST
    TI__Mastermind 24075 points

    Hi Warren,

      Can you try these steps:

    • Flash TPS65982 with existing 3.05 project
    • Open new template in 4.03 customization tool
    • Import settings from Device
      • Customization tool -> Device -> Import settings
    • Save project file

    This should load your existing project file in the updated 4.03 template format, and allow you to save the older project in the newer 4.03 format.

  • 0 in reply to Kedar Manishankar
    Expert 1005 points
    Ok, I spent part of this morning doing what you said. I recently upgraded my computer so had to go through the install process to be able to 'Import settings from Device'. I am using an Aardvark tool to communicate with the TPS65982 part on my board. I was able to do what you said and I don't get the error any longer if I do this. I checked the registers and they are all updated with the values that were on the part on the board. It fixed the problem with the RED 'System Configuration' register. However, there were a few problems I encountered and some questions.

    1) In the error messages that both the Utilities interface tool and the Application Customization tool give, it would be helpful if the Aardvark.dll isn't found that it would tell you to 'Please see user's guide'. I spent a couple of hours trying to remember that I had to copy the 'aardvark.dll' and the 'aardvark_py.py' files over to the applicable directories. I finally remembered that the User guides had information about that. Once I copied them over I could proceed. I could have saved a lot of time if that would have been pointed out when I tried to run the tool.
    2) When reading the device it isn't clear where I have to import the settings to. To get it to work I had to use the 'Shared Device Settings' option, the 'Global Device Settings' doesn't work. However, in newer versions of the AppCustTool, the tab is actually called 'Common Settings', so the name needs to be changed in the Import Dialog. There is no 'Shared Settings' in version 4.03. [Also, it says 'Global Device Settings' but there is only a 'General Settings' tab in the tool].
    3) You said to 'Open new template ...' above. There a many options with this, and I found that in order to read the values completely that I had programmed, I had to choose 'Advanced' or 'App Config GPIO example'. My programming uses a GPIO to switch power profiles so that is the one I finally loaded for the new template.
    4) Minor point... After loading from the device, the register I am currently looking at doesn't get updated. At first I didn't think it loaded correctly, but when I looked at another register and then back, I could see that it had.
    5) In my 3.05 version of the programming, under the 'GPIO Event Map' selection, the settings for one of my GPIO's 'Mapped Events' was 'Sink < 12V Event'. In the 4.03 version of the tool the choice is now 'Sink < Threshold Voltage Event'. This is a difference. Where do I set this threshold?? I looked around and I'm guessing it is in a NEW field at the end of the 'System Configuration' register setup, where it says 'Voltage Threshold for Adjustable GPIO Event'. This makes sense, but I can't find it in either the App Cust Tool user's guide (slvuar8a) or the HostIntTechRefManual user's guide (slvuan1A). The latest Host.. manual on the TI website doesn't talk about these bits in the 0x28 system config register. They would be in byte 18 but the Feb2017 version of this file (the one I could find on the website) doesn't mention them. However, the AppCustomization tool allows me to set this to 12V, so I'm assuming that is the correct field??
    6) The GPIO configuration Data Sets DON'T load from the device load. I have to change those to match the ones I had in the original project manually. I tried import to Global Device Settings tab, but this didn't help. This is a minor issue since they are easy to change, but the device load doesn't bring them back in.
    7) Finally, when I save the binary image I noticed that the upper region changed to 0x12000 from 0x20000. We may have done some programming assuming that the image resides at 0x20000. I'm assuming that changing this value back to 0x20000 won't be a problem.

    Thanks for your help. The original issue was resolved.
    Warren
  • 0 in reply to Kedar Manishankar
    Expert 1005 points

    Please see the questions in the response above

  • 0 in reply to WST
    TI__Mastermind 24075 points
    Hi Warren,
    For 5) you are correct in setting Voltage Threshold for Adjustable GPIO Event bit for the specific GPIO event map you have. Thanks for the helpful advice on making the error messages more descriptive and user-friendly, and we will look to incorporate some of the feedback in later revisions of the tool.