From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Add a flash programming end marker and progress dots
Date: Fri, 7 Mar 2008 07:44:57 +0100 [thread overview]
Message-ID: <200803070744.57697.sr@denx.de> (raw)
In-Reply-To: <20080307021651.GA32706@cideas.com>
On Friday 07 March 2008, Jerry Van Baren wrote:
> Signed-off-by: Gerald Van Baren <vanbaren@cideas.com>
> ---
>
> OK, how about this for a compromise for end marker and progress dots?
Thanks. Nice work. But I see some problems on my PPC4xx system:
a) Crashes upon flashing 16MBytes
=> cp.b 100000 fe000000 1000000
Copy to Flash
Bad trap at PC: 20202020, SR: 29000, vector=1400
NIP: 20202020 XER: 0000005F LR: 20202020 REGS: 0ff15950 TRAP: 1400 DEAR:
7F7F7FEF
MSR: 00029000 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 00
b) Strange output upon "saveenv" with redundant env sectors:
=> saveenv
Saving Environment to Flash...
. done
Un-Protected 1 sectors
. done
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash... |
|
|
|
done
.......|
. done
Protected 1 sectors
. done
Protected 1 sectors
It seems we have to restrict the output length somehow for this 16MByte
problem. Or perhaps use a fixed length for all sizes.
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
=====================================================================
next prev parent reply other threads:[~2008-03-07 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 2:16 [U-Boot-Users] [PATCH] Add a flash programming end marker and progress dots Jerry Van Baren
2008-03-07 6:44 ` Stefan Roese [this message]
2008-03-07 14:08 ` 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=200803070744.57697.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.