Making qemu images - Revision history

Searchworks: remove spam

2010-11-23T23:10:30Z

remove spam

Aqisecoxefi at 22:39, 23 November 2010

2010-11-23T22:39:10Z

Jogness: the number of blocks must also be provided when creating the filesystems

2010-09-17T09:53:19Z

the number of blocks must also be provided when creating the filesystems

94.120.251.160: /* Connex */

2009-04-28T14:13:38Z

‎Connex

Hik at 12:30, 21 February 2009

2009-02-21T12:30:33Z

MatthieuHerrb: use only ext2 in the example, as default kernels only support ext3 through a module.

2008-08-06T10:03:48Z

use only ext2 in the example, as default kernels only support ext3 through a module.

MatthieuHerrb: info on mmc/CF images.

2008-07-31T12:55:12Z

info on mmc/CF images.

MatthieuHerrb: Intructions on building a flash image for gumstix

2008-07-31T10:17:08Z

Intructions on building a flash image for gumstix

New page

= Preparing flash / disk images for qemu =

== Flash images ==

The flash image emulates the flash memory on the Gumstix motherboard. It's a single file that has the size of the emulated flash memory (32MB in the case of the verdex board emulated by qemu). It will contain the same images as the real flash, at the same offsets:

* The u-boot image at offset 0
* The root file system image at offset 256kB
* The kernel image at the end of the image offset 31MB

The following 3 files are needed

* <tt>u-boot-verdex-400-r1587.bin</tt> - u-boot
* <tt>gumstix-basic-image-gumstix-custom-verdex.jffs2</tt> - root file system
* <tt>uImage-2.6.21-r1-gumstix-custom-verdex.bin</tt> - kernel.

Except for the u-boot image which is not yet built by openembedded, those files can be found in the <tt>tmp/deploy/glibc/images/</tt> sub-directory of <tt>gumstix-oe</tt> after running bitbake.

To assemble the image <tt>flash.img</tt> run the following commands:

dd of=flash.img bs=128k count=256 if=/dev/zero
dd of=flash.img bs=128k conv=notrunc if=u-boot-verdex-400-r1587.bin
dd of=flash.img bs=128k conv=notrunc seek=2 if=gumstix-basic-image-gumstix-custom-verdex.jffs2
dd of=flash.img bs=128k conv=notrunc seek=248 if=uImage-2.6.21-r1-gumstix-custom-verdex.bin

[[Category:How_to_-_qemu]]

@@ Line 1: / Line 1: @@
 = Preparing flash / disk images for qemu =
@@ Line 23: / Line 15: @@
 The following 3 files are needed
-* &lt;tt&gt;u-boot-verdex-400-r1587.bin&lt;/tt&gt; - u-boot
+* <tt>u-boot-verdex-400-r1587.bin</tt> - u-boot
-* &lt;tt&gt;gumstix-basic-image-gumstix-custom-verdex.jffs2&lt;/tt&gt; - root file system
+* <tt>gumstix-basic-image-gumstix-custom-verdex.jffs2</tt> - root file system
-* &lt;tt&gt;uImage-2.6.21-r1-gumstix-custom-verdex.bin&lt;/tt&gt; - kernel.
+* <tt>uImage-2.6.21-r1-gumstix-custom-verdex.bin</tt> - kernel.
-Except for the u-boot image which is not yet built by openembedded, those files can be found in the &lt;tt&gt;tmp/deploy/glibc/images/&lt;/tt&gt; sub-directory of &lt;tt&gt;gumstix-oe&lt;/tt&gt; after running bitbake.
+Except for the u-boot image which is not yet built by openembedded, those files can be found in the <tt>tmp/deploy/glibc/images/</tt> sub-directory of <tt>gumstix-oe</tt> after running bitbake.
-To assemble the image &lt;tt&gt;flash.img&lt;/tt&gt; run the following commands:
+To assemble the image <tt>flash.img</tt> run the following commands:
-&lt;pre&gt;
+<pre>
 $ dd of=flash.img bs=128k count=256 if=/dev/zero
 $ dd of=flash.img bs=128k conv=notrunc if=u-boot-verdex-400-r1587.bin
 $ dd of=flash.img bs=128k conv=notrunc seek=2 if=gumstix-basic-image-gumstix-custom-verdex.jffs2
 $ dd of=flash.img bs=128k conv=notrunc seek=248 if=uImage-2.6.21-r1-gumstix-custom-verdex.bin
