summaryrefslogtreecommitdiffstats
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.xml89
1 files changed, 0 insertions, 89 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index 459254c078..1155d8fc85 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -789,95 +789,6 @@
789 </para> 789 </para>
790</section> 790</section>
791 791
792<section id='flashing-images-using-bmaptool'>
793 <title>Flashing Images Using <filename>bmaptool</filename></title>
794
795 <para>
796 An easy way to flash an image to a bootable device is to use
797 <filename>bmaptool</filename>, which is integrated into the
798 OpenEmbedded build system.
799 </para>
800
801 <para>
802 Following, is an example that shows how to flash a Wic image.
803 <note>
804 You can use <filename>bmaptool</filename> to flash any
805 type of image.
806 </note>
807 Use these steps to flash an image using
808 <filename>bmaptool</filename>:
809 <note>
810 Unless you are able to install the
811 <filename>bmap-tools</filename> package as mentioned in the note
812 in the second bullet of step 3 further down, you will need to build
813 <filename>bmaptool</filename> before using it.
814 Build the tool using the following command:
815 <literallayout class='monospaced'>
816 $ bitbake bmap-tools-native
817 </literallayout>
818 </note>
819 <orderedlist>
820 <listitem><para>
821 Add the following to your <filename>local.conf</filename>
822 file:
823 <literallayout class='monospaced'>
824 IMAGE_FSTYPES += "wic wic.bmap"
825 </literallayout>
826 </para></listitem>
827 <listitem><para>
828 Either have your image ready (pre-built) or take the step
829 build the image:
830 <literallayout class='monospaced'>
831 $ bitbake <replaceable>image</replaceable>
832 </literallayout>
833 </para></listitem>
834 <listitem><para>
835 Flash the image to the media by using
836 <filename>bmaptool</filename> depending on your particular
837 setup:
838 <itemizedlist>
839 <listitem><para>
840 If you have write access to the media,
841 use this command form:
842 <literallayout class='monospaced'>
843 $ oe-run-native bmaptool-native bmaptool copy ./tmp/deploy/images/qemux86-64-core-image-minimal-<replaceable>machine</replaceable>.wic /dev/sd<replaceable>X</replaceable>
844 </literallayout>
845 </para></listitem>
846 <listitem><para>
847 If you do not have write access to
848 the media, use the following
849 commands:
850 <literallayout class='monospaced'>
851 $ sudo bash
852 $ 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>
853 </literallayout>
854 <note>
855 If you are using Ubuntu or Debian distributions,
856 you can install the
857 <filename>bmap-tools</filename> package using the
858 following command and then use the tool
859 without specifying
860 <filename>PATH</filename> even from the
861 root account:
862 <literallayout class='monospaced'>
863 $ sudo apt-get install bmap-tools
864 </literallayout>
865 </note>
866 </para></listitem>
867 </itemizedlist>
868 </para></listitem>
869 </orderedlist>
870 </para>
871
872 <para>
873 For help on the <filename>bmaptool</filename> command, use the
874 following command:
875 <literallayout class='monospaced'>
876 $ bmaptool --help
877 </literallayout>
878 </para>
879</section>
880
881<section id='using-pre-built-binaries-and-qemu'> 792<section id='using-pre-built-binaries-and-qemu'>
882 <title>Using Pre-Built Binaries and QEMU</title> 793 <title>Using Pre-Built Binaries and QEMU</title>
883 794