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)

302 次查看（过去 30 天）

Yun Liu 2023-2-27

2
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1920075-error-could-not-connect-to-target-application-xcp-internal-error-timeout-expired-in-response-to

评论： Finn 2024-2-28

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 -

8 个评论
显示 6更早的评论隐藏 6更早的评论

Jacobo 2023-12-11

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 2024-2-28

Please did you solve it ?

请先登录，再进行评论。

请先登录，再回答此问题。

回答（1 个）

Gowthami 2023-4-19

2
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1920075-error-could-not-connect-to-target-application-xcp-internal-error-timeout-expired-in-response-to#answer_1218788

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.