• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 4 answers
  • Subscribers 66 subscribers
  • Views 597 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TPS53688: Tracking UVF/OVF/UVW/OVW threshold and PHASE_CONFIG can't be stored into NVM

Neo.Wang
Intellectual 910 points
Part Number: TPS53688
Other Parts Discussed in Thread: TPS544C26

Hi there,

When trying to modify the TPS53688 configuration through TI Fusion GUI, found Tracking UVF/OVF/UVW/OVW threshold and PHASE_CONFIG can't be stored into NVM. Once i updated them through the GUI and issue "STORE CONFIG TO NVM", then after power cycle the board, all these registers back to original values.

I am using TI Fusion GUI v7.9.3 with on-line mode where a TPS53688 devices is connected.

Please help look into this issue.

Thanks

  • 0
    TI__Genius 11017 points

    Hi Neo, 

    Can you try writing to hardware first before storing to NVM?
    Best,
    Ryan

  • 0 in reply to Ryan Chen
    Intellectual 910 points

    Hi Ryan,

    Actually, all the changes were written to hardware before stored into NVM. 

    Can you try it on your side with Fusion GUI 7.9.3 or 7.9.1?

    Thanks

    Neo

  • 0 in reply to Neo.Wang
    TI__Expert 8630 points

    Hi, Neo,

    Can you send us the project file (.xml). We will have a look

    Regards

    Anne Ngo

    Texas Instruments

  • 0 in reply to Anne Ngo77
    Intellectual 910 points

    Hi Anne,

    Here is the xml file. Please try to modify UV/OV offset threshold or PHASE_CONFIG settings and check if these changes can be stored into NVM.

    Thanks

    Neo

    TPS53688_Intel_B2h_P1_8V_VCCIN_P1_8V_CPU_3plus1_Project File.xml

  • 0 in reply to Neo.Wang
    TI__Genius 11017 points

    Hi Neo, 

    We are seeing similar issues on our end and will get back to you by the end of the week.

    Best,

    Ryan

  • 0 in reply to Neo.Wang
    TI__Expert 8630 points

    Hi, Neo,

    PHASE_CONFIG is stored in NVM. However, the EEh command (PIN_DETECT_OVERRIDE) is set to use "Pin strapping"  for PD_PHASE => Upon reset, PHASE_CONFIG is loaded with value from pin, not from NVM => Change EEh command to use PHASE_CONFIG value stored in NVM instead of pin, issue "Store Config to NVM", and then power cycle device. You should see the new updated PHASE_CONFIG from NVM.

    Regarding OVF/UVF limits: device calculates OVF/UVF as an offset from VOUT_COMMAND. Due to rounding, you might see the hex value off by 1 digit. The decoding of hex value as "Value/Edit" might be incorrect, that cause impression that OVF/UVF can not be saved to NVM. Please ignore the incorrect "Value/Edit" in current GUI. We will fix the issue in next GUI release.

    Regards,

    Anne Ngo

    Texas Instruments

  • 0 in reply to Anne Ngo77
    Intellectual 910 points

    Hi Anne,

    Please also check the changes to below registers can be stored into NVM or not. 

    Also i have seen below error message in the config file, please look into this issue as well.

    Which Fusion GUI version is proven as good for TPS53688 programming? I have a board which needs to bringup today.

    Thanks.

  • 0 in reply to Neo.Wang
    TI__Expert 8630 points

    Hi, Neo,

    The "PMBus Address" (EFh) can be stored to NVM, and so is PHASE_CONFIG (B3h).

    Similar to PHASE_CONFIG (B3h), if  ADDR is set to use pin value in "Override Pinstrapping" (EEh), then "PMBus Address" value stored in NVM is ignored.

    The warning you see just inform you that the SVADDR is set to 00h, might be conflict with the default PSYS address. If your PSYS is not enable, or PSYS address is set to different than SVADDR address, then ignore the warning.

    Regards

    Anne Ngo

    Texas Instruments

  • 0 in reply to Anne Ngo77
    Intellectual 910 points

    HI Anne,

    What's is the PSYS address? i am not able to find more details from datasheet or TRM.

    Where should i enable/disable or set the address for PSYS? Since the SVID address is fixed to 00h for this rail, it can't not be changed.

    BTW, when i downgrade to v7.8.1, this address conflict warning disappeared.

    Thanks

    Neo

  • 0 in reply to Neo.Wang
    TI__Expert 8630 points

    Hi, Neo,

    TPS53688 does not support PSYS setting. Please ignore the warning message. FYI, the warning added in recent GUI to make users aware of the potential conflict if PSYS (if enable) and SVID address are set to the same value.

    Regards

    Anne Ngo

    Texas Instruments

  • 0 in reply to Anne Ngo77
    Intellectual 910 points

    Hi Anne,

    Thanks for clarification.

    In my design, i have TPS544c26 on the same pmbus with tps53688, a known issue is V7.8.1 is not working for TPS544c26 programming. Only V7.9.3 works for TPS544c26.

    As we have many boards need manual programming, it's stupid to switch between V7.8.1 and 7.93 to programming different devices.

    As a workaround, I tried below procedure to programming TPS53688/TPS544c26 with V7.9.3.

    1. use V7.8.1 to generate TPS53688 xml files (UV/OV offset can be modified and displayed with correct values)

    2. use V7.9.3 to program the TPS53688 devices (UV/OV displays incorrect, but per your previous comments, the register values should be correct)

    3. use V7.9.3 to program the TPS544C26 device

    I hope above procedure is fine.

    BTW, when can we expect new FUSION GUI released to have issues fixed? I hope it can fix the TPS53688 UV/OV issue and also keep TPS544c26 programming function not impacted. 

    Thanks

    Neo

  • 0 in reply to Neo.Wang
    TI__Guru 62530 points

    Hi

    As explained, you can use 7.9.3 for both devices and we are working on releasing the new GUI on July. 

    Regards

    Yihe