public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chun Kit Edwin Lau <edwin@micronedge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot stop booting after environment change + Environment in large nand flash
Date: Fri, 27 Jan 2006 10:19:07 -0500	[thread overview]
Message-ID: <1138375147.13654.25.camel@matrix> (raw)

Hi everyone,

	I have tried the large nand (2k erase size, K9F2G08U0M) code from
testing-NAND.  I can erase/read/write the NAND flash in U-Boot.    I
didn't try any ECC code, but things seems to be working out fine.  I
have modded the env_nand.c a bit to add support for environment in NAND
for this chip.  And it seemed ok.

	I have encountered two issues, on my custom AT91RM9200 board

First, when I changed the default U-Boot environment in
include/configs/at91rm9200dk.h.  The resulting U-Boot didn't even boot.
It only have the line

"Uncompressing image"

coming from boot.bin.  And this problem was reproducible.  And again,
the default U-Boot environment was the only thing I changed.  Is there a
limit on the size of each environment variable?  Did I overwrite some
part of the program because the environment was too long?

Second, I used fw_printenv to retrieve the U-Boot environment from
Linux.  (again, I modded it a little to use the large NAND)  CRC didn't
pass, but in U-Boot the CRC was ok.  I uncommented the CRC checking in
fw_printenv.  And found out that one of the environment was corrupted.
But the U-Boot didn't show the corruption.  Any idea for the two
incidents?  Thanx

Edwin

                 reply	other threads:[~2006-01-27 15:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1138375147.13654.25.camel@matrix \
    --to=edwin@micronedge.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