Empathy List Archives

discuss@lists.opencpi.org

OpenCPI Discussion

View all threads

Re: [Discuss OpenCPI] ocpirun response

Miller, Peter

Thu, Jun 14, 2018 1:04 PM

Looks like 1.3.

$ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so

<artifact uuid="ad272dd8-6f53-11e8-9259-5b7323f829f5" ocpi_version="1.3" os="linux" osVersion="x13_3" platform="xilinx13_3" arch="arm" dynamic='0'> <worker name="file_read" model="rcc" package="ocpi.core" specname="ocpi.core.file_read" sizeOfConfigSpace="1066" controlOperations="start,release"> <property name="fileName" type="String" stringLength="1024" readable='1' initial='1'/> <property name="messagesInFile" type="Bool" default='false' readable='1' initial='1'/> <property name="opcode" type="UChar" default='0' readable='1' initial='1'/> <property name="messageSize" default='4096' volatile='1' initial='1'/> <property name="granularity" default='1' readable='1' initial='1'/> <property name="repeat" type="Bool" writable='1'/> <property name="bytesRead" type="ULongLong" volatile='1'/> <property name="messagesWritten" type="ULongLong" volatile='1'/> <property name="suppressEOF" type="Bool" readable='1' initial='1'/> <property name="badMessage" type="Bool" volatile='1'/> <property name="ocpi_debug" type="Bool" isImpl='1' parameter='1' default='false'/> <property name="ocpi_endian" type="Enum" enums="little,big,dynamic" isImpl='1' parameter='1' default='little'/> <port name="out" producer='1' numberOfOpcodes="256" bufferSize='8192'> <protocol dataValueWidth="8" dataValueGranularity="1" diverseDataSizes="0" minMessageValues="0"/> </port> </worker> </artifact>

From: chinkey chinkey@office.geontech.com
Sent: Thursday, June 14, 2018 9:02 AM
To: Miller, Peter PeterM@signalscape.com
Cc: James Kulp jek@parera.com; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] ocpirun response

what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so "

On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com mailto:PeterM@signalscape.com> wrote:

I installed the AV1.3.1 projects using the procedure below, rebuilt everything in core and assets, but get the same failure. I set AV_ALLOW_VERSION_MISMATCH=1 and the Application will run on the zed board using ocpirun, though not successfully. This application will run in CentOS/xsim.

Is the procedure below wrong or incomplete?

cd /opt/opencpi/projects

./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core

cd ~/SS_SDR/Frameworks

mkdir ocpi.assets

cd ocpi.assets

tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz .

If previously registered product exists:

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core

Build

cd ~/SS_SDR/Frameworks/ocpi.core/

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

cd ~/SS_SDR/Frameworks/ocpi.assets

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

-----Original Message-----

From: Miller, Peter

Sent: Wednesday, June 13, 2018 5:52 PM

To: James Kulp <jek@parera.com mailto:jek@parera.com>; discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

Subject: RE: [Discuss OpenCPI] ocpirun response

I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now.

-----Original Message-----

From: discuss <discuss-bounces@lists.opencpi.org mailto:discuss-bounces@lists.opencpi.org> On Behalf Of James Kulp

Sent: Wednesday, June 13, 2018 5:06 PM

To: discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

Subject: Re: [Discuss OpenCPI] ocpirun response

I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed.

On 6/13/18 4:38 PM, Miller, Peter wrote:

Support,

I am running AV1.3.1. Running the following on a ZED board:

ocpirun -t180 -mmac_low_802dot11=hdl

--library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o

cpi.wifiproject/exports"

icmp_demo_file_mac_highlow_phy_txrx_loopback.xml

OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version

mismatch ('' vs. expected '1.3') (try increasing log level) Exiting for exception: For instance "file_read_mac_mpdu" for spec "ocpi.core.file_read": no feasible containers found for any of the 4 implementations found.

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.

-------------- next part -------------- An HTML attachment was

scrubbed...

URL:

<http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme

nts/20180613/adb3d943/attachment.html>

discuss mailing list

discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

