When you run the hardware-software co-design workflow for SoC platforms, you generate an HDL IP core for the DUT algorithm, and then integrate the IP core into the reference design. See Hardware-Software Co-Design Workflow for SoC Platforms.
To test the HDL IP core on the target hardware, generate a software interface model. The software interface model uses AXI driver blocks to test the HDL IP core functionality in external mode simulation.
A target platform, such as ZedBoard, where you want to deploy your software interface model.
The latest version of the third-party synthesis tool, such as Xilinx®
Vivado®. See HDL Language Support and Supported Third-Party Tools and Hardware. In your MATLAB® session, set the path to that installed synthesis tool by
If you are generating the software interface model, install Embedded Coder® and Simulink® Coder™.
Install the HDL Coder™ and Embedded Coder support packages for the target platform. On the MATLAB Toolstrip, click Home > Add-Ons > Get Add-Ons button. See Get and Manage Add-Ons.
When running the IP core generation workflow, you can generate a software interface script and model from the HDL Workflow Advisor UI or at the command line.
From the UI, in the Embedded System Integration > Generate Software Interface task, select the Generate Software interface model check box.
If you are targeting standalone FPGA boards, you cannot generate a software interface model. Instead, you can generate a software interface script and test the IP core by using the MATLAB AXI Master driver.
In the Set Target Reference Design task, set Insert JTAG MATLAB as AXI Master to on. Run the workflow to the Generate Software Interface task.
In the Generate Software Interface task, select the Generate Software interface script check box and run this task.
At the command line, export the HDL Workflow Advisor settings to a script, and then use these properties with the Workflow Configuration object. This script specifies running the software interface task by generating the model and script. If you skip the task by setting RunTaskGenerateSoftwareInterface to false, then the model and script are not generated. See Configure and Run IP Core Generation Workflow with a Script.
% Export Workflow Configuration Script % ... %% Load the Model load_system('hdlcoder_led_blinking'); %% Model HDL Parameters % Set Model HDL parameters % ... hdlset_param('hdlcoder_led_blinking', 'SynthesisTool', 'Xilinx Vivado'); hdlset_param('hdlcoder_led_blinking', 'Workflow', 'IP Core Generation'); % ... % Set Workflow tasks to run hWC.RunTaskGenerateSoftwareInterface = true; hWC.GenerateSoftwareInterfaceModel = true; hWC.GenerateSoftwareInterfaceScript = true; % ... %% Run the workflow hdlcoder.runWorkflow('hdlcoder_led_blinking/led_counter', hWC);
When you run the workflow for SoC platforms, a software interface model is generated to test the HDL IP core functionality. If you have Embedded Coder and Simulink Coder installed, you can generate embedded code from the model and build and run the executable on the ARM processor. When you target standalone FPGA boards, you cannot generate a software interface model because the boards do not have an embedded ARM processor. Instead, generate a software interface script to test the IP core by using the MATLAB AXI Master.
The generated software interface model replaces the DUT algorithm in your original model with AXI driver blocks based on the target platform interface table and reference design settings. To test the HDL IP core functionality, simulate the model in external mode to run on the target hardware. The model has concurrent execution enabled by default, which means that multiple tasks are executed concurrently by the processor on board the SoC platform.
The software interface model has the same name as your original model with the
gm_ and the postfix
generated model from HDL code generation has the prefix
indicate that you are using this model as the software interface model, change the
Open the model
hdlcoder_sfir_fixed_stream. This model maps the
sfir_fixed model to the simplified AXI4-Stream protocol by
Valid signal as an input control
Open the HDL Workflow Advisor for the DUT subsystem. In the
Set Target Device and Synthesis Tool task,
IP Core Generation as Target
workflow and ZedBoard as Target
platform. Click Run this task.
In the Set Target Reference Design task, specify Default system with AXI4-Stream interface as the Target Reference Design. Click Run this task.
In the Set Target Interface task, map the DUT ports to target interfaces in the Target platform interface table. Click Run this task.
Right-click the Generate Software Interface task and select Run to selected task. Run the workflow to generate the software interface model.
The generated software interface model has the name
gm_hdlcoder_sfir_fixed_stream_interface.slx. Because your
original model uses scalar ports for the data ports
y_out_data, the Generate software
interface task displays a warning that AXI4-Stream IIO driver blocks
are not automatically generated in the software interface model. You can either
insert the driver blocks from the Embedded Coder Support Package Library for the target platform in the Simulink Library Browser or rerun the workflow by mapping the data ports to
vector signals. To see a software interface model that has the AXI4-Stream IIO
driver blocks inserted in it, open
The model uses AXI4-Stream IIO
Write (Embedded Coder Support Package for Xilinx Zynq Platform) and AXI4-Stream IIO Read (Embedded Coder Support Package for Xilinx Zynq Platform) blocks for the data ports. The filter ports are
mapped to AXI4-Lite driver blocks.
Configure the model with a stop time of
inf. On the
Hardware tab, the hardware settings specified on the model.
You can then connect, and build and run the application on the target platform to
verify the HDL IP core functionality. See Getting Started with AXI4-Stream Interface in Zynq Workflow.