From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12148 invoked by alias); 13 Oct 2003 11:54:33 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 12139 invoked from network); 13 Oct 2003 11:54:32 -0000 Received: from unknown (HELO sand2.gxn.net) (195.147.249.208) by sources.redhat.com with SMTP; 13 Oct 2003 11:54:32 -0000 Received: from ip02.quartzelec.adsl.gxn.net ([195.147.203.154] helo=server2000.Quartz.local) by sand2.gxn.net with esmtp (Exim 4.20) id 1A91Xa-0002km-UA; Mon, 13 Oct 2003 13:11:11 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Date: Mon, 13 Oct 2003 11:54:00 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "James Yates" To: "Gary Thomas" , Cc: Subject: RE: [ECOS] Scheduler Problem X-SW-Source: 2003-10/txt/msg00193.txt.bz2 Gary, Ho I haven't run any of the test programs. Are these built with the same= memory model. Because I am using a custom bootloader due to project requir= ements everything has to be placed exactly right. Also I have just noticed = that when corrupted output is sent to my serial port once cyg_scheduler_sta= rt() is called, pressing enter on the terminal causes another line of corru= pted out to appear. I think perhaps a rom monitor stub is in the way? I tri= ed disabling all gdb_stub related options but now get no diag output. :-( I will keep at it. Thansk for your help. If you think of anything else I wo= uld be very appreciative. James -----Original Message----- From: Gary Thomas [mailto:gary@mlbassoc.com] Sent: 13 October 2003 12:49 To: iz@vsr.si Cc: James Yates; ecos-discuss@sources.redhat.com Subject: Re: [ECOS] Scheduler Problem On Mon, 2003-10-13 at 05:26, Iztok Zupet wrote: > On Monday 13 October 2003 13:20, James Yates wrote: > > I have just ported eCos to my own custom SH2 platform and I am now at t= he > > point of getting a simple app up and running. I have a bootloader runn= ing ... snip >=20 > You should start the scheduler here, otherwise it's never started: >=20 > Cyg_Scheduler::scheduler.start(); // This function never returns Or, since this is probably just a C program (not C++) cyg_scheduler_start(); Also, James - have you run any of the standard eCos test programs? They are there to test the behaviour of a port and can tell you a lot about what works (and what doesn't). --=20 Gary Thomas MLB Associates -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss