sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

Good point, I'll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I've built for but nothing about an SD card in any of them.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh -s -r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran 'source ./cdk/opencpi-setup.sh -s -r' and confirmed I was pointing at my source build with 'env | grep OCPI'.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I'm not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran './cdk/opencpi-set.sh -s -reset'.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don't see anything in ./exports/zed/ other than 'system.xml' and 'udev-rules'.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don't see the SD card directory.  In './cdk' I see separate directories for 'zed' and 'xilinx13_4'.  './cdk/zed/' contains 'system.xml' and 'udev-rules', './cdk/xilinx13_4' contains some artifacts, binaries and setup scripts.

Sorry I'm having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat '/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*': No such file or directory

#rmdir: failed to remove '/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules': No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command 'make deploy Platform=zed:xilinx13_4' from the top of the tree.  However I don't see  the file path you said would be created.  I see 'exports/xilinx13_4/' which has some artifacts and setup scripts, and I also see 'exports/deploy/xilinx13_4/' that contains 'boot.bin', 'uImage' and 'uramdisk.image.gz'.  I don't see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a 'runtime' and a 'deployment' package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the 'runtime' aspect.  Say the board I'm working with does not have network capabilities... what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I’ll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I’ve built for but nothing about an SD card in any of them.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

[cid:7525f460-e5c3-401d-80b0-e7ff0c4ddb0a]

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I’ll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I’ve built for but nothing about an SD card in any of them.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

Here's a text version

[epaulz@hume-crc-183 opencpi-OpenCPI-2018.Q4-v1.4.0]$ pwd
/home/hume-users/epaulz/opencpi-OpenCPI-2018.Q4-v1.4.0
[epaulz@hume-crc-183 opencpi-OpenCPI-2018.Q4-v1.4.0]$
[epaulz@hume-crc-183 opencpi-OpenCPI-2018.Q4-v1.4.0]$ tree exports/zed/
exports/zed/
+-- system.xml -> ../../platforms/zynq/zynq_system.xml
+-- udev-rules
+-- 98-zedboard.rules -> ../../../project-registry/ocpi.assets/hdl/platforms/zed/98-zedboard.rules

1 directory, 2 files
[epaulz@hume-crc-183 opencpi-OpenCPI-2018.Q4-v1.4.0]$

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I’ll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I’ve built for but nothing about an SD card in any of them.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

that image makes me think that you are on an ubuntu operating system is this the case?

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 11:15 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

[cid:7525f460-e5c3-401d-80b0-e7ff0c4ddb0a]

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I’ll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I’ve built for but nothing about an SD card in any of them.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

I am using an Ubuntu machine to SSH into a more powerful machine that runs CentOS 7, which we are using for development.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 11:40 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

that image makes me think that you are on an ubuntu operating system is this the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 11:15 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

[cid:image001.png@01D4F124.C80D52A0]

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I'll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I've built for but nothing about an SD card in any of them.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh -s -r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran 'source ./cdk/opencpi-setup.sh -s -r' and confirmed I was pointing at my source build with 'env | grep OCPI'.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I'm not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran './cdk/opencpi-set.sh -s -reset'.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don't see anything in ./exports/zed/ other than 'system.xml' and 'udev-rules'.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don't see the SD card directory.  In './cdk' I see separate directories for 'zed' and 'xilinx13_4'.  './cdk/zed/' contains 'system.xml' and 'udev-rules', './cdk/xilinx13_4' contains some artifacts, binaries and setup scripts.

Sorry I'm having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat '/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*': No such file or directory

#rmdir: failed to remove '/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules': No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command 'make deploy Platform=zed:xilinx13_4' from the top of the tree.  However I don't see  the file path you said would be created.  I see 'exports/xilinx13_4/' which has some artifacts and setup scripts, and I also see 'exports/deploy/xilinx13_4/' that contains 'boot.bin', 'uImage' and 'uramdisk.image.gz'.  I don't see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a 'runtime' and a 'deployment' package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the 'runtime' aspect.  Say the board I'm working with does not have network capabilities... what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

hmmm... I grabbed a clean version of the framework and got the following results:

1021  make exports
1022  . exports/opencpi-setup.sh -r
1023  make prerequisites Platforms=centos7
1024  ll
1025  make cleaneverything
1026  make prerequisites Platforms=centos7
1027  ll
1028  rm -rf prerequisites
1029  make prerequisites Platforms=centos7
1030  make prerequisites Platforms=xilinx13_4
1031  make; make Platform=xilinx13_4; make Platform=zed
1032  make deploy Platform=zed:xilinx13_4
1033  ll
1034  cd exports/zed/zed-deploy/
1035  ls
1036  history

