qadc to qdac loopback

MP
Miller, Peter
Thu, Jun 14, 2018 3:38 PM

The goal is to implement a simple iqsample loopback Application from qadc to qdac on Zed+fmcomms3 to measure the round-trip delay. The Application xml is below. It fails with:
No acceptable implementations found in any libraries for "ocpi.assets.devices.ad9361_spi".
The question is: does this need an assembly with nothing in it to get the container?

<!-- The mod_tx_file_rx_app application xml file --> <Application Package="ocpi.assets"> <!-- HDL Components--> <!-- must be instanced here in app XML as a workaround for AV-3799 --> <Instance Component="ocpi.assets.devices.ad9361_spi" name="ad9361_spi"/> <Instance Component="ocpi.assets.devices.ad9361_data_sub" name="ad9361_data_sub"> <Property Name="LVDS_p" value="true"/> <!-- FMCOMMS3 must use LVDS mode --> </Instance> <Instance Component="ocpi.assets.devices.ad9361_adc_sub" name="ad9361_adc_sub"> <Property Name="LVDS_p" value="true"/> <!-- FMCOMMS3 must use LVDS mode --> </Instance> <Instance Component="ocpi.assets.devices.ad9361_config" name="ad9361_config"/> <Instance Component="ocpi.assets.devices.ad9361_config_proxy" Slave="ad9361_config" name="ad9361_config_proxy"/> <Instance Component="ocpi.core.rx" name="rx"> <Property Name="TYPE_p" Value="fmcomms3"/> <Property Name="sample_rate_MHz" Value="20.0"></Property> <Property Name="frequency_MHz" Value="2462.0"></Property> <Property Name="rf_gain_dB" Value="6"></Property> <Property Name="enable_log_info" Value="false"></Property> </Instance> <Instance Component="ocpi.core.tx" name="tx"> <Property Name="TYPE_p" Value="fmcomms3"/> <Property Name="sample_rate_MHz" Value="20.0"></Property> <Property Name="frequency_MHz" Value="2462.0"></Property> <Property Name="rf_gain_dB" Value="0.0"></Property> </Instance> <Instance Component="ocpi.assets.devices.qdac" Model="hdl" name="qdac"/>
<Instance Component="ocpi.assets.devices.qadc" Model="hdl" name="qadc"/>
<Connection>
    <Port Instance="qdac" Name="out"></Port>
    <Port Instance="qadc" Name="in"></Port>
</Connection>
</Application>

