Recovering Dockstar starting from Uboot prompt

[twave]

I was successful originally installing Arch Linux ARM install Linux. Unable to leave well enough alone, I tried some things I learned in reading the forums and ended up with a non usable Dockstar.

I messed up my Dockstar and can only boot up to the <Marvell> prompt. I've researched the forums for the past few days looking for a solution. Either I didn't understand what was being said or the solutions I tried didn't work. I would like to get the Dockstar to a usable point. It can be the original Dockstar pogoplug firmware or the Arch Linux ARM install Linux firmware.

Is there a way of using the nanddump backups I made prior to installing Arch Linux ARM install Linux following the instructions in the Wiki "Arch Linux ARM:Pogoplug_Setboot".

Is it possible to boot the Arch Linux ARM install Linux that I have on a USB Drive so that I can use it to recover? Is there any other method of getting it running again beginning with the Marvell prompt?

[bzboi]

Purchase a CA-42 serial cable and follow the instructions in the first link in my signature.

[twave]

I have a CA-42 cable and have tried that method. It fails to write the kernel with a "Attempt to write non page aligned data" message. In one of the responses I read it says this is due to using the jeff.doozan uboot and that I would have to restore the original uboot. Problem is that I can't find a way to do that.

[bzboi]

I don't use Jeff's uBoot. Does it still rely on chain booting to the original uBoot or can it boot the original Pogoplug kernel natively these days? Also, can you attach a log of your printenv? If you still have your Arch Linux ARM on a USB flash, it may be as simple as fixing your env file and you can boot to Arch Linux ARM.

JTAG would certainly be the easiest way to restore the stock uBoot, but really should be a last resort. You certainly want to try to boot to either the stock kernel or Arch Linux ARM first.

[twave]

Here is printenv in its current state. I have do Arch Linux ARM install on a usb since this device was running it at one point before I decided to make things better .

$this->bbcode_second_pass_code('', '
printenv
ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
if=netconsole ping $serverip
ethaddr=xxxxxx
cesvcid=xxxxxxx
partition=nand0,2
mtddevnum=2
mtddevname=rootfs
serverip=192.168.222.10
ipaddr=192.168.222.25
console=console=ttyS0,115200
bootargs_root=root=/dev/mtdblock2 ro
bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000
stdin=serial
stdout=serial
stderr=serial
bootargs=$(console) $(bootargs_root)
')

[bzboi]

Did you ever figure this out? Did my last PM to you help?

It's a lot riskier in terms of bricking potential, but if you have given up fixing the env settings and just want to restore the original uBoot, you can setup a TFTP server on a Linux/Windows PC on the same network (I use SolarWinds on XP) and do the following:-

1) Download http://jeff.doozan.com/debian/uboot/fil ... iginal.kwb and stick it in your TFTP directory.

2) At uBoot prompt, enter:-
$this->bbcode_second_pass_code('', '
// Set Dockstar IP & netmask
setenv ipaddr xxx.xxx.xxx.xxx
setenv netmask xxx.xxx.xxx.xxx
// Set TFTP server IP
setenv serverip xxx.xxx.xxx.xxx
// Confirm that you can get from Dockstar to TFTP server
ping $(serverip)
// Load uBoot to Dockstar RAM
tftp 0x800000 uboot.mtd0.dockstar.original.kwb
// Erase just enough of NAND to replace uBoot
nand erase 0x0 0x80000
// Write uBoot from RAM to NAND
nand write.e 0x800000 0x0 0x80000')

3) When you're absolutely sure you got it right, reboot.

[dockstarfan]

My dockstar's uboot is still good but pogo linux does not work anymore. I have read "Restoring factory Dockstar/Pogoplug image with a serial cable" and try to restore it. My question is it suggest to use the ramdisk .gz file directly, not the .img file. Does this make sense? Hope somebody did this before can let me know. Thanks.

[dockstarfan]

I used the method described in "Restoring factory Dockstar/Pogoplug image with a serial cable" but got the same "Attempt to write non page aligned data" error as twave. Is this because I am also using Jeff's uboot? I would like to know if anyone has been successful to restore Dockstar's firmware with Jeff's uboot. If there is a success story, please let me know the procedure you were using.
I can install openwrt with no problem, though.

[joeblow]

Hi,

both the links in your sig

http://Arch Linux ARM.com/index.php5?title=Ha ... Reflashing
and
http://Arch Linux ARM.com/index.php5?title=Ha ... n_via_JTAG

end up at the http://www.archlinuxarm.org homepage, even though the "title" is still the same:

http://archlinuxarm.org/?title=Hardware ... Reflashing
and
http://archlinuxarm.org/?title=Hardware ... n_via_JTAG

Is this information no longer valid or available?

thx

[bzboi]

@joeblow, about a year too late:P It's been almost 2 years since I last logged in, and I'm trying to find the Wiki myself to restore a GoFlex Net. I think the links were lost when the forums changed over when the original p l u g b o x linux site changed over to ALARM. I'll try and figure out what the new links are and update my sig if I do figure it out... Cheers.