From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4116 invoked by alias); 18 Aug 2010 20:34:44 -0000 Received: (qmail 4108 invoked by uid 22791); 18 Aug 2010 20:34:43 -0000 X-SWARE-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,TW_CF,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 18 Aug 2010 20:34:36 +0000 Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o7IKYYgO006972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 18 Aug 2010 16:34:34 -0400 Received: from fche.csb (vpn-233-244.phx2.redhat.com [10.3.233.244]) by int-mx03.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o7IKYYw8010746; Wed, 18 Aug 2010 16:34:34 -0400 Received: by fche.csb (Postfix, from userid 2569) id C34ED58159; Wed, 18 Aug 2010 16:34:33 -0400 (EDT) Date: Wed, 18 Aug 2010 20:34:00 -0000 From: "Frank Ch. Eigler" To: Deaf Beed Cc: sid@sourceware.org Subject: Re: Loading image-file in SID. Message-ID: <20100818203433.GD29393@redhat.com> References: <20100719110938.GB12047@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-IsSubscribed: yes Mailing-List: contact sid-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sourceware.org X-SW-Source: 2010-q3/txt/msg00006.txt.bz2 Hi - On Wed, Aug 18, 2010 at 11:13:29PM +0530, Deaf Beed wrote: > [...] > However, once the prints have executed, the control passes to, I > think, the OS idle loop and the simulation does not exit on its own. I > have to stop it. Is there a way to make the simulation exit/finish on > its own? maybe by programming some sid simulation component. The software needs to decide how it wishes to signal its own termination, then some piece of sid configuration needs to map that to a signal to the cfgroot stop! pin. If the sw-gloss* is not used, nor is gdb, then you could jury-rig what is in effect a breakpoint using triggerpoints (connect the watch:pc:value:0xsomething pseudo-pin on the cpu to the cfgroot stop!). Or you could wire up a virtual device such as hw-glue-probe-bus into the bus mapper tree at some particular address, then poke at that address from the arm software code. - FChE