When generating the output using the Model Composer Hub block, you also have the ability to Create and run testbench. When selecting this option, you are enabling the Model Composer verification flow. This causes Model Composer to generate a few more output files, including a makefile, the test bench, tb.cpp, and signals.stim as previously discussed. The purpose of the test bench is to apply input stimuli, generated during Simulink simulation, to the top-level function of the generated C++ or RTL code and compare that function's output against the output samples captured in the signals.stim file. Depending on the output generated, the verification flow runs simulation on the C++ or RTL outputs generated by Model Composer and looks for the same result as generated by Simulink.
- The model is simulated in Simulink and the input and outputs are logged into the signals.stim binary file.
- Model Composer generates the C++ code and a test bench, tb.cpp, which contains a
main()function. - Model Composer launches simulation.
- It verifies that the output from the generated C++ code matches the output logged from the Simulink simulation, signals.stim.
- In case of a mismatch, the mismatched output signal name is reported, as well as the actual and expected values.
- The result is a Pass/Fail returned by Model Composer.
Failed to find a XilinxLibrary block connected to input port.