Can't connect to NAS after installing fvdw. No DHCP

[fvdw]

The console should write a file with name md5check.txt in its main directory (one folder above tftp, in that folder you will find executable filess like md5sum.exe, fvdw-sl-console.exe)
It will contain the output of a command that determines to md5 sum of the .bin file.
Then it will try to read to content of that file, that seems to fail in your case. Is this file present ?
After reading it, it will compare the content with that of the content in the md5 file, this to check that those are the same. This to be sure that the bin file is not corrupt

[Woodani]

Yes, the md5check.txt file is present. Do you want me to post the contents of that file?

[fvdw]

yes please

[Woodani]

Ok it says this:

Code: Select all

0661d93f555a49d636925e7dacce3d7d *u-boot-5big2-spi-3416-1517.bin

[fvdw]

thats the correct content. The console tries to read the first 33 characters from that file, which is the md5 sum. The value you posted matches with the content of the md5 file so the bin file is not corrupt.
The question is now why does the console fails to read the content of md5check.txt file :scratch

How did you set up the console? just extracted the zip file in a folder ?

[Woodani]

I made a folder on my desktop put the archive files in there extracted them to a subfolder and then there was the already created subfolder from the zip so the console files are a few folders deep from my desktop.

If that's an issue I can move the console folder to my desktop or wherever they'd work best. I'll put them on the root of my C:/ drive if you want me to.

[Woodani]

"C:\Users\woodani\Desktop\fvdw v3\fvdw-sl-console-6-18-1-v2-29jul2019-32bits.part1\fvdw-sl-console-6-18-1-v2-29jul2019-32bits" Is the exact file path to the console.exe

Note that the v3 in "fvdw v3" is to indicate to me that was my 3rd attempt at downloading the console programs when I was initially having issues.

[fvdw]

Thats fine. I do not know why reading the check file fails but because the content of the md5check file is oke, it contains the correct md5sum we can also proceed manually instead of using the auto flash feature

To do that you need to switch of 5big2,
start fvdw-sl-console,
chose as action start tftpd server (check that it is really started, tftpd window should pop up)
After thatn chose as action uboot console.
After that start the 5big2 and connect to uboot as you have done previously, you should get the marvell>> prompt.

Behind the marvel prompt type

Code: Select all

setenv ipaddr ${ipaddr};setenv serverip ${serverip}

after that start uploading the bin file and start flash

Code: Select all

bubt u-boot-5big2-spi-3416-1517.bin

this should result in an action that the file is uploaded via tftpd server to 5big2 ((459.732 bytes should be transferred) and flash starts
It will unprotect the flash monitor space and comes up with a warning and question to override env parameters
Answer no (n) to that question

Code: Select all

n

After that erase of flash memory will take place and it will copy the bin file content to flash and protect Flash monitor space again

Remove the protection to be able to modify later the content

Code: Select all

protect off all

If everything went well reboot the nas by command

Code: Select all

reset

In fact this is what the console will do after it has checked the md5 sum (see also the screenshot in help page for flashing uboot

If you have a flash failure or there are not 459.732 bytes uploaded by the bubt command do not perform the reset command !

[Woodani]

Ok, I'm going to attempt this. Wish me luck. I've got everything connected to a UPS so hopefully, a power failure won't be a possibility now.

[fvdw]

:thumbup I wish you luck but I am confident it will go oke