Re: [meta-xilinx] ZynqMP causes tons of recipes to fail to parse because of PMU build
On 17-08-17 23:57, Nathan Rossi wrote:
On 17 August 2017 at 23:12, Mike Looijmans wrote:
I'm attempting to revive my build for the MPSOC machines. If one does
something like this:
MACHINE=zcu102-zynqmp bitbake my-image
I get parsing errors like:
ERROR: ExpansionError during parsing /home/mike/projects/@@@.bb
Traceback (most recent call last):
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
line 412, in DataSmart.expandWithRefs(s='0.${SRCPV}', varname='PV'):
try:
>s = __expand_var_regexp__.sub(varparse.var_sub, s)
try:
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
line 111, in VariableParse.var_sub(match=<_sre.SRE_Match object; span=(2,
10), match='${SRCPV}'>):
else:
>var = self.d.getVarFlag(key, "_content")
self.references.add(key)
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
line 794, in DataSmart.getVarFlag(var='SRCPV', flag='_content', expand=True,
noweakdefault=False, parsing=False):
cachename = var + "[" + flag + "]"
>value = self.expand(value, cachename)
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
line 436, in DataSmart.expand(s='${@bb.fetch2.get_srcrev(d)}',
varname='SRCPV'):
def expand(self, s, varname = None):
>return self.expandWithRefs(s, varname).value
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
line 426, in DataSmart.expandWithRefs(s='${@bb.fetch2.get_srcrev(d)}',
varname='SRCPV'):
except Exception as exc:
>raise ExpansionError(varname, s, exc) from exc
bb.data_smart.ExpansionError: Failure expanding variable SRCPV, expression
was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
Fetcher failure: The SRCREV_FORMAT variable must be set when multiple SCMs
are used.
Looks like a very odd failure, unfortunately I cannot reproduce with
pyro or master on recipes that use version control or dynamic SRCREV
features. Could you provide some build config info and if possible the
recipe that is generating the error?
It's a parsing error, so it fails on one recipe, and when I remove the recipe,
some other fails, and so on. After a dozen or so, I gave up.
There's nothing special about the config. Mainly recipes that inherit gitpkgv
seem affected. I cannot say what triggers it exactly.
The cause is this line in zcu102-zynqmp.conf:
include conf/machine/include/zynqmp-pmu-config.inc
This breaks almost all recipes that use some kind of version control. Adding
this line to any machine's config yields the same error. Removing it results
in:
ERROR: Nothing PROVIDES 'zynqmp-pmu-pmu-firmware'
If you don't need the pmu-firmware built via the meta-xilinx layer
(e.g. you source it externally or via meta-xilinx-tools), you can
remove the include and that dependency.
Actually, at the moment I don't know how to boot the ZynqMP any more, and the
Xilinx website isn't helpful either. I can build all the components (FSBL or
SPL, u-boot, ATF, PMU, kernel, ...) but I have no idea as to how to fit them
together on a card on in the QSPI flash. The README in meta-xilinx doesn't
even mention the ZynqMP.
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
[meta-xilinx] Can't get u-boot to run
When I try to create a BOOT.bin the way I have in the past, u-boot won't
run.
That is, the FPGA loads because the blue LED comes on, but the serial port
never outputs anything.
My googling attempts mostly confuse me, but some of them tell me to do the
following:
My .bif file looks like:
the_ROM_image:
{
[bootloader]/d/.../viv_uzed3a.sdk/Zynq_FSBL/Debug/Zynq_FSBL.elf
/d/.../viv_uzed3b/viv_uzed3a.runs/impl_2/top.bit
/home/rw/poky/build/tmp/deploy/images/microzed-zynq7/u-boot.elf
}
bootgen -image uzed_103.bif -o boot.bin
and copy boot.bin to the micro-SD card.
The two files in /d come from a windows partition, and those files along
with an
older copy of u-boot.elf run properly.
Is there something about the way that u-boot was built that isn't compatible
with this way of loading it? Do I need to re-build u-boot? Perhaps removing
the stuff about SPL? How? My attempt ended in an error, something about ssl
IIRC.
Or is there some meta-something that will do the work for me?
Something to put near the existing
IMAGE_FSTYPES_append = " wic"
WKS_FILES = "sdimage-bootpart.wks"
which does give me a good image?
Or is there a different way to load the FPGA so that I can just use the
above wic
without modification?
Info:
> bitbake core-image-minimal
Loading cache: 100% || Time:
0:00:00
Loaded 1353 entries from dependency cache.
Parsing recipes: 100% |##| Time:
0:00:00
Parsing of 879 .bb files complete (878 cached, 1 parsed). 1354 targets, 81
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION= "1.34.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE = "microzed-zynq7"
DISTRO= "poky"
DISTRO_VERSION= "2.3"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU= "hard"
meta
meta-poky
meta-yocto-bsp= "master:9ea5a31776440abd6468f003c5e1905f079446d3"
meta-xilinx-new = "HEAD:20ae90016aaacec9569c1cb34a60552231fe733d"
meta-webserver= "pyro:5e82995148a2844c6f483ae5ddd1438d87ea9fb7"
meta-mylayer = "master:9ea5a31776440abd6468f003c5e1905f079446d3"
--
Rich Wilson
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] [ZynqMP] Booting from QSPI instead of SD Card
Thanks, Sandeep From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-boun...@yoctoproject.org] On Behalf Of Giordon Stark Sent: Thursday, August 17, 2017 6:10 PM To: meta-xilinx@yoctoproject.org Subject: [meta-xilinx] [ZynqMP] Booting from QSPI instead of SD Card Hi, Many thanks to the folks here for helping me get the SD Card booting working (especially with the data duplicator command to burn the SD card correctly with partitions). What's the general procedure for having the board boot from the QSPI instead of the SD card? Do you need specific software on the computer and transfer over JTAG? Refer UG1209 https://www.xilinx.com/support/documentation/sw_manuals/xilinx2017_1/ug1209-embedded-design-tutorial.pdf It would be great if someone could point me to a set of instructions. Giordon -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
[meta-xilinx] [ZynqMP] Booting from QSPI instead of SD Card
Hi, Many thanks to the folks here for helping me get the SD Card booting working (especially with the data duplicator command to burn the SD card correctly with partitions). What's the general procedure for having the board boot from the QSPI instead of the SD card? Do you need specific software on the computer and transfer over JTAG? It would be great if someone could point me to a set of instructions. Giordon -- ___ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
Re: [meta-xilinx] ZynqMP causes tons of recipes to fail to parse because of PMU build
On 17 August 2017 at 23:12, Mike Looijmans wrote:
> I'm attempting to revive my build for the MPSOC machines. If one does
> something like this:
>
> MACHINE=zcu102-zynqmp bitbake my-image
>
> I get parsing errors like:
>
> ERROR: ExpansionError during parsing /home/mike/projects/@@@.bb
> Traceback (most recent call last):
> File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
> line 412, in DataSmart.expandWithRefs(s='0.${SRCPV}', varname='PV'):
> try:
> >s = __expand_var_regexp__.sub(varparse.var_sub, s)
> try:
> File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
> line 111, in VariableParse.var_sub(match=<_sre.SRE_Match object; span=(2,
> 10), match='${SRCPV}'>):
> else:
> >var = self.d.getVarFlag(key, "_content")
> self.references.add(key)
> File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
> line 794, in DataSmart.getVarFlag(var='SRCPV', flag='_content', expand=True,
> noweakdefault=False, parsing=False):
> cachename = var + "[" + flag + "]"
> >value = self.expand(value, cachename)
>
> File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
> line 436, in DataSmart.expand(s='${@bb.fetch2.get_srcrev(d)}',
> varname='SRCPV'):
> def expand(self, s, varname = None):
> >return self.expandWithRefs(s, varname).value
>
> File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py",
> line 426, in DataSmart.expandWithRefs(s='${@bb.fetch2.get_srcrev(d)}',
> varname='SRCPV'):
> except Exception as exc:
> >raise ExpansionError(varname, s, exc) from exc
>
> bb.data_smart.ExpansionError: Failure expanding variable SRCPV, expression
> was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
> Fetcher failure: The SRCREV_FORMAT variable must be set when multiple SCMs
> are used.
Looks like a very odd failure, unfortunately I cannot reproduce with
pyro or master on recipes that use version control or dynamic SRCREV
features. Could you provide some build config info and if possible the
recipe that is generating the error?
>
>
>
> The cause is this line in zcu102-zynqmp.conf:
>
> include conf/machine/include/zynqmp-pmu-config.inc
>
> This breaks almost all recipes that use some kind of version control. Adding
> this line to any machine's config yields the same error. Removing it results
> in:
> ERROR: Nothing PROVIDES 'zynqmp-pmu-pmu-firmware'
If you don't need the pmu-firmware built via the meta-xilinx layer
(e.g. you source it externally or via meta-xilinx-tools), you can
remove the include and that dependency.
Regards,
Nathan
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
[meta-xilinx] ZynqMP causes tons of recipes to fail to parse because of PMU build
I'm attempting to revive my build for the MPSOC machines. If one does
something like this:
MACHINE=zcu102-zynqmp bitbake my-image
I get parsing errors like:
ERROR: ExpansionError during parsing /home/mike/projects/@@@.bb
Traceback (most recent call last):
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py", line
412, in DataSmart.expandWithRefs(s='0.${SRCPV}', varname='PV'):
try:
>s = __expand_var_regexp__.sub(varparse.var_sub, s)
try:
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py", line
111, in VariableParse.var_sub(match=<_sre.SRE_Match object; span=(2, 10),
match='${SRCPV}'>):
else:
>var = self.d.getVarFlag(key, "_content")
self.references.add(key)
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py", line
794, in DataSmart.getVarFlag(var='SRCPV', flag='_content', expand=True,
noweakdefault=False, parsing=False):
cachename = var + "[" + flag + "]"
>value = self.expand(value, cachename)
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py", line
436, in DataSmart.expand(s='${@bb.fetch2.get_srcrev(d)}', varname='SRCPV'):
def expand(self, s, varname = None):
>return self.expandWithRefs(s, varname).value
File "/home/mike/projects/zynq-platform/bitbake/lib/bb/data_smart.py", line
426, in DataSmart.expandWithRefs(s='${@bb.fetch2.get_srcrev(d)}',
varname='SRCPV'):
except Exception as exc:
>raise ExpansionError(varname, s, exc) from exc
bb.data_smart.ExpansionError: Failure expanding variable SRCPV, expression was
${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher
failure: The SRCREV_FORMAT variable must be set when multiple SCMs are used.
The cause is this line in zcu102-zynqmp.conf:
include conf/machine/include/zynqmp-pmu-config.inc
This breaks almost all recipes that use some kind of version control. Adding
this line to any machine's config yields the same error. Removing it results in:
ERROR: Nothing PROVIDES 'zynqmp-pmu-pmu-firmware'
How does one build zynqmp image these days?
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
