summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-07-10 13:35:21 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-08-15 10:28:11 +0100
commit008732dcb63e95f70f9290e70b54d799c48bce2c (patch)
tree60b63fdefa22b6d929b0c60d7d22ffa50a0f67c7 /documentation
parenta3473f32a67ef821ee6370ea86807b5c6752b3c6 (diff)
downloadpoky-008732dcb63e95f70f9290e70b54d799c48bce2c.tar.gz
sdk-manual: Final edits to the extracting root filesystem section
Verified a good example and updated the text to match that example. (From yocto-docs rev: 8655662b1f031463fafcf11fcd22243a75e817f8) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/sdk-manual/sdk-appendix-obtain.xml48
1 files changed, 26 insertions, 22 deletions
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 @@
278 Root Filesystem Image File:</emphasis> 278 Root Filesystem Image File:</emphasis>
279 You need to find and download the root filesystem image 279 You need to find and download the root filesystem image
280 file that is appropriate for your target system. 280 file that is appropriate for your target system.
281 These files are kept in the 281 These files are kept in machine-specific folders in the
282 <ulink url='&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;/machines/'>Index of Releases</ulink> 282 <ulink url='&YOCTO_DL_URL;/releases/yocto/yocto-&DISTRO;/machines/'>Index of Releases</ulink>
283 in the "machines" directory.</para> 283 in the "machines" directory.</para>
284 284
285 <para>The "machines" directory contains tarballs 285 <para>The machine-specific folders of the "machines" directory
286 (<filename>*.tar.bz2</filename>) for supported machines. 286 contain tarballs (<filename>*.tar.bz2</filename>) for supported
287 The directory also contains flattened root filesystem 287 machines.
288 These directories also contain flattened root filesystem
288 image files (<filename>*.ext4</filename>), which you can use 289 image files (<filename>*.ext4</filename>), which you can use
289 with QEMU directly.</para> 290 with QEMU directly.</para>
290 291
@@ -298,14 +299,15 @@
298 299
299 Where: 300 Where:
300 <replaceable>profile</replaceable> is the filesystem image's profile: 301 <replaceable>profile</replaceable> is the filesystem image's profile:
301 lsb, lsb-dev, lsb-sdk, lsb-qt3, minimal, minimal-dev, sato, 302 lsb, lsb-dev, lsb-sdk, minimal, minimal-dev, minimal-initramfs,
302 sato-dev, sato-sdk, minimal-initramfs, or sdk-ptest. For 303 sato, sato-dev, sato-sdk, sato-sdk-ptest. For information on
303 information on these types of image profiles, see the 304 these types of image profiles, see the "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" chapter in
304 "Images" chapter in the Yocto Project Reference Manual. 305 the Yocto Project Reference Manual.
305 306
306 <replaceable>arch</replaceable> is a string representing the target architecture: 307 <replaceable>arch</replaceable> is a string representing the target architecture:
307 beaglebone, edgerouter, genericx86, genericx86-64, mpc8315e-rdb, 308 beaglebone-yocto, beaglebone-yocto-lsb, edgerouter, edgerouter-lsb,
308 and several versions for qemu*. 309 genericx86, genericx86-64, genericx86-64-lsb, genericx86-lsb,
310 mpc8315e-rdb, mpc8315e-rdb-lsb, and qemu*.
309 311
310<!--> 312<!-->
311 <replaceable>date_time</replaceable> is a date and time stamp. 313 <replaceable>date_time</replaceable> is a date and time stamp.
@@ -317,26 +319,28 @@
317 <filename>core-image-minimal</filename> images. 319 <filename>core-image-minimal</filename> images.
318 </para> 320 </para>
319 321
320 <para>For example, if your target hardware system is a 322 <para>For example, if you plan on using a BeagleBone device
321 BeagleBone board and your image is a 323 as your target hardware and your image is a
322 <filename>core-image-minimal</filename> image, you need 324 <filename>core-image-sato-sdk</filename>
323 to download the following root filesystem image file: 325 image, you can download the following file:
324 <literallayout class='monospaced'> 326 <literallayout class='monospaced'>
325 core-image-minimal-beaglebone-yocto.tar.bz2 327 core-image-sato-sdk-beaglebone-yocto.tar.bz2
326 </literallayout> 328 </literallayout>
327 </para></listitem> 329 </para></listitem>
328 <listitem><para> 330 <listitem><para>
329 <emphasis>Initialize the Cross-Development Environment:</emphasis> 331 <emphasis>Initialize the Cross-Development Environment:</emphasis>
330 You must <filename>source</filename> 332 You must <filename>source</filename> the cross-development
331 the cross-development environment setup script to establish 333 environment setup script to establish necessary environment
332 necessary environment variables.</para> 334 variables.</para>
333 335
334 <para>This script is located in the top-level directory in 336 <para>This script is located in the top-level directory in
335 which you installed the toolchain (e.g. 337 which you installed the toolchain (e.g.
336 <filename>poky_sdk</filename>).</para> 338 <filename>poky_sdk</filename>).</para>
337 339
338 <para>Following is an example for the BeagleBone Board 340 <para>Following is an example based on the toolchain installed
339 previously shown: 341 in the
342 "<link linkend='sdk-locating-pre-built-sdk-installers'>Locating Pre-Built SDK Installers</link>"
343 section:
340 <literallayout class='monospaced'> 344 <literallayout class='monospaced'>
341 $ source ~/poky_sdk/environment-setup-core2-64-poky-linux 345 $ source ~/poky_sdk/environment-setup-core2-64-poky-linux
342 </literallayout> 346 </literallayout>
@@ -353,10 +357,10 @@
353 This command extracts the root filesystem into the 357 This command extracts the root filesystem into the
354 <filename>core2-64-sato</filename> directory: 358 <filename>core2-64-sato</filename> directory:
355 <literallayout class='monospaced'> 359 <literallayout class='monospaced'>
356 $ runqemu-extract-sdk ~/Downloads/core-image-sato-core2-64.tar.bz2 ~/core2-64-sato 360 $ runqemu-extract-sdk ~/Downloads/core-image-sato-sdk-beaglebone-yocto.tar.bz2 ~/beaglebone-sato
357 </literallayout> 361 </literallayout>
358 You could now point to the target sysroot at 362 You could now point to the target sysroot at
359 <filename>core2-64-sato</filename>. 363 <filename>beablebone-sato</filename>.
360 </para></listitem> 364 </para></listitem>
361 </orderedlist> 365 </orderedlist>
362 </para> 366 </para>