[meta-freescale] imxq6 sabre sd locks up when starting Qt5_Cinematic experience

[Trevor Woerner]

(old thread... sorry, just catching up)

On 08/02/14 04:00, Gunnar Roth wrote:
> Btw how can i define the size of the rootfs , so to have more space available? Right now i always did a resize of the partition afterwards,
> but somehow i must be able to give the size of the roots including free space. 

There are a couple variables you can play with in your conf/local.conf
to affect the size of the final image.

First off you can set "IMAGE_OVERHEAD_FACTOR" to a number, say 20
(IMAGE_OVERHEAD_FACTOR = "20"). This will ask that an extra 20% size be
added to your final image.

You can also specify a size (in KB) for your image using IMAGE_ROOTFS_SIZE.

In my experience, however, sometimes these variables get ignored.
Sometimes they're ignored because the code that is used to calculate
these sizes (for the specific build you're doing) doesn't take these
variables into account. If the size you specify is too small, the build
will ignore your request and make the output the size it would have
anyway without any input from you. Sometimes different types of output
will ignore the suggestions you make in your configuration file (e.g.
vmdk versus hddimage).

Nominally you could look in poky/meta/classes/image_types.bbclass and
see how things are calculated. You could also make use of "bitbake -e |
grep <some variable>" to see what your build thinks of the various
things calculated in this bbclass file.

But at the end of the day, unless you have a specific need for the extra
space, all you're doing is increasing the time it takes your "dd"
command to write your cfcard.  If you have a 2GB card and are only using
200MB the "dd" will only take one tenth the time it would take to write
out the entire 2GB card... and all you're doing with all that extra time
is writing empty file space!

There are some intelligent tools [1] that can help you write a 2GB card
with a 200MB image and only take the amount of time that it would take
to write a 200MB card, but those tools aren't integrated into the build
system (yet?). But they certainly work/help if you use them manually
after your build completes but before you write your cfcard (if your
image has lots of empty space added to it, otherwise there's no savings).

Best regards,
    Trevor


[1] https://source.tizen.org/documentation/reference/bmaptool