qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Christopher Covington <cov@codeaurora.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] AArch64 ELF File Loading
Date: Fri, 25 Jul 2014 15:07:25 +0100	[thread overview]
Message-ID: <CAFEAcA8JMu=tqMtpMu9u4_N_-ooUeeWME62iiMXCdWL0M+TLpQ@mail.gmail.com> (raw)
In-Reply-To: <53D2632D.4070700@codeaurora.org>

On 25 July 2014 15:01, Christopher Covington <cov@codeaurora.org> wrote:
> Hi,
>
> I think the AArch64 port has a problem with a self-modifying code sequence
> that appears to run fine on other simulators, but I can't get QEMU to run the
> small bare metal test case I created to try to reproduce the issue. Any help
> would be appreciated.
>
> qemu-system-aarch64 -nodefaults -nographic -monitor none -M virt -semihosting
> -d exec,in_asm /tmp/test-nooverwrite 2>&1 | less
>
> qemu: fatal: Trying to execute code outside RAM or ROM at 0x0000000000000000
>
> qemu-system-aarch64 -nodefaults -nographic -monitor none -M virt -semihosting
> -d exec,in_asm -bios /tmp/test-nooverwrite 2>&1 | less
>
> qemu: fatal: Trying to execute code outside RAM or ROM at 0x0000000000000000
>
> qemu-system-aarch64 -nodefaults -nographic -monitor none -M virt -semihosting
> -d exec,in_asm -kernel /tmp/test-nooverwrite 2>&1 | less

You haven't specified a CPU type, and virt defaults
to cortex-a15. Try "-cpu cortex-a57".

You haven't specified a memory size, and QEMU defaults
to 128MB, which (given the start address of RAM) means
there won't be any RAM at the load address you're trying to
load your test program at. Try "-m 3G", and/or make your
ELF file load at an address closer to the start of RAM.

thanks
-- PMM

  reply	other threads:[~2014-07-25 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25 14:01 [Qemu-devel] AArch64 ELF File Loading Christopher Covington
2014-07-25 14:07 ` Peter Maydell [this message]
2014-07-25 14:35   ` Christopher Covington
2014-07-25 14:41     ` Peter Maydell
2014-07-25 15:05       ` Christopher Covington
2014-07-25 15:17         ` Peter Maydell

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='CAFEAcA8JMu=tqMtpMu9u4_N_-ooUeeWME62iiMXCdWL0M+TLpQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=cov@codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).