-&lt;/pre&gt;
+</pre>
 === Connex ===
@@ Line 42: / Line 34: @@
 For Connex boards with 16MB flash the steps slightly differ:
-&lt;pre&gt;
+<pre>
 $ dd of=cflash.img bs=128k count=128 if=/dev/zero
 $ dd of=cflash.img bs=128k conv=notrunc if=u-boot-connex-400-r1604.bin
 $ dd of=cflash.img bs=128k conv=notrunc seek=2 if=gumstix-basic-image-gumstix-custom-connex.jffs2
 $ dd of=cflash.img bs=128k conv=notrunc seek=120 if=uImage-2.6.21-r1-gumstix-custom-connex.bin
-&lt;/pre&gt;
+</pre>
 == mmc/CF images ==
@@ Line 54: / Line 46: @@
 boot from them or just to store more data in them.
-On the Linux host, the &lt;tt&gt;losetup&lt;/tt&gt;(1) utility is used to access those images as real block devices,
+On the Linux host, the <tt>losetup</tt>(1) utility is used to access those images as real block devices,
 /!\ The current qemu version seems to be limited to 1GB card images. The examples presented here will thus use 1GB images.
@@ Line 74: / Line 66: @@
 In the most simple case, one single partition (VFAT, ext2 or ext3) can cover the whole card. However, in order to boot from the card and use it for the root file system, at least 2 partitions, one small VFAT to hold the kernel and the u-boot script, and a bigger one, ext2  for the root file system. The folloing example shows a basic setup (using fdisk 'p' command):
-&lt;pre&gt;
+<pre>
    Command (m for help): p
@@ Line 85: / Line 77: @@
   /dev/loop0p1               1           7       56196    6  FAT16
   /dev/loop0p2               8         130      987997+  83  Linux
-&lt;/pre&gt;
+</pre>
 === Accessing the partitions ===
-In order to access the partitions, 2 more loop devices have to be created with losetup. The offsets into the main loop device (&lt;tt&gt;/dev/loop0&lt;/tt&gt;) need to be specified. For this, use &lt;tt&gt;fdisk -ul&lt;/tt&gt; to find the starting block of your partitions:
+In order to access the partitions, 2 more loop devices have to be created with losetup. The offsets into the main loop device (<tt>/dev/loop0</tt>) need to be specified. For this, use <tt>fdisk -ul</tt> to find the starting block of your partitions:
-&lt;pre&gt;
+<pre>
 Disk /dev/loop0: 1073 MB, 1073741824 bytes
@@ Line 100: / Line 92: @@
 /dev/loop0p1              63      112454       56196    6  FAT16
 /dev/loop0p2          112455     2088449      987997+  83  Linux
-&lt;/pre&gt;
+</pre>
 Partition 1 starts at block 63 (which is 63*512 = 32256 bytes) and partition 2 starts at block 112455 (which is 112455*512 = 57576960 bytes).
@@ Line 126: / Line 118: @@
 === Copying data ===
-The kernel image (called &lt;tt&gt;uImage&lt;/tt&gt; on the docs on using root on MMC/SD), the u-boot script &lt;tt&gt;gumstix-factory.script&lt;/tt&gt; are needed on /mnt/1.
+The kernel image (called <tt>uImage</tt> on the docs on using root on MMC/SD), the u-boot script <tt>gumstix-factory.script</tt> are needed on /mnt/1.
-To transfer the root filesystem to /mnt/2, un-tar the &lt;tt&gt;gumstix-basic-image-gumstix-custom-verdex.tar.gz&lt;/tt&gt; found in the &lt;tt&gt;tmp/deploy/glibc/images/gumstix-custom-verdex/&lt;/tt&gt; directory.
+To transfer the root filesystem to /mnt/2, un-tar the <tt>gumstix-basic-image-gumstix-custom-verdex.tar.gz</tt> found in the <tt>tmp/deploy/glibc/images/gumstix-custom-verdex/</tt> directory.
 === Cleaning up ===

