When you run the model in external mode, the simulation time advances, but the model receives no video data from the board.
Check the Configuration Parameters of the model. On the Solver pane, uncheck Treat each discrete rate as separate task. For other model settings, see Step 3. Configure Model.
When you run the model in external mode, the simulation stops at T=0.
Check the Configuration Parameters of the model. On the Hardware Implementation pane, expand Target hardware resources and uncheck Run external mode in a background thread.
For other model settings, see Step 3. Configure Model.
The resolution of the HDMI input source must match the resolution captured with the Video Capture block. Your camera may not have been able to negotiate a supported resolution with the FMC-HDMI-CAM card. The camera may fall back to an alternate resolution if negotiation fails.
For example, when you are attempting to get HDMI input from an iPhone or iPad mini, you may see this error:
The resolution of the target for HDMI input did not match the frame size as set in the model. Update the target by changing the camera settings or the model by changing the mask parameters. Actual: 1280x720 Expected: 1920x1080
Match your settings for the camera source and the Video Capture block.
Unplug/reattach your camera to redo the negotiation.
Always use 1080p for the iPhone and iPad mini. If the device was connected and on when you booted, the device falls back to 720p. If you run a simulation without changing anything, you get the message that the resolution does not match.
If you cannot get a particular camera to work, contact tech support.
The ratio between the frame rate and the pixel rate is too large for the automatic Simulink® solver counters.
Copy and paste the fixed step size, X in the error message, to Fixed-step size (fundamental sample time) in Configuration Parameters.
The sample time is pixelSampleTime = 1/(frameRate*totalVideoLines *
totalPixelsPerLine), where totalVideoLines and
totalPixelsPerLine are settings derived from the resolution on
the Frame to Pixels block. These dimensions represent the total frame
size including blanking intervals between active lines and frames. The
frameRate is automatically configured to match the frame size
parameter of the Video Capture block. Most resolutions use 60
fps.
The error message suggests using the variable step solver, but this solver is not supported for multirate models in HDL Workflow Advisor.
You must use the fixed-step solver. If the ratio between the frame rate and the pixel rate is too large for the automatic Simulink solver counters, you may need to customize the step size.
In Configuration Parameters, select Fixed-step and
discrete solver options. Set the Fixed-step
size (fundamental sample time) to auto, or set the
step size to pixelSampleTime = 1/(frameRate*totalVideoLines *
totalPixelsPerLine), where totalVideoLines and
totalPixelsPerLine are settings derived from the resolution on
the Frame to Pixels block. These dimensions represent the total frame
size including blanking intervals between active lines and frames. The
frameRate is automatically configured to match the frame size
parameter of the Video Capture block. Most resolutions use 60
fps.
Your fixed-step size does not account for the blanking intervals added around the active frame by the Frame to Pixels block. The inactive pixels imitate the timing of a physical video system, and many streaming video processing algorithms rely on this space between active lines and frames.
Set the Fixed-step size (fundamental sample time) to
auto, or set the step size to pixelSampleTime = 1/(frameRate*totalVideoLines *
totalPixelsPerLine), where totalVideoLines and
totalPixelsPerLine are settings derived from the resolution on
the Frame to Pixels block. These dimensions represent the total frame
size including blanking intervals between active lines and frames. The
frameRate is automatically configured to match the frame size
parameter of the Video Capture block. Most resolutions use 60
fps.
'/arm-xilinx-linux-gnueabi-gcc' is not recognized as an internal or external command, operable program or batch file.
You have not set up the Xilinx®-ARM® cross-compiler tool path for Embedded Coder® Support Package for Xilinx Zynq® Platform.
Run the manual setup steps in Step 9. Setup for ARM Targeting.
Caused by: Cannot establish an SSH connection to the board with device address "192.168.4.2". Error executing command: FATAL ERROR: Network error: Connection timed out
Check the connection to your Zynq device.
If the device address is 10.10.10.1, you have not run the
manual setup steps for Embedded Coder Support Package for Xilinx
Zynq Platform.
Run the manual setup steps in Step 9. Setup for ARM Targeting.
If your model includes the Video Viewer block, external mode simulation with the default trigger duration settings runs out of memory while processing the video data frames.
Reduce the duration of the external mode trigger to avoid buffering errors. In the Code menu, select External Mode Control Panel. Click the Signal & Triggering button. In the Trigger options section, set Duration to 1.