anonymous254367,

Using v2.1.0, we were able to run the fsk_dig_radio_ctrlr application on the Zed with fmcomms2, which is a close representation of the e310. Below is an abbreviate set of steps for the zed/fmcomms2, that might help with reproducing success on the e310:
  1. Build bitstream: fsk_modem for zed
    1. This happens to be the same HDL assembly that is used for the FSK txrx
    2. Looks like you'll need to build the fsk_modem which is located in the e3xx project, not the one in the assets project
  2. HW Setup: fmcomms2 coax cable from TX1A to RX2A
    1. Yep it's 1->2, for the zed/fmcomms2. Probably just some diversity to spice things up.
  3. Setup zed for Network Mode (i.e. customize your mynetsetup.sh to nfs mount to your dev host cdk and the various projects containing necessary run-time artifacts)
    1. % cd /mnt/ocpi_assets/applications/fsk_dig_radio_ctrlr
    2. % export OCPI_LIBRARY_PATH=/mnt/ocpi_assets/hdl/assemblies/fsk_modem:/mnt/ocpi_core/artifacts:/mnt/ocpi_assets/artifacts
      1. At a minimum, you'll need to edit this so that it points to the e3xx/hdl/assemblies/fsk_modem/
        1. % export OCPI_LIBRARY_PATH=/mnt/ocpi_e3xx(?)/hdl/assemblies/fsk_modem:/mnt/ocpi_core/artifacts:/mnt/ocpi_assets/artifacts
    3. % ocpirun -v -d -x -t 15 fsk_modem_app.xml
      1. must be ran for enough time, -t, so that the entire data file (picture) can flow through the app
  4. On your develop host:
    1. cd assets/applications/fsk_dig_radio_ctrlr
    2. eog fsk_dig_radio_ctrlr_fmcomms_2_3_txrx.bin
Let me know if this helped,

Adam
From: discuss-request@lists.opencpi.org <discuss-request@lists.opencpi.org>
Sent: 13 April 2021 03:30
To: discuss@lists.opencpi.org <discuss@lists.opencpi.org>
Subject: discuss Digest, Vol 34, Issue 3
 
Send discuss mailing list submissions to
        discuss@lists.opencpi.org

To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
        discuss-request@lists.opencpi.org

You can reach the person managing the list at
        discuss-owner@lists.opencpi.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of discuss digest..."

Today's Topics:

   1. Re: SD Card OpenCPI environment for E310 (Aaron Olivarez)
   2. Re: SD Card OpenCPI environment for E310
      (anonymous254367@gmail.com)
   3. Re: SD Card OpenCPI environment for E310 (Aaron Olivarez)


----------------------------------------------------------------------

Message: 1
Date: Mon, 12 Apr 2021 09:01:14 -0500
From: Aaron Olivarez <aaron@olivarez.info>
Subject: [Discuss OpenCPI] Re: SD Card OpenCPI environment for E310
To: anonymous254367@gmail.com
Cc: discuss@lists.opencpi.org
Message-ID:
        <CAGsTUavSAWbG-OGS=uoPNAUX5TtEY-sNsd-Ptg8riHSE3BV7ZQ@mail.gmail.com>
Content-Type: multipart/alternative;
        boundary="0000000000000807d405bfc6f3be"

The FSK application directory has been replaced with
fsk_dig_radio_controller. We are in the processes of removing legacy
applications. To run the fsk_modem_app.xml the e31x and xilinx19_2_aarch32
platform depend on ocpi.core, ocpi.assets, ocpi.platform, and ocpi.osp.e31x
projects.




On Mon, Apr 12, 2021 at 1:48 AM <anonymous254367@gmail.com> wrote:

> Thanks for the comments so far, you have been a huge help.
>
> Copied the updated line from the branch over to the respective file then
> did another install of OpenCPI and the m_port_size() error has disappeared.
>
> *ocpirun -v -t 1 -d -m bias=hdl bias.xml* is now working as intended.
>
> The next step is teh test application which doesn’t appear to be working.
>
>
> Running the following two commands appears to fail:
>
> ./target-xilinx19_2_aarch32/FSK rx
>
> Application properties are found in XML file: app_fsk_rx_e31x.xml
>
> ERROR: No acceptable implementations found in any libraries for
> "ocpi.assets.devices.ad9361_spi". Use log level 8 for more detail.
>
>
> % ./target-xilinx19_2_aarch32/FSK filerw
>
> Application properties are found in XML file: app_fsk_filerw.xml
>
> ERROR: No acceptable implementations found in any libraries for
> "ocpi.assets.comms_comps.mfsk_mapper". Use log level 8 for more detail.
>
>
> My understanding is that xilinx19_2_aarch32 and e31x don’t use ocpi.assets
> as a dependency, only ocpi.core.
> _______________________________________________
> discuss mailing list -- discuss@lists.opencpi.org
> To unsubscribe send an email to discuss-leave@lists.opencpi.org
>
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 2136 bytes
Desc: not available

------------------------------

Message: 2
Date: Tue, 13 Apr 2021 02:57:07 +0000
From: anonymous254367@gmail.com
Subject: [Discuss OpenCPI] Re: SD Card OpenCPI environment for E310
To: discuss@lists.opencpi.org
Message-ID:
        <S40aVdh8MXzmujP4VBmv32kPkfUyndh3fXL96eirIu0@lists.opencpi.org>
