public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: Lance Uyehara <lance@nuvomedia.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] newbie
Date: Sat, 30 Oct 1999 06:59:00 -0000	[thread overview]
Message-ID: <381AF9D9.DB50EEBC@cygnus.co.uk> (raw)
In-Reply-To: <3.0.5.32.19991029170719.00a59a00@mail.nuvomedia.com>

Lance Uyehara wrote:
> 
> I'm in the evaluation stage of a project, and we're looking at ecos as a
> potential kernel solution. I'm currently looking at the ecos configuration
> tool and wondering if people are using this.

Oh, absolutely :-).

> It seems to me like specifying arm pid or arm aeb (for example) is far too
> restricting. Wouldn't we want something more like arm720T or arm7TDMI?
>
> Because any project I develop won't be targeted to run on any development
> board, but rather would be targeted to run on our actual product board.

Currently via anonymous CVS, for ARM we support AEB, PID, Cirrus Logic
CL7111/EDB7211 and Cogent CMA230 boards. One of those might be closer to
your product board. We have other non-public ARM ports as well but you can
only get those with our "early access" program.

> So I guess my main question is are people using the configuration tool, or
> using the repository with hand built makefiles, or is it some combination
> of the two?

It sounds like you need to do a port of a "platform HAL" to your board. It's
probably best to copy one of the existing platform HALs that is closest to
your product board, and start making appropriate changes :-). The way eCos
is architected, it takes surprisingly little time to get a basic port doing
something (there's a lot of stuff you can skip over that isn't needed to get
simple programs running at first).

Comprehensive testing can be tricky though - here at Cygnus we have lots of
automated testing for lots of our customers' board ports that tends to show
up lots of timing problems etc. that would be difficult to find otherwise.
It's something to remember anyway - just because it *appears* to work
doesn't mean it always does, so you should be prepared to do lots of very
repetitive testing if you want a solid port.

I'm sure people on this list would be happy to help answer questions you
have doing the port. Although, of course, Cygnites can't guarantee to answer
questions in great detail nor very quickly because we have to serve our real
support customers first... but we try and help at some level when we have
time.

Jifl
-- 
Cygnus Solutions, 35 Cambridge Place, Cambridge, UK.  Tel: +44 (1223) 728762
"I used to have an open mind but || Get yer free open source RTOS's here...
 my brains kept falling out."    || http://sourceware.cygnus.com/ecos
Help fight spam! http://spam.abuse.net/  These opinions are all my own fault

  reply	other threads:[~1999-10-30  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-29 17:07 Lance Uyehara
1999-10-30  6:59 ` Jonathan Larmour [this message]
2003-01-23 23:51 [ECOS] Could anyone answer me this post thank you very much, Linker script question? where is the fixed_vectors section?(Online waiting for help) Qiang Huang
2003-01-24  1:20 ` Gary D. Thomas
2003-01-24  6:48   ` Jonathan Larmour
2003-01-24  9:13     ` [ECOS] Newbie Santosh Bhat
2003-01-24  9:35 Ravi Kumar B S

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=381AF9D9.DB50EEBC@cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=lance@nuvomedia.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).