Jim, Building from source following https://opencpi.github.io/OpenCPI_Installation.pdf. Takes long time and fails as below: $ git clone https://github.com/opencpi/opencpi.git $ cd opencpi/ $ git tag $ git checkout v1.5.0 $./scripts/install-opencpi.sh $ source ~/opencpi/cdk/opencpi-setup.sh -s >>> Install Xilinx tools $./scripts/install-opencpi.sh xilinx13_4 $ make hdl HdlPlatforms="xsim zed" ============Building HDL implementation ddc.hdl for target(s): xsim zynq : : /home/pbmiller/opencpi/cdk/include/hdl/hdl-lib2.mk:48: *** No core found for "ddc_4243_4ch_v5" on target "xsim". Stop. make[2]: *** [ddc.hdl] Error 2 make[2]: Leaving directory `/home/pbmiller/opencpi/projects/inactive/components' make[1]: *** [hdlcomponents] Error 2 make[1]: Leaving directory `/home/pbmiller/opencpi/projects/inactive' make: *** [hdl] Error 2 $ make deploy Platform=zed:xilinx13_4 Updating exports for platforms: zed:xilinx13_4 Adding files for sw platform: xilinx13_4 Adding files for hw platform: zed mv: cannot stat ‘/tmp/tmp.3eAACyDUgm/zed/sdcard-xilinx13_4/opencpi/zed/xilinx13_4/system.xml’: No such file or directory Also note: Per https://opencpi.github.io/OpenCPI_Installation.pdf section 4.1.2 I tried downloading 2013.4-release.tar.xz and write to SD card without success (zed won't boot). That does work if I try the 2017.1-zed-release.tar version. Could you send me the SD card files (boot.bin devicetree.dtb uImage uramdisk.image.gz) that you are using (don't need opencpi folder)? Sincerely, Peter B. Miller Potomac: (301) 765-9668 -----Original Message----- From: James Kulp <jek@parera.com> Sent: Thursday, September 26, 2019 3:02 PM To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] Programming SD card for Zed Hi Peter, I have just (re)built the xilinx13_4 from source, make the SD card and successfully executed on it. This is based on a development branch rather than 1.5, but I don't know of anything that changed here. After building the source tree for xilinx13_4 (and the driver), I had to do (in the source tree): make deploy Platform=xilinx13_4 make deploy Platform=zed:xilinx13_4 The first line was unexpected and actually *also* builds RPMs as a side effect, and we'll clean it up a bit in 1.6. The result was an SD card in cdk/zed/zed-deploy/sdcard-xilinx13_4 And I used: cp -R -p cdk/zed/zed-deploy/sdcard-xilinx13_4/* /Volumes/BOOT (Where /Volumes/Boot was the mount point of the SD card). I was doing this since we have just done a xilinx19_1_aarch32 version for zed and I wanted to back-test. Jim On 9/26/19 11:15 AM, Miller, Peter wrote: > I only copied the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) - no opencpi/* so no sym links. I think one or more of those files is corrupt. The procedure was: > > 1. $ sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* > /media/sf_SD_card 2. Put the SD card in the zedboard and power up 3. > Open a putty terminal and log in. Success 4. Put the SD card back into > PC/VM/CentOS 5. $ sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* > /media/sf_SD_card 6. Put the SD card in the zedboard and power up 7. > Open a putty terminal and log in. Fails > > I am now installing OpenCPI 1.5 in a fresh CentOS 7.5 VM from source. I will run the scripts and build the boot images. > > Sincerely, > Peter B. Miller > Potomac: (301) 765-9668 > > -----Original Message----- > From: James Kulp <jek@parera.com> > Sent: Thursday, September 26, 2019 10:56 AM > To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org > Subject: Re: [Discuss OpenCPI] Programming SD card for Zed > > Can you describe the failure? I think I understand, but we're doing more testing. > > The sdcard image directories only have symlinks that should remain symlinks, so in fact using cp -L is masking some other problem. > > Jim > > > > > > On 9/26/19 8:09 AM, Miller, Peter wrote: >> ... that would be: >> % sudo cp -RLp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >> >> Sincerely, >> Peter B. Miller >> Potomac: (301) 765-9668 >> >> -----Original Message----- >> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of >> Miller, Peter >> Sent: Thursday, September 26, 2019 7:25 AM >> To: James Kulp <jek@parera.com>; discuss@lists.opencpi.org >> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >> >> Jim, >> Still trying to get OpenCPI 1.5 from RPM, and Zedboard up. I find that the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) from /opt/opencpi/cdk/zed/sdcard-xilinx13_3 can be copied to SD card and the zedboard boots PetaLinux v2013.10. But using the files from /opt/opencpi/cdk/zed/sdcard-xilinx13_4 the zedboard will not boot. >> >> WORKS: >> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* /media/sf_SD_card >> >> FAILS: >> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/sf_SD_card >> >> Also, per Jerry Darko's comment, the instructions in "OpenCPI_Installation.pdf" Section 4.1 should be revised to something like: >> % sudo -RLp cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >> >> Sincerely, >> Peter B. Miller >> Potomac: (301) 765-9668 >> >> -----Original Message----- >> From: James Kulp <jek@parera.com> >> Sent: Wednesday, September 25, 2019 10:46 AM >> To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org >> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >> >> I have certainly had problems with symlinks when mounting a "host" file system into a VM. I solve it by always using NFS, even between a VM and its host. >> I'm not sure that is your issue... >> >> Yes, that is the intention of that directory. >> >> I'm actually doing something similar later today to test some new FPGA loading code... >> >> Jim >> >> >> >> >> >> On 9/25/19 10:39 AM, Miller, Peter wrote: >>> Do you confirm that copying from /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* is correct? >>> Media is write-able - this issue with sym links is a VM problem and I wondered if you had a simple workaround. I'll either chase it down or go to a native linux machine to copy it. >>> >>> Sincerely, >>> Peter B. Miller >>> Potomac: (301) 765-9668 >>> >>> -----Original Message----- >>> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of James >>> Kulp >>> Sent: Wednesday, September 25, 2019 10:32 AM >>> To: discuss@lists.opencpi.org >>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>> >>> This is a source-install vs. rpm-install issue, and the docs should be clearer about this distinction. This is in fact a current work item. >>> >>> If looks like the /media was mounted read-only? >>> >>> Both RPM and source installations should allow you to do this. >>> >>> Not sure what the "VM symbolic link issue" is. Other email? >>> >>> >>> >>> On 9/25/19 10:21 AM, Miller, Peter wrote: >>>> Installed using the instructions at https://www.opencpi.org/services >>>> * sudo yum install yum-utils epel-release >>>> * sudo yum-config-manager --add-repo=http://opencpi.github.io/repo/opencpi.repo >>>> * sudo yum install 'opencpi*' >>>> To prepare the Zed SD card, instructions in https://opencpi.github.io/OpenCPI_Installation.pdf Page 23 say: >>>> " ...OpenCPI source tree, its path is: projects/core/rcc/platforms/xilinx13_4" >>>> which is not there. Instead I find the desired content at: >>>> "/opt/opencpi/cdk/zed/sdcard-xilinx13_4" >>>> >>>> The specified procedure to copy to SD in a CentOS7 VM fails: >>>> $ sudo cp -r /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* >>>> /media/sf_SD_card >>>> cp: cannot create symbolic link >>>> '/media/sf_SD_card/opencpi/xilinx13_4/bin/ntpd': Read-only file >>>> system >>>> cp: cannot create symbolic link >>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so': Read-only >>>> file system >>>> cp: cannot create symbolic link >>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so.10': Read-only >>>> file system >>>> cp: cannot create symbolic link >>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so': Read-only >>>> file system >>>> cp: cannot create symbolic link >>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so.4': Read-only >>>> file system >>>> cp: cannot create symbolic link >>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so': Read-only >>>> file system >>>> cp: cannot create symbolic link >>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so.5': Read-only file system Resulting SD card won't boot the Zedboard. >>>> >>>> Q1. Is the Installation Guide just out of date regarding the location of the content to copy to the SD card? >>>> Q2. Any suggestions for the VM symbolic link copy issue? >>>> Q3. Better to install from source as in "OpenCPI_Installation" rather than from RPMs? >>>> >>>> Sincerely, >>>> Peter B. Miller >>>> Potomac: (301) 765-9668 >>>> >>>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>>> -------------- next part -------------- An HTML attachment was >>>> scrubbed... >>>> URL: >>>> <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attac >>>> h m e nts/20190925/6d8acfb1/attachment.html> >>>> _______________________________________________ >>>> discuss mailing list >>>> discuss@lists.opencpi.org >>>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>> _______________________________________________ >>> discuss mailing list >>> discuss@lists.opencpi.org >>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >> _______________________________________________ >> discuss mailing list >> discuss@lists.opencpi.org >> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. > > --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.