% ocpirun -l 8 --library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports>
OCPI( 8:221.0967): Error Exception: Error: file qadc_qdac_loopback_fmcomms3_app.xml (or qadc_qdac_loopback_fmcomms3_app.xml.xml) does not exist
Exiting for exception: Error: file qadc_qdac_loopback_fmcomms3_app.xml (or qadc_qdac_loopback_fmcomms3_app.xml.xml) does not exist
% cd /mnt/ocpi.wifiproject/applications/qadc_qdac_loopback/
<assets/exports" qadc_qdac_loopback_fmcomms3_app.xml
OCPI( 8:239.0352): Processing XML system configuration file: "/mnt/card/opencpi/system.xml"
OCPI( 8:239.0353): Loading the "rcc" "container" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_rcc_s.so"
OCPI( 8:239.0362): Registering/constructing container driver: rcc
OCPI( 8:239.0362): Registering/constructing driver: rcc
OCPI( 8:239.0363): Loading the "hdl" "container" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_hdl_s.so"
OCPI( 8:239.0382): Registering/constructing container driver: hdl
OCPI( 8:239.0382): Registering/constructing driver: hdl
OCPI( 8:239.0383): Loading the "pio" "transfer" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_pio_s.so"
OCPI( 8:239.0390): Registering/constructing transfer driver: pio
OCPI( 8:239.0390): Registering/constructing driver: pio
OCPI( 8:239.0391): Loading the "dma" "transfer" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_dma_s.so"
OCPI( 8:239.0395): Registering/constructing transfer driver: dma
OCPI( 8:239.0395): Registering/constructing driver: dma
OCPI( 8:239.0395): Transfer Driver manager has protocol ocpi-dma-pio
OCPI( 8:239.0395): Transfer Driver manager has protocol ocpi-smb-pio
OCPI( 8:239.0395): Performing discovery for all transfer drivers
OCPI( 8:239.0395): Performing discovery for all library drivers
OCPI( 8:239.0395): Searching directory /mnt/ocpi.core/exports recursively, from OCPI_LIBRARY_PATH
OCPI( 8:239.0400): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.core/exports/imports", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:242.0290): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.core/exports/lib/rcc/platforms/centos6", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:242.0309): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.core/exports/lib/rcc/platforms/xilinx13_3/README", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:242.0350): Searching directory /mnt/ocpi.assets/exports recursively, from OCPI_LIBRARY_PATH
OCPI( 8:249.0207): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/pcie_4243_hip_s4gx_gen2_x4_128", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:249.0245): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/stratix4", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:249.0246): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/temac_v6", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:249.0248): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/temac_v6_bb", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:249.0346): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/imports", is nonexistent, not a normal file, or a broken link.  It will be ignored
OCPI( 8:249.0346): Performing discovery for all container drivers
OCPI( 8:249.0346): Searching for local Zynq/PL HDL device.
OCPI( 8:249.0346): There is no bitstream loaded on this HDL device: PL:0
OCPI( 8:249.0348): Searching for local PCI-based HDL devices.
OCPI( 8:249.0348): Searching for local HDL simulators.
OCPI( 8:249.0354): No HDL platforms found (no lib/platforms/*) in path /mnt/net/cdk/../project-registry/ocpi.cdk:/mnt/net/cdk/../project-registry/ocpi.wifiproject:/mnt/net/cdk/../project-registry/ocpi.assets:/mnt/net/cdk/../project-registry/ocpi.core:/mnt/net/cdk
OCPI( 8:249.0354): Searching for RCC containers, and implicitly finding one.
OCPI( 8:249.0354): Transport ocpi-scif-dma not supported in this process.  Not loaded/spec'd in system.xml?
OCPI( 8:249.0354): Transport ocpi-socket-rdma not supported in this process.  Not loaded/spec'd in system.xml?
OCPI( 8:249.0355): Transport ocpi-udp-rdma not supported in this process.  Not loaded/spec'd in system.xml?
OCPI( 8:249.0356): Error Exception: No acceptable implementations found in any libraries for "ocpi.assets.devices.ad9361_spi".  Use log level 8 for more detail.
Exiting for exception: No acceptable implementations found in any libraries for "ocpi.assets.devices.ad9361_spi".  Use log level 8 for more detail.

Sincerely,
Peter B. Miller
Potomac: (301) 765-9668

--------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.

The goal is to implement a simple iqsample loopback Application from qadc to qdac on Zed+fmcomms3 to measure the round-trip delay. The Application xml is below. It fails with: No acceptable implementations found in any libraries for "ocpi.assets.devices.ad9361_spi". The question is: does this need an assembly with nothing in it to get the container? <!-- The mod_tx_file_rx_app application xml file --> <Application Package="ocpi.assets"> <!-- HDL Components--> <!-- must be instanced here in app XML as a workaround for AV-3799 --> <Instance Component="ocpi.assets.devices.ad9361_spi" name="ad9361_spi"/> <Instance Component="ocpi.assets.devices.ad9361_data_sub" name="ad9361_data_sub"> <Property Name="LVDS_p" value="true"/> <!-- FMCOMMS3 must use LVDS mode --> </Instance> <Instance Component="ocpi.assets.devices.ad9361_adc_sub" name="ad9361_adc_sub"> <Property Name="LVDS_p" value="true"/> <!-- FMCOMMS3 must use LVDS mode --> </Instance> <Instance Component="ocpi.assets.devices.ad9361_config" name="ad9361_config"/> <Instance Component="ocpi.assets.devices.ad9361_config_proxy" Slave="ad9361_config" name="ad9361_config_proxy"/> <Instance Component="ocpi.core.rx" name="rx"> <Property Name="TYPE_p" Value="fmcomms3"/> <Property Name="sample_rate_MHz" Value="20.0"></Property> <Property Name="frequency_MHz" Value="2462.0"></Property> <Property Name="rf_gain_dB" Value="6"></Property> <Property Name="enable_log_info" Value="false"></Property> </Instance> <Instance Component="ocpi.core.tx" name="tx"> <Property Name="TYPE_p" Value="fmcomms3"/> <Property Name="sample_rate_MHz" Value="20.0"></Property> <Property Name="frequency_MHz" Value="2462.0"></Property> <Property Name="rf_gain_dB" Value="0.0"></Property> </Instance> <Instance Component="ocpi.assets.devices.qdac" Model="hdl" name="qdac"/> <Instance Component="ocpi.assets.devices.qadc" Model="hdl" name="qadc"/> <Connection> <Port Instance="qdac" Name="out"></Port> <Port Instance="qadc" Name="in"></Port> </Connection> </Application> % ocpirun -l 8 --library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports> OCPI( 8:221.0967): Error Exception: Error: file qadc_qdac_loopback_fmcomms3_app.xml (or qadc_qdac_loopback_fmcomms3_app.xml.xml) does not exist Exiting for exception: Error: file qadc_qdac_loopback_fmcomms3_app.xml (or qadc_qdac_loopback_fmcomms3_app.xml.xml) does not exist % cd /mnt/ocpi.wifiproject/applications/qadc_qdac_loopback/ <assets/exports" qadc_qdac_loopback_fmcomms3_app.xml OCPI( 8:239.0352): Processing XML system configuration file: "/mnt/card/opencpi/system.xml" OCPI( 8:239.0353): Loading the "rcc" "container" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_rcc_s.so" OCPI( 8:239.0362): Registering/constructing container driver: rcc OCPI( 8:239.0362): Registering/constructing driver: rcc OCPI( 8:239.0363): Loading the "hdl" "container" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_hdl_s.so" OCPI( 8:239.0382): Registering/constructing container driver: hdl OCPI( 8:239.0382): Registering/constructing driver: hdl OCPI( 8:239.0383): Loading the "pio" "transfer" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_pio_s.so" OCPI( 8:239.0390): Registering/constructing transfer driver: pio OCPI( 8:239.0390): Registering/constructing driver: pio OCPI( 8:239.0391): Loading the "dma" "transfer" driver from "/mnt/net/cdk/lib/linux-x13_3-arm/libocpi_dma_s.so" OCPI( 8:239.0395): Registering/constructing transfer driver: dma OCPI( 8:239.0395): Registering/constructing driver: dma OCPI( 8:239.0395): Transfer Driver manager has protocol ocpi-dma-pio OCPI( 8:239.0395): Transfer Driver manager has protocol ocpi-smb-pio OCPI( 8:239.0395): Performing discovery for all transfer drivers OCPI( 8:239.0395): Performing discovery for all library drivers OCPI( 8:239.0395): Searching directory /mnt/ocpi.core/exports recursively, from OCPI_LIBRARY_PATH OCPI( 8:239.0400): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.core/exports/imports", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:242.0290): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.core/exports/lib/rcc/platforms/centos6", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:242.0309): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.core/exports/lib/rcc/platforms/xilinx13_3/README", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:242.0350): Searching directory /mnt/ocpi.assets/exports recursively, from OCPI_LIBRARY_PATH OCPI( 8:249.0207): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/pcie_4243_hip_s4gx_gen2_x4_128", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:249.0245): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/stratix4", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:249.0246): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/temac_v6", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:249.0248): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/lib/hdl/temac_v6_bb", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:249.0346): Path name found in OCPI_LIBRARY_PATH, "/mnt/ocpi.assets/exports/imports", is nonexistent, not a normal file, or a broken link. It will be ignored OCPI( 8:249.0346): Performing discovery for all container drivers OCPI( 8:249.0346): Searching for local Zynq/PL HDL device. OCPI( 8:249.0346): There is no bitstream loaded on this HDL device: PL:0 OCPI( 8:249.0348): Searching for local PCI-based HDL devices. OCPI( 8:249.0348): Searching for local HDL simulators. OCPI( 8:249.0354): No HDL platforms found (no lib/platforms/*) in path /mnt/net/cdk/../project-registry/ocpi.cdk:/mnt/net/cdk/../project-registry/ocpi.wifiproject:/mnt/net/cdk/../project-registry/ocpi.assets:/mnt/net/cdk/../project-registry/ocpi.core:/mnt/net/cdk OCPI( 8:249.0354): Searching for RCC containers, and implicitly finding one. OCPI( 8:249.0354): Transport ocpi-scif-dma not supported in this process. Not loaded/spec'd in system.xml? OCPI( 8:249.0354): Transport ocpi-socket-rdma not supported in this process. Not loaded/spec'd in system.xml? OCPI( 8:249.0355): Transport ocpi-udp-rdma not supported in this process. Not loaded/spec'd in system.xml? OCPI( 8:249.0356): Error Exception: No acceptable implementations found in any libraries for "ocpi.assets.devices.ad9361_spi". Use log level 8 for more detail. Exiting for exception: No acceptable implementations found in any libraries for "ocpi.assets.devices.ad9361_spi". Use log level 8 for more detail. Sincerely, Peter B. Miller Potomac: (301) 765-9668 --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.