summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml418
1 files changed, 253 insertions, 165 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 6064f96cc4..9eaaea5501 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -44,7 +44,6 @@
44 </note> 44 </note>
45 </legalnotice> 45 </legalnotice>
46 46
47
48 <abstract> 47 <abstract>
49 <imagedata fileref="figures/yocto-project-transp.png" 48 <imagedata fileref="figures/yocto-project-transp.png"
50 width="6in" depth="1in" 49 width="6in" depth="1in"
@@ -180,163 +179,234 @@
180 <title>Setting Up to Use the Yocto Project</title> 179 <title>Setting Up to Use the Yocto Project</title>
181 180
182 <para> 181 <para>
183 The following list shows what you need in order to use a 182 Setting up to use the Yocto Project involves getting your build
184 Linux-based build host to use the Yocto Project to build images: 183 host ready.
184 If you have a native Linux machine that runs a Yocto Project
185 supported distribution as described by the
186 "<ulink url='&YOCTO_DOCS_REF_URL;#detailed-supported-distros'>Supported Linux Distributions</ulink>"
187 section in the Yocto Project Reference Manual, you can prepare
188 that machine as your build host.
189 See the
190 "<link linkend='qs-native-linux-build-host'>Using a Native Linux Machine</link>"
191 section for more information.
185 </para> 192 </para>
186 193
187 <itemizedlist> 194 <para>
188 <listitem><para><emphasis>Build Host</emphasis> 195 If you do not want to use the Yocto Project on a native Linux
189 A build host with a minimum of 50 Gbytes of free disk 196 machine, you can prepare your build host to use
190 space that is running a supported Linux distribution (i.e. 197 <ulink url='https://git.yoctoproject.org/cgit/cgit.cgi/crops/about/'>CROPS</ulink>,
191 recent releases of Fedora, openSUSE, CentOS, Debian, or 198 which leverages
192 Ubuntu). 199 <ulink url='https://www.docker.com/'>Docker Containers</ulink>.
193 </para></listitem> 200 You can set up a build host for Windows, Mac, and Linux
194 <listitem><para><emphasis>Build Host Packages</emphasis> 201 machines.
195 Appropriate packages installed on the build host. 202 See the
196 </para></listitem> 203 "<link linkend='qs-crops-build-host'>Using CROPS and Containers</link>"
197 <listitem><para><emphasis>The Yocto Project</emphasis> 204 section for more information.
198 A release of the Yocto Project. 205 </para>
199 </para></listitem>
200 </itemizedlist>
201
202 <section id='the-linux-distro'>
203 <title>The Linux Distribution</title>
204 206
205 <para> 207 <section id='qs-crops-build-host'>
206 The Yocto Project team verifies each release against recent 208 <title>Using CROPS and Containers</title>
207 versions of the most popular Linux distributions that
208 provide stable releases.
209 In general, if you have the current release minus one of the
210 following distributions, you should have no problems.
211 <itemizedlist>
212 <listitem><para>
213 Ubuntu
214 </para></listitem>
215 <listitem><para>
216 Fedora
217 </para></listitem>
218 <listitem><para>
219 openSUSE
220 </para></listitem>
221 <listitem><para>
222 CentOS
223 </para></listitem>
224 <listitem><para>
225 Debian
226 </para></listitem>
227 </itemizedlist>
228 For a more detailed list of distributions that support the
229 Yocto Project, see the
230 "<ulink url='&YOCTO_DOCS_REF_URL;#detailed-supported-distros'>Supported Linux Distributions</ulink>"
231 section in the Yocto Project Reference Manual.
232 </para>
233 209
234 <para> 210 <para>
235 The OpenEmbedded build system should be able to run on any 211 Follow these steps to get your build host set up with a
236 modern distribution that has the following versions for 212 Poky container that you can use to complete the build
237 Git, tar, and Python. 213 examples further down in the Quick Start:
238 <itemizedlist> 214 <orderedlist>
239 <listitem><para>
240 Git 1.8.3.1 or greater
241 </para></listitem>
242 <listitem><para> 215 <listitem><para>
243 tar 1.27 or greater 216 <emphasis>Reference the Procedure:</emphasis>
217 Work through the first six steps of the procedure
218 in the
219 "<ulink url='&YOCTO_DOCS_DEV_URL;#setting-up-to-use-crops'>Setting Up to Use CROss PlatformS (CROPS)</ulink>"
220 section of the Yocto Project Development Manual.
244 </para></listitem> 221 </para></listitem>
245 <listitem><para> 222 <listitem><para>
246 Python 3.4.0 or greater. 223 <emphasis>Set Up the Poky Container to Use the Yocto Project:</emphasis>
224 Go to
225 <ulink url='https://github.com/crops/poky-container/blob/master/README.md'></ulink>
226 and follow the directions to set up the Poky container
227 on your build host.</para>
228
229 <para>Once you complete the setup instructions for your
230 machine, you need to get a copy of the
231 <filename>poky</filename> repository on your build
232 host.
233 See the
234 "<link linkend='releases'>Yocto Project Release</link>"
235 section to continue.
247 </para></listitem> 236 </para></listitem>
248 </itemizedlist> 237 </orderedlist>
249 If your build host does not meet any of these three listed
250 version requirements, you can take steps to prepare the
251 system so that you can still use the Yocto Project.
252 See the
253 "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</ulink>"
254 section in the Yocto Project Reference Manual for information.
255 </para> 238 </para>
256 </section> 239 </section>
257 240
258 <section id='packages'> 241 <section id='qs-native-linux-build-host'>
259 <title>The Build Host Packages</title> 242 <title>Using a Native Linux Machine</title>
260 243
261 <para> 244 <para>
262 Required build host packages vary depending on your 245 The following list shows what you need in order to use a
263 build machine and what you want to do with the Yocto Project. 246 Linux-based build host to use the Yocto Project to build images:
264 For example, if you want to build an image that can run
265 on QEMU in graphical mode (a minimal, basic build
266 requirement), then the build host package requirements
267 are different than if you want to build an image on a headless
268 system or build out the Yocto Project documentation set.
269 </para> 247 </para>
270 248
271 <para> 249 <itemizedlist>
272 Collectively, the number of required packages is large 250 <listitem><para><emphasis>Build Host</emphasis>
273 if you want to be able to cover all cases. 251 A build host with a minimum of 50 Gbytes of free disk
274 <note> 252 space that is running a supported Linux distribution (i.e.
275 In general, you need to have root access and then install 253 recent releases of Fedora, openSUSE, CentOS, Debian, or
276 the required packages. 254 Ubuntu).
277 Thus, the commands in the following section may or may 255 </para></listitem>
278 not work depending on whether or not your Linux 256 <listitem><para><emphasis>Build Host Packages</emphasis>
279 distribution has <filename>sudo</filename> installed. 257 Appropriate packages installed on the build host.
280 </note> 258 </para></listitem>
281 </para> 259 </itemizedlist>
282 260
283 <para> 261 <section id='the-linux-distro'>
284 The following list shows the required packages needed to build 262 <title>The Linux Distribution</title>
285 an image that runs on QEMU in graphical mode (e.g. essential 263
286 plus graphics support). 264 <para>
287 For lists of required packages for other scenarios, see the 265 The Yocto Project team verifies each release against recent
288 "<ulink url='&YOCTO_DOCS_REF_URL;#required-packages-for-the-host-development-system'>Required Packages for the Host Development System</ulink>" 266 versions of the most popular Linux distributions that
289 section in the Yocto Project Reference Manual. 267 provide stable releases.
290 <itemizedlist> 268 In general, if you have the current release minus one of the
291 <listitem><para><emphasis>Ubuntu and Debian</emphasis> 269 following distributions, you should have no problems.
292 <literallayout class='monospaced'> 270 <itemizedlist>
271 <listitem><para>
272 Ubuntu
273 </para></listitem>
274 <listitem><para>
275 Fedora
276 </para></listitem>
277 <listitem><para>
278 openSUSE
279 </para></listitem>
280 <listitem><para>
281 CentOS
282 </para></listitem>
283 <listitem><para>
284 Debian
285 </para></listitem>
286 </itemizedlist>
287 For a more detailed list of distributions that support the
288 Yocto Project, see the
289 "<ulink url='&YOCTO_DOCS_REF_URL;#detailed-supported-distros'>Supported Linux Distributions</ulink>"
290 section in the Yocto Project Reference Manual.
291 </para>
292
293 <para>
294 The OpenEmbedded build system should be able to run on any
295 modern distribution that has the following versions for
296 Git, tar, and Python.
297 <itemizedlist>
298 <listitem><para>
299 Git 1.8.3.1 or greater
300 </para></listitem>
301 <listitem><para>
302 tar 1.27 or greater
303 </para></listitem>
304 <listitem><para>
305 Python 3.4.0 or greater.
306 </para></listitem>
307 </itemizedlist>
308 If your build host does not meet any of these three listed
309 version requirements, you can take steps to prepare the
310 system so that you can still use the Yocto Project.
311 See the
312 "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</ulink>"
313 section in the Yocto Project Reference Manual for information.
314 </para>
315 </section>
316
317 <section id='packages'>
318 <title>The Build Host Packages</title>
319
320 <para>
321 Required build host packages vary depending on your
322 build machine and what you want to do with the Yocto Project.
323 For example, if you want to build an image that can run
324 on QEMU in graphical mode (a minimal, basic build
325 requirement), then the build host package requirements
326 are different than if you want to build an image on a headless
327 system or build out the Yocto Project documentation set.
328 </para>
329
330 <para>
331 Collectively, the number of required packages is large
332 if you want to be able to cover all cases.
333 <note>
334 In general, you need to have root access and then install
335 the required packages.
336 Thus, the commands in the following section may or may
337 not work depending on whether or not your Linux
338 distribution has <filename>sudo</filename> installed.
339 </note>
340 </para>
341
342 <para>
343 The following list shows the required packages needed to build
344 an image that runs on QEMU in graphical mode (e.g. essential
345 plus graphics support).
346 For lists of required packages for other scenarios, see the
347 "<ulink url='&YOCTO_DOCS_REF_URL;#required-packages-for-the-host-development-system'>Required Packages for the Host Development System</ulink>"
348 section in the Yocto Project Reference Manual.
349 <itemizedlist>
350 <listitem><para><emphasis>Ubuntu and Debian</emphasis>
351 <literallayout class='monospaced'>
293 $ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL; libsdl1.2-dev xterm 352 $ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL; libsdl1.2-dev xterm
294 </literallayout> 353 </literallayout>
295 </para></listitem> 354 </para></listitem>
296 <listitem><para><emphasis>Fedora</emphasis> 355 <listitem><para><emphasis>Fedora</emphasis>
297 <literallayout class='monospaced'> 356 <literallayout class='monospaced'>
298 $ sudo dnf install &FEDORA_HOST_PACKAGES_ESSENTIAL; SDL-devel xterm 357 $ sudo dnf install &FEDORA_HOST_PACKAGES_ESSENTIAL; SDL-devel xterm
299 </literallayout> 358 </literallayout>
300 </para></listitem> 359 </para></listitem>
301 <listitem><para><emphasis>OpenSUSE</emphasis> 360 <listitem><para><emphasis>OpenSUSE</emphasis>
302 <literallayout class='monospaced'> 361 <literallayout class='monospaced'>
303 $ sudo zypper install &OPENSUSE_HOST_PACKAGES_ESSENTIAL; libSDL-devel xterm 362 $ sudo zypper install &OPENSUSE_HOST_PACKAGES_ESSENTIAL; libSDL-devel xterm
304 </literallayout> 363 </literallayout>
305 </para></listitem> 364 </para></listitem>
306 <listitem><para><emphasis>CentOS</emphasis> 365 <listitem><para><emphasis>CentOS</emphasis>
307 <literallayout class='monospaced'> 366 <literallayout class='monospaced'>
308 $ sudo yum install &CENTOS_HOST_PACKAGES_ESSENTIAL; SDL-devel xterm 367 $ sudo yum install &CENTOS_HOST_PACKAGES_ESSENTIAL; SDL-devel xterm
309 </literallayout> 368 </literallayout>
310 <note><title>Notes</title> 369 <note><title>Notes</title>
311 <itemizedlist> 370 <itemizedlist>
312 <listitem><para> 371 <listitem><para>
313 CentOS 6.x users need to ensure that the 372 CentOS 6.x users need to ensure that the
314 required versions of Git, tar and Python 373 required versions of Git, tar and Python
315 are available. 374 are available.
316 For details, See the 375 For details, See the
317 "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</ulink>" 376 "<ulink url='&YOCTO_DOCS_REF_URL;#required-git-tar-and-python-versions'>Required Git, tar, and Python Versions</ulink>"
318 section in the Yocto Project Reference 377 section in the Yocto Project Reference
319 Manual for information. 378 Manual for information.
320 </para></listitem> 379 </para></listitem>
321 <listitem><para> 380 <listitem><para>
322 Extra Packages for Enterprise Linux 381 Extra Packages for Enterprise Linux
323 (i.e. <filename>epel-release</filename>) 382 (i.e. <filename>epel-release</filename>)
324 is a collection of packages from Fedora 383 is a collection of packages from Fedora
325 built on RHEL/CentOS for easy installation 384 built on RHEL/CentOS for easy installation
326 of packages not included in enterprise 385 of packages not included in enterprise
327 Linux by default. 386 Linux by default.
328 You need to install these packages 387 You need to install these packages
329 separately. 388 separately.
330 </para></listitem> 389 </para></listitem>
331 <listitem><para> 390 <listitem><para>
332 The <filename>makecache</filename> command 391 The <filename>makecache</filename> command
333 consumes additional Metadata from 392 consumes additional Metadata from
334 <filename>epel-release</filename>. 393 <filename>epel-release</filename>.
335 </para></listitem> 394 </para></listitem>
336 </itemizedlist> 395 </itemizedlist>
337 </note> 396 </note>
338 </para></listitem> 397 </para></listitem>
339 </itemizedlist> 398 </itemizedlist>
399 </para>
400 </section>
401
402 <para>
403 Once you complete the setup instructions for your
404 machine, you need to get a copy of the
405 <filename>poky</filename> repository on your build
406 host.
407 Continue with the
408 "<link linkend='releases'>Yocto Project Release</link>"
409 section.
340 </para> 410 </para>
341 </section> 411 </section>
342 412
@@ -344,8 +414,9 @@
344 <title>Yocto Project Release</title> 414 <title>Yocto Project Release</title>
345 415
346 <para> 416 <para>
347 The last requirement you need to meet before using the 417 Now that your build host has the right packages (native
348 Yocto Project is getting a Yocto Project release. 418 Linux machine) or you have the Poky container set up
419 (CROPS), you need to get a copy of the Yocto Project.
349 It is recommended that you get the latest Yocto Project release 420 It is recommended that you get the latest Yocto Project release
350 by setting up (cloning in 421 by setting up (cloning in
351 <ulink url='&YOCTO_DOCS_REF_URL;#git'>Git</ulink> terms) a 422 <ulink url='&YOCTO_DOCS_REF_URL;#git'>Git</ulink> terms) a
@@ -356,9 +427,14 @@
356 </para> 427 </para>
357 428
358 <para> 429 <para>
359 Here is an example from an Ubuntu build host that clones the 430 Here is an example from a native Linux machine that is
360 <filename>poky</filename> repository and then checks out the 431 running Ubuntu.
361 latest Yocto Project Release by tag 432 <note>
433 If your build host is using a Poky container, you can
434 use the same Git commands.
435 </note>
436 The example clones the <filename>poky</filename> repository
437 and then checks out the latest Yocto Project Release by tag
362 (i.e. <filename>&DISTRO_REL_TAG;</filename>): 438 (i.e. <filename>&DISTRO_REL_TAG;</filename>):
363 <literallayout class='monospaced'> 439 <literallayout class='monospaced'>
364 $ git clone git://git.yoctoproject.org/poky 440 $ git clone git://git.yoctoproject.org/poky
@@ -404,20 +480,21 @@
404 <title>Building Images</title> 480 <title>Building Images</title>
405 481
406 <para> 482 <para>
407 Now that you have your system requirements in order, you can give 483 You are now ready to give the Yocto Project a try.
408 Yocto Project a try. 484 For this example, you will be using the command line to build
409 You can try out Yocto Project using either the command-line 485 your images.
410 interface or using Toaster, which uses a graphical user 486 <note>
411 interface. 487 A graphical user interface to the Yocto Project is available
412 If you want to try out the Yocto Project using a GUI, see the 488 through Toaster.
413 <ulink url='&YOCTO_DOCS_TOAST_URL;'>Toaster User Manual</ulink> 489 See the
414 for information on how to install and set up Toaster. 490 <ulink url='&YOCTO_DOCS_TOAST_URL;'>Toaster User Manual</ulink>
491 for more information.
492 </note>
415 </para> 493 </para>
416 494
417 <para> 495 <para>
418 To use the Yocto Project through the command-line interface, 496 The remainder of this quick start steps you through the
419 finish this quick start, which presents steps that let you 497 following:
420 do the following:
421 <itemizedlist> 498 <itemizedlist>
422 <listitem><para> 499 <listitem><para>
423 Build a <filename>qemux86</filename> reference image 500 Build a <filename>qemux86</filename> reference image
@@ -477,7 +554,8 @@
477 554
478 <para> 555 <para>
479 <orderedlist> 556 <orderedlist>
480 <listitem><para><emphasis>Be Sure Your Build Host is Set Up:</emphasis> 557 <listitem><para>
558 <emphasis>Be Sure Your Build Host is Set Up:</emphasis>
481 The steps to build an image in this section depend on 559 The steps to build an image in this section depend on
482 your build host being properly set up. 560 your build host being properly set up.
483 Be sure you have worked through the requirements 561 Be sure you have worked through the requirements
@@ -485,7 +563,8 @@
485 "<link linkend='yp-resources'>Setting Up to Use the Yocto Project</link>" 563 "<link linkend='yp-resources'>Setting Up to Use the Yocto Project</link>"
486 section. 564 section.
487 </para></listitem> 565 </para></listitem>
488 <listitem><para><emphasis>Check Out Your Branch:</emphasis> 566 <listitem><para>
567 <emphasis>Check Out Your Branch:</emphasis>
489 Be sure you are in the 568 Be sure you are in the
490 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink> 569 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>
491 (e.g. <filename>poky</filename>) and then check out 570 (e.g. <filename>poky</filename>) and then check out
@@ -505,7 +584,8 @@
505 branch ensures you are using the latest files for 584 branch ensures you are using the latest files for
506 that release. 585 that release.
507 </para></listitem> 586 </para></listitem>
508 <listitem><para><emphasis>Initialize the Build Environment:</emphasis> 587 <listitem><para>
588 <emphasis>Initialize the Build Environment:</emphasis>
509 Run the 589 Run the
510 <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> 590 <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
511 environment setup script to define the OpenEmbedded 591 environment setup script to define the OpenEmbedded
@@ -530,7 +610,8 @@
530 setup script. 610 setup script.
531 </note> 611 </note>
532 </para></listitem> 612 </para></listitem>
533 <listitem><para><emphasis>Examine Your Local Configuration File:</emphasis> 613 <listitem><para>
614 <emphasis>Examine Your Local Configuration File:</emphasis>
534 When you set up the build environment, a local 615 When you set up the build environment, a local
535 configuration file named 616 configuration file named
536 <filename>local.conf</filename> becomes available in 617 <filename>local.conf</filename> becomes available in
@@ -584,7 +665,8 @@
584 </para></listitem> 665 </para></listitem>
585 </itemizedlist> 666 </itemizedlist>
586 </para></listitem> 667 </para></listitem>
587 <listitem><para><emphasis>Start the Build:</emphasis> 668 <listitem><para>
669 <emphasis>Start the Build:</emphasis>
588 Continue with the following command to build an OS image 670 Continue with the following command to build an OS image
589 for the target, which is 671 for the target, which is
590 <filename>core-image-sato</filename> in this example: 672 <filename>core-image-sato</filename> in this example:
@@ -642,7 +724,8 @@
642 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>" 724 "<ulink url='&YOCTO_DOCS_REF_URL;#ref-images'>Images</ulink>"
643 chapter in the Yocto Project Reference Manual. 725 chapter in the Yocto Project Reference Manual.
644 </para></listitem> 726 </para></listitem>
645 <listitem><para><emphasis>Simulate Your Image Using QEMU:</emphasis> 727 <listitem><para>
728 <emphasis>Simulate Your Image Using QEMU:</emphasis>
646 Once this particular image is built, you can start QEMU 729 Once this particular image is built, you can start QEMU
647 and run the image: 730 and run the image:
648 <literallayout class='monospaced'> 731 <literallayout class='monospaced'>
@@ -652,7 +735,8 @@
652 "<ulink url="&YOCTO_DOCS_DEV_URL;#dev-manual-qemu">Using the Quick EMUlator (QEMU)</ulink>" 735 "<ulink url="&YOCTO_DOCS_DEV_URL;#dev-manual-qemu">Using the Quick EMUlator (QEMU)</ulink>"
653 chapter in the Yocto Project Development Manual. 736 chapter in the Yocto Project Development Manual.
654 </para></listitem> 737 </para></listitem>
655 <listitem><para><emphasis>Exit QEMU:</emphasis> 738 <listitem><para>
739 <emphasis>Exit QEMU:</emphasis>
656 Exit QEMU by either clicking on the shutdown icon or by 740 Exit QEMU by either clicking on the shutdown icon or by
657 typing <filename>Ctrl-C</filename> in the QEMU 741 typing <filename>Ctrl-C</filename> in the QEMU
658 transcript window from which you evoked QEMU. 742 transcript window from which you evoked QEMU.
@@ -682,7 +766,8 @@
682 766
683 <para> 767 <para>
684 <orderedlist> 768 <orderedlist>
685 <listitem><para><emphasis>Create a Local Copy of the 769 <listitem><para>
770 <emphasis>Create a Local Copy of the
686 <filename>meta-intel</filename> Repository:</emphasis> 771 <filename>meta-intel</filename> Repository:</emphasis>
687 Building an image for the MinnowBoard Turbot requires 772 Building an image for the MinnowBoard Turbot requires
688 the 773 the
@@ -731,7 +816,8 @@
731 "meta-intel-&DISTRO_NAME_NO_CAP;-&YOCTO_DOC_VERSION;" 816 "meta-intel-&DISTRO_NAME_NO_CAP;-&YOCTO_DOC_VERSION;"
732 in the above example. 817 in the above example.
733 </para></listitem> 818 </para></listitem>
734 <listitem><para><emphasis>Configure the Build:</emphasis> 819 <listitem><para>
820 <emphasis>Configure the Build:</emphasis>
735 To configure the build, you edit the 821 To configure the build, you edit the
736 <filename>bblayers.conf</filename> and 822 <filename>bblayers.conf</filename> and
737 <filename>local.conf</filename> files, both of which are 823 <filename>local.conf</filename> files, both of which are
@@ -836,7 +922,8 @@
836 tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.wic 922 tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.wic
837 </literallayout> 923 </literallayout>
838 </para></listitem> 924 </para></listitem>
839 <listitem><para><emphasis>Write the Image:</emphasis> 925 <listitem><para>
926 <emphasis>Write the Image:</emphasis>
840 You can write the image just built to a bootable media 927 You can write the image just built to a bootable media
841 (e.g. a USB key, SATA drive, SD card, etc.) using the 928 (e.g. a USB key, SATA drive, SD card, etc.) using the
842 <filename>dd</filename> utility: 929 <filename>dd</filename> utility:
@@ -850,7 +937,8 @@
850 <filename>/dev/mmcblk0</filename>, which is most likely an 937 <filename>/dev/mmcblk0</filename>, which is most likely an
851 SD card). 938 SD card).
852 </para></listitem> 939 </para></listitem>
853 <listitem><para><emphasis>Boot the Hardware:</emphasis> 940 <listitem><para>
941 <emphasis>Boot the Hardware:</emphasis>
854 With the boot device provisioned, you can insert the 942 With the boot device provisioned, you can insert the
855 media into the MinnowBoard Turbot and boot the hardware. 943 media into the MinnowBoard Turbot and boot the hardware.
856 The board should automatically detect the media and boot to 944 The board should automatically detect the media and boot to
@@ -914,7 +1002,7 @@
914 <ulink url='&YOCTO_DOCS_SDK_URL;#sdk-extensible'>extensible SDK</ulink>, 1002 <ulink url='&YOCTO_DOCS_SDK_URL;#sdk-extensible'>extensible SDK</ulink>,
915 which are used primarily for application development. 1003 which are used primarily for application development.
916 This manual also provides example workflows 1004 This manual also provides example workflows
917 that use the popular <trademark class='trad'>Eclipse</trademark> 1005 that use the popular <trademark class='trade'>Eclipse</trademark>
918 development environment and that use <filename>devtool</filename>. 1006 development environment and that use <filename>devtool</filename>.
919 See the 1007 See the
920 "<ulink url='&YOCTO_DOCS_SDK_URL;#workflow-using-eclipse'>Workflow using Eclipse™</ulink>" 1008 "<ulink url='&YOCTO_DOCS_SDK_URL;#workflow-using-eclipse'>Workflow using Eclipse™</ulink>"
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-12-09 22:04:19 +0000