public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v6 (cosmetic) 5/5] board/ti/am335x/README: update for NAND boot
Date: Fri, 20 Sep 2013 09:47:45 -0400	[thread overview]
Message-ID: <20130920134745.GD5273@bill-the-cat> (raw)
In-Reply-To: <1379670059-29992-6-git-send-email-pekon@ti.com>

On Fri, Sep 20, 2013 at 03:10:59PM +0530, Pekon Gupta wrote:

> NAND boot mode on AM335x EVM has been verified, and steps
> to use it has been documented and update in this README
> 
> Signed-off-by: Pekon Gupta <pekon@ti.com>
> Acked-by: Peter Korsgaard <jacmet@sunsite.dk>
> ---
>  board/ti/am335x/README | 53 ++++++++++++++++++++++++++++++++++----------------
>  1 file changed, 36 insertions(+), 17 deletions(-)
> 
> diff --git a/board/ti/am335x/README b/board/ti/am335x/README
> index 2a30ab8..b35e24e 100644
> --- a/board/ti/am335x/README
> +++ b/board/ti/am335x/README
> @@ -46,23 +46,42 @@ NAND
>  The AM335x GP EVM ships with a 256MiB NAND available in most profiles.  In
>  this example to program the NAND we assume that an SD card has been
>  inserted with the files to write in the first SD slot and that mtdparts
> -have been configured correctly for the board.  As a time saving measure we
> -load MLO into memory in one location, copy it into the three locatations
> -that the ROM checks for additional valid copies, then load U-Boot into
> -memory.  We then write that whole section of memory to NAND.
> -
> -U-Boot # mmc rescan
> -U-Boot # env default -f -a
> -U-Boot # nand erase.chip
> -U-Boot # saveenv
> -U-Boot # load mmc 0 81000000 MLO
> -U-Boot # cp.b 81000000 81020000 20000
> -U-Boot # cp.b 81000000 81040000 20000
> -U-Boot # cp.b 81000000 81060000 20000
> -U-Boot # load mmc 0 81080000 u-boot.img
> -U-Boot # nand write 81000000 0 260000
> -U-Boot # load mmc 0 ${loadaddr} uImage
> -U-Boot # nand write ${loadaddr} kernel 500000
> +have been configured correctly for the board. All images are first loaded
> +into memory, then written to NAND.
> +
> +Step-1: Building u-boot for NAND boot
> +	Set following CONFIGxx options for NAND device.
> +	CONFIG_SYS_NAND_PAGE_SIZE	number of main bytes in NAND page
> +	CONFIG_SYS_NAND_OOBSIZE		number of OOB bytes in NAND page
> +	CONFIG_SYS_NAND_BLOCK_SIZE	number of bytes in NAND erase-block
> +	CONFIG_SYS_NAND_ECCPOS		ECC map for NAND page
> +	CONFIG_NAND_OMAP_ECCSCHEME	(refer doc/README.nand)
> +
> +Step-2: Flashing NAND via MMC/SD
> +	# select BOOTSEL to MMC/SD boot and boot from MMC/SD card
> +	U-Boot # mmc rescan
> +	# erase flash
> +	U-Boot # nand erase.chip
> +	U-Boot # env default -f -a
> +	U-Boot # saveenv
> +	# flash MLO. Redundant copies of MLO are kept for failsafe
> +	U-Boot # load mmc 0 0x82000000 MLO
> +	U-Boot # nand write 0x82000000 0x00000 0x20000
> +	U-Boot # nand write 0x82000000 0x20000 0x20000
> +	U-Boot # nand write 0x82000000 0x40000 0x20000
> +	U-Boot # nand write 0x82000000 0x60000 0x20000
> +	# flash u-boot.img
> +	U-Boot # load mmc 0 0x82000000 u-boot.img
> +	U-Boot # nand write 0x82000000 0x80000 0x60000
> +	# flash kernel image
> +	U-Boot # load mmc 0 0x82000000 uImage
> +	U-Boot # nand write 0x82000000 ${nandsrcaddr} ${nandimgsize}
> +	# flash filesystem image
> +	U-Boot # load mmc 0 0x82000000 filesystem.img
> +	U-Boot # nand write 0x82000000 {loadaddress} 0x300000

Missing $ on {loadaddress}.  Fine with fixing this up as part of
applying so:

Acked-by: Tom Rini <trini@ti.com>

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130920/71f5ff8e/attachment.pgp>

      reply	other threads:[~2013-09-20 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20  9:40 [U-Boot] [PATCH v6 (cosmetic) 0/5] mtd: nand: omap: optimize and clean-up of OMAP NAND driver Pekon Gupta
2013-09-20  9:40 ` [U-Boot] [PATCH v6 (cosmetic) 1/5] mtd: nand: omap: enable BCH ECC scheme using ELM for generic platform Pekon Gupta
2013-09-20  9:40 ` [U-Boot] [PATCH v6 (cosmetic) 2/5] mtd: nand: omap: optimize chip->ecc.hwctl() for H/W ECC schemes Pekon Gupta
2013-09-20  9:40 ` [U-Boot] [PATCH v6 (cosmetic) 3/5] mtd: nand: omap: optimize chip->ecc.calculate() " Pekon Gupta
2013-09-20  9:40 ` [U-Boot] [PATCH v6 (cosmetic) 4/5] mtd: nand: omap: optimized chip->ecc.correct() " Pekon Gupta
2013-09-20  9:40 ` [U-Boot] [PATCH v6 (cosmetic) 5/5] board/ti/am335x/README: update for NAND boot Pekon Gupta
2013-09-20 13:47   ` Tom Rini [this message]

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=20130920134745.GD5273@bill-the-cat \
    --to=trini@ti.com \
    --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