Regarding the redstone kernel image

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

Regarding the redstone kernel image

Postby minigendo » Sat Mar 26, 2011 6:16 am

Greetings,

When I purchased my dockstar, I was sent a dud, and then a working one. I was allowed to keep the dud. I got to thinking however, that it might be possible to fix it. After hacking together a serial cable and connecting it I can see that it fails to boot on: Verifying Checksum ... Bad Data CRC

Reading through various forums, it seems that I need to reflash the unit. However, I can't seem to find the proper files to make the attempt. The ones mentioned at http://Arch Linux ARM.com/index.php5?title=Ha ... Reflashing either don't exist or I don't have permission to access. Can anyone recommend a location to find the files? Barring that, could anyone give any guidance on how to extract the files from my working dockstar?

My thanks in advance.

I provide the output of the failed boot below just in case anyone is interested.

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
minigendo
 
Posts: 4
Joined: Sat Mar 26, 2011 6:04 am

Re: Regarding the redstone kernel image

Postby minigendo » Sun Mar 27, 2011 12:24 am

Greetings,

The word from pogoplug support is that no dockstar images will be provided. They did point me off to http://pogoplug.com/home-en-developers-open-source.html where kernels are available for Pogoplug Pro, Pogoplug V2, Pogoplug Biz, and Pogoplug V1.

That doesn't seem to help me however. I was hoping to turn the dud dockstar into a linux box, and only need the images so that I can, hopefully, restore it to the point where I can install linux. Is there a way to do this without going back to default dockstar mode first? Alternatively, could I install a better u-boot and then boot linux off a usb drive?

It seems strange that I can't take the image off the working dockstar. Many websites recommend backing up the flash before performing various operations, but I've yet to find one that details how to recover if things do go wrong.

Any help anyone could offer would be most appreciated.
minigendo
 
Posts: 4
Joined: Sat Mar 26, 2011 6:04 am

Re: Regarding the redstone kernel image

Postby WarheadsSE » Sun Mar 27, 2011 7:21 pm

minigendo,

Essentially, if you get a good set of backup images, from the 'Marvell >>' prompt (the default uboot) you should be able to write those images to the nand, after loading them via tftp. So, if you can obtain a good and valid set, you should be all set. I cannot however speak to the specific locations to write them to, as I do not personally have experience with a dockstar.

Best of luck
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Regarding the redstone kernel image

Postby unplugged » Thu Mar 31, 2011 6:23 pm

minigendo, not sure if this helps, but have you seen Jeff's http://jeff.doozan.com/debian?
unplugged
 
Posts: 8
Joined: Fri Sep 03, 2010 2:35 pm

Re: Regarding the redstone kernel image

Postby minigendo » Sat Apr 02, 2011 4:50 pm

My thanks for your suggestions.

In response to WarheadsSE,
Jeff Doozan's site offers a nandump tool. I've dumped the appropriate flash device, and opening the resultant 4 mb file in a tex editor, can actually see the image file within it. Sadly, even after trimming what I assume are the null characters off, I don't get a byte match for the image file.

Given that the bootloader seems to work off memory addresses, I'm going to copy the "good" nandump over and see what happens. I'm hoping a blind copy will leave things pointing where they should, but it seems iffy. Still, it's not like the image being overwritten could be more broken.

In response to unplugged,

I have seen that site, it's where I got the notion of trying a better uboot and a usb boot. Unfortunately, the instructions provided all seem to hinge on having a functional device to work off of. Even if I tftp in the new boot loader, I fear that the steps indicated to create the usb boot drive will alter the nature of my current working unit (on which I would need to run them).

Still, if the nanddump / restore doesn't work, I'll likely be giving it a shot.

My thanks again for the suggestions.
minigendo
 
Posts: 4
Joined: Sat Mar 26, 2011 6:04 am

Re: Regarding the redstone kernel image

Postby minigendo » Sun Apr 03, 2011 6:03 pm

I was successful.

Using Doozan's nandump tool, I made a copy of mtd01 on the working dockstar.

./nanddump -nof usb/mtd1 /dev/mtd1

I then serial cabled into the broken one and interrupted the boot sequence.

By using the tftp server, I loaded the mtd1 file into memory

tftp 0x800000 mtd1

I then erased the flash:

nand erase 0x100000 0x400000

And overwrote it with the entire contents of mtd1 dump.

nand write.e 0x800000 0x100000 0x400000

After power cycling, the device booted right up, working it seems, as a fully functional dockstar. Now I can proceed with ripping out that functionality. If I may ask, does anyone have any favorites with regards to turning the device into a full linux machine?
minigendo
 
Posts: 4
Joined: Sat Mar 26, 2011 6:04 am

Re: Regarding the redstone kernel image

Postby mlitke » Mon May 02, 2011 3:56 am

I have a few Dockstars and could dump and make the images available if you are still interested. I have a couple with the original factory kernel and also a couple with the updated factory kernel. Dumps from the serial connection:

With the newer kernel:
## Booting image at 00800000 ...
Image Name: Linux-2.6.22.18
Created: 2010-10-19 23:05:02 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1979140 Bytes = 1.9 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

With the older kernel:
## 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 ... OK
OK
mlitke
 
Posts: 55
Joined: Sat Apr 30, 2011 5:27 am

Re: Regarding the redstone kernel image

Postby jasonldf » Tue May 03, 2011 1:37 pm

jasonldf
 
Posts: 8
Joined: Sun Dec 12, 2010 3:47 am

Re: Regarding the redstone kernel image

Postby mlitke » Wed May 04, 2011 3:01 pm

I just downloaded the kernel and ramdisk files from the mirror, and the ramdisk is not the same size as what is listed in the Seagate DockStar Reflashing instructions. 11,770,457 versus 11,770,380 bytes. The kernel size matches (1,978,608 bytes).
mlitke
 
Posts: 55
Joined: Sat Apr 30, 2011 5:27 am

Re: Regarding the redstone kernel image

Postby jasonldf » Thu May 05, 2011 2:41 pm

http://www.hardwareluxx.de/community/15 ... st766.html

Seems like the size differed but the offset is more important. I worked that out from google translate.
jasonldf
 
Posts: 8
Joined: Sun Dec 12, 2010 3:47 am

Next

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 7 guests