chris.hinkey@opencpi (v1.4.0gh =)$ ll exports/zed/
total 0
lrwxrwxrwx. 1 chris.hinkey chris.hinkey 36 Apr 12 12:09 system.xml -> ../../platforms/zynq/zynq_system.xml
drwxr-xr-x. 2 chris.hinkey chris.hinkey 31 Apr 12 12:09 udev-rules
drwxr-xr-x. 4 chris.hinkey chris.hinkey 54 Apr 12 12:23 zed-deploy

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 11:42 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

I am using an Ubuntu machine to SSH into a more powerful machine that runs CentOS 7, which we are using for development.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 11:40 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

that image makes me think that you are on an ubuntu operating system is this the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 11:15 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

[cid:image001.png@01D4F124.C80D52A0]

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I’ll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I’ve built for but nothing about an SD card in any of them.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

I followed your exact steps (with a fresh version of the framework) and I'm still getting the same thing.  Not really sure what is going on...

1030  sudo tar xzf OpenCPI-2018.Q4-v1.4.0.tar.gz
1031  cd opencpi-OpenCPI-2018.Q4-v1.4.0/
1032  sudo make exports
1033  ls
1034  . exports/opencpi-setup.sh -r
1035  env | grep OCPI
1036  sudo make prerequisites Platforms=centos7
1037  ll
1038  sudo make cleaneverything
1039  sudo make prerequisites Platforms=centos7
1040  ll
1041  rm -rf prerequisites
1042  sudo rm -rf prerequisites
1043  sudo make prerequisites Platforms=centos7
1044  sudo make prerequisites Platforms=xilinx13_4
1045  sudo make; sudo make Platform=xilinx13_4; sudo make Platform=zed
1046  sudo make deploy Platform=zed:xilinx13_4
1047  ll
1048  ll exports
1049  ll exports/zed
1050  history

[epaulz@hume-crc-183 opencpi-OpenCPI-2018.Q4-v1.4.0]$ ll exports/zed
total 0
lrwxrwxrwx 1 root root 36 Apr 12 14:34 system.xml -> ../../platforms/zynq/zynq_system.xml
drwxr-xr-x 2 root root 31 Apr 12 14:34 udev-rules

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 1:13:43 PM
To: Paulz, Eric; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

hmmm... I grabbed a clean version of the framework and got the following results:

1021  make exports
1022  . exports/opencpi-setup.sh -r
1023  make prerequisites Platforms=centos7
1024  ll
1025  make cleaneverything
1026  make prerequisites Platforms=centos7
1027  ll
1028  rm -rf prerequisites
1029  make prerequisites Platforms=centos7
1030  make prerequisites Platforms=xilinx13_4
1031  make; make Platform=xilinx13_4; make Platform=zed
1032  make deploy Platform=zed:xilinx13_4
1033  ll
1034  cd exports/zed/zed-deploy/
1035  ls
1036  history

chris.hinkey@opencpi (v1.4.0gh =)$ ll exports/zed/
total 0
lrwxrwxrwx. 1 chris.hinkey chris.hinkey 36 Apr 12 12:09 system.xml -> ../../platforms/zynq/zynq_system.xml
drwxr-xr-x. 2 chris.hinkey chris.hinkey 31 Apr 12 12:09 udev-rules
drwxr-xr-x. 4 chris.hinkey chris.hinkey 54 Apr 12 12:23 zed-deploy

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 11:42 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

I am using an Ubuntu machine to SSH into a more powerful machine that runs CentOS 7, which we are using for development.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 11:40 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

that image makes me think that you are on an ubuntu operating system is this the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 11:15 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

[cid:image001.png@01D4F124.C80D52A0]

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I’ll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I’ve built for but nothing about an SD card in any of them.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767

might be something to do with using sudo for everything.  I would try untaring in a directory that is owned by your user instead of root.

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 2:42 PM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I followed your exact steps (with a fresh version of the framework) and I'm still getting the same thing.  Not really sure what is going on...

1030  sudo tar xzf OpenCPI-2018.Q4-v1.4.0.tar.gz
1031  cd opencpi-OpenCPI-2018.Q4-v1.4.0/
1032  sudo make exports
1033  ls
1034  . exports/opencpi-setup.sh -r
1035  env | grep OCPI
1036  sudo make prerequisites Platforms=centos7
1037  ll
1038  sudo make cleaneverything
1039  sudo make prerequisites Platforms=centos7
1040  ll
1041  rm -rf prerequisites
1042  sudo rm -rf prerequisites
1043  sudo make prerequisites Platforms=centos7
1044  sudo make prerequisites Platforms=xilinx13_4
1045  sudo make; sudo make Platform=xilinx13_4; sudo make Platform=zed
1046  sudo make deploy Platform=zed:xilinx13_4
1047  ll
1048  ll exports
1049  ll exports/zed
1050  history

