All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Debugging low level ARM with GDB
Date: Fri, 24 Mar 2006 17:51:59 +0100	[thread overview]
Message-ID: <442423AF.6020400@gmail.com> (raw)
In-Reply-To: <200603241628.34205.paul@codesourcery.com>

Paul Brook wrote:
>>But PC is still wrong. Who sets the PC to KERNEL_LOAD_ADDR
>>(0x10000)?
> 
> 
> What makes you think ti's wrong? There's a small bootloader built into qemu.

Uups. Then it seems that I start things the wrong way. I 
start QEMU with -S -s, then I attach GDB, and GDB 
"complains" that PC is at 0x0 (and not 0x10000). How do I 
have to invoke things in the correct way (and that this 
bootloader is used)  so that system is at 0x10000 if I 
attach GDB and can start with si debugging from there?

>>Then I tried the other way around: Instead of adapting
>>u-boot, it should be possible to adapt hw/integratorcp.c to
>>the address u-boot is linked to by default. This is
>>0x11080000. For my changes see below. With this, I get
> 
> 
> You're obviously using the wrong u-boot config then. 0x11080000 isn't even a 
> RAM address.

Yes, seems that I was unclear here. Sorry. It's for an other 
board. Take this question as the first step for a new 
machine description using integrator as an example.

Thanks for your help and patience!

Dirk

  reply	other threads:[~2006-03-24 16:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 16:10 [Qemu-devel] Debugging low level ARM with GDB Dirk Behme
2006-03-23 16:26 ` Paul Brook
2006-03-24 15:46   ` Dirk Behme
2006-03-24 16:28     ` Paul Brook
2006-03-24 16:51       ` Dirk Behme [this message]
2006-03-24 17:09         ` Paul Brook
2006-03-27 19:48     ` andrzej zaborowski
2006-03-23 19:44 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-03-24 10:35 Schwarz, Konrad
2006-03-24 16:32 ` Paul Brook
2006-03-23  9:25 Dirk Behme

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=442423AF.6020400@gmail.com \
    --to=dirk.behme@googlemail.com \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /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.