From: Joel Sherrill <joel@rtems.org>
To: Luis Machado <luis.machado@linaro.org>
Cc: gdb@sourceware.org
Subject: Re: Running programs on aarch64 simulator
Date: Fri, 8 May 2020 11:44:01 -0500 [thread overview]
Message-ID: <CAF9ehCXyhoofOk2uOwozwa6xeM9EeRe4Lz8ztmneDy3gVYYrYg@mail.gmail.com> (raw)
In-Reply-To: <61220f48-c08e-2da0-81ed-0ea05eb8d082@linaro.org>
On Fri, May 8, 2020 at 11:16 AM Luis Machado <luis.machado@linaro.org>
wrote:
> On 5/8/20 10:44 AM, Joel Sherrill wrote:
> > Hi
> >
> > Can someone please provide an example of how to compile a program to run
> on
> > the aarch64 simulator in gdb? The simple "aarch64-elf main.c -o main"
> does
> > not link and appears to be missing libgloss type symbols.
> >
> > I asked on newlib but got no response. I'm hoping someone here knows.
> >
> > Thanks.
> >
> > --joel
> > RTEMS
> >
>
> Would QEMU be a better option to exercise some bare-metal programs? The
> GDB simulator has not been receiving a lot of maintenance.
>
Long term it is a better option but the gdb simulators have proven more
than
sufficient to work through the basic issues of an RTEMS port and they are
quite simple to use. You can get initialization, context switch, etc.
Definitely
have to move to Qemu to get interrupts worked out and real device drivers.
--joel
prev parent reply other threads:[~2020-05-08 16:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 13:44 Joel Sherrill
2020-05-08 16:09 ` Simon Marchi
2020-05-08 16:57 ` Joel Sherrill
2020-05-08 17:17 ` Simon Marchi
2020-05-11 2:35 ` Simon Marchi
2020-05-11 14:26 ` Nick Clifton
2020-05-11 14:40 ` Joel Sherrill
2020-05-11 17:58 ` Jim Wilson
2020-05-11 18:30 ` Joel Sherrill
2020-05-11 22:13 ` Jim Wilson
2020-05-08 16:16 ` Luis Machado
2020-05-08 16:44 ` Joel Sherrill [this message]
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=CAF9ehCXyhoofOk2uOwozwa6xeM9EeRe4Lz8ztmneDy3gVYYrYg@mail.gmail.com \
--to=joel@rtems.org \
--cc=gdb@sourceware.org \
--cc=luis.machado@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).