U-Boot BDI2000 GDB Debug Problem

I am trying to debug U-Boot using the BDI2000 and gdb. When I enter "c" for continue, I get "Program received signal SIGSTOP, Stopped (signal)." (see below)

Does anyone know what causes this? Thank you.

$ /opt/Embedix/tools/bin/powerpc-linux-gdb GNU gdb 5.1.1 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-pc-linux-gnu

--target=powerpc-linux". (gdb) target remote 10.174.100.208:2001 Remote debugging using 10.174.100.208:2001

0xfff00100 in ?? () (gdb) symbol-file No symbol file now. (gdb) add-symbol-file u-boot 0x1fc0000 add symbol table from file "u-boot" at .text_addr = 0x1fc0000 (y or n) y Reading symbols from u-boot...done. (gdb) b board_init_r Breakpoint 1 at 0x1fc4a60: file board.c, line 551. (gdb) c Continuing.

Program received signal SIGSTOP, Stopped (signal).

0xfff00100 in ?? () (gdb)
Reply to
jobhunts02
Loading thread data ...

That is the reset vector isn't it ? Has a hardware watchdog gone off in the meantime & reset the board. Cheers.

Neil

Reply to
Neil Wilson

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.