I have done both the ocpiadmin install for both platforms and they both appear to work.
I will give the ocpidev for fsk_modem a go when I get the chance.
Currently I am trying to get standalone mode working as that appears simpler than the other options.
I did an export of the OCPI_LIBRARY_PATH and did an echo to check and it appears to be in the correct location.
Aaron Olivarez wrote:
> 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_at_gmail.com](mailto:anonymous254367_at_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_at_lists.opencpi.org
> > To unsubscribe send an email to discuss-leave_at_lists.opencpi.org
Received on Tue Apr 13 2021 - 07:52:07 CDT