Can I generate HDL Code for models with Xilinx System Generator blocks?

Does HDL Coder support code generation for models including Xilinx System Generator for DSP blocks?

Answer 1

[MathWorks Support Team]

Yes, this workflow is supported, and the documentation includes examples illustrating potential usages. This approach requires "targeted" code generation, in which Xilinx System Generator for DSP generates the code for Xilinx blocks, and HDL Coder™ generates code from Simulink blocks.

This overall workflow for Xilinx System Generator within HDL Coder is described at this documentation page; pay particular attention to the requirements and limitations listed near the bottom of the page.

https://www.mathworks.com/help/hdlcoder/ug/code-generation-with-xilinx-system-generator-subsystems.html

Furthermore, the following example may be helpful when getting started. It illustrates the workflow, and elaborates on how this works: "HDL Coder™ generates HDL code from the Simulink blocks, and uses Xilinx System Generator to generate HDL code from the Xilinx System Generator Subsystem blocks."

https://www.mathworks.com/help/hdlcoder/ug/using-xilinx-system-generator-for-dsp-with-hdl-coder.html?s_tid=srchtitle

Answer 2

[Kiran Kintali]

If you have access to R2018a can you try to reproduce the issue in that release? We suspect this is already resolved in 18a release.

Thanks.

[Kiran Kintali]

ok, let us know. Thanks

Answer 3

[Kiran Kintali]

While running the simulation using the TCL script generated by HDL Coder, HDL Coder generates SysGen_with_HDL_Coder_CustomTCL_run.tcl script that is using a Vivado simulation command, launch_modelsim.

The TCL command “launch_modelsim” was supported in older versions of Vivado. Vivado 2017.1 supports following commands to use ModelSim simulator.

    set_property   target_simulator "ModelSim" [current_project]
    launch_simulation -mode "post-synthesis" -type "functional"

In the example above, the options -mode “post_synthesis” and –type “functional” are just for example and should be replaced with an appropriate options.

This issue should be resolved in 18a and older releases. Please confirm.

Thanks