Re: [meta-xilinx] How to boot the ZynqMP?

2017-08-30 Thread Mike Looijmans

On 30-08-17 22:20, Brian Hutchinson wrote:
I too have been wrestling with generating the required images to boot the 
ZCU102 from SD Card using the Yocto + meta-xilinx + meta-xilinx-tools method.


I'm totally striking out.  And I'm working with a Xilinx FAE and striking 
out!  No problem at all doing this kind of thing for ZCU107 or Zedboard but 
ZCU102 is different beast for sure.


I have Ubuntu 16.04 box, I've tried yocto 2.2.1 (morty) and 2.3 (pyro) and I 
get the same result ... my builds die with:



...

| DEBUG: Executing shell function do_deploy
| install: cannot stat 
'/home/hutch/yocto_2.2.1-morty_zcu102/layers/poky/build/tmp/work/zcu102_zynqmp-poky-linux/pmu-firmware/2017.1+gitAUTOINC+122565ec40-r0/build/pmu-firmware/Release/pmu-firmware.elf': 
No such file or directory



Most likely the problem is that the "Release" directory was not created yet. I 
have seen this race condition several times in makefiles.

As a workaround, add a do_compile_prepend with "mkdir Release" or so.

However, this seems to happen in the "do_install" phase, so that's probably 
not the case here.


Another issue can be that actually the "compile" failed. Most of Xilinx' tools 
don't return error codes, so bitbake thinks everything went fine but it didn't 
actually produce outputs. And since do_compile was okay, it won't run again 
and install keeps failing.


Add a do_compile_append() that contains something like:
test -e Release/pmu-firmware.elf
and that would cause do_compile to fail if there's no output.


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


Re: [meta-xilinx] How to boot the ZynqMP?

2017-08-30 Thread Brian Hutchinson
I too have been wrestling with generating the required images to boot the
ZCU102 from SD Card using the Yocto + meta-xilinx + meta-xilinx-tools
method.

I'm totally striking out.  And I'm working with a Xilinx FAE and striking
out!  No problem at all doing this kind of thing for ZCU107 or Zedboard but
ZCU102 is different beast for sure.

I have Ubuntu 16.04 box, I've tried yocto 2.2.1 (morty) and 2.3 (pyro) and
I get the same result ... my builds die with:

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-16.04"
TARGET_SYS= "aarch64-poky-linux"
MACHINE   = "zcu102-zynqmp"
DISTRO= "poky"
DISTRO_VERSION= "2.2.1"
TUNE_FEATURES = "aarch64"
TARGET_FPU= ""
meta
meta-poky
meta-yocto-bsp=
"heads/morty-16.0.1:6a1f33cc40bfac33cf030fe41e1a8efd1e5fad6f"
meta-perl
meta-systemd
meta-gpe
meta-python
meta-efl
meta-ruby
meta-filesystems
meta-gnome
meta-multimedia
meta-networking
meta-webserver
meta-xfce
meta-initramfs
meta-oe   = "morty-16.0.1:fe5c83312de11e80b85680ef237f8acb04b4b26e"
meta-xilinx   = "rel-v2017.1:ea7a5915702079634581c100abb7f3c9643b506e"
meta-xilinx-tools = "rel-v2017.1:26e34432e9a3ce89d97675a1de08581d559ed3d5"

Initialising tasks: 100%
||
Time: 0:00:05
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: pmu-firmware-2017.1+gitAUTOINC+122565ec40-r0 do_deploy: Function
failed: do_deploy (log file is located at
/home/hutch/yocto_2.2.1-morty_zcu102/layers/poky/build/tmp/work/zcu102_zynqmp-poky-linux/pmu-firmware/2017.1+gitAUTOINC+122565ec40-r0/temp/log.do_deploy.8000)
ERROR: Logfile of failure stored in:
/home/hutch/yocto_2.2.1-morty_zcu102/layers/poky/build/tmp/work/zcu102_zynqmp-poky-linux/pmu-firmware/2017.1+gitAUTOINC+122565ec40-r0/temp/log.do_deploy.8000
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing shell function do_deploy
| install: cannot stat
'/home/hutch/yocto_2.2.1-morty_zcu102/layers/poky/build/tmp/work/zcu102_zynqmp-poky-linux/pmu-firmware/2017.1+gitAUTOINC+122565ec40-r0/build/pmu-firmware/Release/pmu-firmware.elf':
No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_deploy (log file is located at
/home/hutch/yocto_2.2.1-morty_zcu102/layers/poky/build/tmp/work/zcu102_zynqmp-poky-linux/pmu-firmware/2017.1+gitAUTOINC+122565ec40-r0/temp/log.do_deploy.8000)
ERROR: Task
(/home/hutch/yocto_2.2.1-morty_zcu102/layers/meta-xilinx-tools/recipes-bsp/pmu/pmu-firmware_git.bb:do_deploy)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 2149 tasks of which 9 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/home/hutch/yocto_2.2.1-morty_zcu102/layers/meta-xilinx-tools/recipes-bsp/pmu/pmu-firmware_git.bb:
do_deploy
Summary: There was 1 ERROR message shown, returning a non-zero exit code


