From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FMpVv-0000oC-TR for qemu-devel@nongnu.org; Fri, 24 Mar 2006 11:51:51 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FMpVu-0000nz-PD for qemu-devel@nongnu.org; Fri, 24 Mar 2006 11:51:51 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FMpVu-0000nw-LF for qemu-devel@nongnu.org; Fri, 24 Mar 2006 11:51:50 -0500 Received: from [64.233.184.224] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FMpWl-0007nS-Od for qemu-devel@nongnu.org; Fri, 24 Mar 2006 11:52:43 -0500 Received: by wproxy.gmail.com with SMTP id i6so995453wra for ; Fri, 24 Mar 2006 08:51:49 -0800 (PST) Message-ID: <442423AF.6020400@gmail.com> Date: Fri, 24 Mar 2006 17:51:59 +0100 MIME-Version: 1.0 Subject: Re: [Qemu-devel] Debugging low level ARM with GDB References: <4422C85F.8040106@gmail.com> <200603231626.24838.paul@codesourcery.com> <44241462.2020202@gmail.com> <200603241628.34205.paul@codesourcery.com> In-Reply-To: <200603241628.34205.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Dirk Behme Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: qemu-devel@nongnu.org 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