Hi I broke my DockStar buy a DockStar?

Hi I broke my DockStar with the following command
# Restore original uBoot
wget http://jeff.doozan.com/debian/uboot/files/uboot/uboot.mtd0.dockstar.original.kwb
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot.mtd0.dockstar.original.kwb
Hi I broke my DockStar with the following command
since they connect more
t there a solution?
or I can buy a DockStar?
or maybe another that DockStar?
thank you

thank you



Edited 1 time(s). Last edit at 02/07/2012 01:47PM by DJDavid.

If your Dockstar is truly "broken" - no serial output and an inactive led - then you will need to JTAG it. I followed the relevant parts of this tutorial and was able to restore uboot.mtd0.dockstar.original.kwb and then the original Dockstar firmware; after that I installed Jeff's u-boot, which has the advantage of setting up the environment variables.

After restoring the original u-boot the original environment was restored by (at the ce> prompt):


--------------------------------------

resetenv

setenv ipaddr 192.168.0.68

setenv serverip 192.168.0.120

setenv ethaddr 00:10:75:XX:XX:XX


setenv console 'console=ttyS0,115200'
setenv bootargs_root 'root=/dev/mtdblock2 ro'
setenv bootcmd 'nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000'





saveenv

nand erase 0x100000 0x400000


tftp 0x800000 ce_kernel_redstone_v63.img
nand write.e 0x800000 0x100000 0x1e30f0


tftp 0x1000000 ce_ramdisk_v2.0b.img.gz



setenv bootargs $(console) root=/dev/mtdblock2 initrd=0x1000000,0xb39a59


bootm 0x800000

After doing that, Jeff's u-boot can be installed via the normal method. Original Dockstar compatible files can be obtaIned from HERE and then using tftp transferred to the Dockstar. The procedure is well documented: just read and be sure!

I used a laptop to desktop IDE convertor as the JTAG/serial header. Also an XBox 360 DVD-Rom drive power cable is compatible (2mm pitch).

------

His Excellency, President for Life, Field Marshal Al Hadji Doctor Idi Amin Dada, VC, DSO, MC, Lord of All the Beasts of the Earth and Fishes of the Seas and Conqueror of the British Empire in Africa in General and Uganda in Particular

Thank you for your reply I vien to buy the Jtag the same link that I hope you ca go to repair my DockStar
by cons I am French so the tutorial is not too obvious even for me to understand with google translation
it is complicated to do with jtag?
DockStar my blinking orange so I is not if there is that the JTAG solution as
thank you again

http://cgi.ebay.fr/Universal-JTAG-Xilinx-Parallel-Cable-III-program-CPLD-e-g-XC2C64A-and-more--/220928927564?pt=BI_Electrical_Equipment_Tools&hash=item337063e74c



Edited 1 time(s). Last edit at 02/08/2012 05:59AM by DJDavid.

Most likely, you only need to get a serial link. It is much easier and cheaper (<5 USD) than J-TAG.

Thank you all

Hello
Now here is my problem do I start the TFTP
screen / dev/ttyUSB0 115200
do I start the DockStar and this is what I have:

U-Boot 2010.09 (Oct 23 2010 - 11:49:22)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x100000, size 0x300000
3145728 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>>

what to do ???
if I
screen /dev/ttyUSB0 115200
setenv ipaddr 192.168.1.25
setenv netmask 255.255.255.0
setenv serverip 192.168.1.4
saveenv

nand erase 0x100000 0x400000
tftp 0x800000 ce_kernel_redstone_v63.img

Marvell>> tftp 0x800000 ce_kernel_redstone_v63.img
Using egiga0 device
TFTP from server 192.168.1.4; our IP address is 192.168.1.25
Filename 'ce_kernel_redstone_v63.img'.
Load address: 0x800000
Loading: ####T #############################################################
####T #############################################################
#####
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>>
why?
any solution?
thank you



Edited 1 time(s). Last edit at 02/10/2012 05:40PM by DJDavid.

