public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] sbc8548: document how to write main flash from alternate flash
Date: Mon, 16 Mar 2015 13:57:00 -0400	[thread overview]
Message-ID: <1426528620-28623-1-git-send-email-paul.gortmaker@windriver.com> (raw)

If you are running on the alternate flash in order to fix a
corrupted main flash image, it might be good to have the steps
for that documented as well.

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
 board/sbc8548/README | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/board/sbc8548/README b/board/sbc8548/README
index feac5e3e63e5..493ea837ba3b 100644
--- a/board/sbc8548/README
+++ b/board/sbc8548/README
@@ -138,6 +138,18 @@ image in the SODIMM that is built with CONFIG_SYS_ALT_BOOT enabled,
 	md eff00000 10
 	protect on all
 
+If you are running the alternate 64MB /CS0 settings and want to update
+the "normal" default 8MB u-boot image, then (built with CONFIG_SYS_ALT_BOOT
+disabled) the steps will become:
+
+	tftp u-boot.bin
+	md 200000 10
+	protect off all
+	erase effa0000 efffffff
+	cp.b 200000 effa0000 60000
+	md effa0000 10
+	protect on all
+
 Finally, if you are running the alternate 64MB /CS0 settings and want
 to update the in-use u-boot image, then (again with CONFIG_SYS_ALT_BOOT
 enabled) the steps will become:
-- 
2.2.1

             reply	other threads:[~2015-03-16 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 17:57 Paul Gortmaker [this message]
2015-03-16 18:37 ` [U-Boot] [PATCH] sbc8548: document how to write main flash from alternate flash York Sun
2015-03-16 19:53   ` [U-Boot] [PATCH v2] " Paul Gortmaker
2015-03-16 20:01     ` York Sun
2015-03-16 20:18       ` Paul Gortmaker

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=1426528620-28623-1-git-send-email-paul.gortmaker@windriver.com \
    --to=paul.gortmaker@windriver.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