From mboxrd@z Thu Jan  1 00:00:00 1970
From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
Date: Sun, 23 Dec 2007 18:06:16 +0900
Subject: [U-Boot-Users] Target support for qemu -M mips
In-Reply-To: <4766A944.90300@comsys.ro>
References: <47666359.3060702@comsys.ro> <47669CB5.8040801@ruby.dti.ne.jp>
	<4766A944.90300@comsys.ro>
Message-ID: <476E2508.5020909@ruby.dti.ne.jp>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Vlad Lungu wrote:
> 
> make qemu_mips_config ; make
> 
> Copy (or symlink) u-boot.bin to mips_bios.bin and launch
> qemu-system-mips -L . /dev/null
> -L . so that qemu picks the BIOS from the current directory and
> /dev/null because qemu wants a disk image. Qemu willl load and launch 
> U-Boot.

$ cd u-boot.git
$ make distclean
$ make qemu_mips_config
$ make CROSS_COMPILE=mips-linux-
$ cp -a u-boot.bin mips_bios.bin
$ qemu-system-mips -L . /dev/nulll

at this point, qemu console window appears but I can't see any u-boot's
bootlog. I tried qemu on Debian testing or the latest CVS, but the same
results.

I use u-boot-1.3.1 + qemu patch, gcc 4.2.1 and binutils 2.18.50.0.1.

Am I miss something?

  Shinya

> Add -hda file.img to Qemu cmd line  in order to emulate a hard-disk and do
> ide reset
> at the U-Boot prompt ; the disk (or disks) should be identified. Check 
> U-Boot doc for booting fromHD :-)
> 
> Add -tftp / and then do dhcp (or directly tftp) and then bootelf (on 
> vmlinux) or bootm (on uimage).
> 
> Main purpose is to be able to develop U-Boot modules with no hardware. 
> Secondary is for me to learn how it works :-) in order
> to develop a free BIOS for the MTI Malta board, as emulated by Qemu 
> (comes with PCI and stuff). Or even for the real board. I have that
> sort-of-working too, but I'm not very happy with  the PCI bus driver .