[ELDK] BDI-2000 debugging

Anthony Jones ajones at clear.net.nz
Tue May 20 01:43:33 CEST 2008

I am using ELDK 4.2 and trying to debug my 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

I think this is the relevant section of the BDI config file:

CPUCLOCK    50000000            ;the CPU clock rate after
processing the init list
BDIMODE     AGENT               ;the BDI working mode
BREAKMODE   HARD                ;SOFT or HARD, HARD uses PPC
hardware breakpoints
MMU         XLAT                ;translate effective to
physical address
PTBASE      0x000000f0

I'm using firmware 1.13 and logic version 1.02

I'm not sure what else I need to check.


// 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
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
The target architecture is set automatically (currently
0x00000100 in ?? ()
(gdb) b start_here
Breakpoint 1 at 0xc0002004
(gdb) c

Breakpoint 1, 0xc0002004 in start_here ()
(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 ()
(gdb) b start_kernel
Breakpoint 2 at 0xc02007f4: file init/main.c, line 513.
(gdb) c

Breakpoint 2, start_kernel () at init/main.c:513
513		smp_setup_processor_id();
(gdb) si
start_kernel () at init/main.c:513
513		smp_setup_processor_id();
Cannot access memory at address 0xc02007f4

More information about the eldk mailing list