Looks like 1.3. $ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so  <artifact uuid="ad272dd8-6f53-11e8-9259-5b7323f829f5" ocpi_version="1.3" os="linux" osVersion="x13_3" platform="xilinx13_3" arch="arm" dynamic='0'> <worker name="file_read" model="rcc" package="ocpi.core" specname="ocpi.core.file_read" sizeOfConfigSpace="1066" controlOperations="start,release"> <property name="fileName" type="String" stringLength="1024" readable='1' initial='1'/> <property name="messagesInFile" type="Bool" default='false' readable='1' initial='1'/> <property name="opcode" type="UChar" default='0' readable='1' initial='1'/> <property name="messageSize" default='4096' volatile='1' initial='1'/> <property name="granularity" default='1' readable='1' initial='1'/> <property name="repeat" type="Bool" writable='1'/> <property name="bytesRead" type="ULongLong" volatile='1'/> <property name="messagesWritten" type="ULongLong" volatile='1'/> <property name="suppressEOF" type="Bool" readable='1' initial='1'/> <property name="badMessage" type="Bool" volatile='1'/> <property name="ocpi_debug" type="Bool" isImpl='1' parameter='1' default='false'/> <property name="ocpi_endian" type="Enum" enums="little,big,dynamic" isImpl='1' parameter='1' default='little'/> <port name="out" producer='1' numberOfOpcodes="256" bufferSize='8192'> <protocol dataValueWidth="8" dataValueGranularity="1" diverseDataSizes="0" minMessageValues="0"/> </port> </worker> </artifact> From: chinkey <chinkey@office.geontech.com> Sent: Thursday, June 14, 2018 9:02 AM To: Miller, Peter <PeterM@signalscape.com> Cc: James Kulp <jek@parera.com>; discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] ocpirun response what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so " On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> wrote: I installed the AV1.3.1 projects using the procedure below, rebuilt everything in core and assets, but get the same failure. I set AV_ALLOW_VERSION_MISMATCH=1 and the Application will run on the zed board using ocpirun, though not successfully. This application will run in CentOS/xsim. Is the procedure below wrong or incomplete? cd /opt/opencpi/projects ./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core cd ~/SS_SDR/Frameworks mkdir ocpi.assets cd ocpi.assets tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz . If previously registered product exists: ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core Register Projects ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core Build cd ~/SS_SDR/Frameworks/ocpi.core/ ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies cd ~/SS_SDR/Frameworks/ocpi.assets ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies -----Original Message----- From: Miller, Peter Sent: Wednesday, June 13, 2018 5:52 PM To: James Kulp <jek@parera.com<mailto:jek@parera.com>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: RE: [Discuss OpenCPI] ocpirun response I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now. -----Original Message----- From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org>> On Behalf Of James Kulp Sent: Wednesday, June 13, 2018 5:06 PM To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed. On 6/13/18 4:38 PM, Miller, Peter wrote: > Support, > I am running AV1.3.1. Running the following on a ZED board: > > > ocpirun -t180 -mmac_low_802dot11=hdl > --library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o > cpi.wifiproject/exports" > icmp_demo_file_mac_highlow_phy_txrx_loopback.xml > > OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version > mismatch ('' vs. expected '1.3') (try increasing log level) Exiting for exception: For instance "file_read_mac_mpdu" for spec "ocpi.core.file_read": no feasible containers found for any of the 4 implementations found. > > 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. > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme > nts/20180613/adb3d943/attachment.html> > _______________________________________________ > discuss mailing list > discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> > http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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. _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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.

Marasco, Aaron

Thu, Jun 14, 2018 1:25 PM

Hi Peter,

This is definitely a strange situation. The fact that your debug listing says "av" and recommends "AV_ALLOW_VERSION_MISMATCH" versus "OCPI_ALLOW_VERSION_MISMATCH" implies that you have a 1.2 or previous "ocpirun" executable somewhere that is being run. When we went OSS, we removed the "AV" prefix and made it "OCPI" as well as changing the internal XML attribute name. Please check "which ocpirun" or if you are using an ACI application, be sure that has been totally rebuilt under 1.3.

As an FYI, you shouldn't need to untar the assets source directly. You can run /opt/opencpi/projects/new_project_source and tell it "assets" as the source. I'm pretty sure it handles all the project registration for you automatically as well (does today, I think it did in 1.3).

Let me know how this works for you,

Aaron

From: discuss discuss-bounces@lists.opencpi.org on behalf of Miller, Peter PeterM@signalscape.com
Sent: Thursday, June 14, 2018 9:04:26 AM
To: EXT-Hinkey, Chris (Geon Technologies)
Cc: discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] ocpirun response

Looks like 1.3.

$ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so

what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so "

On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com mailto:PeterM@signalscape.com> wrote:

Is the procedure below wrong or incomplete?

cd /opt/opencpi/projects

./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core

cd ~/SS_SDR/Frameworks

mkdir ocpi.assets

cd ocpi.assets

tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz .

If previously registered product exists:

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core

Build

cd ~/SS_SDR/Frameworks/ocpi.core/

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

cd ~/SS_SDR/Frameworks/ocpi.assets

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

-----Original Message-----

From: Miller, Peter

Sent: Wednesday, June 13, 2018 5:52 PM

To: James Kulp <jek@parera.com mailto:jek@parera.com>; discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

Subject: RE: [Discuss OpenCPI] ocpirun response

I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now.

-----Original Message-----

From: discuss <discuss-bounces@lists.opencpi.org mailto:discuss-bounces@lists.opencpi.org> On Behalf Of James Kulp

Sent: Wednesday, June 13, 2018 5:06 PM

To: discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

Subject: Re: [Discuss OpenCPI] ocpirun response

I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed.

On 6/13/18 4:38 PM, Miller, Peter wrote:

Support,

I am running AV1.3.1. Running the following on a ZED board:

ocpirun -t180 -mmac_low_802dot11=hdl

--library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o

cpi.wifiproject/exports"

icmp_demo_file_mac_highlow_phy_txrx_loopback.xml

OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version

Sincerely,

Peter B. Miller

Potomac: (301) 765-9668

-------------- next part -------------- An HTML attachment was

scrubbed...

URL:

<http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme

nts/20180613/adb3d943/attachment.html>

discuss mailing list

discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

