All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: adjust image partitions for imx6ulevk
Date: Fri, 29 Jan 2016 11:36:29 +0100	[thread overview]
Message-ID: <20160129103629.GB21464@graute-opti> (raw)
In-Reply-To: <CAP9ODKr1h6ZsWFkX8WVtraW_Ck6tQR08xpg2db8RW4dCT7ZveQ@mail.gmail.com>

On 28/01/16, Otavio Salvador wrote:
> On Thu, Jan 28, 2016 at 9:37 AM, Oliver Graute <oliver.graute@gmail.com> 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.


ok thanks for the hint. I read the wic part in the dev-manual of yocto

 https://www.yoctoproject.org/docs/1.5.2/dev-manual/dev-manual.html

after that I tried to write my own imx-test.wks for wic.

# 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.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=rootfs1 --ondisk mmcblk --fstype=ext4 --label platform --align 4096
part /rescue --source rootfs --rootfs-dir=rootfs2 --ondisk mmcblk --fstype=ext4 --label secondary --align 4096

I also added to my build-imx6ulevk/conf/local.conf

IMAGE_BOOT_FILES = "u-boot.img zImage:kernel"

then I execute:

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'


Where do I need to provide rootfs1 and rootfs2. Can you comment my first try :)

best regards,

Oliver


  reply	other threads:[~2016-01-29 10:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 11:37 adjust image partitions for imx6ulevk Oliver Graute
2016-01-28 13:06 ` Christian Ege
2016-01-29 10:40   ` Oliver Graute
2016-01-28 14:32 ` Otavio Salvador
2016-01-29 10:36   ` Oliver Graute [this message]
2016-01-29 12:16     ` Oliver Graute

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160129103629.GB21464@graute-opti \
    --to=oliver.graute@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.