From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ Ramdisk crc error ]
Date: Fri, 14 Nov 2008 08:46:30 -0500 [thread overview]
Message-ID: <491D8136.8020805@ge.com> (raw)
In-Reply-To: <000301c9463d$18434160$48c9c420$@com>
sean wrote:
> I've upgrade the capacity of Ram size from 256M to 512M on my custom board
> based on SEQUOIA.
>
> (U-boot Version:2008.10-rc2)
>
> I built a ramdisk image which is 72MB.( Also, I modified rd_size to 73728)
>
> When I boot up my board, I've got a message like below.
>
> RAMDISK: Compressed image found at block 0
> crc error
> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
>
> Why does "crc error" occur??
Your RAMdisk image is corrupt, almost undoubtedly in RAM, not the flash
storage version.
> If I use ramdisk image which is 4MB, "crc error" is not appeared.
>
> And also if I use u-boot for 256MB on 512MB board, "crc error" is not
> appeared.
This is indicating your RAM and/or RAM memory map is messed up. I'm
guessing that, if you use the memory write command to write to the 256K
location (0x10000000), you will find that the same value has "magically"
appeared at location 0... IOW, your RAM memory map has two copies of
half of your memory (address aliasing).
If you do a RAM test, it should detect this problem.
> Here are my U-boot source which I modified to upgrade memory.
Sorry, I'm not familiar with the Sequoia family, so I cannot tell you
how to fix this.
Good luck and happy reading,
gvb
prev parent reply other threads:[~2008-11-14 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 9:40 [U-Boot] [ Ramdisk crc error ] sean
2008-11-14 13:46 ` Jerry Van Baren [this message]
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=491D8136.8020805@ge.com \
--to=gerald.vanbaren@ge.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