Hi Peter, This is definitely a strange situation. The fact that your debug listing says "av" and recommends "AV_ALLOW_VERSION_MISMATCH" versus "OCPI_ALLOW_VERSION_MISMATCH" implies that you have a 1.2 or previous "ocpirun" executable somewhere that is being run. When we went OSS, we removed the "AV" prefix and made it "OCPI" as well as changing the internal XML attribute name. Please check "which ocpirun" or if you are using an ACI application, be sure that has been totally rebuilt under 1.3. As an FYI, you shouldn't need to untar the assets source directly. You can run /opt/opencpi/projects/new_project_source and tell it "assets" as the source. I'm pretty sure it handles all the project registration for you automatically as well (does today, I think it did in 1.3). Let me know how this works for you, Aaron ________________________________ From: discuss <discuss-bounces@lists.opencpi.org> on behalf of Miller, Peter <PeterM@signalscape.com> Sent: Thursday, June 14, 2018 9:04:26 AM To: EXT-Hinkey, Chris (Geon Technologies) Cc: discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] ocpirun response Looks like 1.3. $ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so  <artifact uuid="ad272dd8-6f53-11e8-9259-5b7323f829f5" ocpi_version="1.3" os="linux" osVersion="x13_3" platform="xilinx13_3" arch="arm" dynamic='0'> <worker name="file_read" model="rcc" package="ocpi.core" specname="ocpi.core.file_read" sizeOfConfigSpace="1066" controlOperations="start,release"> <property name="fileName" type="String" stringLength="1024" readable='1' initial='1'/> <property name="messagesInFile" type="Bool" default='false' readable='1' initial='1'/> <property name="opcode" type="UChar" default='0' readable='1' initial='1'/> <property name="messageSize" default='4096' volatile='1' initial='1'/> <property name="granularity" default='1' readable='1' initial='1'/> <property name="repeat" type="Bool" writable='1'/> <property name="bytesRead" type="ULongLong" volatile='1'/> <property name="messagesWritten" type="ULongLong" volatile='1'/> <property name="suppressEOF" type="Bool" readable='1' initial='1'/> <property name="badMessage" type="Bool" volatile='1'/> <property name="ocpi_debug" type="Bool" isImpl='1' parameter='1' default='false'/> <property name="ocpi_endian" type="Enum" enums="little,big,dynamic" isImpl='1' parameter='1' default='little'/> <port name="out" producer='1' numberOfOpcodes="256" bufferSize='8192'> <protocol dataValueWidth="8" dataValueGranularity="1" diverseDataSizes="0" minMessageValues="0"/> </port> </worker> </artifact> From: chinkey <chinkey@office.geontech.com> Sent: Thursday, June 14, 2018 9:02 AM To: Miller, Peter <PeterM@signalscape.com> Cc: James Kulp <jek@parera.com>; discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] ocpirun response what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so " On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> wrote: I installed the AV1.3.1 projects using the procedure below, rebuilt everything in core and assets, but get the same failure. I set AV_ALLOW_VERSION_MISMATCH=1 and the Application will run on the zed board using ocpirun, though not successfully. This application will run in CentOS/xsim. Is the procedure below wrong or incomplete? cd /opt/opencpi/projects ./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core cd ~/SS_SDR/Frameworks mkdir ocpi.assets cd ocpi.assets tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz . If previously registered product exists: ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core Register Projects ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core Build cd ~/SS_SDR/Frameworks/ocpi.core/ ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies cd ~/SS_SDR/Frameworks/ocpi.assets ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies -----Original Message----- From: Miller, Peter Sent: Wednesday, June 13, 2018 5:52 PM To: James Kulp <jek@parera.com<mailto:jek@parera.com>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: RE: [Discuss OpenCPI] ocpirun response I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now. -----Original Message----- From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org>> On Behalf Of James Kulp Sent: Wednesday, June 13, 2018 5:06 PM To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed. On 6/13/18 4:38 PM, Miller, Peter wrote: > Support, > I am running AV1.3.1. Running the following on a ZED board: > > > ocpirun -t180 -mmac_low_802dot11=hdl > --library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o > cpi.wifiproject/exports" > icmp_demo_file_mac_highlow_phy_txrx_loopback.xml > > OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version > mismatch ('' vs. expected '1.3') (try increasing log level) Exiting for exception: For instance "file_read_mac_mpdu" for spec "ocpi.core.file_read": no feasible containers found for any of the 4 implementations found. > > 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. > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme > nts/20180613/adb3d943/attachment.html> > _______________________________________________ > discuss mailing list > discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> > http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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. _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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.

Miller, Peter

Thu, Jun 14, 2018 1:34 PM

% which ocpirun
/mnt/net/cdk/bin/linux-x13_3-arm/ocpirun

This is happening on the zedboard where I am using /mnt/card/opencpi/mynetsetup.sh, etc that was originally created under AV1.2 and modified with my mounts. Is the fix to:

go to AV1.3.1 /opt/opencpi/boot_support/zed/OpenCPI-SD-zed/opencpi
copy to SD card
edit to suit (as before for AV1.2)

From: Marasco, Aaron aaron.marasco@bia-boeing.com
Sent: Thursday, June 14, 2018 9:26 AM
To: Miller, Peter PeterM@signalscape.com
Cc: discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] ocpirun response

Hi Peter,

Let me know how this works for you,

Aaron

From: discuss <discuss-bounces@lists.opencpi.org mailto:discuss-bounces@lists.opencpi.org> on behalf of Miller, Peter <PeterM@signalscape.com mailto:PeterM@signalscape.com>
Sent: Thursday, June 14, 2018 9:04:26 AM
To: EXT-Hinkey, Chris (Geon Technologies)
Cc: discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] ocpirun response

Looks like 1.3.

$ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so

From: chinkey <chinkey@office.geontech.com mailto:chinkey@office.geontech.com>
Sent: Thursday, June 14, 2018 9:02 AM
To: Miller, Peter <PeterM@signalscape.com mailto:PeterM@signalscape.com>
Cc: James Kulp <jek@parera.com mailto:jek@parera.com>; discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] ocpirun response

what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so "

On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com mailto:PeterM@signalscape.com%3cmailto:PeterM@signalscape.com>> wrote:

Is the procedure below wrong or incomplete?

cd /opt/opencpi/projects

./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core

cd ~/SS_SDR/Frameworks

mkdir ocpi.assets

cd ocpi.assets

tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz .

If previously registered product exists:

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core

Build

cd ~/SS_SDR/Frameworks/ocpi.core/

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

cd ~/SS_SDR/Frameworks/ocpi.assets

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

-----Original Message-----

