From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26963 invoked by alias); 9 Mar 2005 20:05:39 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 26929 invoked from network); 9 Mar 2005 20:05:35 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 9 Mar 2005 20:05:35 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j29K5Tkn001950 for ; Wed, 9 Mar 2005 15:05:34 -0500 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j29K5Tn22401; Wed, 9 Mar 2005 15:05:29 -0500 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id j29K5L7l004250; Wed, 9 Mar 2005 15:05:29 -0500 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 11AD7800001; Wed, 9 Mar 2005 15:05:21 -0500 (EST) Received: from toenail.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by toenail.toronto.redhat.com (8.13.1/8.12.5) with ESMTP id j29K5KFx014184; Wed, 9 Mar 2005 15:05:20 -0500 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.13.1/8.13.1/Submit) id j29K5KKr014183; Wed, 9 Mar 2005 15:05:20 -0500 Date: Wed, 09 Mar 2005 20:05:00 -0000 From: "Frank Ch. Eigler" To: Imran Shafiq Cc: sid@sources.redhat.com Subject: Re: embedded system emulator help Message-ID: <20050309200520.GD22133@redhat.com> References: <20050307170632.21914.qmail@web51509.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PHCdUe6m4AxPMzOu" Content-Disposition: inline In-Reply-To: <20050307170632.21914.qmail@web51509.mail.yahoo.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2005-q1/txt/msg00025.txt.bz2 --PHCdUe6m4AxPMzOu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2173 Hi - On Mon, Mar 07, 2005 at 09:06:31AM -0800, Imran Shafiq wrote: > [...] automotive subsystems are comprised of [ECU] Electronic > Control Units (e.g fujitsu mb90f598, Powerpc mpc 566) connected > through a BUS system usually CAN. [...] So does that means I have > to implement the whole instruction set for every ECU?? That's right. If you want to simulate software compiled for a given platform, and a model of that platform is not already available, then there is some coding to do. I believe there is no PowerPC model in sid at the moment. > I also have to simulate UART, Timer etc Some UART and timer models are already included in sid. They may be useful as is, or may serve as a basis for derivation. > It should be possible to check the data on the bus So that would > mean I have to implement the CAN protocol?? Well, one doesn't simulate a "protocol" per se, rather entities that perform it. You would need to pick a level of abstraction at which the simulator should model a CAN system. This could be at the controller level, wire level, perhaps even some software level. This allows you to trade of hardware fidelity versus modeling simplicity. > Simulator should also report stack overflows or memory > limitations. Some of this is often best done by instrumentation added by the compiler (check gcc's -fstack-limit options). Or a simulator could also model "missing" physical memory that would trigger bus errors upon attempted access. Think of the latter as mprotect(PROT_NONE). > IS all this possible with SID considering the fact that i have to do > it in 5 months :) . Probably, if you pick another CPU architecture that is already well-supported in sid, such as ARM. If nearly all of your software=20 is to be written in C, you could argue that the difference in the processors is almost immaterial. > Where can i start with an example. any pointers? I would start with one of the classic sid configurations: running an application linked with the eCos RTOS on a model of a board such as the ARM PID. Analyze the application, eCos linkages, memory and peripheral layout, and the corresponding sid configuration. - FChE --PHCdUe6m4AxPMzOu Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCL1cAVZbdDOm/ZT0RAlFlAJ90xANUX02xuoiJuMTdscUADMZAwACfZ1hq S3IHPEGRZUTV95vO80/YoHg= =Rhgn -----END PGP SIGNATURE----- --PHCdUe6m4AxPMzOu--