It would be beneficial to have a seperate hw_emu target available for verification in the VitisBuild flow. The option should also take care of calling emconfigutil to generate the required configuration JSON. In combination with #180, this would increase our debugging capabilites by a lot.
vitis_build_target option in the DataflowBuildConfig (hw or hw_emu)- automatically creates
xrt.ini and emconfig.json
- Automatically creates a minimal C++ driver that simply pushes in
N samples (stored as a template, along with a Makefile)
- Automatically creates a runner script that correctly sets
XCL_EMULATION_MODE
- Automatically passes not only
--target hw_emu but also -g to v++
- Debug mode maybe also settable via a
DataflowBuildConfig option?
- Automatic execution? (As a separate step?)
(May need to be revised accordingly with changes in #27, or with an eventual unified Zynq/Alveo build backend)
It would be beneficial to have a seperate
hw_emutarget available for verification in the VitisBuild flow. The option should also take care of callingemconfigutilto generate the required configuration JSON. In combination with #180, this would increase our debugging capabilites by a lot.vitis_build_targetoption in theDataflowBuildConfig(hworhw_emu)xrt.iniandemconfig.jsonNsamples (stored as a template, along with a Makefile)XCL_EMULATION_MODE--target hw_emubut also-gtov++DataflowBuildConfigoption?(May need to be revised accordingly with changes in #27, or with an eventual unified Zynq/Alveo build backend)