diff options
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/dev-manual/bmaptool.rst | 20 | ||||
-rw-r--r-- | documentation/dev-manual/wic.rst | 2 |
2 files changed, 11 insertions, 11 deletions
diff --git a/documentation/dev-manual/bmaptool.rst b/documentation/dev-manual/bmaptool.rst index 9add72cf3b..f6f0e6afaf 100644 --- a/documentation/dev-manual/bmaptool.rst +++ b/documentation/dev-manual/bmaptool.rst | |||
@@ -4,10 +4,10 @@ Flashing Images Using ``bmaptool`` | |||
4 | ********************************** | 4 | ********************************** |
5 | 5 | ||
6 | A fast and easy way to flash an image to a bootable device is to use | 6 | A fast and easy way to flash an image to a bootable device is to use |
7 | Bmaptool, which is integrated into the OpenEmbedded build system. | 7 | bmaptool, which is integrated into the OpenEmbedded build system. |
8 | Bmaptool is a generic tool that creates a file's block map (bmap) and | 8 | bmaptool is a generic tool that creates a file's block map (bmap) and |
9 | then uses that map to copy the file. As compared to traditional tools | 9 | then uses that map to copy the file. As compared to traditional tools |
10 | such as dd or cp, Bmaptool can copy (or flash) large files like raw | 10 | such as dd or cp, bmaptool can copy (or flash) large files like raw |
11 | system image files much faster. | 11 | system image files much faster. |
12 | 12 | ||
13 | .. note:: | 13 | .. note:: |
@@ -20,13 +20,13 @@ system image files much faster. | |||
20 | $ sudo apt install bmap-tools | 20 | $ sudo apt install bmap-tools |
21 | 21 | ||
22 | - If you are unable to install the ``bmap-tools`` package, you will | 22 | - If you are unable to install the ``bmap-tools`` package, you will |
23 | need to build Bmaptool before using it. Use the following command:: | 23 | need to build bmaptool before using it. Use the following command:: |
24 | 24 | ||
25 | $ bitbake bmap-tools-native | 25 | $ bitbake bmaptool-native |
26 | 26 | ||
27 | Following, is an example that shows how to flash a Wic image. Realize | 27 | Following, is an example that shows how to flash a Wic image. Realize |
28 | that while this example uses a Wic image, you can use Bmaptool to flash | 28 | that while this example uses a Wic image, you can use bmaptool to flash |
29 | any type of image. Use these steps to flash an image using Bmaptool: | 29 | any type of image. Use these steps to flash an image using bmaptool: |
30 | 30 | ||
31 | #. *Update your local.conf File:* You need to have the following set | 31 | #. *Update your local.conf File:* You need to have the following set |
32 | in your ``local.conf`` file before building your image:: | 32 | in your ``local.conf`` file before building your image:: |
@@ -39,19 +39,19 @@ any type of image. Use these steps to flash an image using Bmaptool: | |||
39 | 39 | ||
40 | $ bitbake image | 40 | $ bitbake image |
41 | 41 | ||
42 | #. *Flash the Device:* Flash the device with the image by using Bmaptool | 42 | #. *Flash the Device:* Flash the device with the image by using bmaptool |
43 | depending on your particular setup. The following commands assume the | 43 | depending on your particular setup. The following commands assume the |
44 | image resides in the :term:`Build Directory`'s ``deploy/images/`` area: | 44 | image resides in the :term:`Build Directory`'s ``deploy/images/`` area: |
45 | 45 | ||
46 | - If you have write access to the media, use this command form:: | 46 | - If you have write access to the media, use this command form:: |
47 | 47 | ||
48 | $ oe-run-native bmap-tools-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX | 48 | $ oe-run-native bmaptool-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX |
49 | 49 | ||
50 | - If you do not have write access to the media, set your permissions | 50 | - If you do not have write access to the media, set your permissions |
51 | first and then use the same command form:: | 51 | first and then use the same command form:: |
52 | 52 | ||
53 | $ sudo chmod 666 /dev/sdX | 53 | $ sudo chmod 666 /dev/sdX |
54 | $ oe-run-native bmap-tools-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX | 54 | $ oe-run-native bmaptool-native bmaptool copy build-directory/tmp/deploy/images/machine/image.wic /dev/sdX |
55 | 55 | ||
56 | For help on the ``bmaptool`` command, use the following command:: | 56 | For help on the ``bmaptool`` command, use the following command:: |
57 | 57 | ||
diff --git a/documentation/dev-manual/wic.rst b/documentation/dev-manual/wic.rst index 312f78c403..05e9cb381b 100644 --- a/documentation/dev-manual/wic.rst +++ b/documentation/dev-manual/wic.rst | |||
@@ -503,7 +503,7 @@ Continuing with the example, you can now write the image from the | |||
503 | built your image, and boot from the media. You can write the image by using | 503 | built your image, and boot from the media. You can write the image by using |
504 | ``bmaptool`` or ``dd``:: | 504 | ``bmaptool`` or ``dd``:: |
505 | 505 | ||
506 | $ oe-run-native bmap-tools-native bmaptool copy mkefidisk-201804191017-sda.direct /dev/sdX | 506 | $ oe-run-native bmaptool-native bmaptool copy mkefidisk-201804191017-sda.direct /dev/sdX |
507 | 507 | ||
508 | or :: | 508 | or :: |
509 | 509 | ||