To help you diagnose issues related to code generation, Model Composer generates a log file, model_composer.log, that is written to the Code Directory specified on the Model Composer Hub block.
By default, Model Composer generates code for the model using a streaming
micro-architecture in which blocks run concurrently via task pipelining, or dataflow.
However, in some cases this streaming micro-architecture is not achievable, because the
model includes an
xmcImportFunction block that does not
support streaming for example. In this case, Model Composer generates code in which the
blocks operate sequentially. The Model Composer log file includes information to help
you identify when this condition occurs, and what some possible causes might be.
The log file also contains information related to which blocks are used in the Model Composer model.
If Target on the Model Composer Hub block is set to HLS C++ code, and Create and run testbench is selected, the model_composer.log file will contain the output from running the C++ verification.
If Target is set to IP Catalog or System Generator, information related to running Vitis HLS is provided. In these cases, more detailed information can be found in the vitis_hls.log file which can also be found in the directory specified in Target directory.