[epaulz@hume-crc-183 opencpi-OpenCPI-2018.Q4-v1.4.0]$ ll exports/zed
total 0
lrwxrwxrwx 1 root root 36 Apr 12 14:34 system.xml -> ../../platforms/zynq/zynq_system.xml
drwxr-xr-x 2 root root 31 Apr 12 14:34 udev-rules

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 1:13:43 PM
To: Paulz, Eric; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

hmmm... I grabbed a clean version of the framework and got the following results:

1021  make exports
1022  . exports/opencpi-setup.sh -r
1023  make prerequisites Platforms=centos7
1024  ll
1025  make cleaneverything
1026  make prerequisites Platforms=centos7
1027  ll
1028  rm -rf prerequisites
1029  make prerequisites Platforms=centos7
1030  make prerequisites Platforms=xilinx13_4
1031  make; make Platform=xilinx13_4; make Platform=zed
1032  make deploy Platform=zed:xilinx13_4
1033  ll
1034  cd exports/zed/zed-deploy/
1035  ls
1036  history

chris.hinkey@opencpi (v1.4.0gh =)$ ll exports/zed/
total 0
lrwxrwxrwx. 1 chris.hinkey chris.hinkey 36 Apr 12 12:09 system.xml -> ../../platforms/zynq/zynq_system.xml
drwxr-xr-x. 2 chris.hinkey chris.hinkey 31 Apr 12 12:09 udev-rules
drwxr-xr-x. 4 chris.hinkey chris.hinkey 54 Apr 12 12:23 zed-deploy

From: Paulz, Eric epaulz@vt.edu
Sent: Friday, April 12, 2019 11:42 AM
To: Chris Hinkey; discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

I am using an Ubuntu machine to SSH into a more powerful machine that runs CentOS 7, which we are using for development.

From: Chris Hinkey chinkey@geontech.onmicrosoft.com
Sent: Friday, April 12, 2019 11:40 AM
To: Paulz, Eric epaulz@vt.edu; discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

that image makes me think that you are on an ubuntu operating system is this the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 11:15 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

[cid:image001.png@01D4F124.C80D52A0]

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

can you show me the output of the tree command in the "zed" directory?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Good point, I’ll reply all from now on.

I ran through the process again and sourced the script directly from exports but with the same result.  I see separate directories in exports for each sw and hw platform I’ve built for but nothing about an SD card in any of them.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

sometimes that script acts strange if its not ran from the exports location.  so give "source ./exports/opencpi-setup.sh –s –r" and rerun the make commands a shot.

also if you respond to discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org as well as me more smart people will be able to answer you questions

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 10:01 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Yes, I mistyped.  I ran ‘source ./cdk/opencpi-setup.sh –s –r’ and confirmed I was pointing at my source build with ‘env | grep OCPI’.  Then I ran all of the other make commands for good measure.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

ok that all seems right/reasonable

did you run the environment script by doing "source exports/ocpencpi-setup.sh -r"?  This will change your enviroment (in your current shell) from pointing at the rpm install to the source install.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:43 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

It looks like cdk is a symlink to exports and they are identical for me.  So no I’m not seeing that path in either.

I downloaded the source code .tar.gz from https://github.com/opencpi/opencpi/releases.  I unpacked and then built for centos7 and xilinx13_4 (make && make Platform=xilinx13_4).  Then I ran ‘./cdk/opencpi-set.sh –s –reset’.  Then I ran the commands from your previous email (make Platform=zed then make deploy Platform=zed:xilinx13_4).  Unfortunately I don’t see anything in ./exports/zed/ other than ‘system.xml’ and ‘udev-rules’.

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

I was expecting "make deploy Platform=zed:xilinx13_4" to create a folder in exports/zed/zed-deploy/sdcard-xilinx13_4/opencpi is that not the case?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Friday, April 12, 2019 9:27 AM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Unfortunately I still don’t see the SD card directory.  In ‘./cdk’ I see separate directories for ‘zed’ and ‘xilinx13_4’.  ‘./cdk/zed/’ contains ‘system.xml’ and ‘udev-rules’, ‘./cdk/xilinx13_4’ contains some artifacts, binaries and setup scripts.

Sorry I’m having so many issues.  I want to keep pursuing this because I think it will be very helpful for my project.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

So i think i missed a step all you should need to do is "make Platform=zed"  then the make deploy command should work as i had expected before.

more lengthy explanation:

Make prereqs for centos 7 and xilinx13_4

make prerequisites Platforms=centos7 make prerequisites Platforms=xilinx13_4

Make framework for centos 7 and xilinx 13_4 make make Platform=xilinx13_4

Make platform for hw platfrom

make Platform=zed

Make deployment package# May give error messages(fixed in 1.5):

#mv: cannot stat ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules/*’: No such file or directory

#rmdir: failed to remove ‘/tmp/tmp.MtgFaZ91Rr/zed/sdcard-xilinx13_4/opencpi/udev-rules’: No such file or directory

