[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-omap
Subject:    U-boot at 0x10000
From:       ksriram () ti ! com (Sriram, Kannan)
Date:       2007-06-28 2:25:10
Message-ID: 0A50DBE80DD6674E94F7269DC964A7B618136F () dbde01 ! ent ! ti ! com
[Download RAW message or body]



> -----Original Message-----
> From: linux-omap-open-source-bounces@linux.omap.com
[mailto:linux-omap-
> open-source-bounces@linux.omap.com] On Behalf Of arun c
> Sent: Thursday, June 28, 2007 4:20 PM
> To: linux-omap-open-source@linux.omap.com
> Subject: U-boot at 0x10000
> 
> Hi all,
> 
> 
> Thank you very much Sriram.
> 
> >From the answer i understand,
> 
> 1) While flashing, Nand is addressed at 0x0c000000
> thats why we write xload.bin.ift there
>
Yes, during flashing using CSST, CSST .2nd configures the NAND flash to
be mapped at 0x0c000000 (which typically is on CS1, if you look at your
switch settings).
 
> 2) While booting from nand flash it is addressed(CS0) at 0x0
> Thats why we flash u-boot at 0x10000(0+4*16k=0x10000)
> 
While booting, NAND flash would typically be mapped to 0x08000000 by the
boot ROM code (while Xloader begins to run), and later on be remapped to
a different address (maybe even 0x00) by Xloader or u-boot. Also, while
booting, NAND must be at CS0.

> 
> Is this correct?
> 
> Thanks&warm regards
> Arun c
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source

[prev in list] [next in list] [prev in thread] [next in thread]