All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: u-boot debugging boot with gdb and bdi2000 in lubbock(PXA255) board
Date: 09 Sep 2003 15:24:52 +0200	[thread overview]
Message-ID: <87k78iccwr.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: <3F5D81C3.4050604@cocay.it>

Hello Andrea,

> [u-boot-0.4.6]$ arm-linux-gdb u-boot
> 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-redhat-linux --target=arm-linux"...
> (gdb) target remote bdi:2001
> Remote debugging using bdi:2001
> 0x00000000 in ?? ()
> (gdb) symbol-file
> Discard symbol table from `/home/sorio/Devel/UBoot/u-boot-0.4.6/u-boot'? (y or n) y
> No symbol file now.
> (gdb) add-symbol-file u-boot 0x0
> add symbol table from file "u-boot" at
>         .text_addr = 0x0
> (y or n) y
> Reading symbols from u-boot...done.
> (gdb) b start_armboot
> Breakpoint 1 at 0x80000cb4: file board.c, line 214.
> (gdb) x/16i 0x0
> 0x0:    b       0x54
> 0x4:    ldr     pc, [pc, #20]   ; 0x20
> 0x8:    ldr     pc, [pc, #20]   ; 0x24
> 0xc:    ldr     pc, [pc, #20]   ; 0x28
> 0x10:   ldr     pc, [pc, #20]   ; 0x2c
> 0x14:   ldr     pc, [pc, #20]   ; 0x30
> 0x18:   ldr     pc, [pc, #20]   ; 0x34
> 0x1c:   ldr     pc, [pc, #20]   ; 0x38
> 0x20:   andmi   r0, r0, r0, lsl #2
> 0x24:   andmi   r0, r0, r0, ror #2
> 0x28:   andmi   r0, r0, r0, asr #3
> 0x2c:   andmi   r0, r0, r0, lsr #4
> 0x30:   andmi   r0, r0, r0, lsl #5
> 0x34:   andmi   r0, r0, r0, ror #5
> 0x38:   andmi   r0, r0, r0, asr #6
> 0x3c:   cdple   14, 10, cr11, cr13, cr15, {7}
> (gdb)
> 
> The breackpoint is set to "0x80000cb4", so the bdi never stop!
> My code is built to run on 0x40000000 address.
> Any idea?

It is just something I seem to remember, but can you try to do the
symbol-file manipulations _before_ you give the "target remote"
command?  I know it sounds unlikely, but I think I stumbled across
something like this before.

Cheers
  Detlev

-- 
Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
or Fortran program contains an ad-hoc, informally-specified bug-ridden
slow implementation of half of Common Lisp."

      parent reply	other threads:[~2003-09-09 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09  7:31 [U-Boot-Users] Re: u-boot debugging boot with gdb and bdi2000 in lubbock(PXA255) board Andrea Sorio
2003-09-09  8:11 ` Wolfgang Denk
2003-09-09  8:23   ` Andrea Sorio
2003-09-09  9:06     ` Wolfgang Denk
2003-09-09 13:24 ` Detlev Zundel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k78iccwr.fsf@deepthought.outer.space.org \
    --to=dzu@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.