public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: iz@vsr.si
Cc: James Yates <j.yates@quartzuk.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Scheduler Problem
Date: Mon, 13 Oct 2003 11:49:00 -0000	[thread overview]
Message-ID: <1066045767.30453.22.camel@hermes> (raw)
In-Reply-To: <200310131326.14364.iz@vsr.si>

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 the
> > point of  getting a simple app up and running. I have a bootloader running

 ... snip
> 
> You should start the scheduler here, otherwise it's never started:
> 
>     	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).

-- 
Gary Thomas <gary@mlbassoc.com>
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

  reply	other threads:[~2003-10-13 11:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 11:18 James Yates
2003-10-13 11:26 ` Iztok Zupet
2003-10-13 11:49   ` Gary Thomas [this message]
2003-10-13 11:54 James Yates
2003-10-13 12:01 ` Gary Thomas
2003-10-13 12:14 James Yates
2003-11-18 12:26 [ECOS] scheduler problem Aravind B
2003-11-18 12:36 ` Andrew Lunn
2003-11-19  4:20 Aravind B
2003-11-19  4:41 ` mohanlal jangir
2005-04-01  8:38 [ECOS] Scheduler problem liu hua
2005-04-02  1:52 ` John Newlin
2005-04-04 15:54 ` Nick Garnett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1066045767.30453.22.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=iz@vsr.si \
    --cc=j.yates@quartzuk.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).