From: Joel Sherrill <joel@rtems.org>
To: Joel Sherrill <joel@rtems.org>,
Eli Zaretskii via Gdb <gdb@sourceware.org>,
Newlib <newlib@sourceware.org>
Subject: Re: Microblaze libgloss and gdb simulator
Date: Thu, 22 Apr 2021 19:55:16 -0500 [thread overview]
Message-ID: <CAF9ehCUknPRXc=WKOP+cNtTFhhMydD+yiqrg58-O-j5LS=cOMg@mail.gmail.com> (raw)
In-Reply-To: <YIIUh15eb5YVOr0F@vapier>
On Thu, Apr 22, 2021, 7:27 PM Mike Frysinger <vapier@gentoo.org> wrote:
> 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.
>
I assumed that as well. At least their code on GitHub is now mostly
permissive licenses. I just haven't figured out what precisely that library
would be. I found a directory named xil which I assume is promising.
> ignoring that, the microblaze sim doesn't have syscall support hooked up.
> so
> it's only a CPU simulator atm.
>
So it has no output whatsoever? Does it get used for anything?
We are resurrecting some old work that I did for a Microblaze port. I did
write an inbyte() and outbyte() which would normally come from the xil
library. But I don't have any idea how I figured out there was a uart at a
particular address. I swear I had it working to print then but now it
faults after the first instruction.
Is there any known good executable for it? Even just seeing it operate with
a linked executable that had a crt0 and did something would be helpful at
this point.
--joel
-mike
>
next prev parent reply other threads:[~2021-04-23 0:55 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
2021-04-23 0:55 ` Joel Sherrill [this message]
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='CAF9ehCUknPRXc=WKOP+cNtTFhhMydD+yiqrg58-O-j5LS=cOMg@mail.gmail.com' \
--to=joel@rtems.org \
--cc=gdb@sourceware.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).