Welcome! Log In Create A New Profile

Advanced

NSA-325 Bricked HDD2 LED constantly active

Posted by gazsiazasz 
NSA-325 Bricked HDD2 LED constantly active
June 05, 2016 05:43PM
I have a bricked NSA-325. I tried to uartboot it with kwboot without success:

ubuntu@ubuntu:~/Desktop/kwboot-tool$ sudo ./kwboot -b uboot.2015.10-tld-1.nsa325.mtd0.kwb -t -B 115200 /dev/ttyUSB0 -p
Sending boot message. Please reboot the target...|
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
  5 % [......................................................................]
  6 % [......................................................................]
  8 % [......................................................................]
 10 % [......................................................................]
 11 % [......................................................................]
 13 % [......................................................................]
 15 % [......................................................................]
 17 % [......................................................................]
 18 % [......................................................................]
 20 % [......................................................................]
 22 % [......................................................................]
 23 % [......................................................................]
 25 % [......................................................................]
 27 % [......................................................................]
 29 % [......................................................................]
 30 % [......................................................................]
 32 % [......................................................................]
 34 % [......................................................................]
 35 % [......................................................................]
 37 % [......................................................................]
 39 % [......................................................................]
 41 % [......................................................................]
 42 % [......................................................................]
 44 % [......................................................................]
 46 % [......................................................................]
 47 % [......................................................................]
 49 % [......................................................................]
 51 % [......................................................................]
 53 % [......................................................................]
 54 % [......................................................................]
 56 % [......................................................................]
 58 % [......................................................................]
 59 % [......................................................................]
 61 % [......................................................................]
 63 % [......................................................................]
 64 % [......................................................................]
 66 % [......................................................................]
 68 % [......................................................................]
 70 % [......................................................................]
 71 % [......................................................................]
 73 % [......................................................................]
 75 % [......................................................................]
 76 % [......................................................................]
 78 % [......................................................................]
 80 % [......................................................................]
 82 % [......................................................................]
 83 % [......................................................................]
 85 % [......................................................................]
 87 % [......................................................................]
 88 % [......................................................................]
 90 % [......................................................................]
 92 % [......................................................................]
 94 % [......................................................................]
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]


The device was in use but suddenly stopped working and seems like it is not booting via UART. Is is also not booting anything from NAND neither outputs anything on UART.


Is there anything else I could try?
Re: NSA-325 Bricked HDD2 LED constantly active
June 05, 2016 06:13PM
gazsiazasz,

>
> The device was in use but suddenly stopped working
> and seems like it is not booting via UART. Is is
> also not booting anything from NAND neither
> outputs anything on UART.
>

