[U-Boot-Users] u-boot debugging boot with gdb and bdi2000 in lubbock(PXA255) board

[Juan Antonio Garcia Redondo <juan-antonio.garcia@nabla-designs.com>]

Hello,

I have a lubbock development board and a BDI2000 jtag debuggger.
I would like to debug the boot process before the relocate of the boot code.

My steps to debug the booter:
	o I've modified the config.mk file to enable the debug options
	    DBGFLAGS = -g -DDEBUG.
	   ( I haven't a u-boot.lds.debug for my board (lubbock). Do I need it ?)
	o Start my target, the jtag debugger is configured to stop the execution.
	o Start arm-linug-gdb u-boot
	o The ouput of the gdb is :

************************************************************
Current directory is /home/jgarcia/XSCALE/boot/u-boot-0.4.0/
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"...
(gdb) target remote bdi2000:2001
Remote debugging using bdi2000:2001
0x00000060 in ?? ()
(gdb) b start_armboot
Breakpoint 1 at 0xa030bd4: file board.c, line 214.
(gdb) monitor bi 0xa030bd4
Breakpoint identification is 0
***************************************************************

	o From here, I can stop the execution and debug the sources beginning
with the start_armboot function.

My question is, How can I debug the code __before__ the start_armboot
function ?  I would like to debug the assembler code from the first
instruction ( I can do this with the jtag debugger but I can't see the
related source instruction in the gdb ).

Regards,
      Juan Antonio