From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steven Scholz <steven.scholz@imc-berlin.de>
Date: Wed, 03 Nov 2004 09:57:42 +0100
Subject: [U-Boot-Users] INFO: U-Boot for AT91RM9200DK
In-Reply-To: <1CFEB358338412458B21FAA0D78FE86D2C72B8@rennsmail02.eu.thmulti.com>
References: <1CFEB358338412458B21FAA0D78FE86D2C72B8@rennsmail02.eu.thmulti.com>
Message-ID: <41889D86.80305@imc-berlin.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Paugam Luc wrote:

> Hi all,
> 
> I am currently working on the port of U-Boot onto a custom board 
> containing a ATMEL AT91RM9200. From now I use the ATMEL evaluation 
> board (AT91RM9200-DK).
> 
> To do that, I grabbed the sources of U-Boot from the CVS server 
> and looked at the mailing archive.
> I found the following mail from Steven Scholz which explained that
> ATMEL use a primary bootstrap code 'boot.bin' before booting U-Boot 
> (considered as the secondary bootstrap) from SDRAM.
> 
> I would like to see U-Boot as the unique boot code and get rid of 
> the ATMEL booting method for their AT91RM9200-DK evaluation board.
> 
> Does someone already do this job? 
> As I don't see it inside the current sources of U-Boot?

Of course.
When my ta91_soc.patch from Oct 10 2004 finally gets applied (Wolfgang?), then 
the AT91RM9200 is just an SoC based on ARM920T. And all you have to do is
#define CONFIG_INIT_CRITICAL 1 and write you board specific memsetup() function 
to init clocks and SDRAM.

--
Steven