On 2016-10-02 06:52, Gary Thomas wrote:
On 2016-10-01 15:58, Karim ATIKI wrote:
hi,
I'm building a custom core-image-x11 for my raspberrypi3 board, with poky
krogoth.
In the very last steps:
ERROR: core-image-x11-1.0-r0 do_image_rpi_sdimg: Function failed:
do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)
ERROR: Logfile of failure stored in:
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_rpi_sdimg
| Creating filesystem with Boot partition 40960 KiB and RootFS 430080 KiB
| dd: failed to open
'/core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission
denied
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_rpi_sdimg (log file is located at
/home/kai/yocto/build-rpi3/tmp/work/raspberrypi3-poky-linux-gnueabi/core-image-x11/1.0-r0/temp/log.do_image_rpi_sdimg.16110)
ERROR: Task 16
(/home/kai/yocto/poky-krogoth/meta/recipes-graphics/images/core-image-x11.bb,
do_image_rpi_sdimg) failed
with exit code '1'
NOTE: Tasks Summary: Attempted 4771 tasks of which 4770 didn't need to be rerun
and 1 failed.
No currently running tasks (4367 of 4773)
It looks like it tries to create the image in the path:
/core-image-x11-raspberrypi3-20161001194728.rootfs.rpi-sdimg': Permission
denied
I looked into the bbclass, and at first glance I'd say that the respective path
is "${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.rpi-sdimg"
So ${IMGDEPLOYDIR} seems to be empty.
I haven't found any reference to IMGDEPLOYDIR elsewhere.
Make sure you have the latest [master] revisions. This should have been fixed
by:
commit 4817e2c087097c02755d6309304878e42cf61d3c
Author: Andreas Müller <schnitzelt...@googlemail.com>
Date: Tue Sep 13 02:19:06 2016 +0200
sdcard_image-rpi.bbclass: avoid corrupted images with latest oe-core
That said, you also need a recent checkout of OE-core as the meta-raspberrypi
and OE-core layers need to be in sync. These particular variables were changed
starting with OE core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02
Just use the latest master of both meta-raspberrypi and OE-core
and you should be fine.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
