From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32083 invoked by alias); 22 Aug 2002 17:09:31 -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 32076 invoked from network); 22 Aug 2002 17:09:30 -0000 Received: from unknown (HELO www.jennic.com) (213.143.5.74) by sources.redhat.com with SMTP; 22 Aug 2002 17:09:30 -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 RAA19650; Thu, 22 Aug 2002 17:34:23 +0100 Received: from jenpc60 (jenpc60 [99.99.98.60]) by jensun01.jennic.com (8.9.3/8.9.3) with SMTP id SAA09209; Thu, 22 Aug 2002 18:09:28 +0100 (BST) From: "Robert Cragie" To: "Frank Ch. Eigler" Cc: Subject: RE: Trying to run on pid7t board Date: Thu, 22 Aug 2002 10:09: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: <20020822092212.A8731@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal X-SW-Source: 2002-q3/txt/msg00024.txt.bz2 > 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. OK, I won't mention it to the eCos guys. I see the memory components can have an image file, allowing a boot monitor to be there on 'power up'. > 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. With some further juggling of eCos configuration, I have got it printing to the gdb console (-uart1:gdb), to the console sid was run from (-uart1:stdio) and the tksm tty window. Excellent! Now I am having problems with the timer-related calls (cyg_thread_delay() etc.) - I notice in the list this was also seen by Cristiano Pereira (04-Mar-02). I have done some debugging, and timer interrupt seems to fire once, then a data_abort exception is thrown a bit later; looks like the pc was 0xe59d0044. Ho hum. I will try to get to the bottom of what is going on - if anyone has any ideas, I'd appreciate them. > 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. Sorry for my lack of knowledge; I have only just started getting into sid. It looks really good and I hope to be using it much more in the future. Thanks for your prompt and helpful support. Robert Cragie, Design Engineer _______________________________________________________________ Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK http://www.jennic.com Tel: +44 (0) 114 281 2655