Hi All,
The following doesn't look right to me and I was hoping someone could
comment accordingly.
----------- GDB output begins here. ----------------
Quit
(gdb) p/x $sp
$1 = 0xfe121d04
(gdb) info target
Symbols from "/home/dbanas/NuHo/MBO/S3-1500/uClinux-dist/images/image.elf".
Remote serial target in gdb-specific protocol:
Debugging a target over a serial line.
While running this, GDB does not access memory from...
Local exec file:
`/home/dbanas/NuHo/MBO/S3-1500/uClinux-dist/images/image.elf', file
type elf32-microblaze.
Entry point: 0xfe000000
0xfe000000 - 0xfe114ed0 is .text
0xfe114ed0 - 0xfe114f08 is .intv
0xfe114f08 - 0xfe116a78 is .sdata2
0xfe116a78 - 0xfe122020 is .data
0xfe123000 - 0xfe12e000 is .init
0xfe12e000 - 0xfe14f4bc is .bss
0xfe12e000 - 0xfe1e2000 is .romfs
----------- GDB output ends here. -------------------------
For one thing, my stack pointer is pointing inside my 'data' section, which
doesn't seem right.
For another, my 'bss' and 'romfs' sections overlap. Now, I thought I
remembered a section of kernel code zeroing out the 'bss' section early on
in the boot sequence, and I'm pretty sure I wouldn't want any part of my
'romfs' section to be wiped out.
Thanks, in advance, for any thoughts on the matter,
David Banas
Field Applications Engineer
Nu Horizons Electronics Corp.
2070 Ringwood Avenue
San Jose, CA 95131
(408)434-0800 - office
(415)846-5837 - cell
http://www.nuhorizons.com
<<attachment: winmail.dat>>