Hello,
Based on long-standing requests, captured as https://blueprints.launchpad.net/linaro-android-infrastructure/+spec/create-... , support for creation of filesystem images as build artifacts was implemented. Such images can be (after unbzip2'ing) dd'ed directly to a memory card for streamlined testing for example.
To use this feature, just add "BUILD_FS_IMAGE=1" to a builds config on https://android-build.linaro.org . This will create a $TARGET_PRODUCT.img.bz2 file in addition to usual tarballs. As this doubles size of build artifacts, please use it sparingly (it particular, I'd advise against having that as the default, at least not without Fathi's approval).
The default image size is 2Gb (same as linaro-android-media-create), if you want to override that use FS_IMAGE_SIZE=4G or similar.
Last point is mapping of TARGET_PRODUCT to --dev= switch value of linaro-android-media-create. So far this is:
pandaboard => panda snowball => snowball_sd everything else - as is
Let me know if this needs further tweaking. In particular, some boards have more than 1 --dev= value, e.g. vexpress vs vexpress-a9, snowball_emmc vs snowball_sd.
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog