From: Wolfgang Denk <wd@denx.de>
To: Subodh Nijsure <subodh@best.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Booting linux kernel.
Date: Wed, 03 Jan 2001 22:05:13 +0100 [thread overview]
Message-ID: <200101032105.f03L5DY24101@denx.local.net> (raw)
In-Reply-To: Your message of "Wed, 03 Jan 2001 12:42:19 PST." <200101032042.MAA17739@shell9.ba.best.com>
In message <200101032042.MAA17739@shell9.ba.best.com> you wrote:
>
> I have a custom 860T based board for which I have ppcboot 0.7, register
...
> When I boot the kernel don't see anything on the console, I have the
> boardinfo structure below.
Which board configuration did you chose when building the Linux
kernel, and did you really make sure that machine specific header
file (include/asm-ppc/????) includes the same definition of the Board
Information structure as we use in PPCBoot, and that IMAP_ADDR uses
the same value as your PPCBoot configuration in CFG_IMMR?
> I guess simple question is how do I go about debugging this problem?
...
> Only tools I have is ppc_8xx-gdb and the Macraigor wiggler to which I
> can connect using rproxy. Is there a better tool that I should acquire
> that will help me in debugging this?
If you don't get any communication working at all you need a BDM
debugger, and one that supports the MMU. AFAIK the software that
comes with the wiggler does not.
I know of two working solutions for MMU-capable BDM/JTAG debuggers:
- The BDI2000 by Abatron is the commercial solution; it supports fast
flash programming, provides a telnet interface and talks remote GDB
protocol over the network, so it fits ideally in a Linux based
development environment. For details see www.abatron.ch
- The BDM4GDB project at SourceForge is the Open Source approach to
the same problem. You can build a small adapter that attaches to
the parallel port, and the rest is done in software as a GDB
extension. You have the same debugging capabilities, but are
restricted as you have to use a parallel port on a PC. Also, only
few flash types are supported (but it's easy to add new ones). See
the mailng list at bdm4gdb-users@lists.sourceforge.net. If you
cannot build the (simple) PCB for the adapter yourself, we sell
limited quantities at production cost (< $ 50).
Feel free to contact me for a quote for the BDM4GDB adapter and/or
the BDI2000.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Above all else -- sky.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-03 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 20:42 Booting linux kernel Subodh Nijsure
2001-01-03 21:05 ` Wolfgang Denk [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=200101032105.f03L5DY24101@denx.local.net \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=subodh@best.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).