• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 101 subscribers
  • Views 261 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.

TMDSEMU560V2STM-U: brand new TMDSEMU560V2STM-U not working

vaibhav baid
Prodigy 20 points
Part Number: TMDSEMU560V2STM-U

part supplied does not work with EVM kits. we have tried with multiple kits. see attached data of test with two kits. any suggestions what could be the issue?EMULATOR-Test (2).pdf

  • 0
    TI__Guru**** 424400 points

    The "cable break far" error indicates that there is some connection issue between the device and when the debug probe connects to the JTAG header on the target board. 

    It can be an issue with the debug probe or it can be an issue with JTAG connections on the target board itself.

    For more details on the error, please see the section under "Cable break" in the below document:

    https://dev.ti.com/tirex/explore/node?node=A__ANoamrIZPWD2-6T-NDDWGg__ccs_devtools__FUz-xrs__LATEST

    Based on the pdf you attached, it looks like there is no issue with an XDS200. If the XDS200 is connecting to the same exact header as the XDS560v2, then it could be an issue with the ribbon cable or connector on the XDS560v2 itself.

    If you have another XDS560v2, you can try to see if that will work. If it does, then it would point to the original one being defective.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 20 points
    the error persists.
    there is no way to change ribbon cable as it is fixed.
    Test Results with new DSP kit 6713 are attached.
  • 0 in reply to vaibhav baid
    TI__Guru**** 424400 points

    I tried the same setup you have above:

    -C6713DSK

    -Blackhawk USB560v2

    -CCS 7

    I did not have any issues:

    Hence the issue must be something with your environment. You could have a bad probe. You may want to contact Blackhawk support directly for further assistance.

  • 0 in reply to Ki
    Prodigy 20 points

    not sure why we need to talk to blackhawk support considering this is brand new product which is purchased from TI which does not work. 

  • 0 in reply to vaibhav baid
    TI__Guru**** 424400 points
    vaibhav baid said:
    not sure why we need to talk to blackhawk support

    This product is made by Blackhawk. Hence they would be aware of the best troubleshooting tips for it. If eligible for return, you can try that. I don't know the return process myself but there should be some information regarding this in whatever documents you received when the probe was purchased.