From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26678 invoked by alias); 22 Aug 2002 13:22:20 -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 26671 invoked from network); 22 Aug 2002 13:22:18 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 22 Aug 2002 13:22:18 -0000 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 4B70AB8049; Thu, 22 Aug 2002 09:22:14 -0400 (EDT) Received: (from fche@localhost) by toenail.toronto.redhat.com (8.11.6/8.11.6) id g7MDMDE08783; Thu, 22 Aug 2002 09:22:13 -0400 Date: Thu, 22 Aug 2002 06:22:00 -0000 From: "Frank Ch. Eigler" To: Robert Cragie Cc: sid@sources.redhat.com Subject: Re: Trying to run on pid7t board Message-ID: <20020822092212.A8731@redhat.com> References: <20020821143141.C7180@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rcc@jennic.com on Thu, Aug 22, 2002 at 12:48:55PM +0100 X-SW-Source: 2002-q3/txt/msg00022.txt.bz2 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1965 Hi - On Thu, Aug 22, 2002 at 12:48:55PM +0100, Robert Cragie wrote: > [...] > Adding the -normalmap argument worked - thanks. I will point this out on = the > eCos mailing list, as the default sid flags for the RAM build won't work. This may not concern (interest) the eCos guys. SID can do a better job of emulating the RAM startup environment that eCos expects. This "normalmap" option is just one possibility. Another one is to actually run a copy of RedBoot or cygmon or whatever on SID. Then you can upload your application via a simulated serial port, making it look to gdb etc. much more like it was a real board. > Next step is to try to work out why printf() doesn't work, however this > seems to be an eCos issue. However, while I'm here, can you tell me how t= he > serial ports work on the simulation (i.e. what happens when I write a > character), or point me at some appropriate docs.? For the pid7t configuration, sid models two uarts. The arm-elf-sid script can take options to let you tell it how you'd like these simulated uarts to be connected to the real world. This is done with more --board options. For example "--board=3Dpid7t-uart1:stdio-uart2:3000" would connect the simulated uart1 to the simulator's console, and uart2 to a tcp (listening) socket at port 3000. One can also add a tk-based terminal window, or add one after startup if using tksm. > > Please be aware that in your given mode, sid is attempting to > > emulate a board just after powerup. If your application assumes that i= t's > > being loaded by an already-running monitor, such mismatches need to be > > corrected some way. >=20 > I think I misunderstood the way the gloss component works - I guess it's > more like an on-chip ICE than a debug monitor. I suspect that the sid gloss component proper (simulated system calls) is not even used in these configurations. If you mean the usual simulator debugging interface, then yes, that's right. - FChE --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 232 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9ZOWEVZbdDOm/ZT0RAqhdAJ97pyeZFdn4nUAQI8J1P3Nr9TLzFACfVj6E LgZLjDStS2qXHFy0OcYEQbk= =I/GF -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--