Re: [meta-xilinx] ZCU102 boot issue

2019-03-07 Thread Manjukumar Harthikote Matha
Hi Mike,

> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Mike Looijmans
> Sent: Friday, February 01, 2019 12:19 AM
> To: meta-xilinx@yoctoproject.org
> Subject: Re: [meta-xilinx] ZCU102 boot issue
> 
> On 30-01-19 14:13, Jean-Francois Dagenais wrote:
> > Hi guys,
> >
> >> On Jan 28, 2019, at 14:39, Manjukumar Harthikote Matha
> >> mailto:manju...@xilinx.com>> wrote:
> >>
> >> Hi Alex,
> >> You need additional patches on pmu-firmware
> >> See:https://lists.yoctoproject.org/pipermail/meta-xilinx/2019-January
> >> /004198.html
> >
> > Manju, thanks for your patience and diligence in answering this yet another 
> > time.
> >
> > In my experience, when such an issue is raised again and again, it
> > means it will not go away and it costs a lot in loss of time, money
> > and most importantly, spirit ;)
> >
> > I know it's been discussed before too but if I may add my 2 cents: Am
> > I missing something or without manually patching pmu-firmware, the
> > boards in the meta-xilinx-bsp will not function because of the missing
> > config object? (I still use meta-xilinx-tools so I actually don't
> > know.)  Doesn't this mean Xilinx doesn't fully support the open-source
> > workflow? Or is just the word "support" that should be replaced with
> > "participates"? (In which case it is indeed directly responsible for
> > it)
> >
> > I remember problems with the licensing, but there has to be a
> > solution. Even if not elegant, once automated in yocto recipes, it's
> > better than nothing and a broken board after 5 hours of building!
> >
> > And if this is still not possible, to help people find the very
> > un-obvious source of their issues, perhaps PMU firmware could suffix
> > "(no cfg obj)" to its version? Or anything else printed early which
> > will help people find a xilinx wiki page explaining the problem and the 
> > solutions
> available.
> >
> 
> Simplest solution here would be to just integrate that "default config" patch 
> into the
> standard PMU firmware and then all boards will just boot. It won't prevent 
> the FSBL
> changing the config, so that flow isn't affected negatively.
> 

Please do send a patch if you have for pmu-firmware "default config". We will 
take a look at having them integrated.

> If licensing of my patch is an issue, I'm happy to change the license from 
> GPL into
> whatever Xilinx needs it to be to be able to integrate it.

Thanks,
Manju
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


Re: [meta-xilinx] [PATCH] xsct-tarball: use fetcher cache

2019-03-07 Thread Manjukumar Harthikote Matha



> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Jean-Francois Dagenais
> Sent: Thursday, March 07, 2019 8:39 AM
> To: meta-xilinx@yoctoproject.org
> Subject: [meta-xilinx] [PATCH] xsct-tarball: use fetcher cache
> 
> Without it, whenever a build starts on a fresh tmp directory, the file is 
> actually
> downloaded from http://petalinux.xilinx.com each time. Even though it might 
> be in
> the local download dir or in the SOURCE_MIRROR_URL specified mirror. This
> unnecessarily slows down build bootstrap and puts burden on xilinx.com 
> servers.
> 

Thanks JFD for the patch

