public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Christian Jaeger <christian@jaeger.mine.nu>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] eCos on STR9 ?
Date: Tue, 12 Aug 2008 11:36:00 -0000	[thread overview]
Message-ID: <48A1755F.3000400@jaeger.mine.nu> (raw)

Hello,

My interest is in running an OS on STR9 (STR9xFA, STR911/STR912). There 
is no mention of these chips whatsoever in the CVS sources, and the only 
information regarding running eCos on the STR9 has been the following 
posts by a few people interested in this, but it seems there has still 
nothing come out of this.

(http://sourceware.org/ml/ecos-devel/2006-06/msg00017.html or better: )
http://www.mail-archive.com/ecos-devel@ecos.sourceware.org/msg00160.html

and:

http://sources.redhat.com/ml/ecos-devel/2007-01/msg00001.html

I don't currently have more than maybe a day of time to invest into 
gettting eCos to run on the STR9, otherwise I'll go with another OS (for 
now, anyway). I don't need ethernet functionality, only SPI and some 
manually toggled I/O as well as PWM and variable frequency pulse output 
(I guess I'd do the latter things myself anyway; btw if possible I'd 
like to use all four timers for my application, although one of them 
could run at a constant frequency and so could probably also be used to 
generate ticks) and the usual reset and memory/irq routine setup stuff; 
how difficult would it be to get that much of eCos to run? I don't have 
previous programming experience with the STR9 nor with eCos.

Christian.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2008-08-12 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 11:36 Christian Jaeger [this message]
2008-08-12 12:19 ` Andrew Lunn
2008-08-12 15:03 ` Rob Duncan
2008-08-12 15:15   ` Christian Jaeger
2009-06-16 16:38 ` jerzy dyrda
2009-06-17  5:13   ` Andrew Lunn

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=48A1755F.3000400@jaeger.mine.nu \
    --to=christian@jaeger.mine.nu \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).