From: Nick Garnett <nickg@ecoscentric.com>
To: "Meiring, H, Mnr <meiring@sun.ac.za>" <meiring@sun.ac.za>
Cc: <ecos-devel@ecos.sourceware.org>
Subject: Re: Guidance porting AT91sam7
Date: Tue, 10 Apr 2007 10:18:00 -0000 [thread overview]
Message-ID: <m3wt0k5y8o.fsf@xl5.calivar.com> (raw)
In-Reply-To: <FC829C66C7DA824A96A893C28F1B7AD969E88E@STBEVS01.stb.sun.ac.za>
"Meiring, H, Mnr <meiring@sun.ac.za>" <meiring@sun.ac.za> writes:
> The at91sam7a series seems to be an combination of the 7s and 7x
> series- basically the 7s with an ebi (my view may change as I look
> at more detail). There is however differences with the startup, the
> 7a series have a clock manager that handles that, so the platform
> setup should change a bit. The interrupts seems to be fairly
> similar, but i will first try to get redboot working and then worry
> about interrupts.
>
> I will have a look and shout if I have q's
Be warned that there be dragons here. I added SAM7A series support to
the eCosCentric source tree a little while ago. It was not nice. The
A1 and A2 devices are SAM7's in name only. They differ in lots of ways
from the S and X series, and from the earlier AT91 parts; there are
almost no functional units that remain identical and some, like the
PDC and PIO are very weirdly different. I suspect that they are odd
parts that have been shoehorned into the SAM product line as a
marketing exercise, there is certainly no technical reason for it.
There is further confusion because the SAM7A3 *does* share most
functional units with the S and X series.
I suspect that the A1 and A2 may be discontinued fairly quickly. So
think hard about whether you really want to use the A2. You will be
much better off using an S or X series part, or the A3.
And, of course, eCosCentric can offer you a working port if you want
to save yourself a lot of grief.
--
Nick Garnett eCos Kernel Architect
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
next prev parent reply other threads:[~2007-04-10 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 12:11 Meiring, H, Mnr <meiring@sun.ac.za>
2007-04-09 12:40 ` Andrew Lunn
2007-04-09 15:10 ` Meiring, H, Mnr <meiring@sun.ac.za>
2007-04-10 10:18 ` Nick Garnett [this message]
2007-04-09 12:18 Meiring, H, Mnr <meiring@sun.ac.za>
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=m3wt0k5y8o.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=meiring@sun.ac.za \
/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).