From: Mike Frysinger <vapier@gentoo.org>
To: Joel Sherrill <joel@rtems.org>
Cc: gdb@sourceware.org, newlib@sourceware.org
Subject: Re: Microblaze libgloss and gdb simulator
Date: Thu, 22 Apr 2021 20:27:51 -0400 [thread overview]
Message-ID: <YIIUh15eb5YVOr0F@vapier> (raw)
In-Reply-To: <CAF9ehCWn33H3KA3T153iat2nswTRQ9K=UR1Rio_PNMne-gd4hw@mail.gmail.com> <CAF9ehCV8fPNObXbTALFFpfnOX53ZbKen-EdtNWWrsQNYekxnSQ@mail.gmail.com>
On 22 Apr 2021 17:25, Joel Sherrill wrote:
> Sorry to post to both newlib and gdb but I hope someone in one of the
> communities will have the answer.
>
> Does anyone know how to build and run a hello world on the microblaze
> simulator in gdb using the microblaze-elf target and the code in libgloss?
>
> I don't see a configuration in DejaGNU which would have given me a hint. I
> didn't see any microblaze GCC test results on that list either so that
> appears to line up.
i think the answer is you can't with only released open source projects.
the microblaze gcc config specs refer to a libxil.a that doesn't appear in gcc
or newlib or libgloss, so i assume it's a bsp thing you get from xilinx.
ignoring that, the microblaze sim doesn't have syscall support hooked up. so
it's only a CPU simulator atm.
-mike
next prev parent reply other threads:[~2021-04-23 0:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 22:25 Joel Sherrill
[not found] ` <CAF9ehCV8fPNObXbTALFFpfnOX53ZbKen-EdtNWWrsQNYekxnSQ@mail.gmail.com>
2021-04-23 0:27 ` Mike Frysinger [this message]
2021-04-23 0:55 ` Joel Sherrill
2021-04-23 1:19 ` Mike Frysinger
2021-04-24 5:02 ` Mike Frysinger
2021-04-25 17:21 ` Mike Frysinger
2021-04-25 18:37 ` Michael Eager
2021-04-25 20:27 ` Mike Frysinger
2021-04-25 22:29 ` Michael Eager
2021-04-25 23:34 ` Mike Frysinger
2021-04-26 0:44 ` Michael Eager
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=YIIUh15eb5YVOr0F@vapier \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=joel@rtems.org \
--cc=newlib@sourceware.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).