NSA 325 Bricked

I think I did it. My NSA 325 is bricked.

I followed these instructions, where I did the MTD0 flash using the stock NSA 325 firmware, and I also did rewrite the environment to 0xc0000.

http://forum.doozan.com/read.php?3,12381,17420#msg-17420

If I now boot I get no output on the UART console.

Somehow, at some point I got the UART upload working, but now the UART upload stops at 65% and then the NSA325 reboots. I think that the watchdog kicks in at 65%.

Are there any options left for me to do (besides buying a new NAS?).

/Marc

dirixmjm Wrote:
-------------------------------------------------------
> I think I did it. My NSA 325 is bricked.
>
> I followed these instructions, where I did the
> MTD0 flash using the stock NSA 325 firmware, and I
> also did rewrite the environment to 0xc0000.
>
> http://forum.doozan.com/read.php?3,12381,17420#msg
> -17420
>
> If I now boot I get no output on the UART
> console.
>
> Somehow, at some point I got the UART upload
> working, but now the UART upload stops at 65% and
> then the NSA325 reboots. I think that the watchdog
> kicks in at 65%.
>
> Are there any options left for me to do (besides
> buying a new NAS?).
>
> /Marc

Uart booting should work using the small NSA325 u-boot. Look at my post again where should get the small binary.
http://forum.doozan.com/read.php?3,12381,20220#msg-20220

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/15/2015 04:00PM by bodhi.

bodhi Wrote:
-------------------------------------------------------

>
> Uart booting should work using the small NSA325
> u-boot. Look at my post again where should get the
> small binary.
> http://forum.doozan.com/read.php?3,12381,20220#msg
> -20220

Am I trying / using the correct ones?

-rw-r--r-- 1 root root 296K Aug 15 2014 uboot.2013.10-tld-1.nsa325.small_uart.kwb
-rw-r--r-- 1 root root 306K Aug 30 2014 uboot.2013.10-tld-1.nsa325.uart.kwb

The small binary, which is 295K stops at 65% (the original which is 306K at 63%).

Do you think the upload speed depends highly on the host system? I currently use a somewhat busy router.

dirixmjm,

The smallest one is attached in this post:
http://forum.doozan.com/read.php?2,14351,17193#msg-17193

It does not depend on any host speed, since you are connecting with serial console to boot UART.

Quote

UPDATE: My thought was incorrect. The loading is affected by the how noisy the network environment is. See post below this for how dirixmjm solved it.

If it does not load completely, then check your serial console connection.

PS.

There are cases when the serial module converter has problem. Some of us had difficult time connecting with the effective baud rate and it turned out to be with the serial console hardware.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 5 time(s). Last edit at 03/17/2015 05:53PM by bodhi.

I've moved the UART connection to a different host (normal desktop instead of the router) and now the upload works.
Uploading of the new uboot (through tftboot) also worked.

tftpboot also showed me the (possible) problem with the instructions in the link below.
http://forum.doozan.com/read.php?3,12381,17420#msg-17420

The uboot 2013 is has size 6000 and the uboot 2014 even has size 8000, the uboot commands that did work are:
#load uboot using tftp, tftp responds with file size (6000 or 8000)
tftpboot 0x2000 uboot.kwb
#erase nand
nand erase 0 8000
#write nand
nand write 0x2000 0 8000

The 8000 is crucial instead of the 4(0000)

Thank you for your support.

dirixmjm,

> I've moved the UART connection to a different host
> (normal desktop instead of the router) and now the
> upload works.
> Uploading of the new uboot (through tftboot) also
> worked.

Cool, good job figuring it out! I understood your previous problem now. It is very subtle, it explained a lot of cases where others failed to UART boot the box.

> tftpboot also showed me the (possible) problem
> with the instructions in the link below.
> http://forum.doozan.com/read.php?3,12381,17420#msg
> -17420

The flashing instruction is for executing in Linux shell. So it is slighly different than one at u-boot console. When flashing at Linux prompt, as long as the u-boot image is <= 4 blocks (512k), it will work correctly.

The instruction works for previous 3-block u-boot, also for works for current 4-block u-boot, because how mtd0 was defined.

To generalize, if you know uboot.201x.xx-tld-x.nsa325.mtd0.kwb is 4 blocks or less:

flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot.201x.xx-tld-x.nsa325.mtd0.kwb

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/17/2015 11:38PM by bodhi.