You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If using more than one xclbin file, the first must be released before second is loaded.
(2017.1) Host code may look like this:
clCreateProgramWithBinary(xclbin1); // load first xclbin
... // run with first xclbin
clCreateProgramWithBinary(xclbin2); // load second xclbin
... // run with second xclbin
(2017.4) In the host code, free the current xclbin using clReleaseProgram() and clReleaseKernel() before proceeding to load subsequent xclbin files.
clCreateProgramWithBinary(xclbin1); // load first xclbin
... // run with first xclbin
clReleaseProgram(); // release program
clReleaseKernel(); // release kernel
clCreateProgramWithBinary(xclbin2); // load second xclbin
... // run with second xclbin
clReleaseProgram(); // release program
clReleaseKernel(); // release kernel
If requiring generation of profiling reports
Profiling hardware no longer pre-built in the platform. Instead, it is added compile time to the design.
This requires an update to the xocc command options.
(2017.4) Add the -profile_kernel option the xocc command to enable profile instrumentation when compiling the kernel; set profile=true in the sdaccel.ini file to collect profile data when running the application.
(2019.1) Add the -profile_kernel option the xocc command to enable profile instrumentation when compiling the kernel; set profile=true in the xrt.ini file to collect profile data when running the application.