From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] board/ti/am335x/README: Document NAND programming
Date: Wed, 17 Jul 2013 18:04:41 -0400 [thread overview]
Message-ID: <51E714F9.9090908@ti.com> (raw)
In-Reply-To: <1374097974.8183.369@snotra>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/17/2013 05:52 PM, Scott Wood wrote:
> On 07/17/2013 11:24:30 AM, Tom Rini wrote:
>> The AM335x GP EVM ships with NAND. Document programming of the
>> chip including the redundant locations that the ROM will check.
>>
>> Signed-off-by: Tom Rini <trini@ti.com> --- board/ti/am335x/README
>> | 25 +++++++++++++++++++++++++ 1 file changed, 25
>> insertions(+)
>>
>> diff --git a/board/ti/am335x/README b/board/ti/am335x/README
>> index ccc5e16..3444d7e 100644 --- a/board/ti/am335x/README +++
>> b/board/ti/am335x/README @@ -13,6 +13,31 @@ documented in TI's
>> reference designs: - AM335x EVM SK - Beaglebone White -
>> Beaglebone Black +' +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 erase.part kernel +U-Boot # nand write
>> ${loadaddr} kernel 500000
>
> You've already done a "nand erase.chip"... Why do you need to
> erase "kernel" again?
No, that's just what I get for concatening my instructions too
quickly, thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJR5xT5AAoJENk4IS6UOR1Wr9sP/RtZpkzON7zC5LIqEQCfVFBj
vJCTQYB0xKaMGgYLpQ2uLy5PH4CgPuy3PTmdVrK1Ooqj2YHTmZpBH7yjTl3VTjxd
nrODm1VLQ1kd3QNC94ftOzv5vvISfV8A1HtS8WeoExAphFrcpaTnbbSfhcMpQfR6
m+fEdfpHDtzgh2dKZPqPC29XqgDkN5RtcH6jDV+ZujjyBMHuxCc1wslwJZSz2WSv
lY1GKCxHiJALZyII4nCaT7tsRGWJWWZziqFzK+XObYZzcN9XKVimqZGe2vSTM4pu
sl+Sddp7j6EzfxY6vSWRTAuRIa0uiGKHuGm+yA52qyP6FznzdtLzdr/eNEOs34Q4
ekz15q6l8F9z4witCm9msDhxbzjD6imfVylgJHiDqpc0LopQj7fNw4e6PQ3wRvjD
WWti5eGmTeMwxdlm7awBFi9RrMTSz2NnhIAHcN59CVqaobxf/MxtIGAJ8IZeqL81
T9U2U8EauR1Ba7KrJWhYH8U6zic1KChZ2GyTn21HH78Px+Vf15M+qv6RGm6im9m/
yBO2aygKQYNwEMMGyjNAI2a0cy31FuZhYl7MbpQufi7oWPDUtobBMBOQz/V7wBa9
I5QcZ7Fqcd6R9QG58ioPcIzTxzMBB0cfrKhYKMiO1lvHbSt7jIKkpnErXl7djiGp
7xh5j6JWedBDdA5xZSad
=M00E
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-17 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 16:24 [U-Boot] [PATCH 0/1] Add NAND to board/ti/am335x/README Tom Rini
2013-07-17 16:24 ` [U-Boot] [PATCH 1/1] board/ti/am335x/README: Document NAND programming Tom Rini
2013-07-17 21:52 ` Scott Wood
2013-07-17 22:04 ` Tom Rini [this message]
2013-07-30 13:28 ` Tom Rini
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=51E714F9.9090908@ti.com \
--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