• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 31 subscribers
  • Views 509 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CODECOMPOSER: Unable to connect to XDS560v2 JTAG Emulator

MSPM0L1306: Getting error like Cable break far-from itself

Nitin Bangar
Prodigy 90 points

Part Number: MSPM0L1306

Tool/software:

Hello,

I am using my custom board with MSPM0L1306 in SWD mode 2wire. and it gives me error while flashing code like cable break far-from itself.

One time runs successfully when i did changes in Properties Debug window and it worked but i forgot that settings and now again getting same issue. One time worked means there is only project setting issue.

I am using XDS200 debugger for flashing code

Connection as

1. SWDIO to TMS with pull-up

2. SWCLK to TCK

3. 3.3V to VCC

4. GND to GND

5. Reset to nReset

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\ADMINI~1\AppData\Local\TEXASI~1\
CCS\ccs1271\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Apr 19 2024'.
The library build time was '18:50:34'.
The library package version is '12.7.0.00130'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

[End]

Please guide me.

Thanks,

Nitin

  • 0
    TI__Expert 7871 points

    Hi Nitin,

    After looking into this issue, it seems like there was another case similar to yours for a different device. Since you are using a custom board, you may be missing necessary pull ups or pull downs. You can find the E2E thread here. 

    You mentioned that you were able to flash it once successfully. Were you able to determine if the program was running as intended on the device?

    Does this apply to your situation:

    Please let me know any further findings or if the information I have provided seems to be relevant to what you are experiencing.

    Best,

    Owen

  • 0 in reply to Owen Li
    Prodigy 90 points

    Hello,

    Were you able to determine if the program was running as intended on the device? --> YES I am able to run the code successfully on same same board but again it gave same error.

    Due it i know that the connection is correct.

    please let me know if any setting issue

    Thanks,

    Nitin

  • 0 in reply to Nitin Bangar
    TI__Expert 7871 points

    Hi Nitin,

    Did you read over everything in my last reply? Can you please confirm whether or not any of the content applies to you.

    Best,

    Owen

  • 0 in reply to Owen Li
    TI__Expert 7871 points

    Hi Nitin,

    Furthermore, can you try these actions:

    • Factory reset: pulling reset to GND while device is off and then powering on the device.
    • Share what your Debug properties window looks like
    • I suggest you take look over this E2E thread.

    Please note, we do not recommend using the XDS200 for programming MSPM0. 

    Best,

    Owen

  • 0 in reply to Owen Li
    Prodigy 90 points

    Hello,

    I did Factory Reset still same error.

    In Debug properties window I Kept default settings.

    the pic you shared the same error i got only difference is using XDS200 debugger and connection i already shared above.

    That connection was working in my previous version of board with MCU schematic as it is in current still got cable break error.

    Thanks,

    Nitin

  • 0 in reply to Nitin Bangar
    TI__Expert 7871 points

    Hi Nitin,

    Did you see if any of the steps in the other E2E thread resolve your issue?

    Are you using any of the pins for flashing the code as GPIO, etc?

    The issue makes me want to believe that after the first flash, the pins you are using were configured in some way that prevents any subsequent successful flashes.

    Can you please provide in more detail how you are configuring your pins? What changed between the previous version of the board?

    Best,

    Owen

  • 0 in reply to Owen Li
    Prodigy 90 points

    Hello,

    That E2E thread is not useful for me as i am using MSPM0L1306. I checked it but didn't work.

    One more observation i found that when i connect I2C pins PA0 and PA1 also to Logic analyzer the i am able to flash but stuck at I2C_STATUS_TX_INPROGRESS. I am using BQ90x I2C example code on it. But when I2C pins disconnected from Logic analyzer then get Cable break while flashing.

    Thanks,

    Nitin

  • 0 in reply to Nitin Bangar
    TI__Expert 7871 points

    Hi Nitin,

    I shared this issue with my team and we think that it may be a hardware issue with the custom board. If you'd like, please share the schematic with your local FAE or sales representative and we will perform a review on the layout. Without more information, I am unable to help with this issue at the moment.

    Best,

    Owen

  • 0 in reply to Owen Li
    Prodigy 90 points

    Hello,

    Please check this.

    Regards,

    Nitin

  • 0 in reply to Nitin Bangar
    TI__Expert 7871 points

    Hi Nitin,

    I am unable to read the schematic. Is it possible for you to share the PDF or file with your local FAE or sales representative? This will also allow the whole team to review the schematic.

    Best,

    Owen