From: Kenneth Johansson <kenneth@southpole.se>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot booting from NAND
Date: Fri, 13 Jun 2008 15:47:05 +0200 [thread overview]
Message-ID: <1213364825.29745.17.camel@localhost.localdomain> (raw)
In-Reply-To: <37367b3a0806130624y6f4548f6mb2f8c0a975ad21eb@mail.gmail.com>
On Fri, 2008-06-13 at 10:24 -0300, Alan Carvalho de Assis wrote:
> Hi,
> I am trying to port U-Boot to MX31PDK board, but I getting a problem
> related to lowlevel initialization to boot from NAND flash memory.
>
> The problem is because cpu/arm1136/start.S waste so much space with
> IRQ/FIQ handling and stack initialization then lowlevel_init function
> is placed at 0x400 position. As the NAND controller from i.MX31 copy
> just 2KB to NANDFC internal buffer and lowlevel_init has about 0x6b0
> bytes then the final position is after 0x800 (2KB) then the SDRAM
> initialization routine and NAND block copy to SDRAM doesn't work.
>
> Comparing with RedBoot I verified it place the lowlevel routines at
> 0x120 position then it fit in 2KB and all works fine.
>
> I need help to modify cpu/arm1136/start.S and place the lowlevel_init
> at 0x120 position instead 0x400. I am not ARM assembly expert then any
> help is welcome.
>
I ditched the entire reuse thing when I implemented nand boot for a
5121e platform. 2k was to little space to try to force in the generic
files. just make a new start.S that do only the things it needs to.
basically it only sets up the stack pointer to the internal SRAM. then
the C code relocates the code from the nand controllers internal 2k into
internal SRAM. sets up the memory controller , then reads out u-boot
into dram and jumps to _start.
next prev parent reply other threads:[~2008-06-13 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 13:24 [U-Boot-Users] U-Boot booting from NAND Alan Carvalho de Assis
2008-06-13 13:47 ` Kenneth Johansson [this message]
2008-06-14 21:50 ` Wolfgang Denk
2008-06-16 10:22 ` Kenneth Johansson
2008-07-05 22:32 ` Wolfgang Denk
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=1213364825.29745.17.camel@localhost.localdomain \
--to=kenneth@southpole.se \
--cc=u-boot@lists.denx.de \
/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