I am working with c2000 f28379d. In "external mode ", if I set 1 second for LED BLINK, I am getting the same result. But "connected IO mode" fails . How to synchronize.

[praguna manvi]

Hi @ARUN,

Can you share the model to reproduce this issue?

Answer 1

[Kothuri]

Hi ARUN,

Connected I/O mode and External mode operate differently in terms of how they communicate with the hardware and handle real-time constraints.

• Connected I/O Mode may fail due to timing mismatch as it relies on the communication link between Simulink and the F28379D hardware, which is often slower than the actual hardware processing speed.
• Real-Time Violation is due to if your LED blink logic expects precise 1-second intervals, the communication delay will prevent Connected I/O mode from maintaining the timing.
• In Connected I/O mode, the control logic runs in Simulink on the host computer, and commands are sent to the hardware (e.g., the LED state change) over a communication interface (e.g., USB, UART).
• The hardware acts as an I/O interface, but the timing of operations depends on the communication link and Simulink's execution speed.
• To rectify the issue, set the sample time of your logic to a value that ensures commands are sent frequently enough. For example, use a “fixed-step solver” with a step size of 0.1 seconds.

You can refer the below documentation link for more info on Connected I/O

https://www.mathworks.com/help/releases/R2023b/ti-c2000/ug/connected-io-example.html#responsive_offcanvas

https://www.mathworks.com/help/releases/R2023b/ti-c2000/ug/connected-io-simulation.html#mw_0d413a20-030d-46f7-8523-a7c31f027939