So you use a wired connection, for your pc do not use 192.168.1.251 as IP because it is also used by the standalone kernel running on your nas.
Use for instance 192.168.1.200
- Not sure I got the right firmware file because the file I got once expanded is named : "xfvdw-sl-16-1-xbig2-3oct2015.bin"
Is this OK ?
No this is not correct don't slect a firmware file, you must first upload the standalone kernel, did you read the instructions in the help file :tapfoot
Be sure that you select as kernel the one with kirwood and standalone in its name (UIMAGE-3142-KIRKWOOD-150-standalone)
After uploading and starting te kernel and connecting with telnet you can proceed with installing the firmware by following the instructions
Some remarks
Before the u-boot window close can you see in the window that the kernel is uploaded ?
The u-boot should change when the console interrupts boot process of your nas and some message should be visible in u-boot window. and finally several xxxxx to show upload progress of the kernel.
You should see something like this
- Code: Select all
Marvell>> tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##########################
done
Bytes transferred = 3123520 (2fa940 hex)
Please note that kernel name and ip's are examples, your kernel name and ip's will be different
If that not happens then the kernel is not uploaded and of course telnet can not connect.
Besides using a wored connection between pc and router you should disable all other network interfaces in your pc except the one used for wired connection to your lan. If there are more than 1 NC active the console will not work properly