In my local.conf I've added:

MACHINE ?= "zcu102-zynqmp"

HDF_BASE = "file://"
#HDF_PATH =
"/home/hutch/yocto_pyro_zcu102/layers/poky/build/tmp/deploy/images/zcu102-zynqmp/Xilinx-zcu102-zynqmp.hdf"
#HDF_PATH = "/home/hutch/Downloads/Xilinx/Xilinx-zcu102-zynqmp.hdf"
HDF_PATH = "/home/hutch/Downloads/from_emil/config_mpsoc_wrapper.hdf"

XILINX_SDK_TOOLCHAIN = "/home/hutch/Xilinx/SDK/2017.1/"
XILINX_VER_MAIN = "2017.1"

# add Boot.bin dependency
IMAGE_CLASSES += " xilinx-bootbin"

... and I even added a bunch of BIF_ settings before I learned those were
for 2016.4

Pretty much no matter what my FAE tells me to try (it apparently works for
him) I always get this error about "pmu-firmware.elf': No such file or
directory" ... and I've tried all kind of things.

I'd really like to understand what I'm doing wrong here and find a path
that lets me generate the required images the same way I build images for
every other board I support using the yocto flow.

Regards,

Brian

On Tue, Aug 22, 2017 at 2:25 PM, Manjukumar Harthikote Matha <
manju...@xilinx.com> wrote:

> Hi Giordon,
>
> meta-xilinx-tools with xsct in your path would enable the same way ,
> instead of using the Vivado GUI to generate fsbl/pmu/boot.bin
>
>
>
> http://www.wiki.xilinx.com/Using+meta-xilinx-tools+layer
>
>
>
> Thanks,
>
> Manju
>
>
>
> *From:* meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-bounces@
> yoctoproject.org] *On Behalf Of *Giordon Stark
> *Sent:* Tuesday, August 22, 2017 7:46 AM
> *To:* Mike Looijmans ; Jean-Francois Dagenais <
> jeff.dagen...@gmail.com>
> *Cc:* meta-xilinx@yoctoproject.org
> *Subject:* Re: [meta-xilinx] How to boot the ZynqMP?
>
>
>
> Hi,
>
>
>
> I'll share my experiences as it has been somewhat painful -- but I did
> manage to have success booting from an SD card directly for MPSOC. I'm
> working on QSPI 

[meta-xilinx] [meta-xilinx-tools]Nothing PROVIDES 'python3-pyyaml-native'.

2017-08-30 Thread Brett R. Nicholas
Hi there,

I'm trying to build a (once working) Yocto distribution for the Zedboard. When 
I went back to the project, and attempted to build core-image-minimal I get 
this error:

brett: build $ bitbake core-image-minimal
Loading cache: 100% 
||
 Time: 0:00:00
Loaded 2616 entries from dependency cache.
Parsing recipes: 100% 
|##|
 Time: 0:00:00
Parsing of 1923 .bb files complete (1918 cached, 5 parsed). 2621 targets, 153 
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing PROVIDES 'python3-pyyaml-native'. Close matches:
 python-pyyaml-native
 python3-py-native
 python-py-native
ERROR: Required build target 'core-image-minimal' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 
'virtual/bootloader', 'virtual/dtb', 'python3-pyyaml-native']

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


I've seen this post here 
(https://lists.yoctoproject.org/pipermail/meta-xilinx/2017-April/002717.html). 
Can I still apply this patch if I am not using the meta-petalinux layer? Please 
let me know how I can patch it.

Thanks,

Brett

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