* kgdb on mpc834x
@ 2006-12-13 0:11 Reeve Yang
2006-12-13 4:00 ` Hollis Blanchard
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Reeve Yang @ 2006-12-13 0:11 UTC (permalink / raw)
To: linuxppc-dev
I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
patch for 2.6.14), but gdb client cannot connec to it. I turn on all
necessary kernel hacking options. Our board is customized with
MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me
out? Following are the message from linux boot and gdb client.
## Booting image at ff300000 ...
loaded at: FF300000 FFB71124
relocated to: 00800000 01071124
board data at: 007FFF70 007FFFF8
relocated to: 00805114 0080519C
zimage at: 00805915 00926A5E
initrd at: 00927000 0106E242
avail ram: 01072000 01472000
Linux/PPC load: mem=248M
Uncompressing Linux...done.
Now booting the kernel
mpc834x_sys_init(): exit
id mach(): done
MMU:enter
MMU:hw init
MMU:mapin
MMU:setio
MMU:exit
setup_arch: enter
setup_arch: bootmem
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Malformed response to offset query, timeout
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: kgdb on mpc834x
2006-12-13 0:11 kgdb on mpc834x Reeve Yang
@ 2006-12-13 4:00 ` Hollis Blanchard
2006-12-14 1:08 ` Reeve Yang
2006-12-13 6:18 ` Vitaly Wool
2006-12-13 17:21 ` Geoff Levand
2 siblings, 1 reply; 7+ messages in thread
From: Hollis Blanchard @ 2006-12-13 4:00 UTC (permalink / raw)
To: Reeve Yang; +Cc: linuxppc-dev
On Wed, 2006-12-13 at 00:11 +0000, Reeve Yang wrote:
> I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
> patch for 2.6.14), but gdb client cannot connec to it. I turn on all
> necessary kernel hacking options. Our board is customized with
> MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me
> out? Following are the message from linux boot and gdb client.
>
> ## Booting image at ff300000 ...
>
> loaded at: FF300000 FFB71124
> relocated to: 00800000 01071124
> board data at: 007FFF70 007FFFF8
> relocated to: 00805114 0080519C
> zimage at: 00805915 00926A5E
> initrd at: 00927000 0106E242
> avail ram: 01072000 01472000
>
> Linux/PPC load: mem=248M
> Uncompressing Linux...done.
> Now booting the kernel
> mpc834x_sys_init(): exit
> id mach(): done
> MMU:enter
> MMU:hw init
> MMU:mapin
> MMU:setio
> MMU:exit
> setup_arch: enter
> setup_arch: bootmem
>
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Malformed response to offset query, timeout
Try 'set debug serial 1' in GDB; it will show you the actual data GDB is
receiving.
-Hollis
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: kgdb on mpc834x
2006-12-13 4:00 ` Hollis Blanchard
@ 2006-12-14 1:08 ` Reeve Yang
2006-12-14 6:22 ` Vitaly Wool
2006-12-14 15:13 ` Jimi Xenidis
0 siblings, 2 replies; 7+ messages in thread
From: Reeve Yang @ 2006-12-14 1:08 UTC (permalink / raw)
To: Hollis Blanchard; +Cc: linuxppc-dev
I set "debug serial 1" in gdb, now I'm seeing message like this
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
[
r <Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
[<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
[<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
Malformed response to offset query, timeout
Does it tell any information?
On 12/13/06, Hollis Blanchard <hollis@penguinppc.org> wrote:
> On Wed, 2006-12-13 at 00:11 +0000, Reeve Yang wrote:
> > I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
> > patch for 2.6.14), but gdb client cannot connec to it. I turn on all
> > necessary kernel hacking options. Our board is customized with
> > MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me
> > out? Following are the message from linux boot and gdb client.
> >
> > ## Booting image at ff300000 ...
> >
> > loaded at: FF300000 FFB71124
> > relocated to: 00800000 01071124
> > board data at: 007FFF70 007FFFF8
> > relocated to: 00805114 0080519C
> > zimage at: 00805915 00926A5E
> > initrd at: 00927000 0106E242
> > avail ram: 01072000 01472000
> >
> > Linux/PPC load: mem=248M
> > Uncompressing Linux...done.
> > Now booting the kernel
> > mpc834x_sys_init(): exit
> > id mach(): done
> > MMU:enter
> > MMU:hw init
> > MMU:mapin
> > MMU:setio
> > MMU:exit
> > setup_arch: enter
> > setup_arch: bootmem
> >
> > (gdb) target remote /dev/ttyS0
> > Remote debugging using /dev/ttyS0
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Malformed response to offset query, timeout
>
> Try 'set debug serial 1' in GDB; it will show you the actual data GDB is
> receiving.
>
> -Hollis
>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: kgdb on mpc834x
2006-12-14 1:08 ` Reeve Yang
@ 2006-12-14 6:22 ` Vitaly Wool
2006-12-14 15:13 ` Jimi Xenidis
1 sibling, 0 replies; 7+ messages in thread
From: Vitaly Wool @ 2006-12-14 6:22 UTC (permalink / raw)
To: Reeve Yang; +Cc: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On 12/14/06, Reeve Yang <yang.reeve@gmail.com> wrote:
>
> I set "debug serial 1" in gdb, now I'm seeing message like this
>
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> [
> r <Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
> [<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
> [<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
> Malformed response to offset query, timeout
>
> Does it tell any information?
>
Yes. Apparently your kernel command line is wrong.
Vitaly
[-- Attachment #2: Type: text/html, Size: 1365 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: kgdb on mpc834x
2006-12-14 1:08 ` Reeve Yang
2006-12-14 6:22 ` Vitaly Wool
@ 2006-12-14 15:13 ` Jimi Xenidis
1 sibling, 0 replies; 7+ messages in thread
From: Jimi Xenidis @ 2006-12-14 15:13 UTC (permalink / raw)
To: Reeve Yang; +Cc: linuxppc-dev
On Dec 13, 2006, at 8:08 PM, Reeve Yang wrote:
> I set "debug serial 1" in gdb, now I'm seeing message like this
>
I think you really want to use "set debug remote" to debug the protocol
there are also several "set remote*" gdb command that can help you
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> [
> r <Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
> [<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
> [<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>][<Timeout: 2 seconds>][<Timeout: 2
> seconds>][<Timeout: 2 seconds>]Ignoring packet error, continuing...
> Malformed response to offset query, timeout
>
> Does it tell any information?
you may also want to play with:
(gdb) set remotetimeout 0
0 == infinit, or use some really large value like 20
>
> On 12/13/06, Hollis Blanchard <hollis@penguinppc.org> wrote:
>> On Wed, 2006-12-13 at 00:11 +0000, Reeve Yang wrote:
>>> I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
>>> patch for 2.6.14), but gdb client cannot connec to it. I turn on all
>>> necessary kernel hacking options. Our board is customized with
>>> MPC834x, can someoen who used kgdb to debug kernel on MPC834x
>>> help me
>>> out? Following are the message from linux boot and gdb client.
>>>
>>> ## Booting image at ff300000 ...
>>>
>>> loaded at: FF300000 FFB71124
>>> relocated to: 00800000 01071124
>>> board data at: 007FFF70 007FFFF8
>>> relocated to: 00805114 0080519C
>>> zimage at: 00805915 00926A5E
>>> initrd at: 00927000 0106E242
>>> avail ram: 01072000 01472000
>>>
>>> Linux/PPC load: mem=248M
>>> Uncompressing Linux...done.
>>> Now booting the kernel
>>> mpc834x_sys_init(): exit
>>> id mach(): done
>>> MMU:enter
>>> MMU:hw init
>>> MMU:mapin
>>> MMU:setio
>>> MMU:exit
>>> setup_arch: enter
>>> setup_arch: bootmem
>>>
>>> (gdb) target remote /dev/ttyS0
>>> Remote debugging using /dev/ttyS0
>>> Ignoring packet error, continuing...
>>> Ignoring packet error, continuing...
>>> Ignoring packet error, continuing...
>>> Malformed response to offset query, timeout
>>
>> Try 'set debug serial 1' in GDB; it will show you the actual data
>> GDB is
>> receiving.
>>
>> -Hollis
>>
>>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: kgdb on mpc834x
2006-12-13 0:11 kgdb on mpc834x Reeve Yang
2006-12-13 4:00 ` Hollis Blanchard
@ 2006-12-13 6:18 ` Vitaly Wool
2006-12-13 17:21 ` Geoff Levand
2 siblings, 0 replies; 7+ messages in thread
From: Vitaly Wool @ 2006-12-13 6:18 UTC (permalink / raw)
To: Reeve Yang; +Cc: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
On 12/13/06, Reeve Yang <yang.reeve@gmail.com> wrote:
>
> I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
> patch for 2.6.14), but gdb client cannot connec to it. I turn on all
> necessary kernel hacking options. Our board is customized with
> MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me
> out? Following are the message from linux boot and gdb client.
>
You need to set up the kernel command line appropriately or add a breakpoint
explicitly.
Vitaly
[-- Attachment #2: Type: text/html, Size: 780 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: kgdb on mpc834x
2006-12-13 0:11 kgdb on mpc834x Reeve Yang
2006-12-13 4:00 ` Hollis Blanchard
2006-12-13 6:18 ` Vitaly Wool
@ 2006-12-13 17:21 ` Geoff Levand
2 siblings, 0 replies; 7+ messages in thread
From: Geoff Levand @ 2006-12-13 17:21 UTC (permalink / raw)
To: Reeve Yang; +Cc: linuxppc-dev
Reeve Yang wrote:
> I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
> patch for 2.6.14), but gdb client cannot connec to it. I turn on all
> necessary kernel hacking options. Our board is customized with
> MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me
> out? Following are the message from linux boot and gdb client.
You might have better luck posting to the kgdb mailing list, as this problem
is not specific to your platform, nor to PPC:
kgdb-bugreport@lists.sourceforge.net
-Geoff
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-12-14 15:13 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-13 0:11 kgdb on mpc834x Reeve Yang
2006-12-13 4:00 ` Hollis Blanchard
2006-12-14 1:08 ` Reeve Yang
2006-12-14 6:22 ` Vitaly Wool
2006-12-14 15:13 ` Jimi Xenidis
2006-12-13 6:18 ` Vitaly Wool
2006-12-13 17:21 ` Geoff Levand
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).