that image makes me think that you are on an ubuntu operating system is this the case?
________________________________
From: Paulz, Eric <epaulz_at_vt.edu>
Sent: Friday, April 12, 2019 11:15 AM
To: Chris Hinkey; discuss_at_lists.opencpi.org
Subject: Re: [Discuss OpenCPI] RCC Platform Development
[cid:7525f460-e5c3-401d-80b0-e7ff0c4ddb0a]
________________________________
From: Chris Hinkey <chinkey_at_geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 11:11:04 AM
To: Paulz, Eric; discuss_at_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_at_vt.edu>
Sent: Friday, April 12, 2019 10:18 AM
To: Chris Hinkey; discuss_at_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_at_geontech.onmicrosoft.com>
Sent: Friday, April 12, 2019 10:09 AM
To: Paulz, Eric <epaulz_at_vt.edu>; discuss_at_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_at_lists.opencpi.org<mailto:discuss_at_lists.opencpi.org> as well as me more smart people will be able to answer you questions
________________________________
From: Paulz, Eric <epaulz_at_vt.edu<mailto:epaulz_at_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_at_geontech.onmicrosoft.com<mailto:chinkey_at_geontech.onmicrosoft.com>>
Sent: Friday, April 12, 2019 9:51 AM
To: Paulz, Eric <epaulz_at_vt.edu<mailto:epaulz_at_vt.edu>>; discuss_at_lists.opencpi.org<mailto:discuss_at_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_at_vt.edu<mailto:epaulz_at_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_at_geontech.onmicrosoft.com<mailto:chinkey_at_geontech.onmicrosoft.com>>
Sent: Friday, April 12, 2019 9:32 AM
To: Paulz, Eric <epaulz_at_vt.edu<mailto:epaulz_at_vt.edu>>; discuss_at_lists.opencpi.org<mailto:discuss_at_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_at_vt.edu<mailto:epaulz_at_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_at_geontech.onmicrosoft.com<mailto:chinkey_at_geontech.onmicrosoft.com>>
Sent: Friday, April 12, 2019 8:50 AM
To: Paulz, Eric <epaulz_at_vt.edu<mailto:epaulz_at_vt.edu>>; discuss_at_lists.opencpi.org<mailto:discuss_at_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_at_vt.edu<mailto:epaulz_at_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_at_geontech.onmicrosoft.com<mailto:chinkey_at_geontech.onmicrosoft.com>>
Sent: Tuesday, April 9, 2019 3:49 PM
To: Paulz, Eric <epaulz_at_vt.edu<mailto:epaulz_at_vt.edu>>; discuss_at_lists.opencpi.org<mailto:discuss_at_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_at_vt.edu<mailto:epaulz_at_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_at_geontech.onmicrosoft.com<mailto:chinkey_at_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_at_vt.edu<mailto:epaulz_at_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_at_geontech.onmicrosoft.com<mailto:chinkey_at_geontech.onmicrosoft.com>>
Sent: Thursday, April 4, 2019 2:07 PM
To: Paulz, Eric <epaulz_at_vt.edu<mailto:epaulz_at_vt.edu>>; discuss_at_lists.opencpi.org<mailto:discuss_at_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_at_lists.opencpi.org<mailto:discuss-bounces_at_lists.opencpi.org>> on behalf of Paulz, Eric <epaulz_at_vt.edu<mailto:epaulz_at_vt.edu>>
Sent: Thursday, April 4, 2019 1:41 PM
To: discuss_at_lists.opencpi.org<mailto:discuss_at_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_at_vt.edu<mailto:epaulz_at_vt.edu><mailto:epaulz_at_vt.edu>
Office: 540-231-6180
Cell: 864-243-6767
Received on Fri Apr 12 2019 - 15:39:59 CDT