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.

MSP-EXP432E401Y: Connection issue

Part Number: MSP-EXP432E401Y
Other Parts Discussed in Thread: UNIFLASH, TPS6594-Q1

Hi team,

Using the MSP-EXP432E401Y Launch Pad as a USB-to-I2C tool, customer would like to debug the TPS6594x using the scalable pmic GUI.

When opening the scalable pmic GUI software and connecting the MSP-EXP432E401Y to the PC, the customer noticed that the firmware needs to be updated to 1.0.3.6, and downloaded the 1.0.3.6 firmware on the forum and updated it through uniflash. When the MSP-EXP432E401Y firmware is updated to 1.0.3.6 and connected to the PC, the virtual com port can be seen in the device manager. However, instead of ACCtrl devices, it is the USB serial device that is seen in the port:

Also, in the scalable pmic GUI, you will see "waiting for data", and for a long time cannot see an indication of a successful hardware connection: 

1) Is the above behavior expected?

2) Could you help share a validated version 1.0.3.6 firmware?

3) Why the connection has never been successful in the scalable pmic GUI?

4) Where is the I2C pin after the 1.0.3.6 firmware is flashed in the launch pad?

Thanks.

Best Regards,

Cherry

  • Hi Cherry,

    You should see the GUI show a named port in the Select Port dropdown, which matches what you are seeing. This leads me to believe the firmware of the MSP is functioning properly.

    You should see Hardware Connected in the bottom left corner. When GUI is showing "waiting for data" for a long time, that typically means the AEVM is looking to talk to a device configured as I2C but the clock line is being pulled low. Can you verify there is no clock signal?

    I am looking into finding the 1.0.3.6 firmware and where the I2C pins are after the firmware update. 

    Regards,
    Megan

  • Hi Cherry,

    The latest firmware is in the GUI.  It will be at the following location: C:\Users\xName\guicomposer\runtime\gcruntime.v11\Scalable-PMICs-GUI\app\fw

    The I2C pins are as follows: I2C0 SCL is PB2, I2C SDA is PB3.

    Regards,
    Megan

  • Hi Megan,

    Thanks for your support.

    You should see the GUI show a named port in the Select Port dropdown, which matches what you are seeing. This leads me to believe the firmware of the MSP is functioning properly.

    You should see Hardware Connected in the bottom left corner. When GUI is showing "waiting for data" for a long time, that typically means the AEVM is looking to talk to a device configured as I2C but the clock line is being pulled low. Can you verify there is no clock signal?

    Indeed, the GUI will "waiting for data" after the initial connection. 

      

    If manually disconnect and reconnect using the button in the lower left corner, a pop-up window for "Device setting" appears: 

    At this point, there is only one content in the select port drop-down bar, and it is not the Texas instruments but the Microsoft:

    Thanks and regards,

    Cherry

  • Hi Cherry,

    When you measure the I2C CLK signal with an oscilloscope, what do you see? These results seem to indicate there is no I2C communication between the MSP-EXP432E401Y Launch Pad and TPS6594-Q1.

    Regards,
    Megan