diff --git a/documentation/sdk-manual/sdk-appendix-obtain.xml b/documentation/sdk-manual/sdk-appendix-obtain.xml
index ae30995304..0bb5dd2497 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.xml
+++ b/documentation/sdk-manual/sdk-appendix-obtain.xml
@@ -81,6 +81,13 @@
$ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
+ During execution of the script, you choose the root location
+ for the toolchain.
+ See the
+ "Installed Standard SDK Directory Structure"
+ section and the
+ "Installed Extensible SDK Directory Structure"
+ section for more information.
@@ -175,8 +182,15 @@
Following is an example:
$ cd ~/poky/build/tmp/deploy/sdk
- ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
+ $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
+ During execution of the script, you choose the root location
+ for the toolchain.
+ See the
+ "Installed Standard SDK Directory Structure"
+ section and the
+ "Installed Extensible SDK Directory Structure"
+ section for more information.
@@ -189,55 +203,106 @@
After installing the toolchain, for some use cases you
might need to separately extract a root filesystem:
- You want to boot the image using NFS.
+
+ You want to boot the image using NFS.
- You want to use the root filesystem as the
+
+ You want to use the root filesystem as the
target sysroot.
For example, the Eclipse IDE environment with the Eclipse
Yocto Plug-in installed allows you to use QEMU to boot
- under NFS.
- You want to develop your target application
+ under NFS.
+
+
+ You want to develop your target application
using the root filesystem as the target sysroot.
- To extract the root filesystem, first source
- the cross-development environment setup script to establish
- necessary environment variables.
- If you built the toolchain in the Build Directory, you will find
- the toolchain environment script in the
- tmp directory.
- If you installed the toolchain by hand, the environment setup
- script is located in /opt/poky/&DISTRO;.
-
+ Follow these steps to extract the root filesystem:
+
+
+ Locate and Download the Tarball for the Pre-Built
+ Root Filesystem Image File:
+ You need to find and download the root filesystem image
+ file that is appropriate for your target system.
+ These files are kept in the
+ Index of Releases
+ in the "machines" directory.
-
- After sourcing the environment script, use the
- runqemu-extract-sdk command and provide the
- filesystem image.
-
+ The "machines" directory contains tarballs
+ (*.tar.bz2) for supported machines.
+ The directory also contains flattened root filesystem
+ image files (*.ext4), which you can use
+ with QEMU directly.
-
- Following is an example.
- The second command sets up the environment.
- In this case, the setup script is located in the
- /opt/poky/&DISTRO; directory.
- The third command extracts the root filesystem from a previously
- built filesystem that is located in the
- ~/Downloads directory.
- Furthermore, this command extracts the root filesystem into the
- qemux86-sato directory:
-
- $ cd ~
- $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
- $ runqemu-extract-sdk \
- ~/Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \
- $HOME/qemux86-sato
-
- You could now point to the target sysroot at
- qemux86-sato.
+ The pre-built root filesystem image files
+ follow these naming conventions:
+
+ core-image-profile-arch.tar.bz2
+
+ Where:
+ profile is the filesystem image's profile:
+ lsb, lsb-dev, lsb-sdk, lsb-qt3, minimal, minimal-dev, sato,
+ sato-dev, sato-sdk, minimal-initramfs, or sdk-ptest. For
+ information on these types of image profiles, see the
+ "Images" chapter in the Yocto Project Reference Manual.
+
+ arch is a string representing the target architecture:
+ beaglebone, edgerouter, genericx86, genericx86-64, mpc8315e-rdb,
+ qemuarm, qemuarm64, qemumips, qemumips64, qemuppc, qemux86, or
+ qemux86-64.
+
+
+ The root filesystems provided by the Yocto Project are based
+ off of the core-image-sato and
+ core-image-minimal images.
+
+
+ For example, if your target hardware system is a
+ BeagleBone board and your image is a
+ core-image-minimal image, you need
+ to download the following root filesystem image file:
+
+ core-image-minimal-beaglebone.tar.bz2
+
+
+
+ Initialize the Cross-Development Environment:
+ You must source
+ the cross-development environment setup script to establish
+ necessary environment variables.
+
+ This script is located in the top-level directory in
+ which you installed the toolchain (e.g.
+ poky_sdk).
+
+ Following is an example for the Core2 64-bit
+ architecture:
+
+ $ source ~/poky_sdk/environment-setup-core2-64-poky-linux
+
+
+
+ Extract the Root Filesystem:
+ Use the runqemu-extract-sdk command
+ and provide the root filesystem image.
+
+ Following is an example command that extracts the root
+ filesystem from a previously built root filesystem image that
+ was downloaded from the
+ Index of Releases.
+ This command extracts the root filesystem into the
+ core2-64-sato directory:
+
+ $ runqemu-extract-sdk ~/Downloads/core-image-sato-core2-64.tar.bz2 ~/core2-64-sato
+
+ You could now point to the target sysroot at
+ core2-64-sato.
+
+