Content-Type: multipart/alternative;
        boundary="b1_S40aVdh8MXzmujP4VBmv32kPkfUyndh3fXL96eirIu0"

The dependencies are used during the *ocpidev build* commands, correct?

There is the FSK_App_Getting_Started_Guide and the FSK_App_Getting_Started_Guide_E31x.

I followed the later guide to build the FSK application.

The build commands also appear to be slightly different between the two guides. I have noticed that the former guide mentions *fsk_modem* in section *5 Build the assets project*, which is the application you mention is required for the e31x.

Assuming that ocpi.core, ocpi.assets, ocpi.platform, and ocpi.osp.e31x projects have already been created:

If I use the commands in the FSK_App_Getting_Started_Guide while in the correct directories but replace *xilinx13_3* and *matchstiq_z1* with *xilinx19_2_aarch32* and *e31x* respectively then  the *fsm_modem* application will be built? Will this solve the “ERROR: No acceptable implementations” error?
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 975 bytes
Desc: not available

------------------------------

Message: 3
Date: Mon, 12 Apr 2021 22:48:45 -0500
From: Aaron Olivarez <aaron@olivarez.info>
Subject: [Discuss OpenCPI] Re: SD Card OpenCPI environment for E310
To: anonymous254367@gmail.com
Cc: discuss@lists.opencpi.org
Message-ID:
        <CAGsTUavRoa7ui+9Dit-wr4h9SzWFTsJsvm9Zo4XiYy5ZC3BVfQ@mail.gmail.com>
Content-Type: multipart/alternative;
        boundary="0000000000007b7aed05bfd28249"

Those documents are in need of a refresh.

A  new utility has been created called *ocpiadmin* which facilitates
platform builds. Before invoking it
is assumed you have followed the OpenCPI Installation Guide
<https://opencpi.gitlab.io/releases/latest/docs/OpenCPI_Installation_Guide.pdf>
.
Specifically installing vendor tools, cloning the project, running
install-opencpi.sh, sourcing environment variables. The following command
is also referenced several times in the install guide and these are the
ones you would use for xilinx19_2_aarch32:e31x platform combination:

ocpiadmin install platform xilinx19_2_aarch32

The 'ocpiadmin install platform' command will build the framework and
workers for the given platform in projects
core,platform,assets,assets_ts,tutorial, and if the platform is located in
an OSP project outside the main OpenCPI project will be against that
project as well. After building the RCC platform the next step would be to
build the HDL platform. In your case for the E310 it would be:

ocpiadmin install platform e31x -p ocpi.osp.e3xx

That command will build all the HDL workers in the same set of projects as
before. This will also pull the OSP from gitlab since it's not in the main
OpenCPI project and place it in projects/osps directory. Additionally for
HDL platforms it will build only one HDL assembly by default, the
testbias assembly.

To run the fsk_modem_app.xml you need to build
ocpi.osp.e3xx/hdl/assemblies/fsk_modem hdl assembly. To do so do the
following:

cd projects/osps/ocpi.osp.e3xx/hdl/assemblies/fsk_modem
ocpidev build --hdl-platform e31x

Once the assembly and all workers have been built there are three modes of
running an OpenCPI application:
  1. standalone mode
         All artifacts required for the application are on the E310.
  2. network mode
         E310 connected to NFS server hosted on the development host.
  3. server mode
         ocpiremote utility to load OpenCPI sandbox via SSH. Application
executes from the development host.

Which mode are you planning to use?

Typically you will get the 'No acceptable implementations ' error if
OCPI_LIBRARY_PATH environment variable has not been set correctly.


On Mon, Apr 12, 2021 at 9:57 PM <anonymous254367@gmail.com> wrote:

> The dependencies are used during the *ocpidev build* commands, correct?
>
> There is the FSK_App_Getting_Started_Guide and the
> FSK_App_Getting_Started_Guide_E31x.
>
> I followed the later guide to build the FSK application.
>
> The build commands also appear to be slightly different between the two
> guides. I have noticed that the former guide mentions *fsk_modem* in
> section *5 Build the assets project*, which is the application you
> mention is required for the e31x.
>
> Assuming that ocpi.core, ocpi.assets, ocpi.platform, and ocpi.osp.e31x
> projects have already been created:
>
> If I use the commands in the FSK_App_Getting_Started_Guide while in the
> correct directories but replace *xilinx13_3* and *matchstiq_z1* with
> *xilinx19_2_aarch32* and *e31x* respectively then the *fsm_modem*
> application will be built? Will this solve the “ERROR: No acceptable
> implementations” error?
> _______________________________________________
> discuss mailing list -- discuss@lists.opencpi.org
> To unsubscribe send an email to discuss-leave@lists.opencpi.org
>
-------------- next part --------------
A message part incompatible with plain text digests has been removed ...
Name: not available
Type: text/html
Size: 4301 bytes
Desc: not available

------------------------------

Subject: Digest Footer

_______________________________________________
discuss mailing list -- discuss@lists.opencpi.org
To unsubscribe send an email to discuss-leave@lists.opencpi.org


------------------------------

End of discuss Digest, Vol 34, Issue 3
**************************************