From: Andrew Lunn <andrew@lunn.ch>
To: "Meiring, H, Mnr <meiring@sun.ac.za>" <meiring@sun.ac.za>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] AT91sam7a guidance in porting
Date: Fri, 30 Nov 2007 15:50:00 -0000 [thread overview]
Message-ID: <20071130140036.GB593@lunn.ch> (raw)
In-Reply-To: <FC829C66C7DA824A96A893C28F1B7AD969E898@STBEVS01.stb.sun.ac.za>
On Fri, Nov 30, 2007 at 10:56:16AM +0200, Meiring, H, Mnr <meiring@sun.ac.za> wrote:
>
> Hi all,
>
> I am planning to work most of the next month on the porting of the sam7a2 uC and drivers but would appreciate it if someone can guide me through the process please.
>
> Current Project status:
>
> I copied at91sam7s platform/variant and renamed to at91sam7a and adjusted the ecos.db to make a target at91sam7a2 visible consisting only of the basic hal packages.
> CYGPKG_HAL_ARM
> CYGPKG_HAL_ARM_AT91
> CYGPKG_HAL_ARM_AT91SAM7A
> I also adjusted the memory layout files to only run from ram.
I've not looked at the SAM7A2 much. Is it sufficiently different from
the SAM7 what it needs a whole new platform & variant? If it fits, i
would suggest extending the SAM7S package to cover the A2 as well.
> When using my sam-ice jtag device with gdb server and insight,
> redboot runs successfully, (according to me) I can do mfill, dump
> etc for the whole memory range over the usart.
I would run clocktruth and tm_basic, the kernel test programs. If
clock truth works correctly it means timers are O.K. and basic
interrupt handling is working. tm_basic is a good all round test.
Then just pick a few random tests and see if they work. You could
systematically run all the tests, but that takes a while.
> What next? I suppose I need to add a flash driver for the flash
> chips iplemented, but where to start.
Does the A2 have on-chip flash like the SAM7S? If so, it should be
very easy to make the existing driver work. Just add the cpu id. If
it is an external chip, more work is needed. You need the generic
flash driver for the chip you have, plus a hardware specific driver
for your particular platform. This configures the generic driver for
your setup. Look at the other targets for examples.
What comes after that depends on what you want to do with the
hardware. Get the SPI working? Write an I2C driver etc...
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-11-30 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 9:15 Meiring, H, Mnr <meiring@sun.ac.za>
2007-11-30 15:50 ` Andrew Lunn [this message]
2007-12-03 8:47 ` 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=20071130140036.GB593@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@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).