Error: Simulation Time in Ticks is not supported with XCP Classic Interface.

I am trying to use Monitor and Tune in the hardware tab to generate a code execution profile, and I keep getting the following error

"Error: Simulation Time in Ticks is not supported with XCP Classic Interface."

Simulation time has been specified in seconds, so I have no idea why I am getting this error. My configuration parameters were selected based on the f28379D_profiling_xcp example model (https://www.mathworks.com/help/ti-c2000/ug/profling-external-xcp-mode.html).

Answer 1

[Saurav]

Hi @Zane,

Based on the information provided I’m assuming that the error is related to code execution profiling and the hardware is Texas Instruments C2000 board. This assumption is based on the example documentation being followed. However, since this information has not been explicitly mentioned, please verify it.

Here's a potential workaround you can try in MATLAB R2023b:

1. Open MATLAB R2023b. Navigate to the following path in your MATLAB installation directory: ‘$(MATLABROOT)\R2023b\rtw\c\tlc\mw\setuplib.tlc’.
2. Open the ‘setuplib.tlc’ file in a text editor.
3. Locate line 1430 in the file.
4. Modify this line to read: ‘%elseif 0’.

Let me know if this addresses the error you're experiencing. If you have any further questions or need additional assistance, feel free to reach out!

Thanks!

[Zane]

Hi Saurav,

I apologize for the late response. Unfortunately I have not had the opportunity yet to try the potential fix as this fix requires admin privileges and I need to get IT approval in order to do so. Your assumption is correct though; I am attempting to perform code execution profiling on a TI C2000 device.

Could you please elaborate on the function of the line of code I am replacing?

elseif !FEVAL("codertarget.target.isCoderTarget", ::CompiledModel.Name)

While I don't know what exactly these objects and methods are, based of the context it looks like this line of code checks that the target device of the model is the correct target interfaced with (I'm assuming) embedded coder. To enter that case, FEVAL needs to return false. Forcing this line to zero would probably get it to work, but what would happen if the two target references are mismatched? Is the real issue that my compiled model's target is not the same as the embedded coder target? If so, is fixing that another potential solution? How would one go about fixing that?

Regards,

Zane