• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Linux Stuff / Kernel / Re: Included uImage too large to write to NAND on: April 14, 2009, 05:59:07 AM
I've run into the bad CRC error before.  It ALWAYS happened when I flashed without erasing.  In fact just to test I reflashed my kernel and rebooted and sure enought here it was.  So you might try after getting a successful boot from tFTP:
flash_eraseall /dev/mtd1
nandwrite -pm /dev/mtd1 <yourimage>

Thanks for the tip - much appreciated.
I've done this process 3 times on the plug, I've run flash_eraseall each time.
I've used nandwrite with -p flag, and I've used cat image > /dev/mtd1.  In all of these cases, the 2nd time I cold boot, it fails with bad data CRC.

Your suggestion has one new element I've not seen before:  the -m flag..  I'll try it.
2  Linux Stuff / Kernel / Re: Included uImage too large to write to NAND on: April 13, 2009, 01:30:08 PM

Thanks for suggestion.  I will get to filesystem on USB eventually.  Maybe sooner than I like..

Your words about "length of what is loaded" give me a hint..  At work right now, can't play.  But I will experiment tonight and will report if succes (and will whine some more if fail.)
3  Linux Stuff / Kernel / Re: Rebuilding the kernel on: April 13, 2009, 01:20:46 PM

What did you mean about -
"I'm thinking a troubleshooting forum might be a good idea." ?

Opening a new forum for this? I was thinking that we can post Q&A on the forum itself, which includes troubleshooting, announcements etc...


I think this forum is a great idea.  So far, the forum contributors have been great at trying to help each other.  But some things seem to be just beyond our grasp - maybe with some contribution from knowledgeable Marvell or GlobalScale persons, the forum will be enough (by itself) to help users solve their Sheeva Plug issues.

Note that I do not at all demean the level of expertise represented by the contributors.  But each person has their own set of issues / aspects that they are trying to solve.  When problems align for multiple users, the combined brainpower seems to render a solution that applies to more than one user.

I personally am still struggling, and posts to several different forums in addition to this one have me no closer to a solution.  I'm not complaining about Marvell, nor about GlobalScale.  Just struggling.  The PlugWiki has 'almost' enough docs to give a reasonably linux-experienced person enough to do things.  But when unpredictable results occur, and the personal level of linux-experience is maxed out, it's frustrating.

This is a great product, with a huge amount of promise.  I hope this support forum can grow and be robust to the point where most problems can be solved without relying too heavily on the professionals (at Marvell / GlobalScale.)

Just my .02

4  Linux Stuff / Kernel / Re: Included uImage too large to write to NAND on: April 13, 2009, 08:24:23 AM

I had the exact same problem as moshiach.  Different results..   Undecided

I have re-sized /dev/mtd1 pretty much same as he posted.
I have flashed uImage on to the Plug using both the nandwrite and 'cat > /dev' methods.

In both cases, (after I resized the partition) I can boot once with success.  But only once.

Making zero changes after a cold boot of a fresh flash of uImage, all bootargs are sane and *ought* to boot from flash.

The second time I try to cold boot, it fails every time with Bad Data CRC.

I'm not sure what to try next.  I have 2 suspicions.  But I could be totally wrong..  anyway,

1) flash_eraseall is misbehaving.
2) something is screwy with Plug's Ecc bits.

The uImage file that I flash with is exact same image file that I boot via NFS.  It works via NFS every time.  So I think it safe to rule out "corrupt image file."

Next steps I think are to investigate the beginning pages of each partition;
a) in current state = no boot 'Bad Data CRC'
b) right after a flash_eraseall
c) right after a "successful" flash operation
d) after a failed boot

Any suggestions are most welcome.
Pages: [1]