From: Dan Malek <dmalek@jlc.net>
To: Richard Hendricks <ra6353@email.sps.mot.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: LinuxPPC with BDM
Date: Mon, 13 Sep 1999 13:42:28 -0400 [thread overview]
Message-ID: <37DD3784.F85402CD@jlc.net> (raw)
In-Reply-To: 37DD0BE1.5DA876F@email.sps.mot.com
Richard Hendricks wrote:
>
> The BDM runs into problems when the underlying operating system uses the
> MMUs to implement a page table.
That's the biggest one. Also, all of the BDMs I have used make
assumptions about the target environment. Things like some
monitor support and debug register settings also get in the way.
Motorola's mpc8bug is the only BDM I have found that would let
me download and run....no debug mind you, just get out of the way
and run the code. You have to make sure all of the debug is
disbled before you let it go.
> > I have been using the BDM to download kernels and running them from RAM
> > (stepping through the code, etc). Could this be the cause of the
> > strange behaviour I've seen on the ADS boards ?
Yep. You can only disable all debugging and let it go.
> ... Unfortunately it will
> > only run on a Windows machine due to the wigglers.dll which is
> > required.
I am working with a company right now developing some embedded
tools hosted on a Linux/PPC (possibly Linux/x86) that includes
a BDM interface. More interesting though is the Cygnus InSight and
GDB server I have running for application development. People
forget that it is the application that makes the difference.
Porting and compiling a kernel these days is not a challenge like
getting a real embedded product to market.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-09-13 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 6:02 LinuxPPC with BDM Brendan Simon
1999-09-13 14:36 ` Richard Hendricks
1999-09-13 17:42 ` Dan Malek [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=37DD3784.F85402CD@jlc.net \
--to=dmalek@jlc.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ra6353@email.sps.mot.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;
as well as URLs for NNTP newsgroup(s).