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 -1141)

Other Parts Discussed in Thread: TM4C1294NCPDT

I have an XDS100v2 USB emulator that I am trying to use to program a TM4C1294NCPDT. When ever I try to debug the program I get the following error message:

CORTEX_M4_0: Error connecting to the target: (Error -1141 @ 0x0) Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)

I am using CCS v5.4.0 on a Windows 7 Professional computer.

When I use Test Connection it returns that the JTAG IR Integrity scan-test has succeeded.

Below is an image of the advanced target configuration window with the settings I am trying to use to connect.

Does anyone know what can be causing this error and how can I fix it?

  • Hello Joseph,
    The CCS version, and emulator pack version, being used are pretty old. Can you try updating your CCS version? CCSv6.1.0 is the current latest.

    Thanks
    ki
  • Joseph Marineau said:
    Below is an image of the advanced target configuration window with the settings I am trying to use to connect.

    The image shows that Adaptive clocking has been selected.

    The Cortex-M4 core doesn't use adaptive clocking, so try not selecting adaptive clocking.

    [Given that Test Connection was working, not sure if the selection of adaptive clocking is causing the error]

  • Thank you for responding,

    I uninstalled my CCS and installed the new version. After I again ran the connection test which still came back with no errors. This time when I tried to run the debug I received a different error.

    CORTEX_M4_0: Error connecting to the target: (Error -2062 @ 0x0) Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.641.0)

    Following the advice of Chester Gillon who responded after you I changed the "adaptive clocking" to "fixed default 1.0MHz frequency" and still received the above error.
  • Something else I have attempted to isolate the problem is I created a target configuration that is not connected to a project and tried to load and connect with it. The new target configuration had all of the same settings as the original target configuration shown except the JTAG TCLK Frequency was set to Fixed default 1.0 MHz.

    I launched the target configuration and selected show all cores in the right click menu. With the all the cores shown I tried to connect each core individually. as shown in the image below the CS_DAP_0 core connected but an error message was displayed in the console.

    When I try to connect the actual Cortex M4 core I again get the Error connecting to target, Unable to halt device (error -2062 @0x0).

    I will continue to update if I get any more information or if I find a solution.

  • Hi,

    The GEL error can be disregarded - the DAP probably tried to reset the CortexM4 core and the GEL_Reset() callback was called in the wrong context.

    One additional thing I would try is to unlock the device - something referenced on this thread using the Lmflash utility and the screenshot below using CCSv6. Just launch the target manually and go to menu Tools --> On chip flash

    Hope this helps,

    Rafael