summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml30
1 files changed, 23 insertions, 7 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 25413c97ca..810a689975 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -688,21 +688,37 @@
688 </para> 688 </para>
689 </note> 689 </note>
690 </para></listitem> 690 </para></listitem>
691 <listitem><para><emphasis>Build a Minimal Image for MinnowBoard MAX:</emphasis> 691 <listitem><para><emphasis>Build an Image for MinnowBoard MAX:</emphasis>
692 Use the following command to build the minimal image for 692 The type of image you build depends on your goals.
693 For example, the previous build created a
694 <filename>core-image-sato</filename> image, which is an
695 image with Sato support.
696 It is possible to build many image types for the
693 MinnowBoard MAX. 697 MinnowBoard MAX.
694 Because configuration changes are minimal to set up for 698 Some possibilities are <filename>core-image-base</filename>,
695 this second build, the OpenEmbedded build system can 699 which is a console-only image.
700 Another choice could be a
701 <filename>core-image-full-cmdline</filename>, which is
702 another console-only image but has more full-features
703 Linux system functionality installed.
704 For types of images you can build using the Yocto
705 Project, see the
706 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>"
707 chapter in the Yocto Project Reference Manual.</para>
708 <para>Because configuration changes are minimal to set up
709 for this second build, the OpenEmbedded build system can
696 re-use files from previous builds as much as possible. 710 re-use files from previous builds as much as possible.
697 Re-using files means this second build will be much faster 711 Re-using files means this second build will be much faster
698 than an initial build. 712 than an initial build.
713 For this example, the <filename>core-image-base</filename>
714 image is built:
699 <literallayout class='monospaced'> 715 <literallayout class='monospaced'>
700 $ bitbake core-image-minimal 716 $ bitbake core-image-minimal
701 </literallayout> 717 </literallayout>
702 Once the build completes, the resulting basic console image 718 Once the build completes, the resulting console-only image
703 is located in the Build Directory here: 719 is located in the Build Directory here:
704 <literallayout class='monospaced'> 720 <literallayout class='monospaced'>
705 tmp/deploy/images/intel-corei7-64/core-image-minimal-intel-corei7-64.hddimg 721 tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.hddimg
706 </literallayout> 722 </literallayout>
707 </para></listitem> 723 </para></listitem>
708 <listitem><para><emphasis>Write the Image:</emphasis> 724 <listitem><para><emphasis>Write the Image:</emphasis>
@@ -713,7 +729,7 @@
713 <filename>scripts/contrib/mkefidisk.sh</filename>: 729 <filename>scripts/contrib/mkefidisk.sh</filename>:
714 <literallayout class='monospaced'> 730 <literallayout class='monospaced'>
715 $ sudo $HOME/source/poky/scripts/contrib/mkefidisk.sh <replaceable>HOST_DEVICE</replaceable> \ 731 $ sudo $HOME/source/poky/scripts/contrib/mkefidisk.sh <replaceable>HOST_DEVICE</replaceable> \
716 tmp/deploy/images/intel-corei7-64/core-image-minimal-intel-corei7-64.hddimg <replaceable>TARGET_DEVICE</replaceable> 732 tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.hddimg <replaceable>TARGET_DEVICE</replaceable>
717 </literallayout> 733 </literallayout>
718 In the previous command, 734 In the previous command,
719 <replaceable>HOST_DEVICE</replaceable> is the device node 735 <replaceable>HOST_DEVICE</replaceable> is the device node