From: "Hoefle Marco" <Marco.Hoefle@nanotronic.ch>
To: <gdb@sourceware.org>
Subject: GDB Server for Xilinx Microblaze
Date: Mon, 28 Feb 2011 09:53:00 -0000 [thread overview]
Message-ID: <AE70B6C06C76584786A79592214C3E0A165668@srv01.nanotronic.local> (raw)
Hello,
we are using Linux running on a Xilinx Microblaze in a FPGA.
It runs fine but we lack proper debugging (we are doing it old school
like: printfs...),
so modern stuff like code stepping within an eclipse cdt environment
would be greatly appreciated :-)
Thus I had a look into the new GDB7.2 sources and I saw that there is
some Microblaze stuff in the GDB source itself.
So from my understanding I can use GDB 7.2 on my Debian Workstation and
all I need is to cross-compile the gdb server?
I tried it but it seems that cross-compiling the GDB Server is not a
trivial task as it looks to me that there is no support for the
Microblaze.
Can somebody instruct me how to get the GDB server running on the
Microblaze?
We are running the latest stable Mainline Linux Kernel (2.6.37) and the
GCC cross compiler is version 4.1.2.
Thanks,
Marco
next reply other threads:[~2011-02-28 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 9:53 Hoefle Marco [this message]
2011-02-28 18:20 ` Michael Snyder
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=AE70B6C06C76584786A79592214C3E0A165668@srv01.nanotronic.local \
--to=marco.hoefle@nanotronic.ch \
--cc=gdb@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