From: Dan Malek <dan@netx4.com>
To: "Brown, David (dbrown03)" <DBrown03@harris.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: kgdb and GetDebugChar/PutDebugChar
Date: Tue, 25 Apr 2000 18:15:42 -0400 [thread overview]
Message-ID: <3906190E.5E7C6215@embeddededge.com> (raw)
In-Reply-To: BE1C564723B3D21191FD0000F840E39801D814D4@rfcmx2.rfc.comm.harris.com
"Brown, David (dbrown03)" wrote:
> When KGDB is enabled, no GetDebugChar/PutDebugChar functions exist.
If KGDB works in the rest of the kernel, the functions are there.
> Surely, someone here has done that for the ppc8xx, using maybe SMC2?
It exists in the MontaVista 2.2.13 kernel, and in the 2.3.99 kernel.
The latter is better because it starts very early in the boot, and
you can debug almost anything in the kernel (except stepping over
instructions that disable the interrupts). I will back port the
2.3.xx into the 2.2.14 kernel shortly, or you can do it and send
me the patches.
It uses SMC1 because it is convenient, and it allows debugging
data comm or other features that use SMC2. When you boot a kernel
that uses KGDB, you provide the initial console input to the Linux
prompt, then disconnect your terminal emulator from the serial port,
and start up GDB on the serial port.
You can also use XMON, which is sometimes more useful that gdb.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-04-25 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-25 21:33 kgdb and GetDebugChar/PutDebugChar Brown, David (dbrown03)
2000-04-25 22:15 ` 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=3906190E.5E7C6215@embeddededge.com \
--to=dan@netx4.com \
--cc=DBrown03@harris.com \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.