Can't find nwsp2 on lan

[netokarys]

Hi,

i try to reflash u-boot from site (ftp://lacie-nas.org/u-boot/u-boot-netsp ... 24d58e.kwb) with tool "kwboot" and geting error message:
"0 % [+++++++++++++++++xmodem: Bad message".
Kwboot command is :
"/home/ubuntu/Desktop/kwboot-tool/./kwboot' -t -B 1152000 /dev/ttyUSB0 -b '/home/ubuntu/Desktop/kwboot-tool/u-boot.kwb' -p".
Without -p error is the same.
Another method load from USB:
"fatload usb 0:1 0x2000000 uImage" on command "bootm 0x2000000" i geting error "Bad magic number".
If i write command "go 0x2000000" (in place of command "bootm 0x2000000") my device restarts, with command "md.b 0x600000 0x100" i see that this is not my u-boot code that i flashed from 0x2000000 address.

[netokarys]

Network card on nwsp2 blinking (green and orange) as normal working network card.
I also checked cpu info and got this:

~ # cat /proc/cpuinfo
processor : 0
model name : Feroceon 88FR131 rev 1 (v5l)
Features : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part : 0x131
CPU revision : 1

Hardware : LaCie Network Space v2
Revision : 0000
Serial : 0000000000000000

memory info:

~ # cat /proc/meminfo
MemTotal: 250404 kB
MemFree: 196492 kB
MemAvailable: 232808 kB
Buffers: 8140 kB
Cached: 32412 kB
SwapCached: 0 kB
Active: 23016 kB
Inactive: 22220 kB
Active(anon): 4732 kB
Inactive(anon): 172 kB
Active(file): 18284 kB
Inactive(file): 22048 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 514076 kB
SwapFree: 514076 kB
Dirty: 4 kB
Writeback: 0 kB
AnonPages: 4700 kB
Mapped: 5476 kB
Shmem: 220 kB
Slab: 4460 kB
SReclaimable: 1968 kB
SUnreclaim: 2492 kB
KernelStack: 632 kB
PageTables: 364 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 639276 kB
Committed_AS: 19892 kB
VmallocTotal: 761856 kB
VmallocUsed: 6564 kB
VmallocChunk: 754724 kB

[netokarys]

Can you please send instruction how to flash uboot over ttl or usb port, and the good uboot image for this device (lite)

[fvdw]

Lets get some things clarified here. The picture of the PCB you posted is a lite, but all outputs you posted say that it is classic. There is no way that a lite can produce that output. Also the u-boot version that it runs will only run on a classic and cannot run on a lite. The cpu of the lite and memory deviates from the classic and need a different setup. At least I never tried it.
The lite has only 128 MB memory, the classic 256 MB.
I am prepared to help you but I would appreciate if you could clarify and tell what you are really doing or have been doing

Did you put the u-boot for the classic on a nwsp2 lite ?

If it is a classic and you put a u-boot version for nwsp2 lite on this device you will brick it.
Why do you want to flash it at all? The fvdw vs80 has all options you need (for a classic)

Ps fatload doesn't write an image to flash.
Ps2 flashing lights on a ethernet card doesn't mean that the interface is not broken.

[fvdw]

Did you put the u-boot for the classic on a nwsp2 lite ? :scratch

Although I would be very surprised that it still runs the problem you have with the ethernet card may point in this direction

I see this in your serial output

Code: Select all

[ 16.954342] libphy: orion_mdio_bus: probed
[ 16.958661] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 16.965849] libphy: PHY orion-mdio-mii:08 not found
[ 16.970739] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral


The classic uses phy address 8 while the lite uses 0

also these two lines should be in the dmesg output

Code: Select all

[ 15.190237] orion_mpp_conf: requested MPP12 config unavailable on this hardware


[ 17.237249] leds-gpio: probe of leds-gpio failed with error -22

the setup of gpio for pin12 is different for lite and classic

[netokarys]

Thanks for replay ;) as i posted before the image of my pcb looks like lite. From classic photo that is in this forum i see that there is 2 chips of ram and mine has only 1 so it must be lite version. Is there any chance that somehow wrong u-boot or something else can change pcu info? I was installed fvdw firmware to this same nas and there was no problem until my hdd broke. I put lite u-boot version with no luck, then i tried classic version too but result was the same... Thats why i want to flash it because thats my last hope...

[netokarys]

Can you tell me please what to do step by step? What would you do? Maybe i missed something... Did all by instructions for first time install...

[fvdw]

If you really did put the wrong u-boot in flash and if this "wrong" u-boot seems to run ok for the majority you could use the u-boot command to write a new u-boot version to flash. You will need a tftp server providing the right u-boot image.
You can enter u-boot command prompt by hitting the "enter" key at early loading stage of u-boot. You will then get a marvell>> prompt
The command to write an u-boot image (in u-boot) to flash is:

Code: Select all

bubt name-of-u-boot-image

for the aatched file it would be

Code: Select all

bubt u-boot-nwsp2-lite.bin

You must have a tftp server running in your lan that will respond to u-boot to upload the u-boot image.
(If you have a pc running windows you could use the fvdw-sl console for it (see download section of this forum)
After writing u-boot to flash it will ask you also if you want to overwrite environment, answer "n" (no)

Be 100% sure that you provide a working u-boot image for flash (and not an image with uart header).
attached a version I retrieved from a nwsp2 lite (unzip de archive to get the image .bin file)
ps I do not give any guarantee that this will work, performing the flashing is at your own risk

[fvdw]

after writing to flash reboot the nas by giving in u-boot the command "reset" and keep your fingers crossed if it comes back to live

[netokarys]

Thank you very much ;) i'll try this tomorrow and will post you how it goes. I know a risk but i have no other ideas :)