Hi Maurizio,
you could try to make the system image smaller. Try selecting a barebone build.
I think that might remove gxe_bd, though, so you need to edit
boot/Makefile.common and add it to the list of essential servers, probably.
Hope this helps,
Jiri
Hello Maurizio,
> I've built HelenOS for gxemul mips32 (big endian) but I encountered a
> problem while trying to boot the OS.
>
> The HelenOS bootloader starts, it prints some memory statistics, it
> prints "Inflanting components ... initrd" and finally it hangs.
> I'm using gxemul version 0.6.0 and I call it with these arguments:
>
> $./gxemul -X -E oldtestmips image.boot
>
> Am I doing something wrong?
You are most probably not doing anything wrong. The problem seems to be
related to this:
http://lists.modry.cz/cgi-bin/private/helenos-devel/2011-October/007814.html
In a nutshell, the boot image size exceeds 4 MB which is the largest
size that can fit naturally into the firmware (ROM) memory area on MIPS.
To overcome this limitation on MIPS it is required to completely
redesign the bootstrap process, preferably by utilizing a standard boot
loader (e.g. U-Boot or GRUB 2) and load the kernel and init binaries
from a disk device.
However, this is not as simple as it seems. MSIM currently supports only
a limited block device and I am not sure about the disk support in
GXemul. A grand plan would be to properly support some decent MIPS-based
hardware (e.g. Ben NanoNote, some of the Lemote machines, etc.) and
their emulated counterparts in QEMU.
M.D.
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
