Bricked DS

Hi,
I have a bricked DS. The DS does not boot into a OS. I have a serial connection enabled and the output looks like this:

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>>

Is there a way to get the DS back ro live again?

Thanks,
Thomas

The uboot is stock. You can try this: http://bastel.dyndns.info/~dockstar/recover/guide/

See this: http://bastel.dyndns.info/~dockstar/recover/install.txt for similiar error message.

I received my DS in this state and was forced to do the procedure earlier in the DS's life.

Hi dpffan,
understood! In your tutorial you speak about "ce_ramdisk_v2.0b.img.gz" I can only find "ce_ramdisk_v2.0b.img" from the downloads. I thinks this file is the right one, not zipped?!, right? So I have to use this one right?

I yust want to make sure I'll make a big mistake!

Thanks,
Thomas

I didn't write the guide, bastel from a German forum did the hard work. A similiar guide was found on plugapps some time ago but is now gone.

The transfer size mentioned will help:

(note transfer-size -- Should be 11770380)

The files are right there:
http://bastel.dyndns.info/~dockstar/recover/install.txt
leads to: http://bastel.dyndns.info/~dockstar/recover/
which leads to:
http://bastel.dyndns.info/~dockstar/recover/ce_kernel_redstone_v63.img
http://bastel.dyndns.info/~dockstar/recover/ce_ramdisk_v2.0b.img.gz

gratitude @ all ... just painlessly unbricked a "broken" Dockstar that I picked up ... using my trusty old ftdi-based USB-serial adapter that had come in so handy over the years ... unbricking various routers, NAS devices and a few other boxes.

A big thanks to everyone who left a trail of breadcrumbs/pebbles/documentation, so the rest of us could follow more easily.

bastel, your directions were very nice, succinct and most importantly, _correct_!

=====================================================

• davy's Github Repo's rescue-dg

Edited 1 time(s). Last edit at 01/09/2012 07:56PM by davygravy.

Hi Bastel,
thanks a lot for your help! I've revoked 3 DS's to live again. All three came from a distributor from England and had been bricked! They all showed the same error.

Thanks,
Thomas