Welcome! Log In Create A New Profile

Advanced

NSA-325 Bricked ? HDD2 LED constantly active

Posted by Flecks 
Re: NSA-325 Bricked ? HDD2 LED constantly active
February 28, 2019 09:14PM
It is most likely, as I mentioned, the handshake that would enable the BootROM to start executing uboot did not occur after the image was loaded. If RAM was bad, very likeky that it would have not loaded uboot successfully.

Try the debug mode to see if any thing we can see out of the console:

./kwboot -B 115200 -t /dev/serial0 -d

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 01, 2019 08:40AM
bodhi Wrote:
-------------------------------------------------------
> Try the debug mode to see if any thing we can see
> out of the console:
>
> ./kwboot -B 115200 -t /dev/serial0 -d

root@raspberrypi:/home/pi# ./kwboot.20190228 -B 115200 -t /dev/serial0 -d
Sending debug message. Please reboot the target...|
[Type Ctrl-\ + c to quit]
>

I'm not sure what I can do at that prompt, but my keystrokes are echoed. About 30s later the watchdog timer reboots the NSA. I also tried pushing uboot with the debug flag and got this:

root@raspberrypi:/home/pi# ./kwboot.20190228 -B 115200 -t /dev/serial0 -d -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
Sending debug message. Please reboot the target...-
Sending boot image...
▒i,▒``
>@▒▒▒▒▒>PC▒▒0▒▒▒ww3
▒▒U
▒▒▒▒  0 % [+xmodem: Operation canceled

I also tried this from Ubuntu but the kwboot that you posted to a different thread didn't have the debug flag. Would it be worth trying there as well?
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 01, 2019 02:46PM
nunit,

> I'm not sure what I can do at that prompt, but my
> keystrokes are echoed. About 30s later the
> watchdog timer reboots the NSA.

This debug just to prove that your box is not bricked beyond repair. It did put the BootROM in debbuging mode. And while kwboot is running normally, it received the completed image.

Now we just need ot make the last handshake happen. Did you recheck your serial console wires and header?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 01, 2019 06:05PM
nunit & Flecks,

Have you measured how long did it take to load the NSA325 u-boot-2017.07-tld-1 image? Does it seem that it would take a long time for the load messages to appear? Not sure that it was the case here, but worth trying.

Try setting the xmodem timeout to 2000 ms. And increase this number gradually to see if it helps.
./kwboot.20190228 -B 115200 -t /dev/serial0 -d -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p -o 2000

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 02, 2019 03:54PM
bodhi Wrote:
-------------------------------------------------------

> Now we just need ot make the last handshake happen.
> Did you recheck your serial console wires and header?

I am new to these serial consoles, so I'm not sure how to verify them. I know the cp2102 converter works with an RPi 3 console (that took a bit of figuring out), but after I suspected the USB converter might be part of the issue, I figured out how to connect the RPi 1 GPIO directly to the NSA. I'm thinking that since both of them exhibit the same kwboot problems, they're not likely the source of the problem. Can point me to any methods for confirming that my console connections are indeed good?

> Have you measured how long did it take to load the
> NSA325 u-boot-2017.07-tld-1 image? Does it seem
> that it would take a long time for the load
> messages to appear? Not sure that it was the case
> here, but worth trying.

With the RPi, it takes about 2:45s to load the 2017.07 image, and with the Ubuntu laptop and the cp2102 converter, about 1:30s. In all cases, I wait at least 30 seconds after it completes before hitting ctrl-\ c to bail.

> Try setting the xmodem timeout to 2000 ms. And
> increase this number gradually to see if it
> helps.
>
> ./kwboot.20190228 -B 115200 -t /dev/serial0 -d -b
> uboot.2017.07-tld-1.nsa325.mtd0.kwb -p -o 2000
>

The -o option didn't seem to have any difference with 2s, 5s, and 10s. I also tried it with -s 10000 with to no avail. Could some of the other options like the req-delay possibly help?
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 02, 2019 06:32PM
nunit,

> The -o option didn't seem to have any difference
> with 2s, 5s, and 10s. I also tried it with -s
> 10000 with to no avail. Could some of the other
> options like the req-delay possibly help?

Yes. Try vary the -s and -q starting at:

q 2 -s 1


kwboot
Usage: kwboot [OPTIONS] [-b <image> | -D <image> ] [-B <baud> ] <TTY>

  -b <image>: boot <image> with preamble (Kirkwood, Armada 370/XP)
  -p: patch <image> to type 0x69 (uart boot)
  -D <image>: boot <image> without preamble (Dove)
  -d: enter debug mode
  -a: use timings for Armada XP
  -q <req-delay>:  use specific request-delay
  -s <resp-timeo>: use specific response-timeout
  -o <block-timeo>: use specific xmodem block timeout

  -t: mini terminal

  -B <baud>: set baud rate

===

This is quite strange that it only happens to your and Flecks boxes. I'll have to try with my currently running NSA325 when I get a chance to bring it down.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 03, 2019 07:01AM
Moin,
i have found a NAS325v2 Stock Image (NSA325 v2_V4.81(AALS.1)C0 on my HDD.
Maybe i flashed this image 1-2 years ago, but I am not sure.
Does this information help us any further?

I tested the -o 2000 / -o 5000 / -o 10000 and my result (same like the nunit):

pi@raspberrypi:~ $ ./kwboot -B 115200 -t /dev/ttyAMA0 -d -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p -o 2000
Sending debug message. Please reboot the target.../
Sending boot image...
▒i,▒``
>@▒▒▒▒▒>PC▒▒0▒▒▒ww3
▒▒U
▒▒▒▒  0 % [+xmodem: Operation canceled



Edited 1 time(s). Last edit at 03/03/2019 07:30AM by Flecks.
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 04, 2019 12:01AM
bodhi Wrote:
-------------------------------------------------------
> Yes. Try vary the -s and -q starting at:
q 2 -s 1

Are the arguments for the -q and -s options in milliseconds? If so, then I assume you meant -q 2000 and -s 1000. With values of 2000, 5000, and 10000, the results were the same, i.e. image transferred but no boot. With single digit values for -q and -s, kwboot never detected that the NSA was ready to receive the image.

I tried the above combinations with and without -o 2000 as well and it didn't seem to make a difference.

> This is quite strange that it only happens to your and Flecks boxes. I'll have to try
> with my currently running NSA325 when I get a chance to bring it down.

Thanks again for all your help with this!
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 04, 2019 01:36AM
nunit,

> Are the arguments for the -q and -s options in
> milliseconds? If so, then I assume you meant -q
> 2000 and -s 1000. With values of 2000, 5000, and
> 10000, the results were the same, i.e. image
> transferred but no boot. With single digit values
> for -q and -s, kwboot never detected that the NSA
> was ready to receive the image.

Too bad! and yes, I meant 2 and 1 seconds.

I kept hoping we can resolve this without installing JTAG (because you are so close to booting). But in the worse case, JTAG is most likely going to solve the issue. It seems the NSA325 serial console might have some flaws that we don't know about.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 04, 2019 09:20AM
bodhi Wrote:
-------------------------------------------------------
> I kept hoping we can resolve this without
> installing JTAG (because you are so close to
> booting). But in the worse case, JTAG is most
> likely going to solve the issue. It seems the
> NSA325 serial console might have some flaws that
> we don't know about.

What is involved with getting JTAG on the NSA-325? It sounds like a bit more work than it may be worth to me--especially if it's only going to indicate that I've got a non-trivial hardware failure.
Re: NSA-325 Bricked ? HDD2 LED constantly active
March 04, 2019 02:56PM
nunit,

> What is involved with getting JTAG on the NSA-325?
> It sounds like a bit more work than it may be
> worth to me--especially if it's only going to
> indicate that I've got a non-trivial hardware
> failure.

Yes. A bit of works to get there. So that's why I hesitated to recommend it. If your box were silent during kwboot, then I would recommend JTAG. But it is responsive to download, so it's a hard call.

First you need to solder a JTAG header. And then we'll work on the NSA325 OCD config. joerg has a very good writeup in the Wiki for the Pogo E02:

Quote

Serial Console & JTAG console

Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD

-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: