Dockstar does not boot - serial connection hooked up. Now what?

Hi guys,

I got two dockstars one joined the network and everything went just fine. This other one I could never find via nmap or dhcp. Picked up the Nokia cable and now I have this output.

U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16)

U-Boot code: 00600000 -> 006
7FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB 
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M):
 Done
NAND:
256 MB


CPU : Marvell Feroceon (Rev 1)

CLOUD ENGINES BOARD: REDSTONE:1.0

Streaming disabled 
Write allocate disabled



USB 0: host mode

PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop
 autoboot:  3 
\0x08\0x08\0x08 2 
\0x08\0x08\0x08 1 
\0x08\0x08\0x08 0 

NAND read: device 0 offset 0x100000, size 0x300000


Reading data f
rom 0x100000 --   0% complete.
Reading data from 0x107800 --   1% complete.
Reading data from 0x10f000 --   2% complete.
Reading data from 0x117000 --   3% complete.
Reading data from 0x11e800 --   4% complete.
Reading data from 0x126000 --   5% complete.
Reading data from 0x12e000 --   6% complete.
Reading data from 0x135800 --   7% complete.
Reading data from 0x13d000 --   8% complete.
Reading data from 0x145000 --   9% complete.
Reading data from 0x14c800 --  10% complete.
Reading data from 0x154000 --  11% complete.
Reading data from 0x15c000 --  12% complete.
Reading data from 
0x163800 --  13% complete.
Reading data from 0x16b800 --  14% complete.
Reading data from 0x173000 --  15% complete.
Reading data from 0x17a800 --  16% complete.
Reading data from 0x182800 --  17% complete.
Reading data from 0x18a000 --  18% complete.
Reading data from 0x191800 --  19% complete.
Reading data from 0x199800 --  20% complete.
Reading data from 0x1a1000 --  21% complete.
Reading data from 0x1a8800 --  22% complete.
Reading data from 0x1b0800 --  23% complete.
Reading data from 0x1b8000 --  24% complete.
Reading data from 0x1bf800 --  25% complete.
Reading data from 0x1c7800 --  26% complete.

Reading data from 0x1cf000 --  27% complete.
Reading data from 0x1d7000 --  28% complete.
Reading data from 0x1de800 --  29% complete.
Reading data from 0x1e6000 --  30% complete.
Reading data from 0x1ee000 --  31% complete.
Reading data from 0x1f5800 --  32% complete.
Reading data from 0x1fd000 --  33% complete.
Reading data from 0x205000 --  34% complete.
Reading data from 0x20c800 --  35% complete.
Reading data from 0x214000 --  36% complete.
Reading data from 0x21c000 --  37% complete.
Reading data from 0x223800 
--  38% complete.
Reading data from 0x22b800 --  39% complete.
Reading data from 0x233000 --  40% complete.
Reading data from 0x23a800 --  41% complete.
Reading data from 0x242800 --  42% complete.
Reading data from 0x24a000 --  43% complete.
Reading data from 0x251800 --  44% complete.
Reading data from 0x259800 --  45% complete.
Reading data from 0x261000 --  46% complete.
Reading data from 0x268800 --  47% complete.
Reading data from 0x270800 --  48% complete.
Reading data from 0x278000 --  49% complete.
Reading data from 0x27f800 --  50% complete.

Reading data from 0x287800 --  51% complete.
Reading data from 0x28f000 --  52% complete.
Reading data from 0x297000 --  53% complete.
Reading data from 0x29e800 --  54% complete.
Reading data from 0x2a6000 --  55% complete.
Reading data from 0x2ae000 --  56% complete.
Reading data from 0x2b5800 --  57% complete.
Reading data from 0x2bd000 --  58% complete.
Reading data from 0x2c5000 --  59% complete.
Reading data from 0x2cc800 --  60% complete.
Reading data from 0x2d4000 --  61% complete.
Reading data from 0x2dc000 --  62% complete.

Reading data from 0x2e3800 --  63% complete.
Reading data from 0x2eb800 --  64% complete.
Reading data from 0x2f3000 --  65% complete.
Reading data from 0x2fa800 --  66% complete.
Reading data from 0x302800 --  67% complete.
Reading data from 0x30a000 --  68% complete.
Reading data from 0x311800 --  69% complete.
Reading data from 0x319800 --  70% complete.
Reading data from 0x321000 --  71% complete.
Reading data from 0x328800 --  72% complete.
Reading data from 0x330800 --  73% complete.
Reading data from 0x338000 --  74% complete.
Reading data from
 0x33f800 --  75% complete.
Reading data from 0x347800 --  76% complete.
Reading data from 0x34f000 --  77% complete.
Reading data from 0x357000 --  78% complete.
Reading data from 0x35e800 --  79% complete.
Reading data from 0x366000 --  80% complete.
Reading data from 0x36e000 --  81% complete.
Reading data from 0x375800 --  82% complete.
Reading data from 0x37d000 --  83% complete.
Reading data from 0x385000 --  84% complete.
Reading data from 0x38c800 --  85% complete.
Reading data from 0x394000 --  86% complete.
Reading data from 0x39c000 --  87% complete.

Reading data from 0x3a3800 --  88% complete.
Reading data from 0x3ab800 --  89% complete.
Reading data from 0x3b3000 --  90% complete.
Reading data from 0x3ba800 --  91% complete.
Reading data from 0x3c2800 --  92% complete.
Reading data from 0x3ca000 --  93% complete.
Reading data from 0x3d1800 --  94% complete.
Reading data from 0x3d9800 --  95% complete.
Reading data from 0x3e1000 --  96% complete.
Reading data from 0x3e8800 --  97% complete.
Reading data from 0x3f0800 --  98% complete.
Readi
ng data from 0x3f8000 --  99% complete.
Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-08-31  23:31:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1976384 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... 
Bad Data CRC
CE>>

I issued a 'saveenv' and then 'reset'

Still the same output.

It looks like your device shipped with a bad image on mtd1. You can follow this guide to reflash the partition.

Note to everyone else: Don't follow the above guide unless you're in an identical situation. It is not a good method of 'resetting' a device that you screwed up yourself and we see too many people on this forum (and others) who think it's a good fix-all. It isn't. However, in this very specific instance, it will fix the exact problem it was written to fix.

-- Jeff

Hey Jeff, that worked perfectly. I'm up and going on my second dockstar.

I have a bad image on mtd1. I used the fix Jeff posted above and I got the info below. How do I proceed?

Marvell>> tftp 0x800000 ce_kernel_redstone_v63.img
Using egiga0 device
TFTP from server 10.0.0.1; our IP address is 10.0.0.2
Filename 'ce_kernel_redstone_v63.img'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#####
done
Bytes transferred = 1978608 (1e30f0 hex)
Marvell>> nand write.e 0x800000 0x100000 0x1e30f0

NAND write: device 0 offset 0x100000, size 0x1e30f0
Attempt to write non page aligned data
1978608 bytes written: ERROR
Marvell>>

Did you forget a nand erase command before your write attempt?

You can pad the file to the aligned size with the following command:

dd if=ce_kernel_redstone_v63.img of=ce_kernel_redstone_v63.img.aligned bs=256k conv=sync

-- Jeff

Jeff Wrote:
-------------------------------------------------------
> It looks like your device shipped with a bad image
> on mtd1. You can follow this guide to reflash the
> partition.


I've got the same problem but there is no image to download within the mentioned guide. There's just a broken link. (You get a blank site.)
Is there another mirror?

-- CMS

Jeff Wrote:
-------------------------------------------------------
> Did you forget a nand erase command before your
> write attempt?
>
> You can pad the file to the aligned size with the
> following command:
>
>
> dd if=ce_kernel_redstone_v63.img
> of=ce_kernel_redstone_v63.img.aligned bs=256k
> conv=sync
>
>
> -- Jeff

Hey Jeff i have padded the file like you described bevor. Now i can write the nand but the kernel does not boot.

Marvell>> nand write.e 0x800000 0x100000 0x200000

NAND write: device 0 offset 0x100000, size 0x200000
 2097152 bytes written: OK

...

Marvell>> bootm 0x800000
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1977716 Bytes = 1.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux............................................................................................................................ done, booting the kernel.

Thats all. Nothing else happens.

Any Ideas?

I updated the uboot with http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh.
I can boot from a USB stick with debian, but I can not boot without the USB stick, the original pogoplug.
Here is the part of output of the console.

scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: .....  read_nand_cached: error reading nand off 0x684200 size
 8192 bytes
.  read_nand_cached: error reading nand off 0x797a00 size 8192 bytes
.  read_nand_cached: error reading nand off 0xc40000 size 8192 bytes
read_nand_cached: error reading nand off 0xd87600 size 8192 bytes
read_nand_cached: error reading nand off 0xf0c000 size 8192 bytes
read_nand_cached: error reading nand off 0x12a6000 size 8192 bytes
read_nand_cached: error reading nand off 0x12f4600 size 8192 bytes
read_nand_cached: error reading nand off 0x1be3c00 size 8192 bytes
read_nand_cached: error reading nand off 0x1c0e800 size 8192 bytes
.  read_nand_cached: error reading nand off 0x2036c00 size 8192 bytes
.  read_nand_cached: error reading nand off 0x223a600 size 8192 bytes
 done.
read_nand_cached: error reading nand off 0x797800 size 8192 bytes
read_nand_cached: error reading nand off 0x797800 size 8192 bytes
read_nand_cached: error reading nand off 0x797e00 size 8192 bytes
read_nand_cached: error reading nand off 0xd88000 size 8192 bytes
off = 0xd87724 magic 0x1985 type 0xe002 node.totlen = 2597
read_nand_cached: error reading nand off 0xf0c000 size 8192 bytes
off = 0xf0be38 magic 0x1985 type 0xe002 node.totlen = 1927
read_nand_cached: error reading nand off 0x12a6000 size 8192 bytes
off = 0x12a5bb4 magic 0x1985 type 0xe002 node.totlen = 1750
read_nand_cached: error reading nand off 0x12f4000 size 8192 bytes
off = 0x12f3b60 magic 0x1985 type 0xe002 node.totlen = 2836
read_nand_cached: error reading nand off 0x18c3c00 size 8192 bytes
off = 0x18c3a48 magic 0x1985 type 0xe002 node.totlen = 1768
read_nand_cached: error reading nand off 0x1be3a00 size 8192 bytes
off = 0x1be3420 magic 0x1985 type 0xe002 node.totlen = 2294
read_nand_cached: error reading nand off 0x1c0da00 size 8192 bytes
off = 0x1c0d938 magic 0x1985 type 0xe002 node.totlen = 2708
read_nand_cached: error reading nand off 0x223a800 size 8192 bytes
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...


U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: REDSTONE:1.0

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x300000

Reading data from 0x3ff800 -- 100% complete.
 3145728 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-08-31  23:31:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1976384 Bytes =  1.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
CE>>

I think my mtd0 is still good, but the mtd1 or mtd2 is corrupted. I didn't not backup this device, but I do have mtd1 and mtd2 backup from another dockstar.
Can I just flash that mtd1 and mtd2 image to this dockstar? How can I do it with the serial cable?

Thanks!



Edited 2 time(s). Last edit at 05/01/2011 02:05AM by qingz.

qingz Wrote:
-------------------------------------------------------
> Can I just flash that mtd1 and mtd2 image to this
> dockstar? How can I do it with the serial cable?

Maybe this,
http://www.plugapps.com/index.php5/Hardware:_Seagate_DockStar_Reflashing

But, if you don't have any special need for the original Pogo firmware, I would just install Jeff's Rescue System. I've got three Dockstars all using Jeff's Uboot and Rescue System

laprjns Wrote:
-------------------------------------------------------
> qingz Wrote:
> --------------------------------------------------
> -----
> > Can I just flash that mtd1 and mtd2 image to
> this
> > dockstar? How can I do it with the serial
> cable?
>
> Maybe this,
> http://www.plugapps.com/index.php5/Hardware:_Seaga
> te_DockStar_Reflashing
>
> But, if you don't have any special need for the
> original Pogo firmware, I would just install
> Jeff's Rescue System. I've got three Dockstars
> all using Jeff's Uboot and Rescue System

Good idea!
I installed the Rescue System, everything works fine.

Thank you!