20160606_jeffrey - silenceuncrio/diary GitHub Wiki

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ wic -h
Usage: 

 Create a customized OpenEmbedded image

 usage: wic [--version] | [--help] | [COMMAND [ARGS]]

 Current 'wic' commands are:
    help              Show help for command or one of the topics (see below)
    create            Create a new OpenEmbedded image
    list              List available canned images and source plugins

 Help topics:
    overview          wic overview - General overview of wic
    plugins           wic plugins - Overview and API
    kickstart         wic kickstart - wic kickstart reference


Options:
  --version   show program's version number and exit
  -h, --help  show this help message and exit

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ wic help create > wic.help.create.txt
jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ cat ./wic.help.create.txt 


NAME
    wic create - Create a new OpenEmbedded image

SYNOPSIS
    wic create <wks file or image name> [-o <DIRNAME> | --outdir <DIRNAME>]
        [-e | --image-name] [-s, --skip-build-check] [-D, --debug]
        [-r, --rootfs-dir] [-b, --bootimg-dir]
        [-k, --kernel-dir] [-n, --native-sysroot] [-f, --build-rootfs]
        [-c, --compress-with]

DESCRIPTION
    This command creates an OpenEmbedded image based on the 'OE
    kickstart commands' found in the <wks file>.

    In order to do this, wic needs to know the locations of the
    various build artifacts required to build the image.

    Users can explicitly specify the build artifact locations using
    the -r, -b, -k, and -n options.  See below for details on where
    the corresponding artifacts are typically found in a normal
    OpenEmbedded build.

    Alternatively, users can use the -e option to have 'wic' determine
    those locations for a given image.  If the -e option is used, the
    user needs to have set the appropriate MACHINE variable in
    local.conf, and have sourced the build environment.

    The -e option is used to specify the name of the image to use the
    artifacts from e.g. core-image-sato.

    The -r option is used to specify the path to the /rootfs dir to
    use as the .wks rootfs source.

    The -b option is used to specify the path to the dir containing
    the boot artifacts (e.g. /EFI or /syslinux dirs) to use as the
    .wks bootimg source.

    The -k option is used to specify the path to the dir containing
    the kernel to use in the .wks bootimg.

    The -n option is used to specify the path to the native sysroot
    containing the tools to use to build the image.

    The -f option is used to build rootfs by running "bitbake <image>"

    The -s option is used to skip the build check.  The build check is
    a simple sanity check used to determine whether the user has
    sourced the build environment so that the -e option can operate
    correctly.  If the user has specified the build artifact locations
    explicitly, 'wic' assumes the user knows what he or she is doing
    and skips the build check.

    The -D option is used to display debug information detailing
    exactly what happens behind the scenes when a create request is
    fulfilled (or not, as the case may be).  It enumerates and
    displays the command sequence used, and should be included in any
    bug report describing unexpected results.

    When 'wic -e' is used, the locations for the build artifacts
    values are determined by 'wic -e' from the output of the 'bitbake
    -e' command given an image name e.g. 'core-image-minimal' and a
    given machine set in local.conf.  In that case, the image is
    created as if the following 'bitbake -e' variables were used:

    -r:        IMAGE_ROOTFS
    -k:        STAGING_KERNEL_DIR
    -n:        STAGING_DIR_NATIVE
    -b:        empty (plugin-specific handlers must determine this)

    If 'wic -e' is not used, the user needs to select the appropriate
    value for -b (as well as -r, -k, and -n).

    The -o option can be used to place the image in a directory with a
    different name and location.

    The -c option is used to specify compressor utility to compress
    an image. gzip, bzip2 and xz compressors are supported.

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ wic help list > wic.help.list.txt
jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ cat wic.help.list.txt 


NAME
    wic list - List available OpenEmbedded images and source plugins

SYNOPSIS
    wic list images
    wic list <image> help
    wic list source-plugins

