NSA-325 Bricked ? HDD2 LED constantly active

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Mon, 18 May 2020 17:15:52 -0500

buec65,

> Where can we find JTAG pins on zyxel NSA325.
>
> Has somebody used JATG on the NSA325?

Read my post right above.

And my response to your post:

https://forum.doozan.com/read.php?3,93174,102889#msg-102889

Re: NSA-325 Bricked ? HDD2 LED constantly active

buec65 — Mon, 18 May 2020 12:07:44 -0500

Where can we find JTAG pins on zyxel NSA325.

Has somebody used JATG on the NSA325?

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Mon, 04 Mar 2019 15:56:31 -0600

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

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Mon, 04 Mar 2019 10:20:56 -0600

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

bodhi — Mon, 04 Mar 2019 02:36:52 -0600

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.

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Mon, 04 Mar 2019 01:01:27 -0600

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

Flecks — Sun, 03 Mar 2019 08:01:09 -0600

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

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Sat, 02 Mar 2019 19:32:44 -0600

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  | -D  ] [-B  ] 

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

  -t: mini terminal

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

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Sat, 02 Mar 2019 16:54:29 -0600

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

bodhi — Fri, 01 Mar 2019 19:05:03 -0600

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

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Fri, 01 Mar 2019 15:46:55 -0600

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?

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Fri, 01 Mar 2019 09:40:37 -0600

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

bodhi — Thu, 28 Feb 2019 22:14:14 -0600

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

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Thu, 28 Feb 2019 21:10:11 -0600

bodhi Wrote:
-------------------------------------------------------
> Please try the new kwboot with 2017.07 uboot.

I did try the new kwboot on the RPi with the 2017.07 image (as mentioned above), and the behavior was the same. The image seemed to be pushed completely but then it hangs and the only thing I can do is cancel out of kwboot and power cycle the NSA. So what does that tell us that the newer images are able to kill the watchdog but doesn't otherwise seem to boot?

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Thu, 28 Feb 2019 21:04:54 -0600

Ah:) I forgot that I kill the watchdog in uboot 2017.07 permanently already :) by loading the uboot, the BootROM already activated the watchdog killer.

So that small uboot does not help the issue.

Please try the new kwboot with 2017.07 uboot.

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Thu, 28 Feb 2019 18:34:50 -0600

bodhi Wrote:
-------------------------------------------------------
> Here is the u-boot image that I built to kill
> watchdog:
> uboot.2013.10-bodhi-1-uart.nsa325.test.4.kwb.
>
> Please try kwboot this image instead of the
> 2017.07 image.

Thanks for the quick turnaround. I first tried on my RPi with the new kwboot, and was only able to get 21% before the 30s watchdog timer killed it:

root@raspberrypi:/home/pi# ./kwboot.20190228 -B 115200 -t /dev/serial0 -b uboot.2013.10-bodhi-1-uart.nsa325.test.4.kwb -p
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
  3 % [......................................................................]
  6 % [......................................................................]
  9 % [......................................................................]
 12 % [......................................................................]
 15 % [......................................................................]
 18 % [......................................................................]
 21 % [..................................................+xmodem: Protocol error

The 2017.07 image with the new kwboot also hung after 99% as before. The RPi is a bit slow, so I tried on my Ubuntu laptop with the cp2102 USB converter and got further, but needed more than 30s to complete:

root@nunit-pc:/home/nunit/kwboot-tool# ./kwboot -t -B 115200 /dev/ttyUSB0 -b ../uboot.2013.10-bodhi-1-uart.nsa325.test.4.kwb -p
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
  3 % [......................................................................]
...
 71 % [......................................................................]
 74 % [......................................................................]
 77 % [......................................................................]
 80 % [..................................................+xmodem: Protocol error

All the uboot images from 2014 and older that I've tried seem to fail because of the watchdog timer. What's different about the 2015 and 2017 images that they're able to work around it?

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Thu, 28 Feb 2019 17:52:57 -0600

Here is the u-boot image that I built to kill watchdog: uboot.2013.10-bodhi-1-uart.nsa325.test.4.kwb.

Please try kwboot this image instead of the 2017.07 image.

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Thu, 28 Feb 2019 17:31:19 -0600

Not sure if this attached kwboot version will make any difference.

Please try with the current u-boot 2017.07-tld-1.

I'll come back when I found the small NSA325 u-boot that I built long ago.

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Thu, 28 Feb 2019 09:37:58 -0600

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

> So yours and Flecks situation might be recoverable
> with a different kwboot.
>
> Let me see I can rebuild another kwboot version
> from mainline.

Thanks a bunch for your help with this bodhi!

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Thu, 28 Feb 2019 03:50:00 -0600

nunit,

> Is there anything else that I could try to assess
> where the problem may be? I've seen a few other
> threads that report similar behavior with UART
> boot hanging on the NSA-325. I'm starting to
> suspect that this may be a somewhat common
> hardware failure with no easy fix. It would give
> me warm fuzzies if I could get any response from
> the serial console!

The fact that the BootROM has received the complete image, told me that the only problem is the last Xmodem handshake did not occur, and that is necessary for the BootROM to execute the image.

The other NSA325 brick scenario is different. The u-boot image was not loaded at all. And the box is just not reponsive at all when kwboot starts, with the fan going.

So yours and Flecks situation might be recoverable with a different kwboot.

Let me see I can rebuild another kwboot version from mainline.

Re: NSA-325 Bricked ? HDD2 LED constantly active

Flecks — Thu, 28 Feb 2019 02:20:56 -0600

Quote
bodhi
@Flecks, do you see the same symptom? Ie. 30-second watchdog?

Yes, it sounds like the same problem. But my fan spins doesnt spin and i don't know if the uboot image boots up.

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Thu, 28 Feb 2019 01:35:32 -0600

bodhi Wrote:
-------------------------------------------------------
> At this point, the watchdog has not been disabled.
> The BootROM might have temporarily stops the
> watchdog while the image is being loaded. But
> until after something has permanently disbaled it
> (new u-boot does that first thing), the watchdog
> could still kicks in. So even if you start a
> u-boot image successfully, if it does not disable
> the watchdog, it could still be running and
> preempt every thing.

Understood--"disabled" was a poor word choice.

> > Could there be a RAM issue perhaps that's
> > causing the image not not be received or loaded
> > properly?
>
> That's a possiblity. Since u-boot image is loaded
> to RAM by kwboot, if RAM has issue then it would
> not start.

Is there anything else that I could try to assess where the problem may be? I've seen a few other threads that report similar behavior with UART boot hanging on the NSA-325. I'm starting to suspect that this may be a somewhat common hardware failure with no easy fix. It would give me warm fuzzies if I could get any response from the serial console!

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Thu, 28 Feb 2019 00:46:14 -0600

nunit,

> When I try to load the the latest uboot image
> with kwboot, I can tell the watchdog timer has
> been disabled since about 30s after it starts, the
> fan spins up to full speed for a few seconds, then
> settles down.

> The uboot image takes about 2
> minutes to load

At this point, the watchdog has not been disabled. The BootROM might have temporarily stops the watchdog while the image is being loaded. But until after something has permanently disbaled it (new u-boot does that first thing), the watchdog could still kicks in. So even if you start a u-boot image successfully, if it does not disable the watchdog, it could still be running and preempt every thing.

With that said, usually u-boot starts and then it got reset, not hung like Flecks and your test seems to indicate.

>, but at the end, it's hung and I
> can't do anything else with it other than power
> cycle.

> Could there be a RAM issue perhaps that's causing
> the image not not be received or loaded properly?

That's a possiblity. Since u-boot image is loaded to RAM by kwboot, if RAM has issue then it would not start.

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Wed, 27 Feb 2019 22:12:52 -0600

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

> That’s the HW watchdog kicks in. I’ve solved
> this problem long ago.
>
> Let me find the right binary.

Some background on my particular unit: I used it for a years with only the stock firmware, then lent it to a friend for a few months, and when I got it back, it exhibited these symptoms. I doubt that he made any attempt to put other firmware on it. When I try to load the the latest uboot image with kwboot, I can tell the watchdog timer has been disabled since about 30s after it starts, the fan spins up to full speed for a few seconds, then settles down. The uboot image takes about 2 minutes to load, but at the end, it's hung and I can't do anything else with it other than power cycle.

Could there be a RAM issue perhaps that's causing the image not not be received or loaded properly?

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Wed, 27 Feb 2019 18:58:08 -0600

nunit Wrote:
-------------------------------------------------------
> I have an NSA325v1 that exhibits the exact same
> symptoms (power and hd2 LEDs always lit, reboots
> itself every 30s, etc.).

That’s the HW watchdog kicks in. I’ve solved this problem long ago.

Let me find the right binary.

> After much googling and
> reading the various posts here, I have a working
> serial connections via an RPi v1 as well as a
> cp2102 USB-TTL converter. With both connections, I
> also get the same behavior where kwboot hangs
> after it finishes sending the uboot image:
>
>

> root@raspberrypi:/home/pi# ./kwboot -B 115200 -t
> /dev/serial0 -b
> uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
> Sending boot message. Please reboot the
> target...-
> Sending boot image...
>   0 %
> [......................................................................]
>   1 %
> [......................................................................]
>   3 %
> [......................................................................]
> ...
>  95 %
> [......................................................................]
>  97 %
> [......................................................................]
>  99 % [....................................]
> [Type Ctrl-\ + c to quit]
>

>
> I've tried the download-serial.sh method mentioned
> above, but it seems the watchdog timer reboots
> before the full file can be transferrred:
>
>

> root@raspberrypi:/home/pi# ./download-serial.sh
> /dev/serial0 uboot.1.1.4-nsa325v2-uart.bin
> Now reset or power cycle your Armada 38x board and
> then press enter
> Sleeping
> Out of sleep
> Got something 21
> Got NACK (0x15) character
> The board should be in serial downloader now.
> Sending the binary file
> Sending uboot.1.1.4-nsa325v2-uart.bin, 3713
> blocks: Give your local XMODEM receive command
> now.
> Xmodem sectors/kbytes sent: 1496/187kRetry 0: Got
> bf for sector ACK
>

>
> Is there anything else I can try to unbrick this?
> Or does it look like it may have some fatal
> hardware problem? Thanks much in advance!

@Flecks, do you see the same symptom? Ie. 30-second watchdog?

Re: NSA-325 Bricked ? HDD2 LED constantly active

nunit — Wed, 27 Feb 2019 17:55:40 -0600

I have an NSA325v1 that exhibits the exact same symptoms (power and hd2 LEDs always lit, reboots itself every 30s, etc.). After much googling and reading the various posts here, I have a working serial connections via an RPi v1 as well as a cp2102 USB-TTL converter. With both connections, I also get the same behavior where kwboot hangs after it finishes sending the uboot image:

root@raspberrypi:/home/pi# ./kwboot -B 115200 -t /dev/serial0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
Sending boot message. Please reboot the target...-
Sending boot image...
  0 % [......................................................................]
  1 % [......................................................................]
  3 % [......................................................................]
...
 95 % [......................................................................]
 97 % [......................................................................]
 99 % [....................................]
[Type Ctrl-\ + c to quit]

I've tried the download-serial.sh method mentioned above, but it seems the watchdog timer reboots before the full file can be transferrred:

root@raspberrypi:/home/pi# ./download-serial.sh /dev/serial0 uboot.1.1.4-nsa325v2-uart.bin
Now reset or power cycle your Armada 38x board and then press enter
Sleeping
Out of sleep
Got something 21
Got NACK (0x15) character
The board should be in serial downloader now. Sending the binary file
Sending uboot.1.1.4-nsa325v2-uart.bin, 3713 blocks: Give your local XMODEM receive command now.
Xmodem sectors/kbytes sent: 1496/187kRetry 0: Got bf for sector ACK

Is there anything else I can try to unbrick this? Or does it look like it may have some fatal hardware problem? Thanks much in advance!

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Mon, 25 Feb 2019 15:29:46 -0600

It looks as though your kwboot session has missed the last handshake, so the BootROM did not start running the image.

Re: NSA-325 Bricked ? HDD2 LED constantly active

bodhi — Mon, 25 Feb 2019 15:26:12 -0600

Flecks,

No it has not completed yet. Here is an example

./download-serial.sh /dev/ttyUSB0 u-boot-a38x-2015T1_p18_Thecus-spi-uart.bin 
Now reset or power cycle your Armada 38x board and then press enter
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something -1
Sleeping
Out of sleep
Got something 21
Got NACK (0x15) character
The board should be in serial downloader now. Sending the binary file 
Sending u-boot-a38x-2015T1_p18_Thecus-spi-uart.bin, 7486 blocks: Give your local XMODEM receive command now.
Bytes Sent: 958336   BPS:9796                            

Transfer complete

Your kwboot session looks better:

pi@raspberrypi:~ $ ./kwboot -t -B 115200 /dev/ttyAMA0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
Sending boot message. Please reboot the target...\
Sending boot image...
  0 % [......................................................................]
	   ....
 99 % [....................................]
[Type Ctrl-\ + c to quit]

Re: NSA-325 Bricked ? HDD2 LED constantly active

Flecks — Mon, 25 Feb 2019 08:00:42 -0600

Hey bodhi,
I change everything, cables, UART-Controller (Raspi and Arduino), power supply
and was at the point to buy a new NAS.

So I thought I have nothing to lose and I try one more time the first kwboot.

./kwboot -t -B 115200 /dev/ttyAMA0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p

and got the same, its run to 100% and finish.

Then i tried the 2nd upload test, this one:

./download-serial.sh /dev/ttyAMA0 uboot.1.1.4-nsa325v2-uart.bin

and i got this output 3 times

 ./download-serial.sh /dev/ttyAMA0 uboot.1.1.4-nsa325v2-uart.bin
Now reset or power cycle your Armada 38x board and then press enter

Sleeping
Out of sleep
Got something 21
Got NACK (0x15) character
The board should be in serial downloader now. Sending the binary file
Sending uboot.1.1.4-nsa325v2-uart.bin, 3713 blocks: Give your local XMODEM receive command now.
Xmodem sectors/kbytes sent: 1830/228kRetry 0: Got 4d for sector ACK

Sleeping
Out of sleep
Got something 21
Got NACK (0x15) character
The board should be in serial downloader now. Sending the binary file
Sending uboot.1.1.4-nsa325v2-uart.bin, 3713 blocks: Give your local XMODEM receive command now.
Xmodem sectors/kbytes sent: 1931/241kRetry 0: Got e1 for sector ACK

Sleeping
Out of sleep
Got something 21
Got NACK (0x15) character
The board should be in serial downloader now. Sending the binary file
Sending uboot.1.1.4-nsa325v2-uart.bin, 3713 blocks: Give your local XMODEM receive command now.
Xmodem sectors/kbytes sent: 1426/178kRetry 0: Got bf for sector ACK
Retry 0: Timeout on sector ACK

I think the boot image is successfully transferred to the board.
What is my opinion?

Re: NSA-325 Bricked ? HDD2 LED constantly active

Flecks — Fri, 22 Feb 2019 11:09:19 -0600

Hey,
I was ill the last view days, I will test at Weekend an Arduino Programmer to load the image.:)