fvdw-sl-console for ms windows install without removing HDD

[fvdw]

this what you should see in the command window when it transfers the kernel

gui2.JPG

[NasaMan]

Mhh very strange. I tried several times but everytime Tftpd32 window is empty. I made a reset of the Lacie drive. The stock firmware version is 1.0.2 and I am not able to choose an update.
What point in menu "Action" do I have to choose? I tried the first "Standalone kernel, load and start" and the last one "install fvdw-sl firmware"?
Another point is that the drive LED isn't flickering red after turning on the device. Yesterday it flickered red but after the reset it doesn't.:dontknow:
EDIT1: I tried my other PC and now the drive flickers red.)
EDIT2: I can`t ping the drive after starting and my router also has no device listed the Log_start.jpeg Screenshot shows the log window after starting the device (it appears afte "waiting for u-boot")

[fvdw]

Is your nwsp2 powered off when you start the console ?

Only start the nwsp2 fater the window appears that it is waiting for u-boot

If the Lacie web inetrafce is active it means it did not detect the uboot call
That is detected is vissible by to flashes of the red led then boot will halt and it will enter the u-boot console mode

If u-boot console works you can check by using the -boot console action
After the two flashes of the red ligt you can click on the command window and get the "Marvell>>"" prompt.

If that works we can enter the command manually to download a kernel from the tftp server
To leave the u-boot console you can type reset after the Marveel prompt then the nas will reboot

[NasaMan]

Yes the nwsp2 is powered off and I started only when waiting for u-boot appears

The web interface isn't active after boot. Sorry for this missunderstanding. I posted it to show the network settings and stock-fw settings.

I tried the u-boot console by clicking "Action --> U-boot console" then I got the Marvell prompt. It seems that it has contact to nwsp2. After typing reset the drive was off -no reboot. By the way the red flashes are more than 2. I would guess 5 or 6 EDIT 9 or 10.

[fvdw]

9 -10 flashes, odd did not see that before.
When you get the marvel prompt type "version" without the quotes
To try to laod a kernel type this

Code: Select all

echo setenv ipaddr ${ipaddr}
setenv serverip ${serverip}
tftpboot 0x800000 kernel-file-name-as-present in-tftp-folder
bootm 0x800000

[NasaMan]

Ok I tried. When I type in the first line with

Code: Select all

echo setenv ipaddr $192.168.0.252

I get

Code: Select all

unknow command 'echo'

. If I type it without echo it seems to work. After typing

Code: Select all

setenv serverip $192.168.0.103

I get a blinking cursor and nothing happens until I press Ctrl+C. The same when i type in

Code: Select all

tftpboot 0x800000 UIMAGE-26394-NWSP2CL-STANDALONE-88

:hammerhead

[fvdw]

mm you have the old bootloader without support for gpt partition table but that should matter

oops the echo should indeed not be there
you should exactly type these commands

Code: Select all

setenv ipaddr ${ipaddr}
setenv serverip ${serverip}
tftpboot 0x800000 kernel-file-name-as-present in-tftp-folder
bootm 0x800000

Do not replace ipaddr or serverip by actual ip address

[NasaMan]

Maybee it doesn't likes me?

[fvdw]

no it doesn't transfer the kernel, your windows PC blocks the download for whatever reason (probably firewall), the nas cannot contact the tftp server

[fvdw]

besides your windows pc it can also be the router blocking contact to the tftp server
If I remember well it must be able to contact UDP port 69