I'm actually in a place to test this exact thing.  SD card creation and testing did not get sufficient testing for release 1.5.  It is a manual process that is not part of the test automation yet. Thanks for the clear report. On 9/30/19 3:48 PM, Miller, Peter wrote: > Jim, > Building from source following https://opencpi.github.io/OpenCPI_Installation.pdf. Takes long time and fails as below: > > $ git clone https://github.com/opencpi/opencpi.git > $ cd opencpi/ > $ git tag > $ git checkout v1.5.0 > $./scripts/install-opencpi.sh > $ source ~/opencpi/cdk/opencpi-setup.sh -s > >>> Install Xilinx tools > $./scripts/install-opencpi.sh xilinx13_4 > $ make hdl HdlPlatforms="xsim zed" > ============Building HDL implementation ddc.hdl for target(s): xsim zynq > : > : > /home/pbmiller/opencpi/cdk/include/hdl/hdl-lib2.mk:48: *** No core found for "ddc_4243_4ch_v5" on target "xsim". Stop. > make[2]: *** [ddc.hdl] Error 2 > make[2]: Leaving directory `/home/pbmiller/opencpi/projects/inactive/components' > make[1]: *** [hdlcomponents] Error 2 > make[1]: Leaving directory `/home/pbmiller/opencpi/projects/inactive' > make: *** [hdl] Error 2 > > $ make deploy Platform=zed:xilinx13_4 > Updating exports for platforms: zed:xilinx13_4 > Adding files for sw platform: xilinx13_4 > Adding files for hw platform: zed > mv: cannot stat ‘/tmp/tmp.3eAACyDUgm/zed/sdcard-xilinx13_4/opencpi/zed/xilinx13_4/system.xml’: No such file or directory > > Also note: Per https://opencpi.github.io/OpenCPI_Installation.pdf section 4.1.2 I tried downloading 2013.4-release.tar.xz and write to SD card without success (zed won't boot). That does work if I try the 2017.1-zed-release.tar version. Could you send me the SD card files (boot.bin devicetree.dtb uImage uramdisk.image.gz) that you are using (don't need opencpi folder)? > > > Sincerely, > Peter B. Miller > Potomac: (301) 765-9668 > > -----Original Message----- > From: James Kulp <jek@parera.com> > Sent: Thursday, September 26, 2019 3:02 PM > To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org > Subject: Re: [Discuss OpenCPI] Programming SD card for Zed > > Hi Peter, > > I have just (re)built the xilinx13_4 from source, make the SD card and successfully executed on it. > This is based on a development branch rather than 1.5, but I don't know of anything that changed here. > > After building the source tree for xilinx13_4 (and the driver), I had to do (in the source tree): > > make deploy Platform=xilinx13_4 > make deploy Platform=zed:xilinx13_4 > > The first line was unexpected and actually *also* builds RPMs as a side effect, and we'll clean it up a bit in 1.6. > The result was an SD card in cdk/zed/zed-deploy/sdcard-xilinx13_4 > And I used: > cp -R -p cdk/zed/zed-deploy/sdcard-xilinx13_4/* /Volumes/BOOT > > (Where /Volumes/Boot was the mount point of the SD card). > > I was doing this since we have just done a xilinx19_1_aarch32 version for zed and I wanted to back-test. > > Jim > > > > > > > On 9/26/19 11:15 AM, Miller, Peter wrote: >> I only copied the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) - no opencpi/* so no sym links. I think one or more of those files is corrupt. The procedure was: >> >> 1. $ sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* >> /media/sf_SD_card 2. Put the SD card in the zedboard and power up 3. >> Open a putty terminal and log in. Success 4. Put the SD card back into >> PC/VM/CentOS 5. $ sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* >> /media/sf_SD_card 6. Put the SD card in the zedboard and power up 7. >> Open a putty terminal and log in. Fails >> >> I am now installing OpenCPI 1.5 in a fresh CentOS 7.5 VM from source. I will run the scripts and build the boot images. >> >> Sincerely, >> Peter B. Miller >> Potomac: (301) 765-9668 >> >> -----Original Message----- >> From: James Kulp <jek@parera.com> >> Sent: Thursday, September 26, 2019 10:56 AM >> To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org >> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >> >> Can you describe the failure? I think I understand, but we're doing more testing. >> >> The sdcard image directories only have symlinks that should remain symlinks, so in fact using cp -L is masking some other problem. >> >> Jim >> >> >> >> >> >> On 9/26/19 8:09 AM, Miller, Peter wrote: >>> ... that would be: >>> % sudo cp -RLp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >>> >>> Sincerely, >>> Peter B. Miller >>> Potomac: (301) 765-9668 >>> >>> -----Original Message----- >>> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of >>> Miller, Peter >>> Sent: Thursday, September 26, 2019 7:25 AM >>> To: James Kulp <jek@parera.com>; discuss@lists.opencpi.org >>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>> >>> Jim, >>> Still trying to get OpenCPI 1.5 from RPM, and Zedboard up. I find that the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) from /opt/opencpi/cdk/zed/sdcard-xilinx13_3 can be copied to SD card and the zedboard boots PetaLinux v2013.10. But using the files from /opt/opencpi/cdk/zed/sdcard-xilinx13_4 the zedboard will not boot. >>> >>> WORKS: >>> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* /media/sf_SD_card >>> >>> FAILS: >>> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/sf_SD_card >>> >>> Also, per Jerry Darko's comment, the instructions in "OpenCPI_Installation.pdf" Section 4.1 should be revised to something like: >>> % sudo -RLp cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >>> >>> Sincerely, >>> Peter B. Miller >>> Potomac: (301) 765-9668 >>> >>> -----Original Message----- >>> From: James Kulp <jek@parera.com> >>> Sent: Wednesday, September 25, 2019 10:46 AM >>> To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org >>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>> >>> I have certainly had problems with symlinks when mounting a "host" file system into a VM. I solve it by always using NFS, even between a VM and its host. >>> I'm not sure that is your issue... >>> >>> Yes, that is the intention of that directory. >>> >>> I'm actually doing something similar later today to test some new FPGA loading code... >>> >>> Jim >>> >>> >>> >>> >>> >>> On 9/25/19 10:39 AM, Miller, Peter wrote: >>>> Do you confirm that copying from /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* is correct? >>>> Media is write-able - this issue with sym links is a VM problem and I wondered if you had a simple workaround. I'll either chase it down or go to a native linux machine to copy it. >>>> >>>> Sincerely, >>>> Peter B. Miller >>>> Potomac: (301) 765-9668 >>>> >>>> -----Original Message----- >>>> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of James >>>> Kulp >>>> Sent: Wednesday, September 25, 2019 10:32 AM >>>> To: discuss@lists.opencpi.org >>>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>>> >>>> This is a source-install vs. rpm-install issue, and the docs should be clearer about this distinction. This is in fact a current work item. >>>> >>>> If looks like the /media was mounted read-only? >>>> >>>> Both RPM and source installations should allow you to do this. >>>> >>>> Not sure what the "VM symbolic link issue" is. Other email? >>>> >>>> >>>> >>>> On 9/25/19 10:21 AM, Miller, Peter wrote: >>>>> Installed using the instructions at https://www.opencpi.org/services >>>>> * sudo yum install yum-utils epel-release >>>>> * sudo yum-config-manager --add-repo=http://opencpi.github.io/repo/opencpi.repo >>>>> * sudo yum install 'opencpi*' >>>>> To prepare the Zed SD card, instructions in https://opencpi.github.io/OpenCPI_Installation.pdf Page 23 say: >>>>> " ...OpenCPI source tree, its path is: projects/core/rcc/platforms/xilinx13_4" >>>>> which is not there. Instead I find the desired content at: >>>>> "/opt/opencpi/cdk/zed/sdcard-xilinx13_4" >>>>> >>>>> The specified procedure to copy to SD in a CentOS7 VM fails: >>>>> $ sudo cp -r /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* >>>>> /media/sf_SD_card >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/bin/ntpd': Read-only file >>>>> system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so.10': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so.4': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so.5': Read-only file system Resulting SD card won't boot the Zedboard. >>>>> >>>>> Q1. Is the Installation Guide just out of date regarding the location of the content to copy to the SD card? >>>>> Q2. Any suggestions for the VM symbolic link copy issue? >>>>> Q3. Better to install from source as in "OpenCPI_Installation" rather than from RPMs? >>>>> >>>>> Sincerely, >>>>> Peter B. Miller >>>>> Potomac: (301) 765-9668 >>>>> >>>>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>>>> -------------- next part -------------- An HTML attachment was >>>>> scrubbed... >>>>> URL: >>>>> <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attac >>>>> h m e nts/20190925/6d8acfb1/attachment.html> >>>>> _______________________________________________ >>>>> discuss mailing list >>>>> discuss@lists.opencpi.org >>>>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>>> _______________________________________________ >>>> discuss mailing list >>>> discuss@lists.opencpi.org >>>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>> _______________________________________________ >>> discuss mailing list >>> discuss@lists.opencpi.org >>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. > > --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.

Hi Peter, The first problem is due to the fact that "make hdl" in the top level of the source tree does this for all projects, including "inactive". And the inactive project is *supposed* to certainly build, but that build step is not exercised when RPMs are built for a release.  Our bad... That error in the "inactive" project exercised a rarely used code path in the build engine, which had a bug (when building a pre-synthesized core for a simulator). The workaround is to use the Projects variable to restrict the projects to avoid "inactive", e.g.: make hdl HdlPlatforms="xsim zed" Projects="core assets assets_ts". Note we recommend using the ocpidev command for most project-based actions. But the actual bug fix (which was already in 1.6, and which we *might* fix in a 1.5.1 patch release) is simply: > +++ b/tools/cdk/include/hdl/hdl-core.mk > @@ -106,7 +106,7 @@ $(HdlInstallLibDir): > >  # Install the lib-name directory. This is used for non-real cores >  # or for real cores when a tool requires source listings (for stubs) > -install_lib_dir: | $(HdlInstallLibDir) > +install_lib_dir: build | $(HdlInstallLibDir) The second problem (making the SD card), was also based on "tested for RPM, but not tested in the source tree".  That fix is: > diff --git a/packaging/create-hw-deploy.sh b/packaging/create-hw-deploy.sh > index 26163b5..3d3cc67 100755 > --- a/packaging/create-hw-deploy.sh > +++ b/packaging/create-hw-deploy.sh > @@ -82,6 +82,7 @@ for file in ${file_list[@]}; do >             [ -d $file ] && mkdir -p $opencpi_output_path/$edited_file) >    fi >  done > +[ -e $opencpi_output_path/$hdl_platform/$hdl_rcc_platform/system.xml ] && >  mv $opencpi_output_path/$hdl_platform/$hdl_rcc_platform/system.xml > $opencpi_output_path (There are other issues with the SD card generation process that have been addressed for 1.6). Finally, I have no idea why the standard binary release for the SD card would not boot since that is a "supported" platform for Xilinx. My only guess would be how the SD card itself was formatted prior to putting the files on it. The files you are looking for are in the projects/core/rcc/platforms/xilinx13_4/release directory. Jim On 9/30/19 3:48 PM, Miller, Peter wrote: > Jim, > Building from source following https://opencpi.github.io/OpenCPI_Installation.pdf. Takes long time and fails as below: > > $ git clone https://github.com/opencpi/opencpi.git > $ cd opencpi/ > $ git tag > $ git checkout v1.5.0 > $./scripts/install-opencpi.sh > $ source ~/opencpi/cdk/opencpi-setup.sh -s > >>> Install Xilinx tools > $./scripts/install-opencpi.sh xilinx13_4 > $ make hdl HdlPlatforms="xsim zed" > ============Building HDL implementation ddc.hdl for target(s): xsim zynq > : > : > /home/pbmiller/opencpi/cdk/include/hdl/hdl-lib2.mk:48: *** No core found for "ddc_4243_4ch_v5" on target "xsim". Stop. > make[2]: *** [ddc.hdl] Error 2 > make[2]: Leaving directory `/home/pbmiller/opencpi/projects/inactive/components' > make[1]: *** [hdlcomponents] Error 2 > make[1]: Leaving directory `/home/pbmiller/opencpi/projects/inactive' > make: *** [hdl] Error 2 > > $ make deploy Platform=zed:xilinx13_4 > Updating exports for platforms: zed:xilinx13_4 > Adding files for sw platform: xilinx13_4 > Adding files for hw platform: zed > mv: cannot stat ‘/tmp/tmp.3eAACyDUgm/zed/sdcard-xilinx13_4/opencpi/zed/xilinx13_4/system.xml’: No such file or directory > > Also note: Per https://opencpi.github.io/OpenCPI_Installation.pdf section 4.1.2 I tried downloading 2013.4-release.tar.xz and write to SD card without success (zed won't boot). That does work if I try the 2017.1-zed-release.tar version. Could you send me the SD card files (boot.bin devicetree.dtb uImage uramdisk.image.gz) that you are using (don't need opencpi folder)? > > > Sincerely, > Peter B. Miller > Potomac: (301) 765-9668 > > -----Original Message----- > From: James Kulp <jek@parera.com> > Sent: Thursday, September 26, 2019 3:02 PM > To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org > Subject: Re: [Discuss OpenCPI] Programming SD card for Zed > > Hi Peter, > > I have just (re)built the xilinx13_4 from source, make the SD card and successfully executed on it. > This is based on a development branch rather than 1.5, but I don't know of anything that changed here. > > After building the source tree for xilinx13_4 (and the driver), I had to do (in the source tree): > > make deploy Platform=xilinx13_4 > make deploy Platform=zed:xilinx13_4 > > The first line was unexpected and actually *also* builds RPMs as a side effect, and we'll clean it up a bit in 1.6. > The result was an SD card in cdk/zed/zed-deploy/sdcard-xilinx13_4 > And I used: > cp -R -p cdk/zed/zed-deploy/sdcard-xilinx13_4/* /Volumes/BOOT > > (Where /Volumes/Boot was the mount point of the SD card). > > I was doing this since we have just done a xilinx19_1_aarch32 version for zed and I wanted to back-test. > > Jim > > > > > > > On 9/26/19 11:15 AM, Miller, Peter wrote: >> I only copied the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) - no opencpi/* so no sym links. I think one or more of those files is corrupt. The procedure was: >> >> 1. $ sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* >> /media/sf_SD_card 2. Put the SD card in the zedboard and power up 3. >> Open a putty terminal and log in. Success 4. Put the SD card back into >> PC/VM/CentOS 5. $ sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* >> /media/sf_SD_card 6. Put the SD card in the zedboard and power up 7. >> Open a putty terminal and log in. Fails >> >> I am now installing OpenCPI 1.5 in a fresh CentOS 7.5 VM from source. I will run the scripts and build the boot images. >> >> Sincerely, >> Peter B. Miller >> Potomac: (301) 765-9668 >> >> -----Original Message----- >> From: James Kulp <jek@parera.com> >> Sent: Thursday, September 26, 2019 10:56 AM >> To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org >> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >> >> Can you describe the failure? I think I understand, but we're doing more testing. >> >> The sdcard image directories only have symlinks that should remain symlinks, so in fact using cp -L is masking some other problem. >> >> Jim >> >> >> >> >> >> On 9/26/19 8:09 AM, Miller, Peter wrote: >>> ... that would be: >>> % sudo cp -RLp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >>> >>> Sincerely, >>> Peter B. Miller >>> Potomac: (301) 765-9668 >>> >>> -----Original Message----- >>> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of >>> Miller, Peter >>> Sent: Thursday, September 26, 2019 7:25 AM >>> To: James Kulp <jek@parera.com>; discuss@lists.opencpi.org >>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>> >>> Jim, >>> Still trying to get OpenCPI 1.5 from RPM, and Zedboard up. I find that the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) from /opt/opencpi/cdk/zed/sdcard-xilinx13_3 can be copied to SD card and the zedboard boots PetaLinux v2013.10. But using the files from /opt/opencpi/cdk/zed/sdcard-xilinx13_4 the zedboard will not boot. >>> >>> WORKS: >>> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* /media/sf_SD_card >>> >>> FAILS: >>> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/sf_SD_card >>> >>> Also, per Jerry Darko's comment, the instructions in "OpenCPI_Installation.pdf" Section 4.1 should be revised to something like: >>> % sudo -RLp cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >>> >>> Sincerely, >>> Peter B. Miller >>> Potomac: (301) 765-9668 >>> >>> -----Original Message----- >>> From: James Kulp <jek@parera.com> >>> Sent: Wednesday, September 25, 2019 10:46 AM >>> To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org >>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>> >>> I have certainly had problems with symlinks when mounting a "host" file system into a VM. I solve it by always using NFS, even between a VM and its host. >>> I'm not sure that is your issue... >>> >>> Yes, that is the intention of that directory. >>> >>> I'm actually doing something similar later today to test some new FPGA loading code... >>> >>> Jim >>> >>> >>> >>> >>> >>> On 9/25/19 10:39 AM, Miller, Peter wrote: >>>> Do you confirm that copying from /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* is correct? >>>> Media is write-able - this issue with sym links is a VM problem and I wondered if you had a simple workaround. I'll either chase it down or go to a native linux machine to copy it. >>>> >>>> Sincerely, >>>> Peter B. Miller >>>> Potomac: (301) 765-9668 >>>> >>>> -----Original Message----- >>>> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of James >>>> Kulp >>>> Sent: Wednesday, September 25, 2019 10:32 AM >>>> To: discuss@lists.opencpi.org >>>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>>> >>>> This is a source-install vs. rpm-install issue, and the docs should be clearer about this distinction. This is in fact a current work item. >>>> >>>> If looks like the /media was mounted read-only? >>>> >>>> Both RPM and source installations should allow you to do this. >>>> >>>> Not sure what the "VM symbolic link issue" is. Other email? >>>> >>>> >>>> >>>> On 9/25/19 10:21 AM, Miller, Peter wrote: >>>>> Installed using the instructions at https://www.opencpi.org/services >>>>> * sudo yum install yum-utils epel-release >>>>> * sudo yum-config-manager --add-repo=http://opencpi.github.io/repo/opencpi.repo >>>>> * sudo yum install 'opencpi*' >>>>> To prepare the Zed SD card, instructions in https://opencpi.github.io/OpenCPI_Installation.pdf Page 23 say: >>>>> " ...OpenCPI source tree, its path is: projects/core/rcc/platforms/xilinx13_4" >>>>> which is not there. Instead I find the desired content at: >>>>> "/opt/opencpi/cdk/zed/sdcard-xilinx13_4" >>>>> >>>>> The specified procedure to copy to SD in a CentOS7 VM fails: >>>>> $ sudo cp -r /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* >>>>> /media/sf_SD_card >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/bin/ntpd': Read-only file >>>>> system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so.10': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so.4': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so.5': Read-only file system Resulting SD card won't boot the Zedboard. >>>>> >>>>> Q1. Is the Installation Guide just out of date regarding the location of the content to copy to the SD card? >>>>> Q2. Any suggestions for the VM symbolic link copy issue? >>>>> Q3. Better to install from source as in "OpenCPI_Installation" rather than from RPMs? >>>>> >>>>> Sincerely, >>>>> Peter B. Miller >>>>> Potomac: (301) 765-9668 >>>>> >>>>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>>>> -------------- next part -------------- An HTML attachment was >>>>> scrubbed... >>>>> URL: >>>>> <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/attac >>>>> h m e nts/20190925/6d8acfb1/attachment.html> >>>>> _______________________________________________ >>>>> discuss mailing list >>>>> discuss@lists.opencpi.org >>>>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>>> _______________________________________________ >>>> discuss mailing list >>>> discuss@lists.opencpi.org >>>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>> _______________________________________________ >>> discuss mailing list >>> discuss@lists.opencpi.org >>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. > > --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.

