From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Micron JS28F128J3F75 Uboot setenv problem
Date: Fri, 18 Nov 2011 19:10:26 +0100 [thread overview]
Message-ID: <4EC69F92.2090905@keymile.com> (raw)
In-Reply-To: <3B4EE681DBC17A409A36BD429FA5E58533A3877A@KS-Mail.kathr-b.loc>
Hi,
On 18/11/11 14:57, Spranger, J?rg wrote:
>
> we have a small AT91RM9200 based board, running Linux on it and it worked fine.
> Now we face 2 major changes:
>
> 1. The strataflash JS28F128j3d75 shifted to JS28F128j3f75
>
> 2. The uboot is updated from 2009.01 to 2010.09
>
> Now when I have a new board flashing the bootloader and make a reboot,
> I get the warning
> *** Warning - bad CRC, using default environment
> That is ok, because in the flash on that place are only FFFFs when the flash is erased.
> Normaly I get rid of it, when I make a setenv.
>
> This works with the old u-boot with both types of flash. When I take the new uboot it only
> works with the old flash. The curious thing is that taking the new uboot and the new flash
> the setenv writes the variables into the flash at the right place BUT after a reboot
> I get the same warning. Looking at the flash with md, I can see the hole environment variables
> In place. Also the CRC is the same as when I do it with the old flash.
>
> It seems that there is something different when reading from the device, maybe an initilisation?
>
> This is the point where I have to ask the community where to look next.
>
we had similar problems with a Intel Strata 28F320 when updating from a v2009.08 u-boot to a recent
version. We had to revert one commit (and still do in our local tree). See discussion:
http://lists.denx.de/pipermail/u-boot/2011-March/088382.html
Best regards
Holger
next prev parent reply other threads:[~2011-11-18 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 13:57 [U-Boot] Micron JS28F128J3F75 Uboot setenv problem Spranger, Jörg
2011-11-18 18:10 ` Holger Brunck [this message]
2011-11-21 10:16 ` Jörg Spranger
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=4EC69F92.2090905@keymile.com \
--to=holger.brunck@keymile.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