I’m having trouble generating the build file. I’m using Ubunto 22_04, Xilinx24_1, and a ZCU111 dev kit.
When I type: “ocpiadmin install platform xilinx24_1_aarch64”, the response I get is:
“The RCC platform “xilinx24_1_aarch64” is already defined in this installation…”
When I type: “ocpiadmin --package-id=ocpi.osp.xilinx install platform zcu111”, the response I get is:
“The RCC platform “zcu111” is already defined in this installation…”
When I type “ocpiadmin deploy platfrom xilinx24_1_aarch64 zcu111, the response I get is:
cp: cannot stat ‘…/projects/assets/hdl/assemblies/testbias/container-testbias_zcu111_base/target./.bitz’ : No such file or directory.”
Any help as to what I’m doing wrong would be appriciated, thanks.
Try removing the gen and lib directories in projects/ocpi.osp.xilinx/hdl/platform/zcu111.
This should bring it back to a clean slate that it will rebuild the platform worker.
Make sure you have pulled down the ZynqHeaders and ZynqReleases and are located in /tools/Xilinx directories as described in the getting started guide.
Also to note, in case you were unware the RF Data Converters are not supported on ZCU111. Current support for Xilinx RFSoC in limited to gen3 , zcu111 is gen1.
Also to note, in case you were unware the RF Data Converters are not supported on ZCU111. Current support for Xilinx RFSoC in limited to gen3 , zcu111 is gen1.
Hi Aaron - does this mean that the only way to get RF into the ZCU111 with OpenCPI currently is via an FMCOMMS2/3 board?
At the moment yes. OpenCPI support for the RFDC converter is implemented for gen3. We did not have time to go back and support RFDC gen1 which is what is found on ZCU111.
The ZCU111 OSP was tested with FMCOMMS2/3 board. An FMCOMMS4 board also works.
Thanks for clarifying @aolivarez ! This wasn’t immediately clear to me from the OSP guides; although does explain why the FMCOMMS card was appearing on the hardware setup instructions.
Where you mention it was tested - is there any example of this test (involving the RF path) within the OCPI repositories? There are mentions in the OSP of platform configuration files relating to this - but the files don’t seem to be present in the latest release?
Equally if I look at the FSK app (which I guess may have been a likely test applied) - the zcu111 is not mentioned on the list of available targets.
The files mentioned in the OSP guide that are missing can be found in the previous release v2.4.7 . These files were removed as an attempt to clarify that the latest version of the FSK app is found in the examples project. The hope was to cause cause fewer confusion with having multiple iterations of the same application scattered across supported OSPs.
Due to time constraints we did not implement the new FSK app for all platforms, ideally all OSPs would have been updated. It’s good to know that the ZCU111 is still a platform that is still being considered.
The AD9361 is currently under going a backend source implementation iteration that we are finishing up. We are just about to finish the e310 OSP. We plan to start implementing that version on other platforms soon.