Hello,
I have been attempting to work through the instructions to create the FSK application for the Ettus E310, as provided in the document: OpenCPI FSK App Getting Started Guide (E31x Supplement) OpenCPI Release: v2.4.0.

Every step seems to go correctly until the final building step where the actual executable is meant to be created, ie:
ocpidev build -d <e3xx-project-dir/applications/FSK> --rcc-platform xilinx19_2_aarch32

This command does appear to complete successfully, and creates the necessary filter coefficients, however it does not appear to attempt to generate an executable from the *.cxx files, and no output directory (target-xilinx-19_2) is created.

Output from the compilation command is provided below:

ocpidev build -d /home/opencpi/opencpi-v2.4.0/projects/osps/ocpi.osp.e3xx/applications/FSK --rcc-platform xilinx19_2_aarch32

# Remove old test data files
rm -rf idata/*.dat idata/*.bin odata/*
# Create test input data
python scripts/gen_rrcos_taps.py 128 0.95 `echo "1/64000" | bc -l` `echo "64000*39" | bc -l` 4096 idata/tx_rrcos_taps.dat
********************************************************************************
*** Python: Generate Root-Raised Cosine taps ***
1.2588365809784572
[ 85 96 105 111 115 116 114 109 100 88 72 53 31 6
-21 -50 -81 -113 -145 -177 -207 -235 -259 -280 -295 -305 -307 -302
-287 -263 -229 -184 -128 -60 20 112 217 334 462 602 752 912
1081 1257 1441 1629 1821 2015 2209 2402 2593 2779 2958 3130 3292 3443
3581 3705 3814 3906 3981 4038 4076 4096 4096 4076 4038 3981 3906 3814
3705 3581 3443 3292 3130 2958 2779 2593 2402 2209 2015 1821 1629 1441
1257 1081 912 752 602 462 334 217 112 20 -60 -128 -184 -229
-263 -287 -302 -307 -305 -295 -280 -259 -235 -207 -177 -145 -113 -81
-50 -21 6 31 53 72 88 100 109 114 116 115 111 105
96 85]
127862
31.2163085938
python scripts/gen_rrcos_taps.py 128 0.95 `echo "1/64000" | bc -l` `echo "64000*39" | bc -l` 4096 idata/rx_rrcos_taps.dat
********************************************************************************
*** Python: Generate Root-Raised Cosine taps ***
1.2588365809784572
[ 85 96 105 111 115 116 114 109 100 88 72 53 31 6
-21 -50 -81 -113 -145 -177 -207 -235 -259 -280 -295 -305 -307 -302
-287 -263 -229 -184 -128 -60 20 112 217 334 462 602 752 912
1081 1257 1441 1629 1821 2015 2209 2402 2593 2779 2958 3130 3292 3443
3581 3705 3814 3906 3981 4038 4076 4096 4096 4076 4038 3981 3906 3814
3705 3581 3443 3292 3130 2958 2779 2593 2402 2209 2015 1821 1629 1441
1257 1081 912 752 602 462 334 217 112 20 -60 -128 -184 -229
-263 -287 -302 -307 -305 -295 -280 -259 -235 -207 -177 -145 -113 -81
-50 -21 6 31 53 72 88 100 109 114 116 115 111 105
96 85]
127862
31.2163085938

I have also attempted to build the “ad9361_adc_test” application, and this does compile the *.cxx files and generate an output directory containing executables as expected.

Please could anyone provide guidance as to why the FSK.cxx file is not compiled into an executable?

Thanks in advance,
Chris Cotton

A few quick things. Presumably you did:

ocpiadmin install platform xilinx19_2_aarch32

ocpiadmin install platform -p ocpi.osp.e3xx e31x

And in that app build directory what is actually there (ls -R)?

On 3/2/22 7:14 AM, chris@qelectronics.co.uk wrote:

Hello,
I have been attempting to work through the instructions to create the FSK application for the Ettus E310, as provided in the document: OpenCPI FSK App Getting Started Guide (E31x Supplement) OpenCPI Release: v2.4.0.

Every step seems to go correctly until the final building step where the actual executable is meant to be created, ie:
ocpidev build -d <e3xx-project-dir/applications/FSK> --rcc-platform xilinx19_2_aarch32

This command does appear to complete successfully, and creates the necessary filter coefficients, however it does not appear to attempt to generate an executable from the *.cxx files, and no output directory (target-xilinx-19_2) is created.

Output from the compilation command is provided below:

ocpidev build -d/home/opencpi/opencpi-v2.4.0/projects/osps/ocpi.osp.e3xx/applications/FSK --rcc-platform xilinx19_2_aarch32

# Remove old test data files<br></br>
          rm -rf idata/*.dat idata/*.bin odata/*<br></br>
          # Create test input data<br></br>
          python scripts/gen_rrcos_taps.py 128 0.95 `echo "1/64000" | bc
          -l` `echo "64000*39" | bc -l` 4096 idata/tx_rrcos_taps.dat<br></br>
********************************************************************************<br></br>
          *** Python: Generate Root-Raised Cosine taps ***<br></br>
          1.2588365809784572<br></br>
          [ 85 96 105 111 115 116 114 109 100 88 72 53 31 6<br></br>
          -21 -50 -81 -113 -145 -177 -207 -235 -259 -280 -295 -305 -307
          -302<br></br>
          -287 -263 -229 -184 -128 -60 20 112 217 334 462 602 752 912<br></br>
          1081 1257 1441 1629 1821 2015 2209 2402 2593 2779 2958 3130
          3292 3443<br></br>
          3581 3705 3814 3906 3981 4038 4076 4096 4096 4076 4038 3981
          3906 3814<br></br>
          3705 3581 3443 3292 3130 2958 2779 2593 2402 2209 2015 1821
          1629 1441<br></br>
          1257 1081 912 752 602 462 334 217 112 20 -60 -128 -184 -229<br></br>
          -263 -287 -302 -307 -305 -295 -280 -259 -235 -207 -177 -145
          -113 -81<br></br>
          -50 -21 6 31 53 72 88 100 109 114 116 115 111 105<br></br>
          96 85]<br></br>
          127862<br></br>
          31.2163085938<br></br>
          python scripts/gen_rrcos_taps.py 128 0.95 `echo "1/64000" | bc
          -l` `echo "64000*39" | bc -l` 4096 idata/rx_rrcos_taps.dat<br></br>
********************************************************************************<br></br>
          *** Python: Generate Root-Raised Cosine taps ***<br></br>
          1.2588365809784572<br></br>
          [ 85 96 105 111 115 116 114 109 100 88 72 53 31 6<br></br>
          -21 -50 -81 -113 -145 -177 -207 -235 -259 -280 -295 -305 -307
          -302<br></br>
          -287 -263 -229 -184 -128 -60 20 112 217 334 462 602 752 912<br></br>
          1081 1257 1441 1629 1821 2015 2209 2402 2593 2779 2958 3130
          3292 3443<br></br>
          3581 3705 3814 3906 3981 4038 4076 4096 4096 4076 4038 3981
          3906 3814<br></br>
          3705 3581 3443 3292 3130 2958 2779 2593 2402 2209 2015 1821
          1629 1441<br></br>
          1257 1081 912 752 602 462 334 217 112 20 -60 -128 -184 -229<br></br>
          -263 -287 -302 -307 -305 -295 -280 -259 -235 -207 -177 -145
          -113 -81<br></br>
          -50 -21 6 31 53 72 88 100 109 114 116 115 111 105<br></br>
          96 85]<br></br>
          127862<br></br>
          31.2163085938

I have also attempted to build the “ad9361_adc_test” application, and this does compile the *.cxx files and generate an output directory containing executables as expected.

Please could anyone provide guidance as to why the FSK.cxx file is not compiled into an executable?

Thanks in advance,
Chris Cotton

<pre class="moz-quote-pre" wrap="">_______________________________________________
discuss mailing list -- <a class="moz-txt-link-abbreviated" href="mailto:discuss@lists.opencpi.org">discuss@lists.opencpi.org</a>
To unsubscribe send an email to <a class="moz-txt-link-abbreviated" href="mailto:discuss-leave@lists.opencpi.org">discuss-leave@lists.opencpi.org</a>

Hello Aaron,

Thanks for explaining the reason why the FSK binary wasn’t being built.  Sure enough, adjusting the Makefile as suggested allowed the FSK executable binary to be built, and as a quick check the command ./FSK filerw ran successfully.  The other modes of operation, which use the RF hardware in the Ettus E310, did not run as successfully; for example, a quick attempt to run ./FSK rx resulted in the error: No acceptable implementations found in any libraries for "ocpi.assets.devices.ad9361_adc_sub".  I’m guessing this may be due to compatibility issues between the FSK application and openCPI 2.4.0, a component that I haven’t built correctly, or a mistake in my OCPI_LIBRARY_PATH?

I’m already aware that the fsk_modem_app.xml is the preferred (actively supported?) example program, and have already run that successfully.  I was investigating the FSK application out of curiosity, given that it’s user guides are included in the release documentation for OpenCPI 2.4.0.

On a related not, when creating a new OpenCPI application, is an *.xml file that is invoked using ‘ocpirun’ the preferred approach, or are C-based executables equally acceptable / recommended?

Thanks,

Chris Cotton

Thanks for the information, it has clarified things significantly.

We will continue our development work using the fsk_modem_app as you recommend.

Cheers,

Chris Cotton