pavva94 / snake-os

Automatically exported from code.google.com/p/snake-os
0 stars 1 forks source link

Bought nom-working NAS [No serial, ssh..] - Trying to reflash #287

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. I think that I bougth a dead NAS.
2.
3.

What is the expected output? What do you see instead?
Nothing happens. LED Link SYS, USB1 and USB2 half bright.

What version of the product are you using? On what operating system?
Since I bought on my NAS, it doesn't respond.

Please provide any additional information below.

http://club.dealextreme.com/forums/Forums.dx/threadid.794409

I've trying to fix it, bought new SPI flash to rewrite the flash and relocale. 
I tryed the RayeR's programmer (http://rayer.ic.cz/elektro/spipgm.htm) but 
doesnt work for me.
Now i'm trying reflash a new flash. But, how I do this?
Which files i need to write in flash using fw_def_mtd.zip ?

Looking on ebay, i found this: 
http://www.ebay.com/itm/W25X32-W25X32VSSIG-SOP-IC-NEW-/200697000083
and this: 
http://www.ebay.com/itm/1x-New-ST-M25P32-VMF6-M25P32V6P-M25P32V6G-SOP16-IC-Chip-
/190602409977 .

What of these will work fine to replace the original EN25P32 ?

thanks.

Original issue reported on code.google.com by xpi...@gmail.com on 21 Mar 2012 at 12:43

GoogleCodeExporter commented 8 years ago
What issues do you have with the rayer programmer? It works for me.

That def_fw_mtd package doesn't run proberly here. Probably because it's not 
meant for my box. You should be able to just cat everything together and write 
it to the flash.

cat fw_def_mtd0_bootloader.bin fw_def_mtd1_config.bin fw_def_mtd2_kernel.bin 
fw_def_mtd3_initrd-and-web.bin > fw_def_complete.bin

How to do the flashing depends on the programmer. I use flashrom with the rayer.

You can also just flash fw_def_mtd0_bootloader.bin. With that you should be 
able to get to the bootloader prompt via serial console. From there you can 
load the the snake recovery image or write other images to the flash.

I'd go with the M25P32. I'm not sure if the default firmware supports it though 
(that could explain why it doesn't run on mine). There are also some M25P64's 
on ebay. They are slightly cheaper and should be supported (at least with 
snake).

Original comment by stefansc...@googlemail.com on 24 Mar 2012 at 12:49

GoogleCodeExporter commented 8 years ago
Thanks for your answer. I think will be very usefull.

Last year, I bought 2x of MX25L6405 to try recovery my NAS.
I dont know why, but i has tryed few times read and identify the 
MX25L6405(suported in rayer readme) with his programer and nothing.
Last month, i decided try reprogram again with no sucess.
The rayers programer don't recognize the memory, with or without the LPT cable 
connected, nothing changes.
I saw that version 2.0a was released, so, more test will come.

Last week, I bought 2x of W25x32, and, luckly, i found another programer in my 
work that will help me to program these chip(manual says support the W25x32), 
if i haven't sucess with rayers programer, I'll try this programer (model 
MPT-1020).

I have other NS-K330 working fine, but i don't want open and test his memory 
with the NS-K330 bad.

I'll use the good NS-K330 to use this BusyBox command "cat" to merge these 
files into one file as you said. If fail to program this single file, but 
succeed to program the bootloader, excellent!. I did some progress up to here. 
:)

Sorry for my bad english, i try say all that i want, but sometimes dont know 
how.
And, again, thank you for your help. ;]

Original comment by xpi...@gmail.com on 14 Apr 2012 at 8:18

GoogleCodeExporter commented 8 years ago
[QUOTE]
"You can also just flash fw_def_mtd0_bootloader.bin. With that you should be 
able to get to the bootloader prompt via serial console."
[/QUOTE]

Finally, the Rayer's SPI Programmer works!  They identify the memory... And 
now, how i do to program the memory?

C:\SPIPGM>spipgmw.exe /p fw_def_mtd0_bootloader.bin

SPI FlashROM Programmer 1.9c (C) 2008-2011 by Martin Rehak; rayer@seznam.cz
Compiled by GCC 4.4.0 at 23:20:41, Mar 22 2011
(Win9x/NT/2K/XP compatability)

SPI connected to LPT port at I/O base address: 378h, SCK pulse width: t+0us
FlashROM JEDEC ID, type: EF3016h
Winbond W25X32 (4MB)
ERROR: cannot read page 1024 from file

C:\
Tryed just program the bootloader to finish the job via serial, but failed.
What i need to do now?
I've tryed "cat" these files, but didnt do that with my good NS-K330, can you 
explain ?

Thank you.

Original comment by xpi...@gmail.com on 26 Apr 2012 at 11:31

GoogleCodeExporter commented 8 years ago
I merged with dos command:

copy /b fw_def_bootloader.bin+fw...+fw_def_mtd3_initrd-and-web.bin 
fw_def_complete.bin

Tryed:
C:\SPIPGM>spipgmw.exe /p fw_def_complete.bin

SPI FlashROM Programmer 1.9c (C) 2008-2011 by Martin Rehak; rayer@seznam.cz
Compiled by GCC 4.4.0 at 23:20:41, Mar 22 2011
(Win9x/NT/2K/XP compatability)

SPI connected to LPT port at I/O base address: 378h, SCK pulse width: t+0us
FlashROM JEDEC ID, type: EF3016h
Winbond W25X32 (4MB)
ERROR: cannot read page 16128 from file

C:\SPIPGM>

I dont know how, but i think i need fill with blank code until the 
fw_def_complete.bin becomes 4096KB (now, my folder says that file has 4032KB).

Can someone help me with this?

Regards.

Original comment by xpi...@gmail.com on 27 Apr 2012 at 12:12

GoogleCodeExporter commented 8 years ago
Douglas Gazineu helped me with this.

I used on prompt DOS:
•fsutil file createnew C:\empty.bin 65536

then concatened with:
•copy /b 
fw_def_mtd0_bootloader.bin+fw_def_mtd1_config.bin+fw_def_mtd2_kernel.bin+fw_def_
mtd3_initrd-and-web.bin+empty.bin fw_def_complete_4096.bin

and, programed:
•spipgmw.exe /p fw_def_complete_4096.bin

Resoldered the IC, and, to my surprise, nothing happens...
Nothing on serial, nothing on network...
Yeah... now i dont know what i do... =(

Thank you to Douglas and Stefan for the help.

Original comment by xpi...@gmail.com on 27 Apr 2012 at 5:57

GoogleCodeExporter commented 8 years ago
Try reading the contents of the flash and compare it to the image file. Maybe 
the programming went wrong. That's the only thing I can think of.

Original comment by stefansc...@googlemail.com on 1 May 2012 at 12:12