* [U-Boot-Users] Newbie: gdb and BDI2000
@ 2005-05-20 14:02 Armand Ciejak
2005-05-20 14:33 ` Wolfgang Denk
0 siblings, 1 reply; 3+ messages in thread
From: Armand Ciejak @ 2005-05-20 14:02 UTC (permalink / raw)
To: u-boot
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 at 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [U-Boot-Users] Newbie: gdb and BDI2000
2005-05-20 14:02 [U-Boot-Users] Newbie: gdb and BDI2000 Armand Ciejak
@ 2005-05-20 14:33 ` Wolfgang Denk
2005-05-20 15:09 ` [U-Boot-Users] " Armand Ciejak
0 siblings, 1 reply; 3+ messages in thread
From: Wolfgang Denk @ 2005-05-20 14:33 UTC (permalink / raw)
To: u-boot
In message <d6kqen$5i9$1@sea.gmane.org> you wrote:
>
> My problem is that I can't really debug, here a typical session:
Please show us the COMPLETE list of ALL commands you execute and ALL
output your get.
> armand at linuxcompiler:~/u-boot/u-boot_1.1.2$ ppc-linux-gdb u-boot
> Warning: Cannot initialize solib-absolute-prefix
Where is this warning coming from? How did you set CROSS_COMPILE ?
> 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
There is something missing here. How did you connect to the BDI2000?
Which other commands did you issue?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
\|/ ____ \|/ \|/ ____ \|/
@~/ ,. \~@ @~/ ,. \~@
/_( \__/ )_\ /_( \__/ )_\
\__U_/ \__U_/
^ permalink raw reply [flat|nested] 3+ messages in thread* [U-Boot-Users] Re: Newbie: gdb and BDI2000
2005-05-20 14:33 ` Wolfgang Denk
@ 2005-05-20 15:09 ` Armand Ciejak
0 siblings, 0 replies; 3+ messages in thread
From: Armand Ciejak @ 2005-05-20 15:09 UTC (permalink / raw)
To: u-boot
I have no idea about the warning.
CROSS_COMPILE = ppc_6xx-
Here is a complete session, I only repeat "stepi" until crash:
linuxcompiler:~/u-boot/u-boot_1.1.2$ ppc-linux-gdb u-boot -silent -n
Warning: Cannot initialize solib-absolute-prefix
(gdb) target remote 192.168.1.20:2001
Remote debugging using 192.168.1.20:2001
0xfffffffc in ?? ()
(gdb) stepi
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)
0xfffff030 65 blr
(gdb)
0xfffff034 65 blr
(gdb)
0xfffff038 65 blr
(gdb)
0xfffff03c 65 blr
(gdb)
0xfffff040 65 blr
(gdb)
0xfffff044 65 blr
(gdb)
0xfffff048 65 blr
(gdb)
0xfffff04c 65 blr
(gdb)
0xfffff050 65 blr
(gdb)
0xfffff054 65 blr
(gdb)
0xfffff058 65 blr
(gdb)
0xfffff05c 65 blr
(gdb)
0xfffff060 65 blr
(gdb)
0xfffff064 65 blr
(gdb)
0xfffff068 65 blr
(gdb)
0xfffff06c 65 blr
(gdb)
0xfffff070 65 blr
(gdb)
0xfffff074 65 blr
(gdb)
0xfffff078 65 blr
(gdb)
0xfffff07c 65 blr
(gdb)
0xfffff080 65 blr
(gdb)
0xfffff084 65 blr
(gdb)
0xfffff088 65 blr
(gdb)
0xfffff08c 65 blr
(gdb)
0xfffff090 65 blr
(gdb)
0xfffff094 65 blr
(gdb)
0xfffff098 65 blr
(gdb)
0xfffff09c 65 blr
(gdb)
0xfffff0a0 65 blr
(gdb)
0xfffff0a4 65 blr
(gdb)
0xfffff0a8 65 blr
(gdb)
0xfffff0ac 65 blr
(gdb)
0xfffff0b0 65 blr
(gdb)
0xfffff0b4 in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff0b8 65 blr
(gdb)
0xfffff0bc 65 blr
(gdb)
0xfffff0c0 65 blr
(gdb)
0xfffff0c4 65 blr
(gdb)
0xfffff0c8 65 blr
(gdb)
0xfffff0cc 65 blr
(gdb)
0xfffff0d0 65 blr
(gdb)
0xfffff0d4 65 blr
(gdb)
0xfffff0d8 65 blr
(gdb)
0xfffff0dc in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff0e0 65 blr
(gdb)
0xfffff0e4 in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff0e8 65 blr
(gdb)
0xfffff0ec in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff0f0 65 blr
(gdb)
0xfffff0f4 in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff0f8 65 blr
(gdb)
0xfffff0fc in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff100 65 blr
(gdb)
0xfffff104 in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff108 65 blr
(gdb)
0xfffff10c in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff110 65 blr
(gdb)
0xfffff114 in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff118 65 blr
(gdb)
0xfffff11c in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff120 65 blr
(gdb)
0xfffff124 in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff128 65 blr
(gdb)
0xfffff12c in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff130 65 blr
(gdb)
0xfffff134 in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
65 blr
(gdb)
0xfffff138 65 blr
(gdb)
0xfffff13c in _start_e500 ()
at /home/armand/u-boot/u-boot_1.1.2/lib_ppc/ticks.S:65
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)
Wolfgang Denk wrote:
> In message <d6kqen$5i9$1@sea.gmane.org> you wrote:
>>
>> My problem is that I can't really debug, here a typical session:
>
> Please show us the COMPLETE list of ALL commands you execute and ALL
> output your get.
>
>> armand at linuxcompiler:~/u-boot/u-boot_1.1.2$ ppc-linux-gdb u-boot
>> Warning: Cannot initialize solib-absolute-prefix
>
> Where is this warning coming from? How did you set CROSS_COMPILE ?
>
>> 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
>
> There is something missing here. How did you connect to the BDI2000?
> Which other commands did you issue?
>
> Best regards,
>
> Wolfgang Denk
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-05-20 15:09 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-20 14:02 [U-Boot-Users] Newbie: gdb and BDI2000 Armand Ciejak
2005-05-20 14:33 ` Wolfgang Denk
2005-05-20 15:09 ` [U-Boot-Users] " Armand Ciejak
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox