Where to download the ce_kernel_redstone_v63.img ?

I partially bricked my dockstar couple days ago. Then I got a CA-42 Cable, but when I tried to follow the instruction: http://wejp.k.vu/dockstar/dockstar_repair_with_serial_cable , I could not download the kernel image from plugapps.com, it seems that the website is down except the forum.

Anyone can help me find the file? I appreciate your help!

Try this:
http://archlinuxarm.org/mirror/ce/

Thank you very much for your help.

However, I figured out that the problem comes from "Pogoplug install" as mentioned in

http://forum.doozan.com/read.php?2,243,264#msg-264

I tried to download the file from http://jeff.doozan.com/debian/uboot/uboot-original-mtd0.kwb

But the link is not working any longer, searched online, still no luck..:(

Can you help me find the uboot-original-mtd0.kwb? Thanks!

http://jeff.doozan.com/debian/uboot/files/uboot/uboot.mtd0.dockstar.original.kwb

Thanks a lot!

But by following some instructions that worked for other people, I got several weird issues. So, I'm trying to make one question clear.

As long as I can watch the booting process through the ttl cable (no matter it fails or not), the Dockstar is not "really" bricked, then I should be able to find a way to re-flash it back without JTAG. And the "real brick" only happens when we reflash the mtd0 with any errors.

Am I correct?

Yes, as long as uboot and uboot environment is intact, serial console is good enough to fix most problems.

As you probably already know, you will need the original uboot. Jeff's one will not work for this purpose. This is probably why you tried to find the original uboot in the first place. I learned it the hard way. However, when I did the reflash, my Debian still worked. I flash the original uboot under Debian. If it does not, what you are going to reflash the original uboot in the first place. If you flash it wrong, you might really brick the Dockstar. (I am not saying it will, but just something I never did before.)

It seems I am in nowhere now :(

I want to make it clear to see if anyone could help me.

I was able to run plugapp with no problem, then I decided to try Debian on my dockstar. Reflashing went smooth, but after that it would not reboot, either with usb or not, the orange light blinks forever, however, ping works and I can see the dockstar on my router.

After I got the ttl cable yesterday, I chose to reflash the original uboot because I saw online someone got into the same situation and had it fixed by this way. By following the guide @ http://cyres-server.net/content/linux/dockstar/hsdrp.htm, I got some problems:

Marvell>> resetenv
Unknown command 'resetenv' - try 'help'

so I skipped it and did the following, then I came up with

Marvell>> tftp 0x800000 ce_kernel_redstone_v63.img
Using egiga0 device
TFTP from server 192.168.1.66; our IP address is 192.168.1.75
Filename 'ce_kernel_redstone_v63.img'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #####
done
Bytes transferred = 1978608 (1e30f0 hex)

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

Then I changed it to

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

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

And finally,

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:    1978544 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.

It hangs at there forever, led is not blinking any longer.

If I reboot and don't interrupt the uboot, it shows

U-Boot 2010.09 (Feb 16 2011 - 18:42:49)
UBIT v0.6 by Jeff Doozan and Peter Carmichael

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1752
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             1731
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:silent", error -19
Error reading superblock on volume 'ubi:silent'!
UBIFS not mounted, use ubifs mount to mount volume first!
Using egiga0 device
ping failed; host 10.10.10.5 is not alive
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 

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

Hanging, green light blinks.

Then I restarted the dockstar, and tried this way

Marvell>> setenv serverip 192.168.1.66
Marvell>> setenv ipaddr 192.168.1.75
Marvell>> tftp 0x800000 uboot.mtd0.dockstar.original.kwb
Using egiga0 device
TFTP from server 192.168.1.66; our IP address is 192.168.1.75
Filename 'uboot.mtd0.dockstar.original.kwb'.
Load address: 0x800000
Loading: ####################################
done
Bytes transferred = 524288 (80000 hex)
Marvell>> go 0x800200
## 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 

CE>> run bootcmd_original
## Error: "bootcmd_original" not defined

Then, I don't know where to go.................really frustrating............

Anyone would help?



Edited 2 time(s). Last edit at 06/30/2011 02:28PM by xddy.

Looks like you have already installed replaced the uboot, with Jeff's uboot. The indication is that with Jeff's uboot, the prompt is: Marvell>>.... the original uboot will give you a prompt of "ce>>...". As I said before, with Jeff's uboot, the flash of ce_kernel_redstone_v63.img and etc will not work. The key now is how to reflash back the original uboot given by "uboot.mtd0.dockstar.original.kwb". I don't have any experience with that except reflash it using Debian or other Linux firmware that obviously you cannot do right now.
Another less risky way is to make the Debian work by modifying the environment variables. I don't know if this will work but in the uboot prompt, you should be able to see why it does not boot (with USB drive inserted). You might want to post the response as you did above. After that you can print out the environment parameters to see if they are setting correctly.

Updates: I tried not to interrupt the booting in the last step, then it seems I got something like

[    1.940000] Linux telephony interface: v1.00
[    1.950000] md: linear personality registered for level -1
[    1.950000] md: raid0 personality registered for level 0
[    1.960000] md: raid1 personality registered for level 1
[    2.130000] raid6: int32x1     97 MB/s
[    2.300000] raid6: int32x2    114 MB/s
[    2.470000] raid6: int32x4    122 MB/s
[    2.640000] raid6: int32x8    110 MB/s
[    2.640000] raid6: using algorithm int32x4 (122 MB/s)
[    2.640000] md: raid6 personality registered for level 6
[    2.650000] md: raid5 personality registered for level 5
[    2.650000] md: raid4 personality registered for level 4
[    2.660000] raid5: measuring checksumming speed
[    2.710000]    arm4regs  :  1084.000 MB/sec
[    2.760000]    8regs     :   754.800 MB/sec
[    2.810000]    32regs    :   899.600 MB/sec
[    2.810000] raid5: using function: arm4regs (1084.000 MB/sec)
[    2.820000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    2.820000] dm_crypt using the OCF package.
[    2.830000] sdhci: Secure Digital Host Controller Interface driver
[    2.830000] sdhci: Copyright(c) Pierre Ossman
[    2.840000] usbcore: registered new interface driver usbhid
[    2.840000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    2.850000] TCP cubic registered
[    2.850000] NET: Registered protocol family 1
[    2.860000] NET: Registered protocol family 17
[    2.860000] md: Autodetecting RAID arrays.
[    2.870000] md: autorun ...
[    2.870000] md: ... autorun DONE.
[    7.200000] Empty flash at 0x00de8e44 ends at 0x00de9000
[   10.340000] VFS: Mounted root (jffs2 filesystem) readonly.
[   10.340000] Freeing init memory: 124K
init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST)
starting pid 267, tty '': '/etc/init.d/rcS'
[   12.460000] eth0: link down
[   12.470000] eth0: started
udhcpc (v1.7.0) started
HWADDR 00 0x10 0x75 0x1a 0x9c 0x26
PIP0 156
PIP1 38
cat: can't open '/etc/resolv.conf': No such file or directory
route: SIOCDELRT: No such process
grep: /etc/resolv.conf: No such file or directory
Sending discover...
[   14.100000] eth0: link up, full duplex, speed 100 Mbps
Sending discover...
Sending select for 192.168.1.75...
Lease of 192.168.1.75 obtained, lease time 86400
HWADDR 00 0x10 0x75 0x1a 0x9c 0x26
PIP0 156
PIP1 38
route: SIOCDELRT: No such process
starting pid 377, tty '': '/bin/sh'
-sh-3.2#

It seem like I got it started, but I don't know what to do in the next......

Can you ssh into it at 192.168.1.75?
If you can, you have already the original firmware working. Then do a ping google.com to see if you can get to outside world. If you can reach google, everything should be file. You can reinstall debian or anything else if you like. However, without resolv.com, you might not be able to get DDNS server so you need to set to the direct ip address..

No, I still cannot using putty to do ssh connection to the dockstar.

I also tried to plug the flash drive in, it can be partially recognized, but not mounted like

[ 2531.240000] usb 1-1.3: new high speed USB device using ehci_marvell and address 3
[ 2531.340000] usb 1-1.3: configuration #1 chosen from 1 choice
[ 2531.350000] scsi0 : SCSI emulation for USB Mass Storage devices
[ 2536.380000] scsi 0:0:0:0: Direct-Access     Kingston DT 101 G2        PMAP PQ: 0 ANSI: 0 CCS
[ 2537.980000] sd 0:0:0:0: [sda] 15646720 512-byte hardware sectors (8011 MB)
[ 2537.990000] sd 0:0:0:0: [sda] Write Protect is off
[ 2538.000000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 2538.010000] sd 0:0:0:0: [sda] 15646720 512-byte hardware sectors (8011 MB)
[ 2538.020000] sd 0:0:0:0: [sda] Write Protect is off
[ 2538.020000] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 2538.030000]  sda: sda1 sda2
[ 2538.060000] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 2538.060000] sd 0:0:0:0: Attached scsi generic sg0 type 0

after I hit enter, it goes back to sh-3.2#, then

-sh-3.2# mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (ro)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /tmp type tmpfs (rw)
none on /proc/bus/usb type usbfs (rw)

it seems nothing mounted on it. My understanding is that, if I cannot find a usb drive, I can not install debian or plugapp, am I right?