From: Miller, Peter

Sent: Wednesday, June 13, 2018 5:52 PM

To: James Kulp <jek@parera.com<mailto:jek@parera.com mailto:jek@parera.com%3cmailto:jek@parera.com>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

Subject: RE: [Discuss OpenCPI] ocpirun response

I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now.

-----Original Message-----

From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org mailto:discuss-bounces@lists.opencpi.org%3cmailto:discuss-bounces@lists.opencpi.org>> On Behalf Of James Kulp

Sent: Wednesday, June 13, 2018 5:06 PM

To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

Subject: Re: [Discuss OpenCPI] ocpirun response

I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed.

On 6/13/18 4:38 PM, Miller, Peter wrote:

Support,

I am running AV1.3.1. Running the following on a ZED board:

ocpirun -t180 -mmac_low_802dot11=hdl

--library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o

cpi.wifiproject/exports"

icmp_demo_file_mac_highlow_phy_txrx_loopback.xml

OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version

Sincerely,

Peter B. Miller

Potomac: (301) 765-9668

-------------- next part -------------- An HTML attachment was

scrubbed...

URL:

<http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme

http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme%0b%0b> nts/20180613/adb3d943/attachment.html>

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

% which ocpirun /mnt/net/cdk/bin/linux-x13_3-arm/ocpirun This is happening on the zedboard where I am using /mnt/card/opencpi/mynetsetup.sh, etc that was originally created under AV1.2 and modified with my mounts. Is the fix to: 1. go to AV1.3.1 /opt/opencpi/boot_support/zed/OpenCPI-SD-zed/opencpi 2. copy to SD card 3. edit to suit (as before for AV1.2) From: Marasco, Aaron <aaron.marasco@bia-boeing.com> Sent: Thursday, June 14, 2018 9:26 AM To: Miller, Peter <PeterM@signalscape.com> Cc: discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] ocpirun response Hi Peter, This is definitely a strange situation. The fact that your debug listing says "av" and recommends "AV_ALLOW_VERSION_MISMATCH" versus "OCPI_ALLOW_VERSION_MISMATCH" implies that you have a 1.2 or previous "ocpirun" executable somewhere that is being run. When we went OSS, we removed the "AV" prefix and made it "OCPI" as well as changing the internal XML attribute name. Please check "which ocpirun" or if you are using an ACI application, be sure that has been totally rebuilt under 1.3. As an FYI, you shouldn't need to untar the assets source directly. You can run /opt/opencpi/projects/new_project_source and tell it "assets" as the source. I'm pretty sure it handles all the project registration for you automatically as well (does today, I think it did in 1.3). Let me know how this works for you, Aaron ________________________________ From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org>> on behalf of Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Sent: Thursday, June 14, 2018 9:04:26 AM To: EXT-Hinkey, Chris (Geon Technologies) Cc: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response Looks like 1.3. $ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so  <artifact uuid="ad272dd8-6f53-11e8-9259-5b7323f829f5" ocpi_version="1.3" os="linux" osVersion="x13_3" platform="xilinx13_3" arch="arm" dynamic='0'> <worker name="file_read" model="rcc" package="ocpi.core" specname="ocpi.core.file_read" sizeOfConfigSpace="1066" controlOperations="start,release"> <property name="fileName" type="String" stringLength="1024" readable='1' initial='1'/> <property name="messagesInFile" type="Bool" default='false' readable='1' initial='1'/> <property name="opcode" type="UChar" default='0' readable='1' initial='1'/> <property name="messageSize" default='4096' volatile='1' initial='1'/> <property name="granularity" default='1' readable='1' initial='1'/> <property name="repeat" type="Bool" writable='1'/> <property name="bytesRead" type="ULongLong" volatile='1'/> <property name="messagesWritten" type="ULongLong" volatile='1'/> <property name="suppressEOF" type="Bool" readable='1' initial='1'/> <property name="badMessage" type="Bool" volatile='1'/> <property name="ocpi_debug" type="Bool" isImpl='1' parameter='1' default='false'/> <property name="ocpi_endian" type="Enum" enums="little,big,dynamic" isImpl='1' parameter='1' default='little'/> <port name="out" producer='1' numberOfOpcodes="256" bufferSize='8192'> <protocol dataValueWidth="8" dataValueGranularity="1" diverseDataSizes="0" minMessageValues="0"/> </port> </worker> </artifact> From: chinkey <chinkey@office.geontech.com<mailto:chinkey@office.geontech.com>> Sent: Thursday, June 14, 2018 9:02 AM To: Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Cc: James Kulp <jek@parera.com<mailto:jek@parera.com>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so " On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com<mailto:PeterM@signalscape.com%3cmailto:PeterM@signalscape.com>>> wrote: I installed the AV1.3.1 projects using the procedure below, rebuilt everything in core and assets, but get the same failure. I set AV_ALLOW_VERSION_MISMATCH=1 and the Application will run on the zed board using ocpirun, though not successfully. This application will run in CentOS/xsim. Is the procedure below wrong or incomplete? cd /opt/opencpi/projects ./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core cd ~/SS_SDR/Frameworks mkdir ocpi.assets cd ocpi.assets tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz . If previously registered product exists: ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core Register Projects ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core Build cd ~/SS_SDR/Frameworks/ocpi.core/ ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies cd ~/SS_SDR/Frameworks/ocpi.assets ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies -----Original Message----- From: Miller, Peter Sent: Wednesday, June 13, 2018 5:52 PM To: James Kulp <jek@parera.com<mailto:jek@parera.com<mailto:jek@parera.com%3cmailto:jek@parera.com>>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> Subject: RE: [Discuss OpenCPI] ocpirun response I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now. -----Original Message----- From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org%3cmailto:discuss-bounces@lists.opencpi.org>>> On Behalf Of James Kulp Sent: Wednesday, June 13, 2018 5:06 PM To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> Subject: Re: [Discuss OpenCPI] ocpirun response I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed. On 6/13/18 4:38 PM, Miller, Peter wrote: > Support, > I am running AV1.3.1. Running the following on a ZED board: > > > ocpirun -t180 -mmac_low_802dot11=hdl > --library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o > cpi.wifiproject/exports" > icmp_demo_file_mac_highlow_phy_txrx_loopback.xml > > OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version > mismatch ('' vs. expected '1.3') (try increasing log level) Exiting for exception: For instance "file_read_mac_mpdu" for spec "ocpi.core.file_read": no feasible containers found for any of the 4 implementations found. > > 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. > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme%0b%0b>> nts/20180613/adb3d943/attachment.html> > _______________________________________________ > discuss mailing list > discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> > http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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. _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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.

