All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liviu Ionescu <ilg@livius.net>
To: Tsung-Han Lin <tsunghan.tw@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-arm <qemu-arm@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] target-arm: fix semihosting ram base issue
Date: Sat, 18 Jun 2016 08:57:53 +0300	[thread overview]
Message-ID: <630F50C7-F9D7-457A-8FEA-62CBED76E86F@livius.net> (raw)
In-Reply-To: <CA+BS1oGcMDdG_j9M6zMV3gqV-Gjg=rEMdkCSzp3J=VXw5bu7QA@mail.gmail.com>


> On 18 Jun 2016, at 01:22, Tsung-Han Lin <tsunghan.tw@gmail.com> wrote:
> 
> ... It seems like to me that the issue is the default address assumed by qemu, which is 0x0.
> (since Eclipse QEMU uses the same code, I believe they have the same problem.)

it uses the same main code, but with many improvements. 

if I remember right, for semihosting there were several small problems requiring changes, but they were all fixed now. you can give it a try (http://gnuarmeclipse.github.io/qemu/options/).

in addition to semihosting, which I use for running the CMSIS++ tests, GNU ARM Eclipse QEMU also implements graphical animated LEDs for a selection of boards, which might be very convenient for simple blinky tests.


regards,

Liviu

  reply	other threads:[~2016-06-18  5:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  2:37 [Qemu-devel] [RFC] target-arm: fix semihosting ram base issue Tsung-Han Lin
2016-06-17  8:43 ` Peter Maydell
2016-06-17  9:21   ` Tsung-Han Lin
2016-06-17 16:22 ` Liviu Ionescu
2016-06-17 22:22   ` Tsung-Han Lin
2016-06-18  5:57     ` Liviu Ionescu [this message]
2016-06-18  6:11       ` Tsung-Han Lin
2016-06-23 17:26 ` Peter Maydell
2016-06-24 15:46   ` Peter Maydell
2016-06-24 15:55   ` Tsung-Han Lin

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=630F50C7-F9D7-457A-8FEA-62CBED76E86F@livius.net \
    --to=ilg@livius.net \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=tsunghan.tw@gmail.com \
    /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.