Re: Build problems with MSC Q7, Yocto and Chromium

[Gary Thomas <gary@mlbassoc.com>]

[-- Attachment #1: Type: text/plain, Size: 5452 bytes --]

On 2015-10-29 09:10, Gary MacDonald wrote:
> Thanks, I'm using the MSC provided build of Yocto which is based on Dizzy, my GCC version is 4.8.4.
>
> the log file is as follows:
>
>
> Build Configuration:
> BB_VERSION        = "1.24.0"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-14.04"
> TARGET_SYS        = "arm-poky-linux-gnueabi"
> MACHINE           = "q7imx6_demo"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.7.1"
> TUNE_FEATURES     = "arm armv7a vfp neon callconvention-hard cortexa9"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto
> meta-yocto-bsp    = "dizzy-msc:ff482c2522f7092216a4ac7b335393a5294d97d5"
> meta-msc-ldk-core = "MyMscLdk:ea32771751fe4747d3f4bcaaf3587cb024410337"
> meta              = "master:1c61d459a72806e1277d789f12d696e3bf5d1504"
> meta-fsl-arm.git  = "dizzy:de09415bac404f1edd25f0d84f90b2dc3ce7bb82"
> meta-fsl-demos.git = "dizzy:48cb0bcdd226d2e7eee1fdc222713e1dff93342c"
> meta-oe           = "dizzy:6413cdb66acf43059f94d0076ec9b8ad6a475b35"
> meta-gnome        = "master:77582ef1bedd7c36c6aa708ffd474d613e55ad9d"
> meta-browser      = "master:6ae140b29f0201fe3bb470da8c96c9e142294ebf"
>
> NOTE: Preparing runqueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> NOTE: Running task 5138 of 5140 (ID: 7, /home/ub3/msc-ldk/sources/meta-msc-ldk/meta-msc-ldk-core/recipes-core/images/msc-image-base.bb <http://msc-image-base.bb>, do_rootfs)
> NOTE: recipe msc-image-base-1.0-r0: task do_rootfs: Started
> WARNING: log_check: There is a warn message in the logfile
> WARNING: log_check: Matched keyword: [warn]
> WARNING: log_check: warning: Schema 'org.freedesktop.gstreamer-0.10.default-elements' has path '/desktop/gstreamer/0.10/default-elements/'.  Paths starting with '/apps/',
> '/desktop/' or '/system/' are deprecated.
>
> ERROR: Error: The image creation script '/home/ub3/msc-ldk/build/CE85-demo/tmp/work/q7imx6_demo-poky-linux-gnueabi/msc-image-base/1.0-r0/temp/create_image.sdcard' returned 1:
> 0+0 records in
> 0+0 records out
> 0 bytes (0 B) copied, 1.6863e-05 s, 0.0 kB/s
> Model:  (file)
> Disk /home/ub3/msc-ldk/build/CE85-demo/tmp/deploy/images/q7imx6_demo/msc-image-base-q7imx6_demo-20151027094908.rootfs.sdcard: 726MB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
> Disk Flags:
>
> Number  Start   End     Size    Type     File system  Flags
>   1      4194kB  12.6MB  8389kB  primary               lba
>   2      12.6MB  721MB   709MB   primary
>
> 766+1 records in
> 766+1 records out
> 392400 bytes (392 kB) copied, 0.000782631 s, 501 MB/s
> mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
> mkfs.vfat: unable to create /home/ub3/msc-ldk/build/CE85-demo/tmp/work/q7imx6_demo-poky-linux-gnueabi/msc-image-base/1.0-r0/boot.img
> mkfs.fat 3.0.26 (2014-03-07)
> WARNING: exit code 1 from a shell command.
>
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in: /home/ub3/msc-ldk/build/CE85-demo/tmp/work/q7imx6_demo-poky-linux-gnueabi/msc-image-base/1.0-r0/temp/log.do_rootfs.12583
> NOTE: recipe msc-image-base-1.0-r0: task do_rootfs: Failed
> ERROR: Task 7 (/home/ub3/msc-ldk/sources/meta-msc-ldk/meta-msc-ldk-core/recipes-core/images/msc-image-base.bb <http://msc-image-base.bb>, do_rootfs) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 5139 tasks of which 5138 didn't need to be rerun and 1 failed.

It's not really clear why this is failing (no error message at the point of failure).

Try applying this patch to your meta-fsl-arm tree to see if it helps:
commit 928e817c442b0771f89317289046f51c07460b0f
Author: Gary Thomas <gary@mlbassoc.com>
Date:   Mon Jun 15 08:41:33 2015 -0600

     image_types_fsl: Fix boot.img overwrite error

>
> On Thu, Oct 29, 2015 at 10:53 AM, Otavio Salvador <otavio.salvador@ossystems.com.br <mailto:otavio.salvador@ossystems.com.br>> wrote:
>
>     Hello Gary,
>
>     On Thu, Oct 29, 2015 at 5:55 AM, Gary MacDonald <garymacbo@gmail.com <mailto:garymacbo@gmail.com>> wrote:
>     > I have an MSC Q7 board and I'm trying to build Yocto to include an
>     > accelerated Chromium.
>     >
>     > I seem to be really struggling to get the HW acceleration/GPU to kick in.
>     > I'm trying to get the OSSystems meta-browser layer to work, but for some
>     > reason I'm unable to fathom, the build always fails at do_rootfs when I add
>     > the CORE_IMAGE_EXTRA_INSTALL+="chromium"  into the local.conf file.
>
>     The MSC is not supported by FSL Community BSP so it may include subtle
>     changes which impact this feature, or not. I suggest you to use Fido -
>     or Jethro with GCC 4.9 - for Chromium as it is known to have issues
>     with GCC 5.2 at this moment.
>
>     Apart from that, I suggest you to check the rootfs error to see if it
>     provides any tip where the problem is.
>
>     --
>     Otavio Salvador                             O.S. Systems
>     http://www.ossystems.com.br http://code.ossystems.com.br
>     Mobile: +55 (53) 9981-7854 <tel:%2B55%20%2853%29%209981-7854>            Mobile: +1 (347) 903-9750 <tel:%2B1%20%28347%29%20903-9750>
>
>
>
>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: 0001-image_types_fsl-Fix-boot.img-overwrite-error.patch --]
[-- Type: text/x-patch, Size: 2005 bytes --]

From 928e817c442b0771f89317289046f51c07460b0f Mon Sep 17 00:00:00 2001
From: Gary Thomas <gary@mlbassoc.com>
Date: Mon, 15 Jun 2015 08:41:33 -0600
Subject: [PATCH] image_types_fsl: Fix boot.img overwrite error

Recent updates to the MSDOS tools (OE-core is now at 3.0.28) have made
it an error to overwrite an image using mkfs.vfat:
  mkfs.vfat: file XXXX/tmp/work/nitrogen6x-poky-linux-gnueabi/network-demo-image/1.0-r0/boot.img already exists
  mkfs.fat 3.0.28 (2015-05-16)
  WARNING: exit code 1 from a shell command.

This patch fixes the problem by removing any old/stale images before
trying to create the VFAT file system images.

Change-Id: I74e02fd512b43315b29698f534192632d7780df2
Signed-off-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
---
 classes/image_types_fsl.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/classes/image_types_fsl.bbclass b/classes/image_types_fsl.bbclass
index 1ebcb06..b542549 100644
--- a/classes/image_types_fsl.bbclass
+++ b/classes/image_types_fsl.bbclass
@@ -152,6 +152,7 @@ generate_imx_sdcard () {
 	# Create boot partition image
 	BOOT_BLOCKS=$(LC_ALL=C parted -s ${SDCARD} unit b print \
 	                  | awk '/ 1 / { print substr($4, 1, length($4 -1)) / 1024 }')
+        rm -f ${WORKDIR}/boot.img
 	mkfs.vfat -n "${BOOTDD_VOLUME_ID}" -S 512 -C ${WORKDIR}/boot.img $BOOT_BLOCKS
 	mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${MACHINE}.bin ::/${KERNEL_IMAGETYPE}
 
@@ -255,6 +256,7 @@ generate_mxs_sdcard () {
 		BOOT_BLOCKS=$(LC_ALL=C parted -s ${SDCARD} unit b print \
 	        | awk '/ 2 / { print substr($4, 1, length($4 -1)) / 1024 }')
 
+		rm -f ${WORKDIR}/boot.img
 		mkfs.vfat -n "${BOOTDD_VOLUME_ID}" -S 512 -C ${WORKDIR}/boot.img $BOOT_BLOCKS
 		mcopy -i ${WORKDIR}/boot.img -s ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGETYPE}-${MACHINE}.bin ::/${KERNEL_IMAGETYPE}
 		if test -n "${KERNEL_DEVICETREE}"; then
-- 
1.9.1