From: richardretanubun <richardretanubun@ruggedcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] saveenv to flash for MPC8360ERDK evaluation board.
Date: Thu, 22 May 2008 10:00:03 -0400 [thread overview]
Message-ID: <48357C63.9050708@ruggedcom.com> (raw)
Hi,
I am trying to update the u-boot for the LogicPD/Freescale MPC8360ERDK
evaluation board and found some problems with saving the environment
configurations to flash.
What I found is that in u-boot 1.3.2 the saveenv command works ok, but
since u-boot 1.3.3-rc1 (and I suspect later version) the command does
not save the environment variable.
from the git-trees, I rolled back /drivers/mtd/cfi_flash.c to the u-boot
1.3.2 version and now the saveenv command seems to work again.
I think some change in there (maybe cmd_set_amd_read_jedec_ids, when
info->device_id is populated)
causes the flash writing mishap.
Have anyone else experienced this as well?
Any suggestions are also welcome.
Thank you,
Richard Retanubun
**RuggedCom Inc.
30 Whitmore Road,
Woodbridge, Ontario,
Canada, L4L 7Z4
next reply other threads:[~2008-05-22 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 14:00 richardretanubun [this message]
2008-05-23 15:38 ` [U-Boot-Users] saveenv to flash for MPC8360ERDK evaluation board Detlev Zundel
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=48357C63.9050708@ruggedcom.com \
--to=richardretanubun@ruggedcom.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