To build a project and generate an executable, bitstream, and SD Card boot image:
- Right-clicklab1in theProject Explorerand selectBuild Projectfrom the context menu that appears.
The SDSoC™ system compiler stdout is directed to the Console tab. The functions selected for hardware are compiled using Vivado® HLS into IP blocks and integrated into a generated Vivado tools hardware system based on the selected base platform. The system compiler then invokes Vivado synthesis, place and route tools to build a bitstream, and invokes the ARM GNU compiler and linker to generate an application ELF executable file.
- In theSDx Project Settingswindow, under theReportstab, below theProject Explorertab, double-click to open theData Motion Network Report.
This report shows the connections done by the SDx environment and the types of data transfers for each function implemented in hardware. For details, see
Application Code Optimization.
![](//www.rushcopely.com/html_docs/xilinx2017_1/sdsoc_doc/topics/images/ug1028_images/lab1_data_motion_network_report.png)
- Open thelab1/Release/_sds/swstubs/mmult.cppfile, to see how the SDx system compiler replaced the original
mmult
function with one named_p0_mmult_1_noasync
that performs transfers to and from the FPGA usingcf_send_i
andcf_wait
functions. The SDx system compiler also replaces calls tommult
with_p0_mmult_1_noasync
inlab1/Release/_sds/swstubs/main.cpp. The SDx system compiler uses these rewritten source files to build the ELF that accesses the hardware functions.