Pogoplug mobile: Invalid CRC

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Pogoplug mobile: Invalid CRC

Postby benm » Sat Jan 26, 2013 1:24 pm

Hello,

I wonder if someone could help.

I have been trying to get netconsole to work on my Pogoplug Mobile. For some reason, most of my failed attempts have triggered a reversion to the stock Pogoplug firmware. Each time this has happened, I have logged in, and reinstalled uBoot in order to reboot into Arch Linux.

$this->bbcode_second_pass_code('', '
killall hbwd
cd /tmp
wget http://archlinuxarm.org/os/ppv4/ppv4-install.sh
chmod +x ppv4-install.sh
./ppv4-install.sh
')

Now however, the ppv4-install.sh script fails with a CRC error.

$this->bbcode_second_pass_code('', '
/tmp # ./ppv4-install.sh
######################################
##
## Pogoplug Series 4 U-Boot Installer
##
######################################

## PREPARATION
# Switching to /tmp...
# Ensuring we're ready to proceed...
killall: hbwd: no process killed
# Checking board revision...
Too many bit errors @ 0xa0000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa0800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa1000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa1800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa2000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa2800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa3000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa3800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa4000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa4800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa5000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa5800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa6000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa6800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa7000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa7800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa8000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa8800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa9000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa9800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaa000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaa800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xab000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xab800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xac000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xac800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xad000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xad800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xae000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xae800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaf000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaf800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb0000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb0800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb1000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb1800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb2000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb2800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb3000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb3800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb4000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb4800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb5000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb5800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb6000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb6800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb7000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb7800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb8000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb8800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb9000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb9800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xba000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xba800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbb000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbb800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbc000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbc800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbd000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbd800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbe000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbe800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbf000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbf800 -- Can't correct!
PAGE DATA:
OOB:
-- Invalid CRC32 on parameters: 0xdd202c9 != 0xbc637c15
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ABORTING!!! UNSUPPORTED MODEL
===================================
This installer is ONLY for Series 4
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
/tmp #
')

Does this mean my flash is corrupt? If so is there anything I can do about it? (Probably not I suppose!)

Many thanks,

Ben
benm
 
Posts: 3
Joined: Sat Jan 26, 2013 12:56 pm

Re: Pogoplug mobile: Invalid CRC

Postby benm » Sat Jan 26, 2013 3:27 pm

P.S. Output from dmesg:

$this->bbcode_second_pass_code('', '
<6>[ 5.900000] XCE: BLPARAMS: -- Loading properties [c4b95ecc].
<6>[ 5.900000] XCE: BLPARAMS: -- MTD @ [c45c0c00].
<6>[ 5.910000] XCE: BLPARAMS: Locating parameter block...
<6>[ 5.910000] XCE: BLPARAMS: reading 2048 bytes @ a0000
<6>[ 5.920000] XCE: BLPARAMS: -- Too many bit errors -- Can't correct!
')
benm
 
Posts: 3
Joined: Sat Jan 26, 2013 12:56 pm

Re: Pogoplug mobile: Invalid CRC

Postby benm » Sat Jan 26, 2013 9:04 pm

Problem solved!

My initial guess when I posted this question was that the area of NAND where the environment is stored was bad. But dmesg didn't show any bad blocks (at least not there).

So I copied fw_printenv, fw_setenv and the configuration file fw_env.config into the root filesystem of the stock firmware and undid the changes I had made earlier trying to get the netconsole to work. I can now boot Arch Linux again.

Incidentally, according to this post

http://forum.doozan.com/read.php?3,14,10863#msg-10863

the Arch version of uBoot does not support netconsole anyway.
benm
 
Posts: 3
Joined: Sat Jan 26, 2013 12:56 pm


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 3 guests