From: Vitaly Bordug <vbordug@ru.mvista.com>
To: sudheer <urwithsudheer@gmail.com>
Cc: kernelnewbies@nl.linux.org, linuxppc-embedded@ozlabs.org
Subject: Re: regarding kgdb in ppc
Date: Tue, 23 Jan 2007 11:49:17 +0300 [thread overview]
Message-ID: <20070123114917.5668a578@localhost.localdomain> (raw)
In-Reply-To: <45B5A499.4060401@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3649 bytes --]
On Tue, 23 Jan 2007 11:30:57 +0530
sudheer wrote:
> Vijay Sampath wrote:
> > Sorry no idea. The configuration and options for kgdb are different
> > in my architecture. In make menuconfig, under "Kernel Hacking', I
> > enable kgdb and choose its serial port (ttyS0 or ttyS1). After this
> > if I just pass a string with "kgdb" in it in the commandline, it
> > halts early on. Looks like kgdb function is different in your
> > architecture. You will have to read the code that implements your
> > kgdb setup. Clearly it is not happy with the arguments you are
> > passing it, as evident in the output.
> >
> > BTW I am using Linux kernel version 2.6.16 on a IBM405EP board. kgdb
> > breakpoint is setup in setup_arch() in arch/ppc/kernel/setup.c.
> > Note I also enabled CONFIG_WANT_EARLY_SERIAL in the processor
> > configuration. Not sure if this is important.
> >
> In my setup i have one serial port on the target(MPC8540) and one on
> host(x86). The document(kgdb_docu_full-2.4.pdf) by default considers
> having two serial ports(two on target and two on host).
>
To be correct, usually one serial is for serial console, the other-for kgdb. Yet you can either disable serial console, or
have its output into kgdb. host requires only one serial to be tied on ppc_85xx-gdb.
> Can anyone plz guide me how to proceed when i have only one serial
> port . ?
>
having one serial is not a comfy case for serial kgdb.
> I want to know the initilization steps for estrablishing the serial
> communication between kgdb(in target) and gdb on host. I tried one or
> two ways but couldnot succeed.
I'd consider kgdboe - it works pretty well with 8540 gianfar (or at least used to work for me so tinkering might be trivial).
>
> Thanks
> Sudheer
> > Vijay
> >
> > On 12/30/06, sudheer <urwithsudheer@gmail.com> wrote:
> >> Vijay, Thanks for the reply.
> >> But before trying these options i want to clear one more issue.
> >> While booting the kgdb kernel the kernel claims "kgdb
> >> initialisation failure." I have observed it very lately.
> >>
> >> Memory CAM mapping: CAM0=256Mb, CAM1=0Mb, CAM2=0Mb residual: 0Mb
> >> Linux version 2.6.15.5 (root@Sudheer) (gcc version 3.4.4) #2 Fri
> >> Dec 29 17:58:40 IST
> >> 2006
> >> KGDB cannot initialize I/O yet.
> >> Invalid syntax for option kgdb8250=
> >> Malformed early option 'kgdb8250'
> >> Built 1 zonelists
> >> Kernel command line: console=ttyS0,115200 root=/dev/ram rw
> >> kgdbwait kgdb8250=0,115200
> >> OpenPIC Version 1.2 (1 CPUs and 60 IRQ sources) at fcfbb000
> >> PID hash table entries: 2048 (order: 11, 32768 bytes)
> >> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> >>
> >>
> >>
> >>
> >> I have changed the kgdb8250 arg to 1,0, but the result is same.
> >> And ......
> >> I have checked the serial cable NULL Mode connecting x86 systems
> >> serially- with Cat and echo and this is fine.
> >> When i try with Unpatched kernel on target and host(x86) - cat <
> >> /dev/ttyS0 doesnt wait and returns to prompt.
> >> I tried with 2.6.13 and 2.6.15.5 with resepective kgdb patches,
> >> but the result is same (kgdb Initialization failure). I am not
> >> sure where am doing the mistake.
> >> Please guide me in right way and also please let me know if any
> >> more details are required.
> >> Happy New Year in Advance.
> >>
> >> Thanks
> >> Sudheer
> >>
> >>
> >>
> >>
>
>
> >>
> >>
> >
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-23 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 16:20 regarding kgdb in ppc Anumolu Sudheer
2006-11-30 4:33 ` Anumolu Sudheer
[not found] ` <d16b1c80611300036x36ec0009r2eb20ebbc6966a97@mail.gmail.com>
[not found] ` <12c9fc1a0611300924r406e95acie5c2053c1433ab33@mail.gmail.com>
[not found] ` <d16b1c80611301101n5f9ea44died47d2ff1bac4221@mail.gmail.com>
[not found] ` <12c9fc1a0611302029h36f29943s119f8ad70b95f2c4@mail.gmail.com>
[not found] ` <12c9fc1a0612010331p2c33c048j1af6006deda14abb@mail.gmail.com>
[not found] ` <d16b1c80612010540k7600f0e1n92fadd3d539d75bf@mail.gmail.com>
[not found] ` <12c9fc1a0612040805p64f23a7bj42fd27891294dfc2@mail.gmail.com>
2006-12-24 8:20 ` sudheer
2006-12-27 14:18 ` sudheer
2006-12-29 0:34 ` Reeve Yang
2006-12-29 1:02 ` Vijay Sampath
2006-12-30 11:27 ` sudheer
2006-12-31 1:53 ` Vijay Sampath
2007-01-23 6:00 ` sudheer
2007-01-23 8:49 ` Vitaly Bordug [this message]
2007-01-23 14:47 ` sudheer
2007-01-23 14:58 ` Sergei Shtylyov
2007-01-29 11:38 ` sudheer
2007-01-29 13:00 ` Sergei Shtylyov
2007-01-31 3:39 ` sudheer
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=20070123114917.5668a578@localhost.localdomain \
--to=vbordug@ru.mvista.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=urwithsudheer@gmail.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).