aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-start.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/dev-manual-start.xml')
-rw-r--r--documentation/dev-manual/dev-manual-start.xml93
1 files changed, 93 insertions, 0 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index b59f54b085..bcee11ba22 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -328,6 +328,99 @@
</para>
</section>
+<section id='flashing-images-using-bmap-tool'>
+ <title>Flashing Images Using <filename>bmap-tool</filename></title>
+
+ <para>
+ An easy way to flash an image to a bootable device is to use
+ <filename>bmap-tool</filename>, which is integrated into the
+ OpenEmbedded build system.
+ </para>
+
+ <para>
+ Following, is an example that shows how to flash a Wic image.
+ <note>
+ You can use <filename>bmap-tool</filename> to flash any
+ type of image.
+ </note>
+ Use these steps to flash an image using
+ <filename>bmap-tool</filename>:
+ <orderedlist>
+ <listitem><para>
+ Add the following to your <filename>local.conf</filename>
+ file:
+ <literallayout class='monospaced'>
+ IMAGE_FSTYPES += "WIC WIC.BMAP"
+ </literallayout>
+ </para></listitem>
+ <listitem><para>
+ Either have your image ready (pre-built) or take the step
+ build the image:
+ <literallayout class='monospaced'>
+ $ bitbake <replaceable>image</replaceable>
+ </literallayout>
+ </para></listitem>
+ <listitem><para>
+ Flash the image to the media by using the
+ <filename>bmap-tool</filename> depending on your particular
+ setup:
+ <itemizedlist>
+ <listitem><para>
+ If you have write access, use this command form:
+ <literallayout class='monospaced'>
+ $ oe-run-native bmap-tool copy ./tmp/deploy/images/qemux86-64/core-image-minimal-<replaceable>machine</replaceable>.wic /dev/sd<replaceable>X</replaceable>
+ </literallayout>
+ </para></listitem>
+ <listitem><para>
+ If you do not have write access, use the following
+ commands:
+ <literallayout class='monospaced'>
+ $ sudo bash
+ $ PATH=tmp/sysroots/x86_64-linux/usr/bin/ bmaptool copy ./tmp/deploy/images/qemux86-64/core-image-minimal-<replaceable>machine</replaceable>.wic /dev/sd<replaceable>X</replaceable>
+ </literallayout>
+ <note>
+ If you are using Ubuntu 16.10 or Debian,
+ you can install
+ <filename>bmaptool</filename> using the
+ following command and then use the tool
+ without specifying
+ <filename>PATH</filename> even from the
+ root account:
+ <literallayout class='monospaced'>
+ $ sudo apt-get install bmap-tool
+ </literallayout>
+ </note>
+ </para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ </orderedlist>
+ </para>
+
+ <para>
+ For help on the <filename>bmaptool</filename> command, use
+ <filename>bmaptool --help</filename>:
+ <literallayout class='monospaced'>
+ $ bmaptool --help
+ usage: bmaptool [-h] [--version] [-q] [-d] {create,copy} ...
+
+ Create block map (bmap) and copy files using bmap. The documentation can be
+ found here: source.tizen.org/documentation/reference/bmaptool
+
+ optional arguments:
+ -h, --help show this help message and exit
+ --version show program's version number and exit
+ -q, --quiet be quiet
+ -d, --debug print debugging information
+
+ subcommands:
+ {create,copy}
+ create generate bmap for an image file (which should be a sparse
+ file)
+ copy write an image to a block device using bmap
+ </literallayout>
+ </para>
+</section>
+
<section id='using-pre-built-binaries-and-qemu'>
<title>Using Pre-Built Binaries and QEMU</title>