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