Marasco, Aaron

Thu, Jun 14, 2018 1:42 PM

Peter,

This sounds like the /mnt/net/cdk is coming from the wrong machine or copy of the CDK; examine the mynetsetup.sh to see how/where /mnt/net is mounted. You can run "strings $(which ocpirun) | grep MISMATCH" and see if it says OCPI_ALLOW_VERSION_MISMATCH or AV_ALLOW_VERSION_MISMATCH.

Incidentally, we already added "ocpirun --version" just a few days ago to our develop, so it will be there for 1.4.

Aaron

From: Miller, Peter PeterM@signalscape.com
Sent: Thursday, June 14, 2018 9:34:04 AM
To: Marasco, Aaron
Cc: discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] ocpirun response

% which ocpirun

/mnt/net/cdk/bin/linux-x13_3-arm/ocpirun

This is happening on the zedboard where I am using /mnt/card/opencpi/mynetsetup.sh, etc that was originally created under AV1.2 and modified with my mounts. Is the fix to:

go to AV1.3.1 /opt/opencpi/boot_support/zed/OpenCPI-SD-zed/opencpi
copy to SD card
edit to suit (as before for AV1.2)

Hi Peter,

Let me know how this works for you,

Aaron

Looks like 1.3.

$ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so

what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so "

On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com mailto:PeterM@signalscape.com%3cmailto:PeterM@signalscape.com>> wrote:

Is the procedure below wrong or incomplete?

cd /opt/opencpi/projects

./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core

cd ~/SS_SDR/Frameworks

mkdir ocpi.assets

cd ocpi.assets

tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz .

If previously registered product exists:

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core

Build

cd ~/SS_SDR/Frameworks/ocpi.core/

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

cd ~/SS_SDR/Frameworks/ocpi.assets

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

-----Original Message-----

From: Miller, Peter

Sent: Wednesday, June 13, 2018 5:52 PM

Subject: RE: [Discuss OpenCPI] ocpirun response

I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now.

-----Original Message-----

From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org mailto:discuss-bounces@lists.opencpi.org%3cmailto:discuss-bounces@lists.opencpi.org>> On Behalf Of James Kulp

Sent: Wednesday, June 13, 2018 5:06 PM

To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

Subject: Re: [Discuss OpenCPI] ocpirun response

I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed.

On 6/13/18 4:38 PM, Miller, Peter wrote:

Support,

I am running AV1.3.1. Running the following on a ZED board:

ocpirun -t180 -mmac_low_802dot11=hdl

--library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o

cpi.wifiproject/exports"

icmp_demo_file_mac_highlow_phy_txrx_loopback.xml

OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version

Sincerely,

Peter B. Miller

Potomac: (301) 765-9668

-------------- next part -------------- An HTML attachment was

scrubbed...

URL:

<http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme

http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme%0b%0b> nts/20180613/adb3d943/attachment.html>

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