@@ Line 1: / Line 1: @@
 = Preparing flash / disk images for qemu =
@@ Line 15: / Line 23: @@
 The following 3 files are needed
-* <tt>u-boot-verdex-400-r1587.bin</tt> - u-boot
+* &lt;tt&gt;u-boot-verdex-400-r1587.bin&lt;/tt&gt; - u-boot
-* <tt>gumstix-basic-image-gumstix-custom-verdex.jffs2</tt> - root file system
+* &lt;tt&gt;gumstix-basic-image-gumstix-custom-verdex.jffs2&lt;/tt&gt; - root file system
-* <tt>uImage-2.6.21-r1-gumstix-custom-verdex.bin</tt> - kernel.
+* &lt;tt&gt;uImage-2.6.21-r1-gumstix-custom-verdex.bin&lt;/tt&gt; - kernel.
-Except for the u-boot image which is not yet built by openembedded, those files can be found in the <tt>tmp/deploy/glibc/images/</tt> sub-directory of <tt>gumstix-oe</tt> after running bitbake.
+Except for the u-boot image which is not yet built by openembedded, those files can be found in the &lt;tt&gt;tmp/deploy/glibc/images/&lt;/tt&gt; sub-directory of &lt;tt&gt;gumstix-oe&lt;/tt&gt; after running bitbake.
-To assemble the image <tt>flash.img</tt> run the following commands:
+To assemble the image &lt;tt&gt;flash.img&lt;/tt&gt; run the following commands:
-<pre>
+&lt;pre&gt;
 $ dd of=flash.img bs=128k count=256 if=/dev/zero
 $ dd of=flash.img bs=128k conv=notrunc if=u-boot-verdex-400-r1587.bin
 $ dd of=flash.img bs=128k conv=notrunc seek=2 if=gumstix-basic-image-gumstix-custom-verdex.jffs2
 $ dd of=flash.img bs=128k conv=notrunc seek=248 if=uImage-2.6.21-r1-gumstix-custom-verdex.bin
-</pre>
+&lt;/pre&gt;
 === Connex ===
@@ Line 34: / Line 42: @@
 For Connex boards with 16MB flash the steps slightly differ:
-<pre>
+&lt;pre&gt;
 $ dd of=cflash.img bs=128k count=128 if=/dev/zero
 $ dd of=cflash.img bs=128k conv=notrunc if=u-boot-connex-400-r1604.bin
 $ dd of=cflash.img bs=128k conv=notrunc seek=2 if=gumstix-basic-image-gumstix-custom-connex.jffs2
 $ dd of=cflash.img bs=128k conv=notrunc seek=120 if=uImage-2.6.21-r1-gumstix-custom-connex.bin
-</pre>
+&lt;/pre&gt;
 == mmc/CF images ==
@@ Line 46: / Line 54: @@
 boot from them or just to store more data in them.
-On the Linux host, the <tt>losetup</tt>(1) utility is used to access those images as real block devices,
+On the Linux host, the &lt;tt&gt;losetup&lt;/tt&gt;(1) utility is used to access those images as real block devices,
 /!\ The current qemu version seems to be limited to 1GB card images. The examples presented here will thus use 1GB images.
@@ Line 66: / Line 74: @@
 In the most simple case, one single partition (VFAT, ext2 or ext3) can cover the whole card. However, in order to boot from the card and use it for the root file system, at least 2 partitions, one small VFAT to hold the kernel and the u-boot script, and a bigger one, ext2  for the root file system. The folloing example shows a basic setup (using fdisk 'p' command):
-<pre>
+&lt;pre&gt;
    Command (m for help): p
@@ Line 77: / Line 85: @@
   /dev/loop0p1               1           7       56196    6  FAT16
   /dev/loop0p2               8         130      987997+  83  Linux
-</pre>
+&lt;/pre&gt;
 === Accessing the partitions ===
