But how can I debug application, compiled separately (u-boot)? I can
load u-boot elf file to RAM using XMD (I'm using Spartan-3e kit), can
run it and even set breakpoints, but I see assembler only.
I tried to run mb-gdb in the directory where u-boot has been compiled
and connect to XMD remotely. Connection goes through, but I still cannot
see source though I add symbol table from elf file:
[leonid@mylinux u-boot]$
/home/leonid/LM125/uClinux/petalinux-v0.10-rc1/tools/linux-i386/microbla
ze-uclinux-tools/bin/microblaze-uclinux-gdb u-boot-s.elf
GNU gdb 5.3Xilinx EDK 8.1.01 Build EDK_I.19.4
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=microblaze-uclinux"...(no debugging symbols found)...
(gdb) target remote 192.168.0.70:1234
Remote debugging using 192.168.0.70:1234
0x23fc0008 in ?? ()
(gdb) add-symbol-file u-boot-s.elf 0x23fc0000
add symbol table from file "u-boot-s.elf" at
.text_addr = 0x23fc0000
(y or n) y
Reading symbols from u-boot-s.elf...(no debugging symbols found)...done.
(gdb)
Also I didn't get this " no debugging symbols found" thing - I have -g
as part of CFLAGS.