Peter, This sounds like the /mnt/net/cdk is coming from the wrong machine or copy of the CDK; examine the mynetsetup.sh to see how/where /mnt/net is mounted. You can run "strings $(which ocpirun) | grep MISMATCH" and see if it says OCPI_ALLOW_VERSION_MISMATCH or AV_ALLOW_VERSION_MISMATCH. Incidentally, we already added "ocpirun --version" just a few days ago to our develop, so it will be there for 1.4. Aaron ________________________________ From: Miller, Peter <PeterM@signalscape.com> Sent: Thursday, June 14, 2018 9:34:04 AM To: Marasco, Aaron Cc: discuss@lists.opencpi.org Subject: RE: [Discuss OpenCPI] ocpirun response % which ocpirun /mnt/net/cdk/bin/linux-x13_3-arm/ocpirun This is happening on the zedboard where I am using /mnt/card/opencpi/mynetsetup.sh, etc that was originally created under AV1.2 and modified with my mounts. Is the fix to: 1. go to AV1.3.1 /opt/opencpi/boot_support/zed/OpenCPI-SD-zed/opencpi 2. copy to SD card 3. edit to suit (as before for AV1.2) From: Marasco, Aaron <aaron.marasco@bia-boeing.com> Sent: Thursday, June 14, 2018 9:26 AM To: Miller, Peter <PeterM@signalscape.com> Cc: discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] ocpirun response Hi Peter, This is definitely a strange situation. The fact that your debug listing says "av" and recommends "AV_ALLOW_VERSION_MISMATCH" versus "OCPI_ALLOW_VERSION_MISMATCH" implies that you have a 1.2 or previous "ocpirun" executable somewhere that is being run. When we went OSS, we removed the "AV" prefix and made it "OCPI" as well as changing the internal XML attribute name. Please check "which ocpirun" or if you are using an ACI application, be sure that has been totally rebuilt under 1.3. As an FYI, you shouldn't need to untar the assets source directly. You can run /opt/opencpi/projects/new_project_source and tell it "assets" as the source. I'm pretty sure it handles all the project registration for you automatically as well (does today, I think it did in 1.3). Let me know how this works for you, Aaron ________________________________ From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org>> on behalf of Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Sent: Thursday, June 14, 2018 9:04:26 AM To: EXT-Hinkey, Chris (Geon Technologies) Cc: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response Looks like 1.3. $ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so  <artifact uuid="ad272dd8-6f53-11e8-9259-5b7323f829f5" ocpi_version="1.3" os="linux" osVersion="x13_3" platform="xilinx13_3" arch="arm" dynamic='0'> <worker name="file_read" model="rcc" package="ocpi.core" specname="ocpi.core.file_read" sizeOfConfigSpace="1066" controlOperations="start,release"> <property name="fileName" type="String" stringLength="1024" readable='1' initial='1'/> <property name="messagesInFile" type="Bool" default='false' readable='1' initial='1'/> <property name="opcode" type="UChar" default='0' readable='1' initial='1'/> <property name="messageSize" default='4096' volatile='1' initial='1'/> <property name="granularity" default='1' readable='1' initial='1'/> <property name="repeat" type="Bool" writable='1'/> <property name="bytesRead" type="ULongLong" volatile='1'/> <property name="messagesWritten" type="ULongLong" volatile='1'/> <property name="suppressEOF" type="Bool" readable='1' initial='1'/> <property name="badMessage" type="Bool" volatile='1'/> <property name="ocpi_debug" type="Bool" isImpl='1' parameter='1' default='false'/> <property name="ocpi_endian" type="Enum" enums="little,big,dynamic" isImpl='1' parameter='1' default='little'/> <port name="out" producer='1' numberOfOpcodes="256" bufferSize='8192'> <protocol dataValueWidth="8" dataValueGranularity="1" diverseDataSizes="0" minMessageValues="0"/> </port> </worker> </artifact> From: chinkey <chinkey@office.geontech.com<mailto:chinkey@office.geontech.com>> Sent: Thursday, June 14, 2018 9:02 AM To: Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Cc: James Kulp <jek@parera.com<mailto:jek@parera.com>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so " On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com<mailto:PeterM@signalscape.com%3cmailto:PeterM@signalscape.com>>> wrote: I installed the AV1.3.1 projects using the procedure below, rebuilt everything in core and assets, but get the same failure. I set AV_ALLOW_VERSION_MISMATCH=1 and the Application will run on the zed board using ocpirun, though not successfully. This application will run in CentOS/xsim. Is the procedure below wrong or incomplete? cd /opt/opencpi/projects ./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core cd ~/SS_SDR/Frameworks mkdir ocpi.assets cd ocpi.assets tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz . If previously registered product exists: ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core Register Projects ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core Build cd ~/SS_SDR/Frameworks/ocpi.core/ ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies cd ~/SS_SDR/Frameworks/ocpi.assets ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies -----Original Message----- From: Miller, Peter Sent: Wednesday, June 13, 2018 5:52 PM To: James Kulp <jek@parera.com<mailto:jek@parera.com<mailto:jek@parera.com%3cmailto:jek@parera.com>>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> Subject: RE: [Discuss OpenCPI] ocpirun response I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now. -----Original Message----- From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org%3cmailto:discuss-bounces@lists.opencpi.org>>> On Behalf Of James Kulp Sent: Wednesday, June 13, 2018 5:06 PM To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> Subject: Re: [Discuss OpenCPI] ocpirun response I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed. On 6/13/18 4:38 PM, Miller, Peter wrote: > Support, > I am running AV1.3.1. Running the following on a ZED board: > > > ocpirun -t180 -mmac_low_802dot11=hdl > --library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o > cpi.wifiproject/exports" > icmp_demo_file_mac_highlow_phy_txrx_loopback.xml > > OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version > mismatch ('' vs. expected '1.3') (try increasing log level) Exiting for exception: For instance "file_read_mac_mpdu" for spec "ocpi.core.file_read": no feasible containers found for any of the 4 implementations found. > > 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. > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme%0b%0b>> nts/20180613/adb3d943/attachment.html> > _______________________________________________ > discuss mailing list > discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> > http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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. _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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.

Miller, Peter

Thu, Jun 14, 2018 2:19 PM

Copy /opt/opencpi to /opt/opencpi_mac80211
On SD card, modify mynetsetup.sh to do: source /mnt/card/opencpi/zynq_net_setup.sh $1 /opt/opencpi_mac80211 cdk
Replace /opt/opencpi_mac80211/boot_support/zed/OpenCPI-SD-zed/opencpi/lib/linux-x13_3-arm/opencpi-3.10.0-xilinx-dirty-v14.7.ko with our modified kernel code.
So my "copy" on this machine apparently came from the original development VM rather than as above. I have implemented the above three steps and now getting OCPI_ALLOW and so am on AV1.3.1. And with the revised Petalinux kernel code, so I'm happy.

Thanks for the great service!

From: Marasco, Aaron aaron.marasco@bia-boeing.com
Sent: Thursday, June 14, 2018 9:42 AM
To: Miller, Peter PeterM@signalscape.com
Cc: discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] ocpirun response

Peter,

Incidentally, we already added "ocpirun --version" just a few days ago to our develop, so it will be there for 1.4.

Aaron

From: Miller, Peter <PeterM@signalscape.com mailto:PeterM@signalscape.com>
Sent: Thursday, June 14, 2018 9:34:04 AM
To: Marasco, Aaron
Cc: discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] ocpirun response

% which ocpirun

/mnt/net/cdk/bin/linux-x13_3-arm/ocpirun

This is happening on the zedboard where I am using /mnt/card/opencpi/mynetsetup.sh, etc that was originally created under AV1.2 and modified with my mounts. Is the fix to:

go to AV1.3.1 /opt/opencpi/boot_support/zed/OpenCPI-SD-zed/opencpi
copy to SD card
edit to suit (as before for AV1.2)

From: Marasco, Aaron <aaron.marasco@bia-boeing.com mailto:aaron.marasco@bia-boeing.com>
Sent: Thursday, June 14, 2018 9:26 AM
To: Miller, Peter <PeterM@signalscape.com mailto:PeterM@signalscape.com>
Cc: discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] ocpirun response

Hi Peter,

Let me know how this works for you,

Aaron

Looks like 1.3.

$ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so

what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so "

On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com mailto:PeterM@signalscape.com%3cmailto:PeterM@signalscape.com>> wrote:

Is the procedure below wrong or incomplete?

cd /opt/opencpi/projects

./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core

cd ~/SS_SDR/Frameworks

mkdir ocpi.assets

cd ocpi.assets

tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz .

If previously registered product exists:

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets

ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core

Build

cd ~/SS_SDR/Frameworks/ocpi.core/

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

cd ~/SS_SDR/Frameworks/ocpi.assets

ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies

-----Original Message-----

From: Miller, Peter

Sent: Wednesday, June 13, 2018 5:52 PM

Subject: RE: [Discuss OpenCPI] ocpirun response

I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now.

-----Original Message-----

From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org mailto:discuss-bounces@lists.opencpi.org%3cmailto:discuss-bounces@lists.opencpi.org>> On Behalf Of James Kulp

Sent: Wednesday, June 13, 2018 5:06 PM

To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

Subject: Re: [Discuss OpenCPI] ocpirun response

I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed.

On 6/13/18 4:38 PM, Miller, Peter wrote:

Support,

I am running AV1.3.1. Running the following on a ZED board:

ocpirun -t180 -mmac_low_802dot11=hdl

--library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o

cpi.wifiproject/exports"

icmp_demo_file_mac_highlow_phy_txrx_loopback.xml

OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version

Sincerely,

Peter B. Miller

Potomac: (301) 765-9668

-------------- next part -------------- An HTML attachment was

scrubbed...

URL:

<http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme

http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme%0b%0b> nts/20180613/adb3d943/attachment.html>

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

discuss mailing list

discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>

http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org

