C2000 - Issue Running Monitor and Tune in Simulink Model

Programming the image from the TMDSCNCD28379D on the EEPROM using the FT_PROG utility caused two COM ports to become one working one in our first prototype, with the ability to communicate actively. However, in subsequent boards, this did not occur. In order to get the system to appear in the COM ports section, we had to go to the Texas Instruments Debug Probes section and go to properties of either the XDS100 Class Auxiliary or Debug ports, and override the normal device behavior by selecting the Load VCP option. This then allows the use of the XDS100 Class USB Serial Port for deploying built programs to target, but does not allow active communication.

Without this setting enabled on either of the two XDS100 probes, their corresponding COM port does not appear and thus it cannot be programmed as a target.

In either of the two configurations, when the computer tries to connect with the board with an open line of communication after deploying the build, it gives the following error.

We asked in the TI forum, and they encouraged us to post this also on Mathworks Forum.

https://e2e.ti.com/support/tools/simulation-hardware-system-design-tools-group/sim-hw-system-design/f/simulation-hardware-system-design-tools-forum/1575732/tida-01606-f28379d-com-port-active-communication-issues/6079880

Answer 1

[Abhipsa]

Hello @ITDEPT, I understand that when running Monitor and Tune for a Simulink model targeting a C2000 board (like F28379D), the connection fails — only one COM port appears after programming the board with FT_PROG, or no COM ports appear at all, and Simulink cannot establish an external-mode connection.”

Everything points to a host-to-target comms problem (COM/VCP driver/enumeration for the XDS probe), which blocks External mode (Monitor & Tune) from opening the serial link. If your model builds and deploys but only fails at connect time, the model is fine.

Quick ways to double-check it’s not the model:

• The model generates code and runs standalone on the board (e.g., LED blink or algorithm runs without Monitor & Tune).
• Failure happens only when “Monitor & Tune” tries to connect (timeout/can’t open COM). -> Host/driver/port issue.
• serialportlist("available") in MATLAB doesn’t show the board’s COM port, or the Device Manager doesn’t expose an “XDS100 Class USB Serial Port (COMx)”. -> Driver/VCP config.

You can reach out to MathWorks support, for furthur assistance