DJDavid Wrote:
-------------------------------------------------------
> Hello
> Now here is my problem do I start the TFTP
> ......
> 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>>
> why?
> any solution?
> thank you

I had seen the same thing before. It is because you are using Jeff's uboot. In order for this approach of restoring the origintal firmware to work, you need to use the original uboot. I don't know how to restore the original uboot though. I was able to do that because I can still boot into the USB drive running Debian. In that case, I think Jeff had given instructions how to restore the original uboot. I don't know how to reflash uboot from uboot, though.

OK
I found some command on this forum of jeff
TFTP 0 x 800000 uboot-original - mtd0 .kwb
GB 0 x 800200


run bootcmd_original


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


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


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


Streaming disabled
Write allocate disabled



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


NAND read: device 0 offset 0 x 100000, size 0 x 300000


Reading data from 0x3ff800--100% complete.
3145728 bytes read: OK
# Booting image at 00800000...
Bad Magic Number
This > > run bootcmd_original
# Error: "bootcmd_original" not defined
This > >

voila:
starting pid 285, tty'': '/ etc / init.d / rcS'
[8.800000] eth0: link down
[8.800000] eth0: started
udhcpc (v1.7.0) started
0x50 0x43 0x00 HWADDR 00 0x02 0x02
PIP0 2
PIP1 2
Sending discover ...
[10.450000] eth0: link up, full duplex, speed 100 Mbps
Sending discover ...
Sending select for 192.168.1.2 ...
Received DHCP NAK
0x50 0x43 0x00 HWADDR 00 0x02 0x02
PIP0 2
PIP1 2
Unexpected Argument: nak
siaddr = 192.168.1.254
interface = eth0
PATH = / sbin :/ usr / sbin :/ bin :/ usr / bin
PWD = /
SHLVL = 1
message = requested address is not available
HOME = /
dhcptype = 6
ip = 0.0.0.0
_ = / bin / printenv

Sending discover ...
Sending select for 192.168.1.2 ...
Received DHCP NAK
0x50 0x43 0x00 HWADDR 00 0x02 0x02
PIP0 2
PIP1 2
Unexpected Argument: nak
siaddr = 192.168.1.254
interface = eth0
PATH = / sbin :/ usr / sbin :/ bin :/ usr / bin
PWD = /
SHLVL = 1
message = requested address is not available
HOME = /
dhcptype = 6
ip = 0.0.0.0
_ = / bin / printenv

I type commands
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot.mtd0.kwb
and since it starts up and turns over
is there a way to recover the DockStar?
food works because the hard drive spins
thank you



Edited 2 time(s). Last edit at 02/11/2012 01:42PM by DJDavid.

DJDavid Wrote:
-------------------------------------------------------
> I type commands
> flash_erase /dev/mtd0 0 4
> nandwrite /dev/mtd0 uboot.mtd0.kwb
> and since it starts up and turns over
> is there a way to recover the DockStar?
> food works because the hard drive spins
> thank you

I am not sure I understand what you did.
Where did you typed "flash_erase /dev/mtd0 0 4" and "nandwrite /dev/mtd0 uboot.mtd0.kwb"? Did you have some sort of linux running?
If you restored original uboot, you should see the prompt from serial console becomes ce> instead of Marvell>, If it does, you can recover the original firmware as you did previously. BTW, what is "food works"?



Edited 1 time(s). Last edit at 02/11/2012 09:04PM by twinclouds.

twinclouds Wrote:
-------------------------------------------------------
> BTW, what is "food works"?

He's French and he uses Google translate. I guess the original part of the phrase was sth like "Bloc d'alimentation fonctionne, car .." which means
"The power supply is working, because ...". L'alimentation also means food in French so that Google translate apparently confused both meanings.

My problem is that I have nothing that appears in the window with my serial port
the DockStar is plugged because the HDD is running
but I do not have the LED lights at startup
So what to do?
with a JTAG?
thank you



Edited 1 time(s). Last edit at 02/13/2012 09:11AM by DJDavid.