OK the problem was this: I was running the Zed with an SD card burned with our Petalinux rebuild to add tools to the kernel to support mac80211. To get network development to work we need to modify the host as well: 1. Copy /opt/opencpi to /opt/opencpi_mac80211 2. On SD card, modify mynetsetup.sh to do: source /mnt/card/opencpi/zynq_net_setup.sh $1 /opt/opencpi_mac80211 cdk 3. Replace /opt/opencpi_mac80211/boot_support/zed/OpenCPI-SD-zed/opencpi/lib/linux-x13_3-arm/opencpi-3.10.0-xilinx-dirty-v14.7.ko with our modified kernel code. So my "copy" on this machine apparently came from the original development VM rather than as above. I have implemented the above three steps and now getting OCPI_ALLOW and so am on AV1.3.1. And with the revised Petalinux kernel code, so I'm happy. Thanks for the great service! From: Marasco, Aaron <aaron.marasco@bia-boeing.com> Sent: Thursday, June 14, 2018 9:42 AM To: Miller, Peter <PeterM@signalscape.com> Cc: discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] ocpirun response Peter, This sounds like the /mnt/net/cdk is coming from the wrong machine or copy of the CDK; examine the mynetsetup.sh to see how/where /mnt/net is mounted. You can run "strings $(which ocpirun) | grep MISMATCH" and see if it says OCPI_ALLOW_VERSION_MISMATCH or AV_ALLOW_VERSION_MISMATCH. Incidentally, we already added "ocpirun --version" just a few days ago to our develop, so it will be there for 1.4. Aaron ________________________________ From: Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Sent: Thursday, June 14, 2018 9:34:04 AM To: Marasco, Aaron Cc: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: RE: [Discuss OpenCPI] ocpirun response % which ocpirun /mnt/net/cdk/bin/linux-x13_3-arm/ocpirun This is happening on the zedboard where I am using /mnt/card/opencpi/mynetsetup.sh, etc that was originally created under AV1.2 and modified with my mounts. Is the fix to: 1. go to AV1.3.1 /opt/opencpi/boot_support/zed/OpenCPI-SD-zed/opencpi 2. copy to SD card 3. edit to suit (as before for AV1.2) From: Marasco, Aaron <aaron.marasco@bia-boeing.com<mailto:aaron.marasco@bia-boeing.com>> Sent: Thursday, June 14, 2018 9:26 AM To: Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Cc: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response Hi Peter, This is definitely a strange situation. The fact that your debug listing says "av" and recommends "AV_ALLOW_VERSION_MISMATCH" versus "OCPI_ALLOW_VERSION_MISMATCH" implies that you have a 1.2 or previous "ocpirun" executable somewhere that is being run. When we went OSS, we removed the "AV" prefix and made it "OCPI" as well as changing the internal XML attribute name. Please check "which ocpirun" or if you are using an ACI application, be sure that has been totally rebuilt under 1.3. As an FYI, you shouldn't need to untar the assets source directly. You can run /opt/opencpi/projects/new_project_source and tell it "assets" as the source. I'm pretty sure it handles all the project registration for you automatically as well (does today, I think it did in 1.3). Let me know how this works for you, Aaron ________________________________ From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org>> on behalf of Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Sent: Thursday, June 14, 2018 9:04:26 AM To: EXT-Hinkey, Chris (Geon Technologies) Cc: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response Looks like 1.3. $ ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so  <artifact uuid="ad272dd8-6f53-11e8-9259-5b7323f829f5" ocpi_version="1.3" os="linux" osVersion="x13_3" platform="xilinx13_3" arch="arm" dynamic='0'> <worker name="file_read" model="rcc" package="ocpi.core" specname="ocpi.core.file_read" sizeOfConfigSpace="1066" controlOperations="start,release"> <property name="fileName" type="String" stringLength="1024" readable='1' initial='1'/> <property name="messagesInFile" type="Bool" default='false' readable='1' initial='1'/> <property name="opcode" type="UChar" default='0' readable='1' initial='1'/> <property name="messageSize" default='4096' volatile='1' initial='1'/> <property name="granularity" default='1' readable='1' initial='1'/> <property name="repeat" type="Bool" writable='1'/> <property name="bytesRead" type="ULongLong" volatile='1'/> <property name="messagesWritten" type="ULongLong" volatile='1'/> <property name="suppressEOF" type="Bool" readable='1' initial='1'/> <property name="badMessage" type="Bool" volatile='1'/> <property name="ocpi_debug" type="Bool" isImpl='1' parameter='1' default='false'/> <property name="ocpi_endian" type="Enum" enums="little,big,dynamic" isImpl='1' parameter='1' default='little'/> <port name="out" producer='1' numberOfOpcodes="256" bufferSize='8192'> <protocol dataValueWidth="8" dataValueGranularity="1" diverseDataSizes="0" minMessageValues="0"/> </port> </worker> </artifact> From: chinkey <chinkey@office.geontech.com<mailto:chinkey@office.geontech.com>> Sent: Thursday, June 14, 2018 9:02 AM To: Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com>> Cc: James Kulp <jek@parera.com<mailto:jek@parera.com>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org> Subject: Re: [Discuss OpenCPI] ocpirun response what is the result of: "ocpixml get ~/SS_SDR/Frameworks/ocpi.core/components/file_read.rcc/target-linux-x13_3-arm/file_read_s.so " On 2018-06-14 08:54, Miller, Peter <PeterM@signalscape.com<mailto:PeterM@signalscape.com<mailto:PeterM@signalscape.com%3cmailto:PeterM@signalscape.com>>> wrote: I installed the AV1.3.1 projects using the procedure below, rebuilt everything in core and assets, but get the same failure. I set AV_ALLOW_VERSION_MISMATCH=1 and the Application will run on the zed board using ocpirun, though not successfully. This application will run in CentOS/xsim. Is the procedure below wrong or incomplete? cd /opt/opencpi/projects ./new_project_source core/ ~/SS_SDR/Frameworks/ocpi.core cd ~/SS_SDR/Frameworks mkdir ocpi.assets cd ocpi.assets tar xf /opt/opencpi/projects/assets/opencpi-assets-v1.3.1.tar.xz . If previously registered product exists: ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks unregister project ocpi.core Register Projects ocpidev -d ~/SS_SDR/Frameworks register project ocpi.assets ocpidev -d ~/SS_SDR/Frameworks register project ocpi.core Build cd ~/SS_SDR/Frameworks/ocpi.core/ ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies cd ~/SS_SDR/Frameworks/ocpi.assets ocpidev build --rcc-hdl-platform xsim --rcc-hdl-platform zed --rcc-hdl-platform matchstiq_z1 --hdl-platform xsim --hdl-platform zed --hdl-platform matchstiq_z1 --no-assemblies -----Original Message----- From: Miller, Peter Sent: Wednesday, June 13, 2018 5:52 PM To: James Kulp <jek@parera.com<mailto:jek@parera.com<mailto:jek@parera.com%3cmailto:jek@parera.com>>>; discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> Subject: RE: [Discuss OpenCPI] ocpirun response I know how this happened. In this VM now running AV1.3.1, I missed the step to update the core and assets from 1.3 to 1.3.1. Doing so now. -----Original Message----- From: discuss <discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org<mailto:discuss-bounces@lists.opencpi.org%3cmailto:discuss-bounces@lists.opencpi.org>>> On Behalf Of James Kulp Sent: Wednesday, June 13, 2018 5:06 PM To: discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> Subject: Re: [Discuss OpenCPI] ocpirun response I'm not exactly sure how you ended up with unversioned artifacts, but setting the OCPI_ALLOW_VERSION_MISMATCH environment variable to 1, will allow this to proceed. On 6/13/18 4:38 PM, Miller, Peter wrote: > Support, > I am running AV1.3.1. Running the following on a ZED board: > > > ocpirun -t180 -mmac_low_802dot11=hdl > --library-path="/mnt/ocpi.core/exports:/mnt/ocpi.assets/exports:/mnt/o > cpi.wifiproject/exports" > icmp_demo_file_mac_highlow_phy_txrx_loopback.xml > > OCPI( 2:509.0389): Rejected 'file_read' ONLY because of AV Version > mismatch ('' vs. expected '1.3') (try increasing log level) Exiting for exception: For instance "file_read_mac_mpdu" for spec "ocpi.core.file_read": no feasible containers found for any of the 4 implementations found. > > 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. > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attachme%0b%0b>> nts/20180613/adb3d943/attachment.html> > _______________________________________________ > discuss mailing list > discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> > http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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. _______________________________________________ discuss mailing list discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org<mailto:discuss@lists.opencpi.org%3cmailto:discuss@lists.opencpi.org>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org --------------------------- 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.