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.

TPS65917-Q1: EVM Connecting ERROR

Part Number: TPS65917-Q1
Other Parts Discussed in Thread: USB2ANY, TPS65916

Hi,

My customer is using TPS65917-Q1 EVM
He has a issue at startup GUI.
Please see the attached file.
This is a picture when this error occurred.

Customer did J26 is high and confirmed RESET_OUT is high level on EVM.
But this error occurs.

Could you let me know the reason about this error, please?

TPS65971_GUI.pdf

Best regards,
Shimizu

  • Hi,

    I have assigned your request to responsible Applications Engineer and we will get back to you as soon as possible.

    Regards,

    Murthy
  • Hi Shimizu,

    I'm sorry for the inconvenience. This is a known issue with the current GUI, and will be fixed in a future revision. Until then, please use the SMPSx_FORCE or SMPSx_VOLTAGE registers listed in the "POWER" group with addresses 0x1XX. These are the same register, just accessed through a different I2C address.

    Regards,
    Karl
  • Hello Shimizu-san,

    Let me correct my previous response. The error is because the "DVS" registers are only supported through I2C2, which is multiplexed with GPIO_2 and GPIO_4. So if you want to access these registers, then you would first need to configure GPIO_2 and GPIO_4 to the I2C2 functions, and then connect the I2C1 clock and data lines to the I2C2 clock and data lines. But after you do this, you should be able to communicate to the device using the "DVS" registers.

    Or as I mentioned before, you can access them from the "POWER" registers, using the registers with the same name. They are physically the same register, but just accessed using a different I2C bus and different I2C address.

    Regards,
    Karl
  • Hi Karl-san,

    Thank you for your support.
    I add a question about below.

    >The error is because the "DVS" registers are only supported through I2C2,
    >which is multiplexed with GPIO_2 and GPIO_4.
    >So if you want to access these registers,
    >then you would first need to configure GPIO_2 and GPIO_4 to the I2C2 functions, and then connect the I2C1 clock and data lines to the I2C2 clock and data lines.
    >But after you do this, you should be able to communicate to the device using the "DVS" registers.
    [Additional Question]
    Does this mean that user can not write/read "DVS" register by GUI?

    Best regards,
    Shimizu

  • Hi Shimizu-san,

    > Does this mean that user can not write/read "DVS" register by GUI?
    Not in its default configuration. But if you follow the procedure to set GPIO_2 and GPIO_4 (by writing PRIMARY_SECONDARY_PAD registers) and connect I2C1 lines to GPIO_2 and GPIO_4, then the GUI can read/write to the "DVS" registers.

    Regards,
    Karl
  • Hi Karl-san,

    Thank you for your support.
    I recommended to customer to using "POWER" registers which is your advice at first post.
    But in case of POWER" registers, this Error occurred, this error number is 52.
    Please see below picture.
    and then, this Error hadn't occurred after pushed [continue] bottom.
    What is this error at using "POWER" registers?
    Could you confirm at your bench, please?

    Best regards,
    Shimizu

  • Hi Shimizu-san,

    I've never seen this error before. It sounds like the MSP430 was not initialized correctly. I understand the issue went away after clicking OK.

    Do you get this error every time you use the GUI? If so, could you share with me the steps to reproduce the issue? I just tried it on my bench and could read the POWER registers without errors.

    Regards,
    Karl
  • Hi Karl-san,

    Thank you for your support.
    Your understaning is correct.

    This issue went away after clicking [Continue] bottom.
    and I get this error every time I use the GUI.
    Please see the attached file which is wrote detail.

    I used USB cable. Should I use USB2ANY?

    TPS65917-Q1EVM.pptx

    Best regards,
    Shimizu

  • Hi Shimizu-san,

    I was able to reproduce the issue on another setup in our lab. I fixed the error and we just uploaded the new version to ti.com overnight. Please try the new GUI in the TPS65916 EVM folder. Let me know if you still have issues.
    www.ti.com/.../tps65916evm

    Regards,
    Karl