1. This forum section is a read-only archive which contains old newsgroup posts. If you wish to post a query, please do so in one of our main forum sections (here). This way you will get a faster, better response from the members on Motherboard Point.

U-Boot BDI2000 GDB Debug Problem

Discussion in 'Embedded' started by jobhunts02, Apr 9, 2005.

  1. jobhunts02

    jobhunts02 Guest

    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
    (gdb) target remote
    Remote debugging using
    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

    Program received signal SIGSTOP, Stopped (signal).
    0xfff00100 in ?? ()
    jobhunts02, Apr 9, 2005
    1. Advertisements

  2. jobhunts02

    Neil Wilson Guest

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

    Neil Wilson, Apr 11, 2005
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.