From: Evgeniy Dushistov <dushistov@mail.ru>
To: John Dallaway <john@dallaway.org.uk>
Cc: Nodir Kodirov <nodir.qodirov@gmail.com>,
eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCos package for Atmel at91sam9260ek board
Date: Mon, 04 Jan 2010 09:58:00 -0000 [thread overview]
Message-ID: <20100104095650.GA18435@rain> (raw)
In-Reply-To: <4B41A5B3.6020103@dallaway.org.uk>
On Mon, Jan 04, 2010 at 08:24:19AM +0000, John Dallaway wrote:
> Hi Nodir
>
> Nodir Kodirov wrote:
>
> > I am trying to port eCos on Atmel's AT92SAM9260 board. I found it is
> > already done and details are in
> > http://www.ecoscentric.com/ecospro/doc.cgi/html/ecospro-ref/arm-sam9260ek-setup.html.
> > In order to build Redboot I should run command:
> > $ ecosconfig new at91sam9260ek redboot
> > which gives me "Unknown target at91sam9260ek".
> >
> > Also, I think I shoud have
> > $ cd $ECOS_REPOSITORY/hal/arm/arm9/sam9260ek
> > directory, which I could not find even after eCos repository update.
> >
> > It seems I should buy those packages from eCosCentric, is it right?
>
> The board support referred to in the documentation you cite is indeed
> available from eCosCentric only. Another option is to create your own
> port based on one of the existing free eCos ports to other AT91SAM926x
> parts. For example, Ronetix has ported eCos to the AT91SAM9261:
>
> http://download.ronetix.info/sk-eb926x/ecos/
>
Also there is port to at91sam9263:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000819
it still wait to review during last six months.
--
/Evgeniy
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2010-01-04 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 3:10 [ECOS] " Nodir Kodirov
2010-01-04 8:24 ` [ECOS] " John Dallaway
2010-01-04 9:58 ` Evgeniy Dushistov [this message]
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=20100104095650.GA18435@rain \
--to=dushistov@mail.ru \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=nodir.qodirov@gmail.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).