Error: "Could not connect to target application: XCP internal error: timeout expired, in response to XCP CONNECT command" using Monitor and Tune for F280025C MCU (C2000)

I have a launch pad for the F280025C, I was able to monitor and tune with the launch pad configuration file. However, when I power the launchpad using external power supply (not power from the USB), and using an external JTAG debug probe TMDSEMU110-U (connecting TMS, TCK, Vref, GND), i was unable to monitor and tune it anymore. Though I can flash it.

I used F28002x configuration file and modified to the way that I can use an external JTAG debugger probe, and use it as my configuration file. I was able to flash the code to the MCU, however, Matlab cannot was unable to monitor the hardware afterward. I am using internal clock, but i also tried to set the CLK as 20MHz using external CLK as well and still not working. The JTAG clock is set to 2.5MHz. I made sure the external mode COM is set to the correct COM.

Here are screenshot of my configuration and initialization for my hardware implementation setting:

CCS configuration file -

Matlab hardware implementation -

Build Summery on simulink -

[德才]

same problem,do you slove it?

[Marc]

same problem, any update?

[Parth Patel]

same Issue with C2000 blockset

[Gustavo Blanco]

same problem

[Jacobo]

Same problem and not related with OSCCLK (launchPad 79D - 10MHz)

[Mahesh Bharath Pudutha]

I am facing the exactly same problem for a very long time. But the controller which I am using is TMS320F28335 delfino series. Is JTAG mandatory to deal with such problems?

The error looks like the below:

Error:External Mode Open Protocol Connect command failed

Caused by:

Could not connect to target application: XCP internal error: timeout expired, in response to XCP CONNECT command

[Jacobo]

ESP32-WROVER has same issue.

According to Arun it can be solved (see link below), but not working as well~

https://www.mathworks.com/matlabcentral/answers/2005517-troubleshooting-esp32-wroom-esp32wrover-setup-error-in-simulink-support-package-for-arduino-hardware

[Finn]

Please did you solve it ?

Answer 1

[Gowthami]

Hello,

The external mode requires an active COMM port connection between the target and the host PC.

Kindly check if there is any COMM port connection present under the device manager--> ports, If not you will not be able to run the external model.

I could also suspect the issue because of specific clocking options. If this is the case, kindly go through the following solution:

For the TI F280025C Launchpad board, the external oscillator mentioned in the user guide is 20 MHz and not 10 MHz. 20 MHz is the default value for the oscillator clock frequency when using an external oscillator for the TI F280025C Launchpad.

If you switch to the internal oscillator and then switch back to the external oscillator, you will need to manually update the configuration box to reflect the oscillator clock (OSCCLK) frequency appropriate for the specific board you are using. Please change the oscillator clock frequency from 10 MHz to 20 MHz in the configuration settings.

[Gustavo Blanco]

Do the ADC's have a limit on how small the sample time can be? The problem is resolved if the sample time is 0.001 seconds for the ADCs, but I want a smaller sample time.

[Mahesh Bharath Pudutha]

I am facing the exactly same problem for a very long time. But the controller which I am using is TMS320F28335 delfino series. Is JTAG mandatory to deal with such problems? Kindly give me a solution.

The error looks like the below:

Error:External Mode Open Protocol Connect command failed

Caused by:

Could not connect to target application: XCP internal error: timeout expired, in response to XCP CONNECT command

[vallela]

Has anyone got the solution for this?

[vallela]

Has anyone got the solution for this?

[Ibrahim]

As mentionned by @Gowthami you should set 20MHz instead 10 with this Target.

For F28388D it must be 25 as described in datasheet of TI