From: Martin Laabs <martin.laabs@mailbox.tu-dresden.de>
To: John Dallaway <john@dallaway.org.uk>, ecos-devel@ecos.sourceware.org
Subject: Re: eCos on AT91SAM9 - call to action
Date: Wed, 16 Mar 2011 17:07:00 -0000 [thread overview]
Message-ID: <4D80EE4C.3090703@mailbox.tu-dresden.de> (raw)
In-Reply-To: <4D809BF2.6040205@dallaway.org.uk>
Hello,
my port based on the one of Evgeniy Dushitov at the very beginning. However
- after some weeks I discovered that it was very hard to support more CPUs
out of the AT91SAM9 family with that code-base.
So I started from beginning, reusing only some code snipplet from Evgeniy.
I made the decision to split the port into three packages.
The at91sam9 package contains all the stuff that is common to all at91sam9
CPUs. The at91sam9260 package contains the CPU specific
definitions/function and the board package handles all the board specific
things like pin assignment, linker scripts etc.
I used the atmel register definitions to generate the includes for the
register that are common to every at91sam9 cpu and the cpu specific parts.
The names are not equal to the ones in the at91 packages - but its worth
the price for a (nearly) complete register description that is also equal
to the ones in the datasheets.
I also changed the pin handling to a somewhat better readable style. I.e.
#define SPI1_NPCS0
AT91SAM9_PIN(AT91SAM9_PIN_TYPE_PERIPH_A,AT91SAM9_PIN_PORT_B, 3)
Currently we ported the SPI driver in polled and dma mode (including the
cache coherency handling), the serial driver and ethernet peripheral. I
also wrote code for the SSI but this is to application specific.
Board support is limited to the AT91SAM9260EK and our specific board.
However we plan to add the olimex eval board of the AT91SAM9260 soon.
The include files for all other processors are generated as well. So
porting to other CPUs and/or boards should be no great deal.
Currently we use our own GIT server. But I think we can open it for
publicly - at least reading access. I will ask for permission to open the
GIT server and publish the URL if someone want to look on the code base.
Greetings,
Martin Laabs
next prev parent reply other threads:[~2011-03-16 17:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 11:16 John Dallaway
2011-03-16 13:40 ` Grant Edwards
2011-03-16 14:31 ` AW: " Richard Rauch
2011-03-16 17:07 ` Martin Laabs [this message]
2011-03-16 18:18 ` John Dallaway
2011-03-16 18:35 ` Michael Bergandi
2011-03-17 10:14 ` Martin Laabs
2011-03-17 13:13 ` John Eigelaar
2011-06-16 13:38 ` Frank Pagliughi
2011-06-16 14:05 ` John Dallaway
2011-06-16 14:16 ` John Eigelaar
2011-06-16 14:27 ` eCos on AT91SAM3 [ was Re: eCos on AT91SAM9 - call to action ] John Dallaway
2011-06-16 14:29 ` eCos on AT91SAM9 - call to action Frank Pagliughi
2011-06-20 15:18 ` Eagle 100 (Stellaris LM3S6918) Frank Pagliughi
2011-06-20 16:17 ` Stanislav Meduna
2011-06-21 11:05 ` John Dallaway
2011-06-21 16:34 ` Christophe Coutand
2011-06-23 14:31 ` John Dallaway
2011-06-23 16:48 ` Frank Pagliughi
2011-06-23 17:57 ` Christophe Coutand
2011-07-10 20:38 ` Ilija Kocho
2011-07-12 8:57 ` Christophe Coutand
2011-07-13 14:52 ` Ilija Kocho
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=4D80EE4C.3090703@mailbox.tu-dresden.de \
--to=martin.laabs@mailbox.tu-dresden.de \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
--cc=uni@martinlaabs.de \
/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).