Jim, 1. I ran " make hdl HdlPlatforms="xsim zed" Projects="core assets assets_ts" successfully. 2. I ran "make deploy Platform=zed:xilinx13_4" fails as: $ sudo make deploy Platform=zed:xilinx13_4 Updating exports for platforms: zed:xilinx13_4 Adding files for sw platform: xilinx13_4 Adding files for hw platform: zed mv: cannot stat ‘/tmp/tmp.4lEAoCj8eV/zed/sdcard-xilinx13_4/opencpi/zed/xilinx13_4/system.xml’: No such file or directory 3. Regarding the SD card, a. I copy the prebuilt files from projects/core/rcc/platforms/xilinx13_3 to the SD card and the zed boots successfully. b. I then download "2017.1-zed-release.tar" from Xilinx and write over the same SD card, and the zed boots successfully. c. I copy the files in projects/core/rcc/platforms/xilinx13_4 to the SD card, and the zed will not boot. d. I download "2013.4-release.tar.xz" from Xilinx and write to the SD card, and the zed will not boot. e. Repeat steps a. and b. and the zed boots successfully. Seems like the Xilinx content is defective. Sincerely, Peter B. Miller Potomac: (301) 765-9668 -----Original Message----- From: James Kulp <jek@parera.com> Sent: Monday, September 30, 2019 5:54 PM To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org Subject: Re: [Discuss OpenCPI] Programming SD card for Zed Hi Peter, The first problem is due to the fact that "make hdl" in the top level of the source tree does this for all projects, including "inactive". And the inactive project is *supposed* to certainly build, but that build step is not exercised when RPMs are built for a release. Our bad... That error in the "inactive" project exercised a rarely used code path in the build engine, which had a bug (when building a pre-synthesized core for a simulator). The workaround is to use the Projects variable to restrict the projects to avoid "inactive", e.g.: make hdl HdlPlatforms="xsim zed" Projects="core assets assets_ts". Note we recommend using the ocpidev command for most project-based actions. But the actual bug fix (which was already in 1.6, and which we *might* fix in a 1.5.1 patch release) is simply: > +++ b/tools/cdk/include/hdl/hdl-core.mk > @@ -106,7 +106,7 @@ $(HdlInstallLibDir): > > # Install the lib-name directory. This is used for non-real cores > # or for real cores when a tool requires source listings (for stubs) > -install_lib_dir: | $(HdlInstallLibDir) > +install_lib_dir: build | $(HdlInstallLibDir) The second problem (making the SD card), was also based on "tested for RPM, but not tested in the source tree". That fix is: > diff --git a/packaging/create-hw-deploy.sh > b/packaging/create-hw-deploy.sh index 26163b5..3d3cc67 100755 > --- a/packaging/create-hw-deploy.sh > +++ b/packaging/create-hw-deploy.sh > @@ -82,6 +82,7 @@ for file in ${file_list[@]}; do > [ -d $file ] && mkdir -p > $opencpi_output_path/$edited_file) > fi > done > +[ -e $opencpi_output_path/$hdl_platform/$hdl_rcc_platform/system.xml > +] && > mv $opencpi_output_path/$hdl_platform/$hdl_rcc_platform/system.xml > $opencpi_output_path (There are other issues with the SD card generation process that have been addressed for 1.6). Finally, I have no idea why the standard binary release for the SD card would not boot since that is a "supported" platform for Xilinx. My only guess would be how the SD card itself was formatted prior to putting the files on it. The files you are looking for are in the projects/core/rcc/platforms/xilinx13_4/release directory. Jim On 9/30/19 3:48 PM, Miller, Peter wrote: > Jim, > Building from source following https://opencpi.github.io/OpenCPI_Installation.pdf. Takes long time and fails as below: > > $ git clone https://github.com/opencpi/opencpi.git > $ cd opencpi/ > $ git tag > $ git checkout v1.5.0 > $./scripts/install-opencpi.sh > $ source ~/opencpi/cdk/opencpi-setup.sh -s > >>> Install Xilinx tools > $./scripts/install-opencpi.sh xilinx13_4 $ make hdl HdlPlatforms="xsim > zed" > ============Building HDL implementation ddc.hdl for target(s): xsim > zynq > : > : > /home/pbmiller/opencpi/cdk/include/hdl/hdl-lib2.mk:48: *** No core found for "ddc_4243_4ch_v5" on target "xsim". Stop. > make[2]: *** [ddc.hdl] Error 2 > make[2]: Leaving directory `/home/pbmiller/opencpi/projects/inactive/components' > make[1]: *** [hdlcomponents] Error 2 > make[1]: Leaving directory `/home/pbmiller/opencpi/projects/inactive' > make: *** [hdl] Error 2 > > $ make deploy Platform=zed:xilinx13_4 > Updating exports for platforms: zed:xilinx13_4 Adding files for sw > platform: xilinx13_4 Adding files for hw platform: zed > mv: cannot stat > ‘/tmp/tmp.3eAACyDUgm/zed/sdcard-xilinx13_4/opencpi/zed/xilinx13_4/syst > em.xml’: No such file or directory > > Also note: Per https://opencpi.github.io/OpenCPI_Installation.pdf section 4.1.2 I tried downloading 2013.4-release.tar.xz and write to SD card without success (zed won't boot). That does work if I try the 2017.1-zed-release.tar version. Could you send me the SD card files (boot.bin devicetree.dtb uImage uramdisk.image.gz) that you are using (don't need opencpi folder)? > > > Sincerely, > Peter B. Miller > Potomac: (301) 765-9668 > > -----Original Message----- > From: James Kulp <jek@parera.com> > Sent: Thursday, September 26, 2019 3:02 PM > To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org > Subject: Re: [Discuss OpenCPI] Programming SD card for Zed > > Hi Peter, > > I have just (re)built the xilinx13_4 from source, make the SD card and successfully executed on it. > This is based on a development branch rather than 1.5, but I don't know of anything that changed here. > > After building the source tree for xilinx13_4 (and the driver), I had to do (in the source tree): > > make deploy Platform=xilinx13_4 > make deploy Platform=zed:xilinx13_4 > > The first line was unexpected and actually *also* builds RPMs as a side effect, and we'll clean it up a bit in 1.6. > The result was an SD card in cdk/zed/zed-deploy/sdcard-xilinx13_4 > And I used: > cp -R -p cdk/zed/zed-deploy/sdcard-xilinx13_4/* /Volumes/BOOT > > (Where /Volumes/Boot was the mount point of the SD card). > > I was doing this since we have just done a xilinx19_1_aarch32 version for zed and I wanted to back-test. > > Jim > > > > > > > On 9/26/19 11:15 AM, Miller, Peter wrote: >> I only copied the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) - no opencpi/* so no sym links. I think one or more of those files is corrupt. The procedure was: >> >> 1. $ sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* >> /media/sf_SD_card 2. Put the SD card in the zedboard and power up 3. >> Open a putty terminal and log in. Success 4. Put the SD card back >> into PC/VM/CentOS 5. $ sudo cp >> /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* >> /media/sf_SD_card 6. Put the SD card in the zedboard and power up 7. >> Open a putty terminal and log in. Fails >> >> I am now installing OpenCPI 1.5 in a fresh CentOS 7.5 VM from source. I will run the scripts and build the boot images. >> >> Sincerely, >> Peter B. Miller >> Potomac: (301) 765-9668 >> >> -----Original Message----- >> From: James Kulp <jek@parera.com> >> Sent: Thursday, September 26, 2019 10:56 AM >> To: Miller, Peter <PeterM@signalscape.com>; discuss@lists.opencpi.org >> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >> >> Can you describe the failure? I think I understand, but we're doing more testing. >> >> The sdcard image directories only have symlinks that should remain symlinks, so in fact using cp -L is masking some other problem. >> >> Jim >> >> >> >> >> >> On 9/26/19 8:09 AM, Miller, Peter wrote: >>> ... that would be: >>> % sudo cp -RLp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >>> >>> Sincerely, >>> Peter B. Miller >>> Potomac: (301) 765-9668 >>> >>> -----Original Message----- >>> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of >>> Miller, Peter >>> Sent: Thursday, September 26, 2019 7:25 AM >>> To: James Kulp <jek@parera.com>; discuss@lists.opencpi.org >>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>> >>> Jim, >>> Still trying to get OpenCPI 1.5 from RPM, and Zedboard up. I find that the embedded OS and boot files (boot.bin devicetree.dtb opencpi uImage uramdisk.image.gz) from /opt/opencpi/cdk/zed/sdcard-xilinx13_3 can be copied to SD card and the zedboard boots PetaLinux v2013.10. But using the files from /opt/opencpi/cdk/zed/sdcard-xilinx13_4 the zedboard will not boot. >>> >>> WORKS: >>> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_3/* /media/sf_SD_card >>> >>> FAILS: >>> % sudo cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/sf_SD_card >>> >>> Also, per Jerry Darko's comment, the instructions in "OpenCPI_Installation.pdf" Section 4.1 should be revised to something like: >>> % sudo -RLp cp /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* /media/xyz >>> >>> Sincerely, >>> Peter B. Miller >>> Potomac: (301) 765-9668 >>> >>> -----Original Message----- >>> From: James Kulp <jek@parera.com> >>> Sent: Wednesday, September 25, 2019 10:46 AM >>> To: Miller, Peter <PeterM@signalscape.com>; >>> discuss@lists.opencpi.org >>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>> >>> I have certainly had problems with symlinks when mounting a "host" file system into a VM. I solve it by always using NFS, even between a VM and its host. >>> I'm not sure that is your issue... >>> >>> Yes, that is the intention of that directory. >>> >>> I'm actually doing something similar later today to test some new FPGA loading code... >>> >>> Jim >>> >>> >>> >>> >>> >>> On 9/25/19 10:39 AM, Miller, Peter wrote: >>>> Do you confirm that copying from /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* is correct? >>>> Media is write-able - this issue with sym links is a VM problem and I wondered if you had a simple workaround. I'll either chase it down or go to a native linux machine to copy it. >>>> >>>> Sincerely, >>>> Peter B. Miller >>>> Potomac: (301) 765-9668 >>>> >>>> -----Original Message----- >>>> From: discuss <discuss-bounces@lists.opencpi.org> On Behalf Of >>>> James Kulp >>>> Sent: Wednesday, September 25, 2019 10:32 AM >>>> To: discuss@lists.opencpi.org >>>> Subject: Re: [Discuss OpenCPI] Programming SD card for Zed >>>> >>>> This is a source-install vs. rpm-install issue, and the docs should be clearer about this distinction. This is in fact a current work item. >>>> >>>> If looks like the /media was mounted read-only? >>>> >>>> Both RPM and source installations should allow you to do this. >>>> >>>> Not sure what the "VM symbolic link issue" is. Other email? >>>> >>>> >>>> >>>> On 9/25/19 10:21 AM, Miller, Peter wrote: >>>>> Installed using the instructions at https://www.opencpi.org/services >>>>> * sudo yum install yum-utils epel-release >>>>> * sudo yum-config-manager --add-repo=http://opencpi.github.io/repo/opencpi.repo >>>>> * sudo yum install 'opencpi*' >>>>> To prepare the Zed SD card, instructions in https://opencpi.github.io/OpenCPI_Installation.pdf Page 23 say: >>>>> " ...OpenCPI source tree, its path is: projects/core/rcc/platforms/xilinx13_4" >>>>> which is not there. Instead I find the desired content at: >>>>> "/opt/opencpi/cdk/zed/sdcard-xilinx13_4" >>>>> >>>>> The specified procedure to copy to SD in a CentOS7 VM fails: >>>>> $ sudo cp -r /opt/opencpi/cdk/zed/sdcard-xilinx13_4/* >>>>> /media/sf_SD_card >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/bin/ntpd': Read-only file >>>>> system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmp.so.10': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/libgmpxx.so.4': >>>>> Read-only file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so': Read-only >>>>> file system >>>>> cp: cannot create symbolic link >>>>> '/media/sf_SD_card/opencpi/xilinx13_4/lib/liblzma.so.5': Read-only file system Resulting SD card won't boot the Zedboard. >>>>> >>>>> Q1. Is the Installation Guide just out of date regarding the location of the content to copy to the SD card? >>>>> Q2. Any suggestions for the VM symbolic link copy issue? >>>>> Q3. Better to install from source as in "OpenCPI_Installation" rather than from RPMs? >>>>> >>>>> Sincerely, >>>>> Peter B. Miller >>>>> Potomac: (301) 765-9668 >>>>> >>>>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>>>> -------------- next part -------------- An HTML attachment was >>>>> scrubbed... >>>>> URL: >>>>> <http://lists.opencpi.org/pipermail/discuss_lists.opencpi.org/atta >>>>> c h m e nts/20190925/6d8acfb1/attachment.html> >>>>> _______________________________________________ >>>>> discuss mailing list >>>>> discuss@lists.opencpi.org >>>>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.or >>>>> g >>>> _______________________________________________ >>>> discuss mailing list >>>> discuss@lists.opencpi.org >>>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >>> _______________________________________________ >>> discuss mailing list >>> discuss@lists.opencpi.org >>> http://lists.opencpi.org/mailman/listinfo/discuss_lists.opencpi.org >>> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. >> --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. > > --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. --------------------------- This email and any files transmitted with it are confidential and intended solely for the use of Signalscape, Inc. and the addressed individual or entity. If you have received this email in error please delete it. Information in this email may be subject to the Privacy Act of 1974 and any unauthorized review, use, disclosure, or distribution is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company.