Date: Thu, 29 Dec 2016 05:12:58 -0800 From: Jason Harmening <jason.harmening@gmail.com> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: freebsd-arm@freebsd.org Subject: Re: loading 'VIRT' kernel in qemu Message-ID: <CAM=8qa=RZJvRXX1H3hWS%2BSnOv_Hxnp=6P71SE%2Bt6d6D9Kbxx8A@mail.gmail.com> In-Reply-To: <BA5B89E5-9187-4BD3-A036-554F3CF6F671@bluezbox.com> References: <CAM=8qa=pSRphmsbvy1L7fgPFDDK4xhozfrr3tj5fojd8w7fFjg@mail.gmail.com> <BA5B89E5-9187-4BD3-A036-554F3CF6F671@bluezbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 28, 2016 at 11:25 AM, Oleksandr Tymoshenko <gonzo@bluezbox.com> wrote: > > On Dec 27, 2016, at 1:48 PM, Jason Harmening <jason.harmening@gmail.com> > wrote: > > Hi everyone, > > I'm making some tweaks to the armv6 pmap to mirror some recent i386 > changes. I don't have arm hardware readily available, so I thought I'd > give qemu a whirl instead of asking other people to test my changes for > me. Since I need SMP but don't need any specific peripheral hw, the 'VIR= T' > kernel seems like my best bet. > > I've successfully booted mips[64] under qemu, so naively starting out w/ > the same steps I use for mips: > > 1). build armv6 world and VIRT kernel, install world to temp directory > 2). use makefs(8) to build a 4GB (little endian) fs image from temp dir > 3). Run qemu: > qemu-system-arm -M virt -kernel <VIRT kernel binary> -hda <fs image> > -nographic -m 1024 > > ...fails immediately: > qemu: fatal: Trying to execute code outside RAM or ROM at 0xc1000100 > > R00=3D00000000 R01=3D00000000 R02=3D00000000 R03=3D00000000 > R04=3D00000000 R05=3D00000000 R06=3D00000000 R07=3D00000000 > R08=3D00000000 R09=3D00000000 R10=3D00000000 R11=3D00000000 > R12=3D00000000 R13=3D00000000 R14=3D00000000 R15=3Dc1000100 > > hmm, looks pretty close to KERNVIRTADDR. > > Most online docs for qemu-system-arm seem to assume a prebuilt linux kern= el > and initrd, the rest are...fragmented-to-nonexistent. I've seen a few > hints that I might need to wrap the kernel image up along w/ u-boot, but > the u-boot images seem to be very SoC-specific. > > Any help would be much appreciated, sorry for the n00b question. > > > Hi Jason, > > It looks like for VIRT kernel is supposed to be used with UEFI. At least > this part of NanoBSD sources hints at it: > http://sources.freebsd.org/HEAD/src/tools/tools/nanobsd/ > embedded/qemu-armv7.cfg > You can probably use NanoBSD-generated image for your experiments > Ah, thanks! That should make things a good deal easier. Using the nanobsd-generated images and the qemu invocation from qemu-armv7.cfg, I get a bit further but end up with a repeating prefetch abort: Prefetch Abort Exception PC at 0xFF176790 CPSR 0x80000113 This is either in UEFI or very early in kernel bootstrap, since the copyright hasn't printed yet...haven't poked at it to figure out where the pc comes from yet. > VERSATILEPB kernel used to work with QEMU but I=E2=80=99ve just tried to = boot > it and it doesn=E2=80=99t seem to work. Will need some time to track down= what=E2=80=99s > wrong > with it. VERSATILEPB kernel needs a wrapper to make it act as a ROM > image. Wrapper and command to run it you can find here: > https://github.com/freebsd/crochet/blob/master/board/VersatilePB/setup.sh > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAM=8qa=RZJvRXX1H3hWS%2BSnOv_Hxnp=6P71SE%2Bt6d6D9Kbxx8A>