The behaviour that is observed when the baud rate is raised to 921600—no data for a few seconds, then sampling resumes—is often caused by a combination of these factors:
- Buffering Delay The serial port needs a moment to start sending data at high speed. During this time, no signal appears.
- Wrong Clock Setting Your board uses a 10 MHz oscillator, but Simulink may default to 20 MHz. This mismatch causes SCI timing issues. ➤ Fix: In Hardware Settings → Clocking, set OSCCLK = 10 MHz.
- Pin Setup SCI_A uses GPIO42 (TX) and GPIO43 (RX). If not correctly set in Simulink, data won't send. ➤ Fix: Set the right pins for SCI_A.
- Computer-Side Serial Limits Your PC may delay starting serial communication, especially at very high baud rates.
Next Steps Recommendation
- Correct the oscillator setting and GPIO configuration.
- Apply a streaming buffer pattern (MathWorks Fast Serial Data Monitoring examples are very effective).
- Rebuild and re-run with high baud. If the first few seconds are still blank but then streaming starts, the issue is resolved—this startup delay is expected behavior under this mode with high-speed streaming.
If the system never outputs data, it’s likely an OSCCLK or pin misconfiguration. Fixing those should restore full external-mode operation, even at 921,600 bps.
A similar issue has been discussed below in the MATLAB Answer. Refer it for more info:
Let me know once you've tried the above—I'd be happy to help validate any settings in your Simulink model or suggest next steps!