Hello,
Here my problem: I want to debug u-boot for a custom board based on the MPC8540 CPU. The board I'm working on is actually from Metrowerks (EVAL8540), which is similar to the MPC8540ADS. I got the source of u-boot 1.1.2 and modified the MPC8540ADS configuration (Memory size, ...). I compiled uboot with the debug option (I add a defined in the u-boot_1.1.2/include/configs/board_name.h file). Obviously after copying the u-boot.bin to the flash memory via the BDI2000, the sytem doesn't start: no output on the serial port!!!
My problem is that I can't really debug, here a typical session:
armand@linuxcompiler:~/u-boot/u-boot_1.1.2$ ppc-linux-gdb u-boot Warning: Cannot initialize solib-absolute-prefix GNU gdb Yellow Dog Linux (5.2.1-4b_8) 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=i386-redhat-linux --target=ppc-linux"... 0xfffffffc in ?? () (gdb) si 0xfffff000 65 blr (gdb) 0xfffff004 65 blr (gdb) 0xfffff008 in _start_e500 () at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65 65 blr (gdb) 0xfffff00c in _start_e500 () at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65 65 blr (gdb) 0xfffff010 65 blr . . . (gdb) 0xfffff140 65 blr (gdb) 0xfffff144 in _start_e500 () at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65 65 blr (gdb) 0xfffff148 65 blr (gdb) 0xfffff14c 65 blr (gdb) 0xfffff150 65 blr (gdb)
Program received signal SIGSTOP, Stopped (signal). 0x00000000 in ?? () (gdb)
I think I'm doing something wrong but what ???
thanks
Armand
More info: - ppc-linux-gdb installed from the ELDK 3.1 - BDI2000 for MPC85xx rev C with the latest firmware - cross compiler from ELDK 3.1