public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] OneNAND alternative to X-Load
Date: Thu, 24 May 2007 13:29:43 +0200	[thread overview]
Message-ID: <200705241329.43541.sr@denx.de> (raw)
In-Reply-To: <10757753.post@talk.nabble.com>

Hi Pete,

On Wednesday 23 May 2007, Pete MacKay wrote:
> We're developing a PXA-270-based machine that will boot from OneNAND.  I
> wanted to share my ideas (and code) with anyone faced with this challenge,
> since this forum (esp. Kyungmin Park - thank you!!) was quite helpful.
>  I'll start off explaining my u-boot code, then when I get some time I'll
> submit my PXA-270 platform driver as a patch (currently works on 2.6.18).
>
> We use a common approach: in lacking JTAG we have chip select jumpers that
> swap CS0/CS1 between NOR and OneNAND.  The OneNAND has a bottom-mapped 2K
> boot buffer of which 1K is valid, which is where the level 1 boot loader
> fits.  It uses two memory-mapped 'bufferrams' to ping-pong data out of the
> NAND pages, but you want to use BUFFERRAM1 only as writing BUFFERRAM0 can
> corrupt BOOTRAM0 on some revs of the chip.  (We're executing out of
> BOOTRAM0 so that's bad :).
>
> There is open-source code called "x-loader" that is a stripped-down u-boot
> for the level 1 boot loader.  What I did was integrate the level 1
> function into u-boot itself with a custom configuration and linker script.
> In the top u-boot Makefile I added this:
>
> myboard_config	:	unconfig
> 	@./mkconfig $(@:_config=) arm pxa myboard
>
> myboard_onenand_config	:	unconfig
> 	@./mkconfig $(@:_config=) arm pxa myboard
> 	@echo "LDSCRIPT := $(TOPDIR)/board/myboard/u-boot.onenand.lds" >>
> include/config.mk

Did you take a look at the currently implemented NAND booting support in 
U-Boot? Right now the PPC440EPx Sequoia board is the only board in this 
NAND_SPL infrastructure. Please take a look at doc/README.nand-boot-ppc440 
for some more details. And the sequoia board config file too of course.

Your approach is a little different. It would be best, if you could at least 
try to match the infrastructure of nand_spl a little better. For example the 
nand_spl/board/xxx directory with the upon compiletime created links to the 
common files.

Please let me know, if you feel that your OneNAND booting support for your 
board can be implemented in this infrastructure.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2007-05-24 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  5:29 [U-Boot-Users] OneNAND alternative to X-Load Pete MacKay
2007-05-24 11:29 ` Stefan Roese [this message]
     [not found] <2453.69.30.123.186.1179897401.squirrel@architechnical.net>
2007-05-30  1:27 ` Kyungmin Park

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=200705241329.43541.sr@denx.de \
    --to=sr@denx.de \
    --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