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.

Error connecting to the target: (Error -183 @ 0x0)

Other Parts Discussed in Thread: TMS320F2802

Hello!

I am trying to connect the TMS320-XDS100v3 on CCv6. I hit "file" --> "new" --> "Target configuration file". In Target configurations, I made a new configuration file and gave it a name. At "Connection" I chose Texas Instruments XDS100v3 USB Debug Probe and under "Board or Device" I checked TMS320F2802. Saved the file and went to the advanced options to see if everything was OK. 

I right-clicked on "XDS100v3.ccxml" and then "Launch Selected Configuration"

Then I right-clicked "Texas Instruments XDS100v3 USb Probe_0/C28xx (Disconnected : Unknown)" --> "Connect Target" and this error message comes up:

Error connecting to the target:
(Error -183 @ 0x0)
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
(Emulation package 5.1.641.0)

Any idea how I can fix this error and connect the device?

  • Hi Kris,

    Which CCS version are you using? Also, did you try replacing the data cable?

    Regards,
    Gautam
  • Hi Gautam!

    I'm using Code Composer version 6.1.0. By "data cable", do you mean the usb-cable to the xds100? If so, no I have not, but I don't think the cable is the problem. I will try to replace it though just to be sure.

  • Hi,

    The specific error is explained better at this post:
    e2e.ti.com/.../1458499

    Hope this helps,
    Rafael
  • Hi Desouza!

    I'm afraid it didn't help me much. I tried to change the TCLK speed as recommended in one of the posts and the other one only told me how important the usb-cable is. That it has to be good quality cables. I did try to change the usb-cables, but the same error occures. The one post with the company, they had big problem with the usb-cables and they thought they were in order... I do think the usb-cable is in order, but I might be wrong.

    Do you have any more ideas on how I can connect the xds100v3? Thanks for the replies!
  • When you connect the datacable are you able to see the emulator powered up? ie check your device manager whether the emulator is detected or not.

    Regards,
    Gautam
  • Would my Build Settings have anything to do with it? (Project --> Show Build Settings)
  • Both red and green leds are powered and the XDS100v3 is shown recognized at controll panel --> usb-devices.

  • Hi,

    How exactly is your XDS100 being recognized by Control Panel? The reason is that another customer had trouble with his XDS100v3 from Olimex and the string shown in Control Panel was radically different than the one I saw with mine...

    Also, if you are using the same Olimex XDS100v3, can you double-check where that small board adapter is placed? In my case the board adapter is closer to the JTAG debug probe. If I flip the cable and leave the adapter end connected to the target board instead, I get connection errors.

    Hope this helps,

    Rafael

  • When I plug in the usb from the xds100, I can see from"Devices and printers" that it shows the XDS100v3 (I'm from Norway, so it's written in norwegian):

    Here is how I'm connecting it:

    I used to connect to the 14-pin jtag on the right side of the picture above, but now when I switched it finally connected! But now a new error has shown...The xds is connected to a PCB I've designed:

    As I right-click on "Texas Instruments XDS100 XDS100v3 USB Debug Probe_0/C28xx" and hit "connect target" it says "suspended", which I think is the right behavior? A new message says "No Source available for "0x3ff7bf" and my variable doesn't have any values:

      As you can see on the picture, I'm currently running proj_lab05a.c. Sorry for all the pictures as it can be confusing, but it would be nice of you if you helped me with this problem too. Thanks!

  • Hi,

    Thanks for sending the details; you surely got past the basic connection error, as CCS is able to properly communicate with the device.

    Kristian Agustin Jensen said:
    As I right-click on "Texas Instruments XDS100 XDS100v3 USB Debug Probe_0/C28xx" and hit "connect target" it says "suspended", which I think is the right behavior?

    Yes, it is. You are connecting to the core manually, as described on section 4.2 of the page below:

    processors.wiki.ti.com/.../Debug_Handbook_for_CCS

    Kristian Agustin Jensen said:
    A new message says "No Source available for "0x3ff7bf"

    For reference check this post.

    Kristian Agustin Jensen said:
    my variable doesn't have any values:

    It is because at this point your processor has no code and symbols loaded. The same section above explains how to load code to the core, thus allowing you to see the global variables in the expressions view.

    Hope this helps,

    Rafael

  • "After the debugger launches, connection can be established by right-clicking on the core and selecting Connect. Once the core finishes executing its initialization GEL script (if one is required), the code or symbols can be loaded by going to menu Run --> Load --> Load Program or Load symbols".

    This might be a dumb question, but which file am I looking for when I hit "Run" --> "Load" --> "Load Symbol"? Something about BOOT ROM, but I can't find this file... Thanks in advance!

  • Hi,

    If you already have code loaded and running on your device, the .out file created when you build your project will have the debug symbols - no special file is needed. Obviously that your project must have been built with debug symbols (the -g option) - that is likely the case, as it is the default configuration of any project.

    Hope this helps,
    Rafael
  • Thanks you for being so helpful! I get values on the expressions now, but the values doesn't seem right. For example gMotorVars.Flag_enableSys = 40985. This values should be a bool value, 0 if I remember correctly. 

    It think this is because of my coding in the hal.c file where the channels have not been changed yet. I will take a look at it.