• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 392 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.

TPS65987EVM: Some problems with TPS65987EVM.

user6403867
Prodigy 50 points

Part Number: TPS65987EVM

Some problems with TPS65987EVM.

(1) When I read the SPI FLASH firm and check it, the firm version is incorrect as shown in the following image.
When I check it in debug mode it seems that all the settings are not written like the second image.

(2) When trying to execute "Re-Flash EVM Firmware (Recovery)" to solve (1), the following error is displayed.
Also, even if the template is written in "Flash from current project", the writing fails.

(3) When "FTDI Sweep I2C address range" is executed, it fails and the address is not detected.

I changed the FTDI driver version to 2.8.2 and tried it, referring to other threads, but I could not connect.


See below for configuration.
microB USB⇔PC
typeC USB←AC adapter(5V)

Win10 64bit

  • 0
    TI__Genius 9630 points

    Hello,

    In the second image, the settings are not written because you did not hit "read". If you notice right below the register, there are three buttons, "read" "write" and "clear". Please press read to see the settings you've flashed to your device. For more information on debug mode, check out this video: https://training.ti.com/tps6598x-gui-tool-displayport-alternate-mode-debugging . 

    To confirm, you are able to connect to your device in debug mode, but you are not able to connect when you sweep I2C addresses?

    Regards,

    Emma

  • 0 in reply to Emma Hoying
    TI__Genius 9630 points

    Hello,

    Another note, GUI 6.1.1 has a bug with the "Re-Flash EVM Firmware (Recovery)". It will be fixed in the 6.1.2 release. The "flash from current project" should work, however, so let's continue to debug your issue. 

    Regards,

    Emma

  • 0 in reply to Emma Hoying
    Prodigy 50 points

    Hello,

    As a result of reconfirmation, "Sweep I2C address range" fails while supplying 5V with the AC adapter. On the other hand, if 5V is not supplied, the address will be
    0x00 to 0x7f is detected.
    Similarly, in the debug mode, the connection availability changes depending on the presence or absence of 5V power supply.
    ①Which is correct with or without 5V power supply during I2C communication?
    ②Is there a possibility that a problem will occur by communicating without 5VS power supply and executing "Flash Delete" or "Re-Flash EVM firmware"?
    Regards,
    Oryoji
  • 0 in reply to user6403867
    TI__Genius 9630 points

    Hi Oryoji,

    You must supply power to the EVM in addition to plugging in the microB connector. This is because the flash and TPS65987D require power to communicate via I2C. Power is usually supplied through the barrel jack connector or through a source device connected to the Type-C connector. How are you powering the board? If you do not supply power to the TPS65987D, the GUI will not be able to communicate with the device. 

    In the S4 switch bank on the EVM, if the first 3 switches are in their off position, Port1 I2C2: 0x38 will be the address that the GUI will use.  

    Thanks,

    Emma

  • 0 in reply to Emma Hoying
    Prodigy 50 points

    Hello,

    As a result of exchanging the microB USB cable for I2C communication,
    the address was detected correctly and it was possible to write to Flash.
    Regards,
    Oryoji
  • 0 in reply to user6403867
    TI__Genius 9630 points

    Hi Oryoji,

    Glad your issue was solved. You can do I2C communication over the microB connector. If you were unable to do this, you could have had a bad cable. 

    Thanks,

    Emma

    Please click  "This resolved my issue" button if this post answers your question.