From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] MIPS emulation
Date: Fri, 4 Jul 2008 03:44:17 +0100 [thread overview]
Message-ID: <20080704024417.GP7007@networkno.de> (raw)
In-Reply-To: <200807032102.50356.luke@dashjr.org>
Luke -Jr wrote:
> On Saturday 28 June 2008, Thiemo Seufer wrote:
> > Luke -Jr wrote:
> > > On Friday 27 June 2008, Luke -Jr wrote:
> > > > Is it possible to just emulate a MIPS CPU without any kind of ELF
> > > > loader/BIOS/boot process, ideally letting me watch/debug the
> > > > instruction flow and registers?
> > >
> > > In particular, I get this log output when I try to boot a flash image:
> > >
> > > cpu_mips_handle_mmu_fault pc bfc00000 ad bfc00000 rw 2 mmu_idx 0 smmu 1
> > > cpu_mips_handle_mmu_fault address=bfc00000 ret 0 physical 1fc00000 prot 3
> > > do_raise_exception_err: 15 0
> > > do_interrupt enter: PC bfc00000 EPC 00000000 instruction bus error
> > > exception do_interrupt: PC bfc00380 EPC bfc00000 cause 6
> > > S 00400006 C 00000418 A 00000000 D 00000000
> > > do_raise_exception_err: 15 0
> > > do_interrupt enter: PC bfc00380 EPC bfc00000 instruction bus error
> > > exception do_interrupt: PC bfc00380 EPC bfc00000 cause 6
> > > S 00400006 C 00000418 A 00000000 D 00000000
> >
> > An "instruction bus error" means Qemu wasn't able to fetch an instruction
> > from address 0xbfc00000, which should correspond to the very begin of
> > your flash image. This looks like your Qemu build is broken for some
> > reason. Did you build with gcc4, per chance?
>
> Just tried and got this same thing with a vanilla checkout of trunk compiled
> with GCC 3.4.6...
Well, the -pflash option works well enough for me to execute the first
instructions of a YAMON or redboot image. I figure you'll have to chase
this down yourself with the help of gdb. (The IBE is triggered by the
do_unassigned_access call in exec-all.h:get_phys_addr_code.)
Thiemo
next prev parent reply other threads:[~2008-07-04 2:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 18:50 [Qemu-devel] MIPS emulation Luke -Jr
2008-06-28 14:01 ` Luke -Jr
2008-06-28 19:39 ` Thiemo Seufer
2008-06-28 22:12 ` Luke -Jr
2008-07-04 2:02 ` Luke -Jr
2008-07-04 2:44 ` Thiemo Seufer [this message]
2008-07-04 3:27 ` Luke -Jr
2008-07-06 1:45 ` Luke -Jr
2008-07-06 4:52 ` Thiemo Seufer
2008-07-06 5:12 ` Luke -Jr
2008-07-07 1:46 ` Luke -Jr
2008-07-07 18:08 ` Luke -Jr
2008-07-08 4:13 ` [Qemu-devel] mapping devices to 0xfffe0000+ Luke -Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080704024417.GP7007@networkno.de \
--to=ths@networkno.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.