This is a tough one. The fact that you can run kwboot, and has loaded a complete u-boot image, indicates that your bootROM works, and your serial port also works. At this point, did it just hang there or was the box reset after 30 seconds?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked HDD2 LED constantly active
June 05, 2016 06:43PM
If I don't load the u-boot, then the NAS is constantly rebooting about every minute. The fan is running slow.
If I am uploading the u-boot the fan speed is changing but at the end it is just hanging here. There is also garbage character at the end of the last line (can't see here) but nothing happens after that.

I have noticed that the power LED and the HDD2 LED are always on (The power LED blinks once right after plugging in the power).
The power button is not working, the only way to power off the NAS is to unplug the power cord.
Re: NSA-325 Bricked HDD2 LED constantly active
June 05, 2016 07:28PM
> If I don't load the u-boot, then the NAS is
> constantly rebooting about every minute. The fan
> is running slow.

1. This is the HW watchdog in action when you run u-boot from NAND. Is it 2014 version or 2015.10?

I've encoded a command to kill the watchdog in the new u-boot 2015.10. So that's why it did not restart the box , as oppose to running normally with u-boot in NAND.


> There is also garbage character at the end of the
> last line (can't see here) but nothing happens
> after that.

2. This is quite interesting.

Possibilities:

A. The bootROM does not know what to do next. ie. bug.

B. The bootROM did try to load and execute uboot image, but perhaps encountered a bad RAM area thus it has crashed but could not output the error intelligently (see number 2 above).

...Let me think a bit. If there is no way to see the problem now, I think you'll need JTAG to unbrick this box.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked HDD2 LED constantly active
July 04, 2016 03:34PM
I tried with both. With the 2015.10 version it wasn't rebooting if I remember right.


I get an ST-Link-V2-1 and compiled the latest OpenOCD.
Do you have an OpenOCD config file for NSA-325?
(I still have to buy some header pins for the JTAG interface to solder in)

I also noticed in some forum threads on the internet the same symptoms with this NAS, maybe it is a design defect(?)
Re: NSA-325 Bricked HDD2 LED constantly active
July 04, 2016 10:55PM
gazsiazasz,

> I also noticed in some forum threads on the
> internet the same symptoms with this NAS, maybe it
> is a design defect(?)

I do believe so. It is a good possibility now that's a defect, it's very rare, but we can get stuck at this point. I came across a few users reported similar problem.

I don't have OpenOCD config file for NSA325 yet. I was going to work on this, but sidetracked by other things. See these posts for other Kirkwood OpenOCD configs:

Pogo E02:
http://forum.doozan.com/read.php?3,21789

Dockstar:
http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirate

Iomega iConnect:
https://wiki.openwrt.org/toh/iomega/iconnect#installation_of_openwrt_from_trunk

NOTE: the NSA325 has DDR3 RAM.

This is from my u-boot GitHub
https://github.com/mibodhi/u-boot-kirkwood/blob/2016.05-kirkwood-tld-2/board/zyxel/nsa325/kwbimage.cfg

# Boot Media configurations
#BOOT_FROM	uart
BOOT_FROM       nand
NAND_ECC_MODE   default
NAND_PAGE_SIZE  0x0800

# SOC registers configuration using bootrom header extension
# Maximum KWBIMAGE_MAX_CONFIG configurations allowed

# Configure RGMII-0 interface pad voltage to 1.8V
DATA 0xFFD100e0 0x1b1b1b9b

#Dram initalization
DATA 0xFFD01400 0x4301503E      # DDR Configuration register
DATA 0xFFD01404 0xB9843000      # DDR Controller Control Low
DATA 0xFFD01408 0x33137777      # DDR Timing (Low)
DATA 0xFFD0140C 0x16000C55      # DDR Timing (High)
DATA 0xFFD01410 0x04000000      # DDR Address Control
DATA 0xFFD01414 0x00000000	#  DDR Open Pages Control
DATA 0xFFD01418 0x00000000	#  DDR Operation
DATA 0xFFD0141C 0x00000672	#  DDR Mode
DATA 0xFFD01420 0x00000004	#  DDR Extended Mode
DATA 0xFFD01424 0x0000F14F	#  DDR Controller Control High
DATA 0xFFD01428 0x000D6720	# DDR3 ODT Read Timing
DATA 0xFFD0147C 0x0000B571	# DDR2 ODT Write Timing
DATA 0xFFD01504 0x1FFFFFF1      # CS[0]n Size
DATA 0xFFD01508 0x20000000      # CS[1]n Base address to 512Mb
DATA 0xFFD0150C 0x1FFFFFF4      # CS[1]n Size 512Mb Window enabled for CS1
DATA 0xFFD01514 0x00000000      # CS[2]n Size, window disabled
DATA 0xFFD0151C 0x00000000      # CS[3]n Size, window disabled
DATA 0xFFD01494 0x00120000      #  DDR ODT Control (Low)
DATA 0xFFD01498 0x00000000      #  DDR ODT Control (High)
DATA 0xFFD0149C 0x0000E803      # CPU ODT Control

DATA 0xFFD015D0 0x00000630
DATA 0xFFD015D4 0x00000046
DATA 0xFFD015D8 0x00000008
DATA 0xFFD015DC 0x00000000
DATA 0xFFD015E0 0x00000023
DATA 0xFFD015E4 0x00203C18
DATA 0xFFD01620 0x00384800
DATA 0xFFD01480 0x00000001
DATA 0xFFD20134 0x66666666
DATA 0xFFD20138 0x00066666

DATA 0xFFD10100 0x00004000
DATA 0xFFD10104 0xFFFFBFFF

# End of Header extension
DATA 0x0 0x0

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 07/04/2016 11:10PM by bodhi.
NAZIM
Re: NSA-325 Bricked HDD2 LED constantly active
January 30, 2017 01:00PM
Hello,
i have same problem. i tried update my nsa325v2 and failed. HDD2 led constantly active.

i tried to send data over uart, but nothing happend:

1 i have connected nsa325v2 to computer over uart.
2 run kwboot command.
3 "Please reboot the target" message shown and an indicator spinning.
4 Rebooted nsa325v2.
5 indicator stops in seconds and nothing happend..

have you find any solution about this?

bodhi Wrote:
-------------------------------------------------------
> > If I don't load the u-boot, then the NAS is
> > constantly rebooting about every minute. The fan
> > is running slow.
>
> 1. This is the HW watchdog in action when you run
> u-boot from NAND. Is it 2014 version or 2015.10?
>
> I've encoded a command to kill the watchdog in the
> new u-boot 2015.10. So that's why it did not resta
> rt the box , as oppose to running normally with u-
> boot in NAND.
>
>
> > There is also garbage character at the end of th
> e
> > last line (can't see here) but nothing happens
> > after that.
>
> 2. This is quite interesting.
>
> Possibilities:
>
> A. The bootROM does not know what to do next. ie.
> bug.
>
> B. The bootROM did try to load and execute uboot i
> mage, but perhaps encountered a bad RAM area thus
> it has crashed but could not output the error inte
> lligently (see number 2 above).
>
> ...Let me think a bit. If there is no way to see
> the problem now, I think you'll need JTAG to unbri
> ck this box.
Re: NSA-325 Bricked HDD2 LED constantly active
January 30, 2017 01:11PM
NAZIM,

> Hello,
> i have same problem. i tried update my nsa325v2 an
> d failed. HDD2 led constantly active.
>
> i tried to send data over uart, but nothing happen
> d:
>
> 1 i have connected nsa325v2 to computer over uart.
> 2 run kwboot command.
> 3 "Please reboot the target" message shown and an
> indicator spinning.
> 4 Rebooted nsa325v2.
> 5 indicator stops in seconds and nothing happend..
>
> have you find any solution about this?
>

No, not yet. I have forgot about this, being busy with other topics here. Thanks for reporting this. If I have some time in the next few days I'll revisit it.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked HDD2 LED constantly active
February 04, 2017 02:46PM
@NAZIM,

Let me restate this problem, see if I describe it correctly.


> i have same problem. i tried update my nsa325v2 an
> d failed. HDD2 led constantly active.

You let it boot normally (without kwboot), the NSA325 seems to be stuck at boot. Nothing happens, and the HDD2 LED is solid green. Did the box reset at every 30 seconds and back to the same behavior again?

Have you try to unplug the serial console and power up, let it boot to see the same behavior occurs?

>
> i tried to send data over uart, but nothing happen
> d:
>
> 1 i have connected nsa325v2 to computer over uart.
> 2 run kwboot command.
> 3 "Please reboot the target" message shown and an
> indicator spinning.
> 4 Rebooted nsa325v2.
> 5 indicator stops in seconds and nothing happend..
>

When you ran kwboot and power up, the kwboot indicator was spinning for a while and then stopped. Nothing happened after that and the box did not reset?

-bodhi
===========================
Forum Wiki
bodhi's corner
NAZIM
Re: NSA-325 Bricked HDD2 LED constantly active
February 12, 2017 03:08PM
Sorry for late response @Bodhi,

And you are right. You completely defined my problem.
Re: NSA-325 Bricked HDD2 LED constantly active
February 12, 2017 03:38PM
NAZIM,

Quote

When you ran kwboot and power up, the kwboot indicator was spinning for a while and then stopped. Nothing happened after that and the box did not reset?

If the above is true, then it meant the NAS325-v2 has received the kwboot message (the fact that the watchdog did not run every 30 seconds). But it stuck waiting, it probably meant that the RX pin was OK when kwboot started, but TX it was not so it never responded to kwboot.

BTW, the fact that u-boot in NAND did not start, indicated that the a NAND sector within the first 512K was marked as bad (possibly the 1st sector).

I'll think of some workaround in kwboot.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: