diff --git a/documentation/sdk-manual/sdk-appendix-obtain.xml b/documentation/sdk-manual/sdk-appendix-obtain.xml
index 78203a093c..c80828e753 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.xml
+++ b/documentation/sdk-manual/sdk-appendix-obtain.xml
@@ -278,13 +278,14 @@
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
+ These files are kept in machine-specific folders in the
Index of Releases
in the "machines" directory.
- The "machines" directory contains tarballs
- (*.tar.bz2) for supported machines.
- The directory also contains flattened root filesystem
+ The machine-specific folders of the "machines" directory
+ contain tarballs (*.tar.bz2) for supported
+ machines.
+ These directories also contain flattened root filesystem
image files (*.ext4), which you can use
with QEMU directly.
@@ -298,14 +299,15 @@
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.
+ lsb, lsb-dev, lsb-sdk, minimal, minimal-dev, minimal-initramfs,
+ sato, sato-dev, sato-sdk, sato-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,
- and several versions for qemu*.
+ beaglebone-yocto, beaglebone-yocto-lsb, edgerouter, edgerouter-lsb,
+ genericx86, genericx86-64, genericx86-64-lsb, genericx86-lsb,
+ mpc8315e-rdb, mpc8315e-rdb-lsb, and qemu*.
date_time is a date and time stamp.
@@ -317,26 +319,28 @@
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:
+ For example, if you plan on using a BeagleBone device
+ as your target hardware and your image is a
+ core-image-sato-sdk
+ image, you can download the following file:
- core-image-minimal-beaglebone-yocto.tar.bz2
+ core-image-sato-sdk-beaglebone-yocto.tar.bz2
Initialize the Cross-Development Environment:
- You must source
- the cross-development environment setup script to establish
- necessary environment variables.
+ 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 BeagleBone Board
- previously shown:
+ Following is an example based on the toolchain installed
+ in the
+ "Locating Pre-Built SDK Installers"
+ section:
$ source ~/poky_sdk/environment-setup-core2-64-poky-linux
@@ -353,10 +357,10 @@
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
+ $ runqemu-extract-sdk ~/Downloads/core-image-sato-sdk-beaglebone-yocto.tar.bz2 ~/beaglebone-sato
You could now point to the target sysroot at
- core2-64-sato.
+ beablebone-sato.