-In order to access the partitions, 2 more loop devices have to be created with losetup. The offsets into the main loop device (<tt>/dev/loop0</tt>) need to be specified. For this, use <tt>fdisk -ul</tt> to find the starting block of your partitions:
+In order to access the partitions, 2 more loop devices have to be created with losetup. The offsets into the main loop device (&lt;tt&gt;/dev/loop0&lt;/tt&gt;) need to be specified. For this, use &lt;tt&gt;fdisk -ul&lt;/tt&gt; to find the starting block of your partitions:
-<pre>
+&lt;pre&gt;
 Disk /dev/loop0: 1073 MB, 1073741824 bytes
@@ Line 92: / Line 100: @@
 /dev/loop0p1              63      112454       56196    6  FAT16
 /dev/loop0p2          112455     2088449      987997+  83  Linux
-</pre>
+&lt;/pre&gt;
 Partition 1 starts at block 63 (which is 63*512 = 32256 bytes) and partition 2 starts at block 112455 (which is 112455*512 = 57576960 bytes).
@@ Line 118: / Line 126: @@
 === Copying data ===
-The kernel image (called <tt>uImage</tt> on the docs on using root on MMC/SD), the u-boot script <tt>gumstix-factory.script</tt> are needed on /mnt/1.
+The kernel image (called &lt;tt&gt;uImage&lt;/tt&gt; on the docs on using root on MMC/SD), the u-boot script &lt;tt&gt;gumstix-factory.script&lt;/tt&gt; are needed on /mnt/1.
-To transfer the root filesystem to /mnt/2, un-tar the <tt>gumstix-basic-image-gumstix-custom-verdex.tar.gz</tt> found in the <tt>tmp/deploy/glibc/images/gumstix-custom-verdex/</tt> directory.
+To transfer the root filesystem to /mnt/2, un-tar the &lt;tt&gt;gumstix-basic-image-gumstix-custom-verdex.tar.gz&lt;/tt&gt; found in the &lt;tt&gt;tmp/deploy/glibc/images/gumstix-custom-verdex/&lt;/tt&gt; directory.
 === Cleaning up ===

@@ Line 105: / Line 105: @@
 === Formatting and mounting ===
-   mkfs -t vfat /dev/loop1
+The loop device will extend to the end of the image file, even though the partition does not. For this reason it is important to specify the amount of blocks when creating the filesystem. The number of blocks were shown in the previous fdisk output. (Be aware that mkfs may give a warning about a block count mismatch. This is because the loop device may be larger than the partition. In this situation, the warning can be ignored.)
    mkfs -t ext2 /dev/loop2
    mkdir /mnt/1

@@ Line 38: / Line 38: @@
 $ dd of=cflash.img bs=128k conv=notrunc if=u-boot-connex-400-r1604.bin
 $ dd of=cflash.img bs=128k conv=notrunc seek=2 if=gumstix-basic-image-gumstix-custom-connex.jffs2
-$ dd of=cflash.img bs=128k conv=notrunc seek=120 if=uImage-2.6.21-r1-gumstix-custom-connex.bin"
+$ dd of=cflash.img bs=128k conv=notrunc seek=120 if=uImage-2.6.21-r1-gumstix-custom-connex.bin
 </pre>

@@ Line 47: / Line 47: @@
 === Partitionning the card ===
-In the most simple case, one single partition (VFAT, ext2 or ext3) can cover the whole card. However, in order to boot from the card and use it for the root file system, at least 2 partitions, one small VFAT one to hold the kernel and the u-boot script, and the other one, ext2 or 3 for the root file system. The folloing example shows a basic setup (using fdisk 'p' command):
+In the most simple case, one single partition (VFAT, ext2 or ext3) can cover the whole card. However, in order to boot from the card and use it for the root file system, at least 2 partitions, one small VFAT to hold the kernel and the u-boot script, and a bigger one, ext2  for the root file system. The folloing example shows a basic setup (using fdisk 'p' command):
 <pre>
@@ Line 89: / Line 89: @@
    mkfs -t vfat /dev/loop1
-   mkfs -t ext3 /dev/loop2
+   mkfs -t ext2 /dev/loop2
    mkdir /mnt/1