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 * This happens to be the same HDL assembly that is used for the FSK txrx * 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 * 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) * % cd /mnt/ocpi_assets/applications/fsk_dig_radio_ctrlr * % export OCPI_LIBRARY_PATH=/mnt/ocpi_assets/hdl/assemblies/fsk_modem:/mnt/ocpi_core/artifacts:/mnt/ocpi_assets/artifacts * At a minimum, you'll need to edit this so that it points to the e3xx/hdl/assemblies/fsk_modem/ * % export OCPI_LIBRARY_PATH=/mnt/ocpi_e3xx(?)/hdl/assemblies/fsk_modem:/mnt/ocpi_core/artifacts:/mnt/ocpi_assets/artifacts * % ocpirun -v -d -x -t 15 fsk_modem_app.xml * must be ran for enough time, -t, so that the entire data file (picture) can flow through the app 4. On your develop host: * cd assets/applications/fsk_dig_radio_ctrlr * 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 >

Hi Adam, This post has been useful. My assumption was the standalone mode would be easiest, at least getting a test application to work. I have instead changed to Network mode. There was a problem with changing the mynetstup.sh but afterwards the sourcing created the mnt directories and were linked to the correct folders. I had to add the ospi_e31x directory as well as the ocpi_core and ocpi_asset (as per standard instructions). There are high hopes as I am getting data in fsk_dig_radio_ctrlr_fmcomms_2_3_txrx.bin with the o*cpirun -v -d -x -t 15 fsk_modem_app.xml* command. However, the *eog fsk_dig_radio_ctrlr_fmcomms_2_3_txrx.bin* command produces an error that the file isn’t recognized as an image. I have tried different times for -t with the file size increasing with more time. The file seems to be a different size everytime I run the ocpirun command with the same -t value. Using a spectrum analyzer I am getting a signal at 2.45GHz so I assume it is transmitting. Any thoughts why the .bin file isn’t reading correctly? Is the demodulation not working as intended?