• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 797 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:

TPS53659: Skylake processor FIVR issue

TPS53659: How to setting and trigger VR_HOT# and PIN_ALT#?

Jan Bob
Intellectual 280 points
Part Number: TPS53659

Dear Expert,

We want to know VR_HOT# and PIN_ALT# setting and trigger method through GUI.

1. Which one is VR_HOT setting value?  and what is the relationship between them? Can TMAX be set low then 90C?

We had tried to modify warm/fault limit, but they will return to original value after refresh all parameters.

2. Why OTW/OTF are all asserted but VR_HOT pin still keep high?

3. Which one is PIN_ALT# setting?

  • 0
    TI__Expert 4060 points
    Hi Jan,

    The VR_HOT# and PIN_ALT# settings cannot be changed through the Fusion GUI as they are only accessible through the SVID Bus on pins 20-22 and not through PMBus. The pin description table in the datasheet lists the SVID registers of each flag. Those functions are part of the Intel proprietary features inside the controller and so Intel hardware has to be used for communication, we cannot put SVID functionality into our dongles and Fusion GUI. Since they're independent registers on a separate bus the GUI cannot change their values from whatever the defaults may be.

    1) For TMAX, 90C is the lowest setting possible. Per the datasheet (page 23), only 90C to 125C in 5C steps is allowed. Are you saving the new settings to NVM before refreshing the settings and/or power cycling the part?

    2) The VR_HOT# setting is likely higher than 115C which is why it would not assert during the fault. You would need to read the VR_HOT# register through the SVID bus to see what it's set to.

    3) None of those settings are PIN_ALT# as it's set through the SVID bus. MFR_PIN_MAX (A3h) is linked to the PIN_ALT SVID register (same value) but can only be written to via the SVID bus.

    Please let me know if you have any other questions.

    Thanks,

    Carmen
  • 0
    TI__Expert 5830 points
    Hi Jan,
    Please see my comments here.
    1. VR_HOT# is asserted if READ_TEMP is above TMAX, and the minimum setting of TMAX is 90°C
    TEMP_WARN_LIMIT is not an NVM bit, so it will be fixed in 105°C every power cycle, but it still works if you change the number on the fly.
    As for TEMP_FAULT_LIMIT, there are only two options in NVM, first one is 115°C and the 2nd one is 135°C, you can check the option "NVM_OT_FAULT_LIMIT" in MFR_SPECIFIC_13 to change it, and it still works if you change the number on the fly.

    2. You need to check VR_HOT# pin voltage thru meter or scope.
    3. PIN_ALT# is asserted by PIN_MAX, however, it is not effective right away, you need to store the new value to NVM and re-cycle 3V3, then the new setting works.

    Thanks.
    Chasel