Intel Atom C2000, Руководство по началу работы

Страница: 46 / 86

Installing, Building, and Running Yocto*
46 Getting Started Guide
Note: Please note the following:
−
If there are build errors that appears to be script errors such as the one shown in the
following example, verify that
/bin/sh
is linked to
/bin/bash
as described in
step 7.
[: 128: cmdline: unexpected operator |
− If the build fails and
bitbake
command needs to be executed again, repeat step 15 to
source oe-init-build-env.
− Log files (including errors and warnings) for the build are included in the
~/poky/build/tmp/log directory.
−
If an error is returned stating
bitbake
is not installed, verify that you sourced the
oe-
init-build-env file
in
~/poky
as described in Step 15 .
− The command may take several hours to complete, depending on the particular
software development machine and network speed.
Verify that the hddimg is created in
~/poky/build/tmp/deploy/images/core- image-
sato-sdk-mohonpeak-<timestamp>.hddimg
Note: If the build failed, this file may exist with no content. Verify that the file size is on the order of
hundreds of MB.
6.2 Creating the Linux* Boot Disk
6.2.1 Locating the hddimg
If you have created your own hddimg via the process in Section 6.1 , your hddimg is located in
~/poky/build/tmp/deploy/images/core-image-sato-sdk-mohonpeak-
<timestamp>.hddimg.
6.2.2 Creating the Boot Disk
Note: Special care must be taken when creating the boot disk, since any misidentification of the
target disk can overwrite critical data. You are encouraged to backup your data if there is any doubt
about which disk you will be writing to in the following steps.
Select which of the following two sections to complete depending on the type of boot disk you
are creating.
6.2.2.1 Creating a USB Boot Disk
Note:
To create a USB Boot Disk using SDK image, follow the instructions in Section 6.2.2.2 . The
following instructions may not create a bootable disk for SDK image in all cases.
Identify the device name for your USB boot disk. In a typical case, this will be/dev/sdf.
Study the output of one or more of the following commands to give confidence as to
which disk is which:
# sudo parted -l # df -h
# cat /proc/partitions