make deploy Platform=zed:xilinx13_4

Now ./cdk/zed/zed-deploy/sdcard-xilinx13_4 should exist.

I would note that the correct boot files do not get put in for xilinx13_4: boot.bin,  uImage, and uramdisk.image.gz... this will be fixed in 1.5.

The above should not matter for his purposes since he is using this just for the opencpi directory

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 11, 2019 3:33 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks, this is very helpful.

I switched over to a source build.  My source tree is built for both centos7 and xilinx13_4.  I ran the command ‘make deploy Platform=zed:xilinx13_4’ from the top of the tree.  However I don’t see  the file path you said would be created.  I see ‘exports/xilinx13_4/’ which has some artifacts and setup scripts, and I also see ‘exports/deploy/xilinx13_4/’ that contains ‘boot.bin’, ‘uImage’ and ‘uramdisk.image.gz’.  I don’t see anything about an SD card.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

In order to do rcc platform development you will need to switch over to a source build to get access to the framework build system.

you basically need to port over the binaries that the framework builds this is what that section of the doc is trying to describe.

for example if i have a source tree that is built for xilinx13_3 and i run the command "make deploy Platform=matchstiq_z1:xilinx13_3"
this will put everything that is needed for standalone mode into a single folder in  "exports/matchstiq_z1/matchstiq_z1-deploy/sdcard-xilinx13_3/opencpi"

you will need to specify a hdl platform even if you haven created yours yet I would recommend just running the command "make deploy Platform=matchstiq:erics_sw_platform" (after building the framework for your new software platform)  this should give you what you would need to test the rcc side of things on your platform.

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 2:25 PM
To: Chris Hinkey
Subject: Re: [Discuss OpenCPI] RCC Platform Development

RPM, version 1.4

On Apr 9, 2019, at 14:00, Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com> wrote:

trying to find the right people for help to answer your question.  I'll get back to you shortly.

Are you using a source build tor rpm enviroment?

From: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Tuesday, April 9, 2019 1:05 PM
To: Chris Hinkey
Subject: RE: [Discuss OpenCPI] RCC Platform Development

Thanks for your response, that does help.  I have a quick follow-up question:

I have built a simple application and run is successfully on my development machine.  I am now following the steps in 4.2.1 of the Platform Development Guide trying to create a ‘runtime’ and a ‘deployment’ package so that I can test it on a SDR board.  The document seems to make the assumption that the development and embedded systems can share files over a network and this fulfills the ‘runtime’ aspect.  Say the board I’m working with does not have network capabilities… what would be the best way to create a runtime/deployment package all in one and load the whole thing onto an SD card that the board can reference when trying to run an OpenCPI application?

Hope this makes sense and thanks in advance.

• Eric

From: Chris Hinkey <chinkey@geontech.onmicrosoft.commailto:chinkey@geontech.onmicrosoft.com>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>; discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development

all the rcc platforms xilinx13_3/4 in the core project afre for embedded radios
one other place to look that might be useful to look is geontech's implementation of the xilinx18_2 rcc platform https://github.com/Geontech/sw_xilinx18_2

what you essentially need to do is to set the make file to point to your compiler and set any flags that are needed for this compiler then build the framework from source and move these executables to the platform to run them.  In order for the build tools to recognize the new platform that you created the project that you created it in has to be registered in your project registry.  one way to determine if the tools can see your platform at all is to use the command "ocpidev show rcc platforms"

The fact that the platforms we have use SD cards too boot is maybe a poor choice of words in the documentation.  Outside of opencpi you have a way to boot your platform, you have a compiler to compile executables, and you have some way to get built executable on to the platform use those in order to complete your task.

hope this helps

From: discuss <discuss-bounces@lists.opencpi.orgmailto:discuss-bounces@lists.opencpi.org> on behalf of Paulz, Eric <epaulz@vt.edumailto:epaulz@vt.edu>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss@lists.opencpi.orgmailto:discuss@lists.opencpi.org
Subject: [Discuss OpenCPI] RCC Platform Development

Hello,

I am working on an RCC platform for an embedded target (AstroSDR) on which the existing OS must remain as is.  The main challenge I'm facing is that all examples of enabling execution for GPP platforms recommend running Petalinux on the target, and all other examples of RCC platforms seem to be for development (I could be wrong on this).  Another issue is that the board is not configured to boot from an SD card as is detailed in the Platform Development Guide.  I attended the training workshop late last month and picked up some great tips, but I'm still struggling to get the platform to build properly so that I can test it out with some basic apps.

Are there any steps that I may be missing or existing cases similar to this that could be referenced?

Thanks,

Eric C. Paulz
Computer Engineer
Hume Center for National Security & Technology
epaulz@vt.edumailto:epaulz@vt.edumailto:epaulz@vt.edu
Office: 540-231-6180
Cell: 864-243-6767