From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=60517 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oqon6-00085d-VT for qemu-devel@nongnu.org; Wed, 01 Sep 2010 10:59:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Oqon5-0000eG-Fh for qemu-devel@nongnu.org; Wed, 01 Sep 2010 10:59:56 -0400 Received: from mail-gx0-f173.google.com ([209.85.161.173]:43306) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Oqon5-0000eA-C9 for qemu-devel@nongnu.org; Wed, 01 Sep 2010 10:59:55 -0400 Received: by gxk26 with SMTP id 26so3560040gxk.4 for ; Wed, 01 Sep 2010 07:59:54 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20100901135216.GD22311@gmail.com> References: <4C7E46AB.1010006@gmail.com> <20100901135216.GD22311@gmail.com> From: Anitha Boyapati Date: Wed, 1 Sep 2010 20:29:34 +0530 Message-ID: Subject: Re: [Qemu-devel] Qemu as Instruction Set Simulator without any OS Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Robin Randhawa Cc: qemu-devel@nongnu.org On 1 September 2010 19:22, Robin Randhawa wrote: [...] >> My exact requirement is to test a gcc cross-compiler using DejaGnu for >> a given target (AVR32). While the cross-compiler is ready, there is no >> simulator. Since there is not much of OS support, I am trying to >> evaluate if Qemu can still be considered for this purpose. > > I see. That makes sense. I thought that AVR32 support never made it to > the mainline. Has that changed ? > Not yet. Maybe sooner :-) >> The usage scenario probably goes like this: >> >> 1. Qemu-target should be invoked with the application (yes, >> bare-metal) waiting for some gdb connection. =A02. target-gdb is invoked >> with the same application >> >> I am referring to the example given in >> http://wiki.qemu.org/download/qemu-doc.html#gdb_005fusage : >> >> > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append >> > "root=3D/dev/hda" >> >> However, in my case kernel image doesn't exist. > > Got that. Note that your system mode emulation would have to cater for > loading the bare-metal image (qemu has well defined APIs for this). Some > emulations add some intelligence over and above the bare-metal image > loading, such as the ARM Realview emulation which checks to see if the > image passed to the "-kernel" argument is a Linux image in which case > some special case initialisation is done (instead of a 'raw' load). > I was thinking along similar lines. Little more source code probing should give me better overview. >> As to the requirement >> of bootloader, I need to investigate further as various types of >> memories (FLASH & SRAM for program and data sections) exist. > > Most of that can be easily faked as simple RAM at the appropriate > offsets in your platform description to start off with. > Yep, I hope so. Thanks for the help :-) Best Regards Anitha