• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 1324 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.

TPS65983: Share Settings Across All Channels issue in the TPS65983 Application Customization Tool v2.18.1

Axel Cheng
Prodigy 170 points

Part Number: TPS65983

Hi everyone,

I have a question about the "Share Settings Across All Channels" config. the default setting is checked. It means the TI FW should use the same setting that set in the "Shared Device Settings" page for all channels. So I save this project file and build a TI FW for testing.

But it doesn't share the setting across all channels because I load the project file w/ share setting and uncheck the "Share Settings Across All Channels" config. There are two device setting page: device 1 and device 2, only the device 1 is my setting. Device 2 setting is not the same as device 1 but not the default setting.

1. Is there someone get the same question, can I trust the default shared setting or just config each device to make it correct?

2. Is there any simple way to check or identify the shared setting in output TI binary?

 

Thank you for your attention.

  • 0
    TI__Mastermind 36756 points
    Hi Axel,

    1. Disabling the "Share Setting Across All Channels" setting is used when you want to program multiple TPS6598x devices using a single flash chip. You can also use it to have potentially two different configurations that can be loaded onto the TPS65983 device. When "Share Settings Across All Channels" both I2C ports will receive the same configuration.
    May I know what you want to do with this setting?

    2. You can check the output binary by loading it onto an EVM. With the Application Customization Tool you can then import the settings from that EVM by selecting Device --> Import Settings From Device.

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

    1. Our device is two port TB3 device and it should share the same TI configuration. At first time, I checked the "Share Setting ..." option and setup TI FW w/ our config in v2.14 config tool. But our partner member said that it not enough. Furthermore, it needed to enable the "show Bitfield Ranges" then set both Device1 and Device2 in the config tool, then the two port used the same setting exactly. But now v2.18.1 tool can't follow this procedure. Therefore, they tell me to ask this question here.

    I am not familiar with HW, but I know our device has two TPS65983 chips. Hence, do I need to use "Share Setting ..." option or not?
    And if I need to use(check) the option, all I need to do is setup the Shared Device Settings then the two port setting are the same, could you help me to confirm the tool just works like what I think.

    2. Unfortunately, our HW member doesn't have the EVM of TPS65983. I can't do this testing. Could you kindly explan below setting items in Import device setting for our HW reference?
    A: USB to I2C Adapter
    B: I2C Address
    C: Test Read (Mode Register 0x3)
    D: Import Settings To: Shared Device Settings
  • 0 in reply to Axel Cheng
    TI__Mastermind 36756 points
    Hi Axel,

    1. Yes, you are correct. When you select "Share Setting.." option, all devices will receive the same configuration. In your case, both TPS65983 will receive the same configuration.

    2.
    A. select the USB to I2C adapter that you are using. (same device used to load the code onto the device.)
    B. Enter the I2C address of the primary TPS65983.
    C. After entering the I2C address, click on Test Read (Mode Register 0x3). This should return: APP
    D. Import settings to: Shared Device Settings. This will change the settings in the Shared Device Settings tab to what is loaded onto the TPS65983 that you are reading from. Once you click OK, the device will be read.

    Thank you,
    Eric
  • 0 in reply to Eric Beljaars
    Prodigy 170 points
    Dear Eric,
    Thanks for your explanation, it is clear to me now.
    And I also have some question about below description in the TPS65983_Firmware_Release_Notes_04_33_00_20170331.pdf

    Since FW release 3.59, USB Billboard spec version 1.21 has been implemented in the firmware. This version of Billboard
    spec is NOT identified by Windows 10. This could result into Windows10 not identifying the Billboard class correctly.

    Does this behavior also occur in thunderbolt or only in USB3.1 ?
    How do I check USB Billboard info in Windows10 ? using utility like USBView.exe?