[ELDK] BDI-2000 debugging

[Markus Klotzbücher]

Hi Anthony,

Anthony Jones <ajones at clear.net.nz> writes:

> I am using ELDK 4.2 and trying to debug my 2.6.24.2 kernel
> using a BDI-2000 on an MPC852T. I can step through the
> kernel before it initialises the MMU but not after (see
> below). The kernel is working OK but I can't get the
> debugging to work. I have set both CONFIG_DEBUG_INFO=y and
> CONFIG_BDI_SWITCH=y.

Ok.

> I think this is the relevant section of the BDI config file:
>
> [TARGET]
> CPUCLOCK    50000000            ;the CPU clock rate after
> processing the init list
> BDIMODE     AGENT               ;the BDI working mode
> (LOADONLY | AGENT)
> BREAKMODE   HARD                ;SOFT or HARD, HARD uses PPC
> hardware breakpoints
> MMU         XLAT                ;translate effective to
> physical address
> PTBASE      0x000000f0

Looks good to me.

> I'm using firmware 1.13 and logic version 1.02
>
> I'm not sure what else I need to check.
>
> Anthony
>
> // transcript of gdb session
>
> GNU gdb Red Hat Linux (6.7-1rh)
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and
> redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type
> "show copying"
> and "show warranty" for details.
> This GDB was configured as "--host=i686-pc-linux-gnu
> --target=ppc-linux".
> The target architecture is set automatically (currently
> powerpc:common)
> ..
> 0x00000100 in ?? ()
> (gdb) b start_here
> Breakpoint 1 at 0xc0002004
> (gdb) c
> Continuing.
>
> Breakpoint 1, 0xc0002004 in start_here ()

The MMU is running here already, so where is it that you say debugging
is working?

> (gdb) si
> 0xc0002008 in start_here ()
> (gdb) si
> 0xc000200c in start_here ()
> (gdb) si
> 0xc0002010 in start_here ()
> (gdb) si
> 0xc0002014 in start_here ()
> (gdb) si
> 0xc0002018 in start_here ()
> (gdb) si
> 0xc000201c in start_here ()
> (gdb) si
> 0xc0002020 in start_here ()

Are you *really* sure you compiled your kernel with debug information?
It doesn't seem so here, otherwise I would expect to see more
information.

Best regards

Markus Klotzbücher

--
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de