Building a rtems image

[Sambeet Panigrahi]

I corrected the qemu.sh script.The image runs now but I get a error No
Multiboot Header found. Can you help me to find a solution to it.
On 4/04/2016 2:23 PM, Sambeet Panigrahi wrote:

> I have been trying to build a RTEMS image for GRUB2 following the
> instructions from:
> https://devel.rtems.org/wiki/Building/Grub
>
> I have followed all instructions and placed the image  and the directory
> structure in /home/sambeet/SimulRTEMS, the tree command in the directory
> gives
>
> .
> |-- examples
> |   `-- ticker.exe
> |-- grub.cfg
> |-- mkimage.sh
> |-- qemu.sh
> `-- rtems-boot.img
>
> But when I do the following:
>
> Holmes sambeet # ./qemu.sh
>

You did not provide the disk image, see the qemu.sh script, ie '-hda $1'.

qemu-system-i386: -hda -hdb: Could not open '-hdb': No such file or
> directory
>

This makes sense because you are missing the file for the -hda option and
so qemu uses -hdb as the name of the file.


> I get the following output instead of Ticker.exe running and GRUB screen
> appearing.
>
> I have also followed the instructions from
>
> http://jin-yang.github.io/blog/build-a-RTEMS-environment.html. There's the
> same error there too.
>
> I want to create and build a RTEMS image without using the usual
> RTEMS-testing module to understand the process in detail.Can someone please
> help?
>

The file rtems-boot.img is a boot disk which qemu's BIOS will load and boot
and load grub, the -hda $1 option. In the image is a default grub script
that should chain to the grub script on the hard disk, the -hdb fat:.. Qemu
should create a hard disk with an MSDOS partition based on the host's local
directory you run the script from. That disk will be the directory tree you
see. Be careful there is a limit to the number of files qemu can handle
when doing this.

The 2 srage script lets you change or generate a specific grub script
without needing to rebuild the boot disk image.

Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20160404/fa478a0c/attachment-0002.html>