From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 96D54E00B9E; Fri, 29 Jan 2016 04:17:10 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (oliver.graute[at]gmail.com) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.53 listed in list.dnswl.org] Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id F2DF7E00A92 for ; Fri, 29 Jan 2016 04:17:05 -0800 (PST) Received: by mail-wm0-f53.google.com with SMTP id r129so65951039wmr.0 for ; Fri, 29 Jan 2016 04:17:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=1N5TKyQ+9wqrp4dkGU9fOOgKPrVGOUKhhK4AOOlAsWA=; b=k7KhbGDVsDKGZHYMFcZ30UXoyIr/SjBpJlt5raDWc6Tor6tPGG/Yt/sh5/Ho3R4Em1 nYMm8AGHATUFLIlk2FCMjUL1+zs2PPJmgU6hwmJcf/KXeCHdZyJY0M0DjbV9f0zJwWgn TP2O3HovMMFsIedx0w/kvMV25X0nlXNa3H4N/LJHwnoUnvopiNycJnliQhX8sTQRxk5y VS+Rcy/G3RfMedq/56CU05qNSI6G3yK74fa1vwqzRuXYit34R5WVHWSx0ZukfZC7IVJI M9dXDseF0Mh+QKco3y44ZhmGQvtH0Z+L7OnEnC/Y/Lge03h41E9nGLWXgj3nXNm7SiAH AgNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=1N5TKyQ+9wqrp4dkGU9fOOgKPrVGOUKhhK4AOOlAsWA=; b=IlMmVYixp9h6WPL79BGfDRUlLUGeuW/G8EyiRvvRi9aOFBK/n017+Gr3hWC/tJhXxn f/2+vr3yC6UXpgemNk05kwlXRwDmW6XMLX8LG0k3a/f9N2b+wBT1bweaHio0h+9zunG6 R1gzQL7hC3ANlCH8/0SxCR6r6j31WIQIw59GzC3Bbtvxmaf1Qz3X3yYmiTVsn0lQGKqo scm5yQ9WBcl6xz2wBUL5Zu++w4Db56MnZz4sQtFCBCvq7AffdLf/+3dclh1bm1ivgifP ULkfqK1eYCBNhET0rVx/0ENs5kYjokdjLr6quB+GEvw+Alx6baRz4bHu00glI5Qm+YFT v+aQ== X-Gm-Message-State: AG10YOS5VrheRpGb9x7gokcVwpyYkJJ/dbVJoDlZQINU+kwtFbAeKEt6NPXMLyEQW4xUTw== X-Received: by 10.28.224.212 with SMTP id x203mr8789550wmg.29.1454069824418; Fri, 29 Jan 2016 04:17:04 -0800 (PST) Received: from localhost (x55b1e45f.dyn.telefonica.de. [85.177.228.95]) by smtp.gmail.com with ESMTPSA id x189sm7425541wmg.1.2016.01.29.04.17.03 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 29 Jan 2016 04:17:03 -0800 (PST) Date: Fri, 29 Jan 2016 13:16:03 +0100 From: Oliver Graute To: meta-freescale@yoctoproject.org Message-ID: <20160129121603.GA3347@graute-opti> Mail-Followup-To: meta-freescale@yoctoproject.org References: <20160128113740.GA21464@graute-opti> <20160129103629.GB21464@graute-opti> MIME-Version: 1.0 In-Reply-To: <20160129103629.GB21464@graute-opti> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: adjust image partitions for imx6ulevk X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2016 12:17:10 -0000 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 29/01/16, Oliver Graute wrote: > On 28/01/16, Otavio Salvador wrote: > > On Thu, Jan 28, 2016 at 9:37 AM, Oliver Graute wrote: > > > whats is the right way to adjust the flash partitions for my imx6ulevk? > > > > > > I need a bootstream partition, two rootfs partitions with 125 MB each > > > and a data partitions with 730 MB. > > > > > > during some code investigation I found image_types_fsl.bbclass where > > > some partitioning seems to happen. Is this the point to start? > > > > For this kind of use-case the wic is better. > > > wic create imx-test.wks -e fsl-image > > and get the follwing output: > > > Done. > Creating image(s)... > > Couldn't get 'bitbake -e rootfs1' output. > Bitbake failed with error: > Loading cache...done. > Loaded 2378 entries from dependency cache. > ERROR: Nothing PROVIDES 'rootfs1' > > Summary: There was 1 WARNING message shown. > Summary: There was 1 ERROR message shown, returning a non-zero exit code. > > Couldn't get 'bitbake -e rootfs1' output. > Bitbake failed with error: > Loading cache...done. > Loaded 2378 entries from dependency cache. > ERROR: Nothing PROVIDES 'rootfs1' I updated my imx-test.wks file, I replaced rootfs1 and rootfs2 by my fsl-image # short-description: Create SD card image with a boot partition and two rootfs # long-description: # Create an image that can be written onto a SD card using dd for use # with i.MX SoC family # It uses u-boot # # The disk layout used is: # - --------- --------- ------------ ------------ ----------- # | | u-boot | /boot | rootfs 1 | rootfs 2 | data | # - --------- --------- ------------ ------------ ----------- # ^ ^ ^ ^ ^ # | | | | | # 0 1kiB 4MiB 4MiB + 8MiB 4MiB + 8Mib + rootfs 1 + rootfs 2 + data IMAGE_EXTRA_SPACE (default 10MiB) # part u-boot --source rawcopy --sourceparams="file=u-boot-imx6ulevk.img" --ondisk mmcblk --no-table --align 1 part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 4096 --size 8M --extra-space 0 part / --source rootfs --rootfs-dir=fsl-image --ondisk mmcblk --fstype=ext4 --label platform --align 4096 part /rescue --source rootfs --rootfs-dir=fsl-image --ondisk mmcblk --fstype=ext4 --label secondary --align 4096 wic create imx-test.wks -e fsl-image Checking basic build environment... Done. Creating image(s)... Info: The new image(s) can be found here: /var/tmp/wic/build/imx-test-201601291301-mmcblk.direct The following build artifacts were used to create the image(s): ROOTFS_DIR: build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/rootfs ROOTFS_DIR["/rescue"]: build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/rootfs BOOTIMG_DIR: KERNEL_DIR: build-imx6ulevk/tmp/deploy/images/imx6ulevk NATIVE_SYSROOT: build-imx6ulevk/tmp/sysroots/x86_64-linux The image(s) were created using OE kickstart file: then I write the image to my sdcard with: dd if=imx-test-201601291200-mmcblk.direct of=sdb bs=4M && sync something is booting from that sd image. Is this the way to go? some further hints or corrections? how do I define the partition size? best regards, Oliver