DESCRIPTION
    This command enumerates the set of available canned images as well
    as help for those images.  It also can be used to list available
    source plugins.

    The first form enumerates all the available 'canned' images.
    These are actually just the set of .wks files that have been moved
    into the /scripts/lib/wic/canned-wks directory).

    The second form lists the detailed help information for a specific
    'canned' image.

    The third form enumerates all the available --sources (source
    plugins).  The contents of a given partition are driven by code
    defined in 'source plugins'.  Users specify a specific plugin via
    the --source parameter of the partition .wks command.  Normally
    this is the 'rootfs' plugin but can be any of the more specialized
    sources listed by the 'list source-plugins' command.  Users can
    also add their own source plugins - see 'wic help plugins' for
    details.

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ wic list images
  directdisk                    		Create a 'pcbios' direct disk image
  mkgummidisk                   		Create an EFI disk image
  mkhybridiso                   		Create a hybrid ISO image
  sdimage-bootpart              		Create SD card image with a boot partition
  directdisk-gpt                		Create a 'pcbios' direct disk image
  qemux86-directdisk            		Create a qemu machine 'pcbios' direct disk image
  directdisk-multi-rootfs       		Create multi rootfs image using rootfs plugin
  mkefidisk                     		Create an EFI disk image

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ wic list sdimage-bootpart help

Creates a partitioned SD card image. Boot files
are located in the first vfat partition.

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/sources/poky/scripts/lib/wic/canned-wks$ ls -al
total 40
drwxrwxr-x 2 jeffrey jeffrey 4096  6月  6 13:25 .
drwxrwxr-x 9 jeffrey jeffrey 4096  6月  6 11:08 ..
-rw-rw-r-- 1 jeffrey jeffrey  457  5月 19 15:07 directdisk-gpt.wks
-rw-rw-r-- 1 jeffrey jeffrey 1171  5月 19 15:07 directdisk-multi-rootfs.wks
-rw-rw-r-- 1 jeffrey jeffrey  433  5月 19 15:07 directdisk.wks
-rw-rw-r-- 1 jeffrey jeffrey  548  5月 19 15:07 mkefidisk.wks
-rw-rw-r-- 1 jeffrey jeffrey  549  5月 19 15:07 mkgummidisk.wks
-rw-rw-r-- 1 jeffrey jeffrey  360  5月 19 15:07 mkhybridiso.wks
-rw-rw-r-- 1 jeffrey jeffrey  535  5月 19 15:07 qemux86-directdisk.wks
-rw-rw-r-- 1 jeffrey jeffrey  362  5月 19 15:07 sdimage-bootpart.wks

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/sources/poky/scripts/lib/wic/canned-wks$ cat sdimage-bootpart.wks 
# short-description: Create SD card image with a boot partition
# long-description: Creates a partitioned SD card image. Boot files
# are located in the first vfat partition.

part /boot --source bootimg-partition --ondisk mmcblk --fstype=vfat --label boot --active --align 4 --size 16
part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/build_small$ wic create sdimage-bootpart -e core-image-minimal
Checking basic build environment...
Done.

Creating image(s)...

Error: No boot files defined, IMAGE_BOOT_FILES unset

jeffrey@jeffrey-virtual-machine:~/fsl-release-bsp/sources$ find . -name "*.conf" -exec grep -H "IMAGE_BOOT_FILES" {} \;
./poky/meta-yocto-bsp/conf/machine/beaglebone.conf:IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO"
./poky/scripts/lib/bsp/substrate/target/arch/arm/conf/machine/machine.conf:IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO"
./poky/meta/conf/documentation.conf:IMAGE_BOOT_FILES[doc] = "Whitespace separated list of files from ${DEPLOY_DIR_IMAGE} to place in boot partition. Entries will be installed under a same name as the source file. To change the destination file name, pass a desired name after a semicolon (eg. u-boot.img;uboot)."

mtdparts=[memory type designator]:[size]([name of partition]),[size]([name of partition]),-([name of final partition])