> Signed-off-by: Jean-Francois Dagenais 
> ---
>  classes/xsct-tarball.bbclass | 9 +
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/classes/xsct-tarball.bbclass b/classes/xsct-tarball.bbclass index
> c5a1b74..bc321a9 100644
> --- a/classes/xsct-tarball.bbclass
> +++ b/classes/xsct-tarball.bbclass
> @@ -1,7 +1,7 @@
>  XSCT_LOADER ?= "${XSCT_STAGING_DIR}/SDK/${XILINX_VER_MAIN}/bin/xsct"
> 
> -XSCT_URL ?= "http://petalinux.xilinx.com/sswreleases/rel-v2018.3/xsct-trim/;
> -XSCT_TARBALL ?= "xsct.tar.xz"
> +XSCT_URL ?= "http://petalinux.xilinx.com/sswreleases/rel-v2018.3/xsct-
> trim/xsct.tar.xz"
> +XSCT_TARBALL ?= "xsct_${XILINX_VER_MAIN}.tar.xz"
>  XSCT_DLDIR ?= "${DL_DIR}/xsct/"
>  XSCT_STAGING_DIR ?= "${STAGING_DIR}-xsct"
> 
> @@ -70,9 +70,10 @@ python xsct_event_extract() {
>  localdata = bb.data.createCopy(d)
>  localdata.setVar('FILESPATH', "")
>  localdata.setVar('DL_DIR', xsctdldir)
> -srcuri = d.expand("${XSCT_URL}${XSCT_TARBALL};md5sum=%s" %
> chksum_tar)
> +srcuri = d.expand("${XSCT_URL};md5sum=%s;downloadfilename=%s"
> +   % (chksum_tar, tarballname))
>  bb.note("Fetching xsct binary tarball from %s" % srcuri)
> -fetcher = bb.fetch2.Fetch([srcuri], localdata, cache=False)
> +fetcher = bb.fetch2.Fetch([srcuri], localdata)
>  fetcher.download()
>  localpath = fetcher.localpath(srcuri)
>  if localpath != tarballpath and os.path.exists(localpath) and not
> os.path.exists(tarballpath):
> --
> 2.11.0
> 
> --
> ___
> meta-xilinx mailing list
> meta-xilinx@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


[meta-xilinx] [PATCH] xsct-tarball: use fetcher cache

2019-03-07 Thread Jean-Francois Dagenais
Without it, whenever a build starts on a fresh tmp directory, the file
is actually downloaded from http://petalinux.xilinx.com each time. Even
though it might be in the local download dir or in the SOURCE_MIRROR_URL
specified mirror. This unnecessarily slows down build bootstrap and puts
burden on xilinx.com servers.

Signed-off-by: Jean-Francois Dagenais 
---
 classes/xsct-tarball.bbclass | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/classes/xsct-tarball.bbclass b/classes/xsct-tarball.bbclass
index c5a1b74..bc321a9 100644
--- a/classes/xsct-tarball.bbclass
+++ b/classes/xsct-tarball.bbclass
@@ -1,7 +1,7 @@
 XSCT_LOADER ?= "${XSCT_STAGING_DIR}/SDK/${XILINX_VER_MAIN}/bin/xsct"
 
-XSCT_URL ?= "http://petalinux.xilinx.com/sswreleases/rel-v2018.3/xsct-trim/;
-XSCT_TARBALL ?= "xsct.tar.xz"
+XSCT_URL ?= 
"http://petalinux.xilinx.com/sswreleases/rel-v2018.3/xsct-trim/xsct.tar.xz;
+XSCT_TARBALL ?= "xsct_${XILINX_VER_MAIN}.tar.xz"
 XSCT_DLDIR ?= "${DL_DIR}/xsct/"
 XSCT_STAGING_DIR ?= "${STAGING_DIR}-xsct"
 
@@ -70,9 +70,10 @@ python xsct_event_extract() {
 localdata = bb.data.createCopy(d)
 localdata.setVar('FILESPATH', "")
 localdata.setVar('DL_DIR', xsctdldir)
-srcuri = d.expand("${XSCT_URL}${XSCT_TARBALL};md5sum=%s" % 
chksum_tar)
+srcuri = d.expand("${XSCT_URL};md5sum=%s;downloadfilename=%s"
+ % (chksum_tar, tarballname))
 bb.note("Fetching xsct binary tarball from %s" % srcuri)
-fetcher = bb.fetch2.Fetch([srcuri], localdata, cache=False)
+fetcher = bb.fetch2.Fetch([srcuri], localdata)
 fetcher.download()
 localpath = fetcher.localpath(srcuri)
 if localpath != tarballpath and os.path.exists(localpath) and not 
os.path.exists(tarballpath):
-- 
2.11.0

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx