cant load login into Uboot

[HanzPöta]

Hello

I found out about plugout yesterday. After I found my old NSv2 in the basement and wanted to play around with it a litte.
My NSv2 was just the housing, the HD had been removed by me for quite some time now, because I used it somewhere else. So I pluged in a new 500G HDD with was laying around, which is not formated properly at all, so far.

I read through alle the posts and howto's how to install the modified system and forund out about the fvdw-sl-console you are offering. After switching from Linux to Windows and downloading all the stuff I thought I start with upgrading the u-boot env.

I started the console, started uboot upgrade chose the delivered u-boot-nwsp2-classic-gpt-usbboot-80b.img to install, entered "no" and the protection off to continue and flashed the uboot. It exceuted everything and was done straight without any problems. Then I restarted ("restart") and the NS started up, the HDD was spinning up und running and I thougth everythin was fine.

Then I wanted to continue with installing the firmware but I can't get into u-boot any more.

SO my question is, did I brick it? Everything went smoth, wenn I put the power up the front LED ist constant blue, after doing a long press on the powerbutton it reboots, and the LED is blinking red/blue or blinking blue. Because I have no working System on the HDD i can't check so far if it is still booting and if I just locked out of u-boot.

To get access to the uboot so far i have tried:
direct connection laptop to NSv2 over Ethernet from Win and Debian with fvdw-sl-console, clunc and the lacie-uboot pyhton script (https://github.com/maximeh/lacie-uboot)
and connection over a linksys router, with dhcp on and no other device connected. In the Router Interface the MAC of the NSv2 is not even listed (and I have not tested it on any other router)

Now I was thinking that I still could install the system dircetly on the HD from Linux Console as it was once necessary, to cheq if it at least works.
But I hope that someone could help me that I may get into the u-boot env and install everything from Windows. Because it seemed the easyer way, and if isomething goes wrong with installing the system manually and the Box would not start up because of this, there was no way of knowing, at least for me.

thanks in advance H.P.

[fvdw]

are you sure you have a nwsp2 CLASSIC and not a lite !

If you have a lite, then it is pity but you then uploaded a u-boot version not suitable for that device and then you are in trouble

[HanzPöta]

oh dear,

argh,... i do have (had ? ^^ ) a lite. I found the old Harddrive and it still had the GPT Tabe on it with all the original Partitions, so it seems like it is a lite. I didn't even consider it,

[Jocko]

Hi HanzPöta,

To valid what NWSP2 version you have, see the topic http://www.plugout.net/viewtopic.php?f=11&t=213

[HanzPöta]

Hello Joko,
it is a slim.

so are there any ideas to recover the old uboot or getting it some way to work again properly?

[Jocko]

I didn't understand well if you still get or no longer an u-boot console.

If yes, you should be able to restore the uboot if you have a backup and in the other case I think that the only way is to use a serial access (http://lacie.nas-central.org/wiki/Serial_port_%28Network_space_2%29)

As I don't have a nwsp2 lite, I can not send you the uboot for this nas type

[fvdw]

@Jocko nope that won't work anymore.

Pretty sure that it was liet because he mentioned that the original disk had a GPT partition table. That was not used on the classic.

the problem is that there is now a u-boot version for a nwsp2 classic in the flash memory. The bootloader will try to load it but it will not run because u-boot is setup for a different main board. The nwsp2 and classic and lite are very different.
Because u-boot doesn't start the clunc interface will not run as it is part of u-boot so the fvdw-sl console is useless in this case.
The only way to bring it back to live is to reflash the nwsp2 lite with a compatible u-boot image.
I have a u-boot image for the lite but the problem will be to get it on the flash. For this you will need JTAG connection and appropriate software.
Recently I bricked my spd8020 because I corrupted the flash but I was able to restore because bootstrap was running on it. Bootstrap is a basic binary that can load u-boot in ram by using hyper terminal. If that works on the nwsp2 lite then the u-boot version in ram can be used to burn a new version to flash memory. To see if bootstrap is running you should use a serial connection connected the the serial interface. If you power up the nwsp2 lite the bootstrap should become visible if it is also used on the nwsp2 lite to load u-boot.

The ram version for u-boot will be a special one that one unfortunate I don't have. So I am afraid this one is lost. You can do some reading on the internet to see if the JTAG way is a real possibility

[HanzPöta]

Thank you guys,

Now I know where I (probably) stand.
I'll try my luck.

Well than I'll have to get the Serial up and running and have to see what I can do.