From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22166 invoked by alias); 22 Aug 2002 11:48:59 -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 22157 invoked from network); 22 Aug 2002 11:48:58 -0000 Received: from unknown (HELO www.jennic.com) (213.143.5.74) by sources.redhat.com with SMTP; 22 Aug 2002 11:48:58 -0000 Received: from jensun01.jennic.com (jensun01.jennic.com [99.99.98.151]) by www.jennic.com (8.9.3/8.9.3) with ESMTP id MAA18728; Thu, 22 Aug 2002 12:13:51 +0100 Received: from jenpc60 (jenpc60 [99.99.98.60]) by jensun01.jennic.com (8.9.3/8.9.3) with SMTP id MAA28056; Thu, 22 Aug 2002 12:48:56 +0100 (BST) From: "Robert Cragie" To: "Frank Ch. Eigler" Cc: Subject: RE: Trying to run on pid7t board Date: Thu, 22 Aug 2002 04:48:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20020821143141.C7180@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal X-SW-Source: 2002-q3/txt/msg00021.txt.bz2 > Aha. The remapper is indeed involved, as is the eCos startup sequence. > It seems that after the access to 0xb000020, the 0x0-0xffff mapping window > into 0x4000000 disappears. In such circumstances, the code can only work > if the running PC switches over to the ROM area (0x40008048). In some > versions of eCos, this is forced by the first few instructions, apparently > not yours. This would explain the slightly odd startup sequence of: ldr r0,=10f mov pc,r0 10: ldr r0,=MEM_RESET str r0,[r0] i.e. the second opcode just moves the pc to where it would have gone anyway. > There are a couple of possible workarounds. If you are positive that your > eCos application will run correctly on a board of interest, then you could > toggle sid's remapper setting (add "-normalmap" to the "--board" argument > sublist as in "--board=pid7t-normalmap"). Other ways would involve tweak ing > the eCos startup sequence, or the executable, or sid loading/startup. 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. 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 the serial ports work on the simulation (i.e. what happens when I write a character), or point me at some appropriate docs.? > Please be aware that in your given mode, sid is attempting to > emulate a board just after powerup. If your application assumes that it's being loaded by > an already-running monitor, such mismatches need to be corrected some way. I think I misunderstood the way the gloss component works - I guess it's more like an on-chip ICE than a debug monitor. Thanks for your help Robert Cragie, Design Engineer _______________________________________________________________ Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK http://www.jennic.com Tel: +44 (0) 114 281 2655