From: Geoffrey Espin <espin@idiom.com>
To: "Siders, Keith" <keith_siders@toshibatv.com>
Cc: "Linux-Mips (E-mail)" <linux-mips@oss.sgi.com>
Subject: Re: Debugging of embedded target applications
Date: Tue, 7 May 2002 15:33:51 -0700 [thread overview]
Message-ID: <20020507153351.B12509@idiom.com> (raw)
In-Reply-To: <7DF7BFDC95ECD411B4010090278A44CA379AA1@ATVX>; from Siders, Keith on Tue, May 07, 2002 at 05:05:36PM -0500
On Tue, May 07, 2002 at 05:05:36PM -0500, Siders, Keith wrote:
> I am using x86 Linux for host development to a MIPS Linux embedded target. I
> finally have a hardware debugger for my target board that works, but I have
> to get large application files downloaded in a timely fashion. The debugger
> must download to the target via JTAG, therefore downloads have lots of bits
> of overhead, i.e. downloads are slow. Is there anything like a gdb server
> that can I run on the target to connect to a remote client via ethernet? I
If you have a Linux Ethernet driver working, then most people
boot and mount with an NFS root disk. Then you just cross-compile
additional apps and tools and adding to your NFS disk. Presumably
including gdb (not tried it). Then just debug "normally" -- with
the CLI. The JTAG hardware debugger is not used (or maybe just
to initially bootstrap the kernel and trap certain exceptions).
RH7.1 fs at: ftp://ftp.linux.sgi.com/pub/linux/mips/mipsel-linux/root/
And see: http://www.linux.sgi.com/downloads.html
Once your basic apps are complete, then you can think about
creating a JFFS2 partition (after the MTD flash driver's debuggged)
and using that for standalone bootup.
Actually, my first approach was to flash the linux kernel with
just a cramfs'd busybox and then NFS mount my home directory from
a startup script.
To save (a lot of) space in applications checkout uclibc.org.
Shared libs support with uclibc is real close for MIPS, but for
now use static linking.
Geoff
--
Geoffrey Espin
espin@idiom.com
--
next prev parent reply other threads:[~2002-05-07 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 22:05 Debugging of embedded target applications Siders, Keith
2002-05-07 22:15 ` Daniel Jacobowitz
2002-05-07 22:44 ` Geoffrey Espin
2002-05-08 1:43 ` Daniel Jacobowitz
2002-05-08 2:25 ` Geoffrey Espin
2002-05-08 2:32 ` Daniel Jacobowitz
2002-05-08 18:16 ` Jun Sun
2002-05-07 22:33 ` Geoffrey Espin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-08 13:05 Siders, Keith
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=20020507153351.B12509@idiom.com \
--to=espin@idiom.com \
--cc=keith_siders@toshibatv.com \
--cc=linux-mips@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox