From: sudheer <urwithsudheer@gmail.com>
To: kernelnewbies@nl.linux.org
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: regarding kgdb in ppc
Date: Sun, 24 Dec 2006 13:50:26 +0530 [thread overview]
Message-ID: <458E384A.108@gmail.com> (raw)
In-Reply-To: <12c9fc1a0612040805p64f23a7bj42fd27891294dfc2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]
Hello All
> Hi Shakti
>
> > Then executed the command mkinird and copied and added initrd
> in the
> > grub.conf - situation is same.
> > I changed the root parameter to LABEL=/ - situation is same.
>
> Basically, block device, initrd support for ramdisk should be enabled:
> CONFIG_BLK_DEV_RAM
> CONFIG_BLK_DEV_INITRD
>
> Double check your .config file.
>
>
> I have checked all the above and are enabled in the config. I have
> tried changing the kernel command line argumnets.
>
> I get the same error saying: (All from init/main.c)
> ----
> unable to open an initial console
> No init found. Try passing init= option to kernel.
-----
I am able to debug the kernel on x86 systems. Thanks for all the support.
Now I am working with kgdb on mpc8540 board.
target kernel version - linux-2.6.13
KGDB version - linux-2.6.13-kgdb-2.3
I am getting the following error:
root@localhost sudheer]# /opt/eldk-3.1.1/usr/bin/ppc_85xx-gdb vmlinux
GNU gdb Red Hat Linux (6.3.0.0-1.21_1rh)
...
This GDB was configured as "--host=i386-redhat-linux --target=ppc-linux"...
(gdb) set remotebaud 115200
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
Ignoring packet error, continuing...
On the target side, i could see that the target kernel kgdb waiting for
host communication.
On the target board with kernel version - linux-2.6.13 , I could boot
it only after applying the patches:
1. Gain_Phy_update
2.patch-2.6.14-rc5
3.Phy_Platform_Update
The patch-2.6.14-rc5 when applied , deleted the file
arch/ppc/platforms/pcore.c and
pcore.h but the kernel boots well.
In the KGDB version - linux-2.6.13-kgdb-2.3
The ppc-lite.patch tries to modify the pcore.c which is not available.
I am not sure wether this affects the serial communication establishment.
Please help me to solve this.
Thanks
Sudheer
[-- Attachment #2: Type: text/html, Size: 2689 bytes --]
next prev parent reply other threads:[~2006-12-24 8:43 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 [this message]
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
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=458E384A.108@gmail.com \
--to=urwithsudheer@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linuxppc-embedded@ozlabs.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 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).