linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: sudheer <urwithsudheer@gmail.com>
To: Vijay Sampath <vsampath@gmail.com>
Cc: kernelnewbies@nl.linux.org, linuxppc-embedded@ozlabs.org
Subject: Re: regarding kgdb in ppc
Date: Sat, 30 Dec 2006 16:57:35 +0530	[thread overview]
Message-ID: <45964D27.6020708@gmail.com> (raw)
In-Reply-To: <758a2bbf0612281702u3a4f383bi14e418410bd4f912@mail.gmail.com>

Vijay Sampath wrote:
>> >  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.
>
> You need to pass init=/path/to/initprogram and console=ttySx,9600n81
> or something similar. This will however only work if you have
> configured your root filesystem correctly. This could be a ramdisk,
> harddisk partition, flash or nfs. The method for doing each is
> different.
>
>> >  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...
>
> This probably means that gdb on host could not communicate with the
> gdb stub on target. To ensure target is running gdb stub, connect a
> terminal program (example minicom on /dev/ttyS0) and ensure you are
> getting output similar to this line: "$T0740:30300a00;01:c0621fb0;#45"
>
> If you are getting this output, you should be able to close the
> terminal program and connect gdb using the same serial port. If you
> are not getting this output, then there could be many things wrong.
> Did you try passing the kgdb=halt argument to the kernel.
>
> Vijay
>
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

  reply	other threads:[~2006-12-30 11:27 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 [this message]
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=45964D27.6020708@gmail.com \
    --to=urwithsudheer@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=vsampath@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).