public inbox for
 help / color / mirror / Atom feed
From: Evgeniy Dushistov <>
Subject: at91sam9263ek support ver. beta 2
Date: Thu, 05 Feb 2009 13:39:00 -0000	[thread overview]
Message-ID: <> (raw)


here is updated version of series of patches to support at91sam9263ek.
I recieved and signed papers from fsf and I hope in near future they recive them.

High level changes:
- as discussed earlier, there is now arm7 package, and all variants of at91 use it,
and at91sam9 uses arm9
- there is now romram startup, so it is possible to program nor flash, press reset and you see
redboot message during next power on

Here is link to patches with description.

This patch introduces arm7 package, now all at91 variants are based on arm7 package.
So it is now possible to introduce another at91 variant based on arm9.
And hal_cache.h and so on stuff will be used from these package:

Change default delay in getting character via serial line method,
to correctly handle 115200 baudrate case:

This patch separate board's pio layout.
Extract each variant of pio's layout to separate header file:

Move common for arm9 code for work with mmu into common header (var_mmu.h):

hal package for at91sam9263ek and at91sam9.
 Support only starting from ram, and output to dbgu port.
 	- ecos library + hello world working.
 	- starting redboot using jtag
 	- starting redboot from flash using at91bootstrap
 Changes from previous version:
 - add romram and jtag variants of startup

implement support of pio interrupts in the way as ordinal interrupts work:

Support atmel norflash that possible to install on  at91sam9263-ek board:

can support for at91sam9263ek:

Any comments?

             reply	other threads:[~2009-02-05 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 13:39 Evgeniy Dushistov [this message]
2009-08-13  9:26 ` John Eigelaar
2009-08-13 11:29   ` Re[2]: " Evgeniy Dushistov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).