Unable to flash the Uboot to Zyxel NSA325 (v1)

Hello all,

A couple of days ago my ZyXEL NSA325 v1 died. Only the POWER and the HDD2 LEDs are lit and the box gets in the reboot loop - restarting every 30-40 sec.
So I read a couple of threads about using kwboot. I followed this and this topics. At first I was constantly getting a "bad message" error, but at some point (don't know how and why) the process makes it to the point of:

Sending boot message. Please reboot the target...\
Sending boot image...
0 % [......................................................................]
1 % [......................................................................]
................................................>
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]

At this point the NSA325 is not at the reboot loop anymore, but now my issues is that nothing happens next?! I cannot write down nothing in the terminal, even the Ctrl+C is doing nothing. If I reboot the box (unplug the power cord and plug it back in) the box again runs into the reboot loop issue... I've repeatedly entered the same kwboot command over and over again and I'm always get stuck here. Please, advise me what I am doing wrong.

For serial connection I am using a USB to UART TTL CP2102 converter, and Ubuntu 22.04 laptop. I've tried with both "uboot.2017.07-tld-1.nsa325.mtd0.kwb" and "uboot.2023.04-tld-1.nsa325.kwb"

Metodi,

> A couple of days ago my ZyXEL NSA325 v1 died. Only
> the POWER and the HDD2 LEDs are lit and the box
> gets in the reboot loop - restarting every 30-40
> sec.

This is not exactly "died". You must be running stock FW? and that's the behaviour of the watchdog. If you are stuck and can not boot into Linux for about 30 seconds, this box's watchdog will kick in and reset the box.


> 99 % [....................................]
> [Type Ctrl-\ + c to quit]
>
> At this point the NSA325 is not at the reboot loop
> anymore,

Because the new u-boot image has a watchdog killer command in the header.

> but now my issues is that nothing happens
> next?!

> For serial connection I am using a USB to UART TTL
> CP2102 converter, and Ubuntu 22.04 laptop. I've
> tried with both
> "uboot.2017.07-tld-1.nsa325.mtd0.kwb" and
> "uboot.2023.04-tld-1.nsa325.kwb"

You probably are not doing anything wrong. It might be a bad memory or something else that crash the starting of the u-boot image after it was loaded.

=====

Connect the normal serial console using picocom on you Ubuntu laptop (adjust ttyUSB0 with the device name Ubuntu assigned to this serial converter):

picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0

And power up the NSA325. Let it run until the box got reset. And post the entire serial console log here (if there is any output).

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

bodhi,

I installed picocom and run the command as you write it down, so I get to this:

sudo picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0
picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : yes
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

So at this point I am getting confused. Should I type and execute the commands from this terminal window, or I should open another [standard] Linux terminal and run the commands from there? If I try to do the latter, I am getting the "bad message" error every time. If I stop/close the picocom tab I always success to upload the uboot image. I do a little change to the picocom command, adding "-c" option. At this point I am able to write in the picocom terminal tab, but do not know how to execute the command. Instead, when press "Enter" it adds a new row.

sudo picocom -c --b 115200 --f n --p n --d 8 /dev/ttyUSB0
picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : yes
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

These are what I get last. Both tabs was running simultaneously:

This is from Ubuntu terminal tab:

terminal: Connection timed out
sudo kwboot -t -B 115200 /dev/ttyUSB0 -b /home/user/Downloads/uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
kwboot version 2022.01+dfsg-2ubuntu2.5
Patching image boot signature to UART
Aligning image header to Xmodem block size
Sending boot message. Please reboot the target...|
Waiting 2s and flushing tty
Sending boot image header (512 bytes)...
  0 % [+++++++++++++++++
xmodem: Bad message
sudo kwboot -t -B 115200 /dev/ttyUSB0 -b /home/user/Downloads/uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
kwboot version 2022.01+dfsg-2ubuntu2.5
Patching image boot signature to UART
Aligning image header to Xmodem block size
Sending boot message. Please reboot the target...|
Waiting 2s and flushing tty
Sending boot image header (512 bytes)...
 25 % [....                                                                  ]
Done
����������'�

xmodem: Connection timed out
sudo kwboot -t -B 115200 /dev/ttyUSB0 -b /home/user/Downloads/uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
kwboot version 2022.01+dfsg-2ubuntu2.5
Patching image boot signature to UART
Aligning image header to Xmodem block size
Sending boot message. Please reboot the target...\
Waiting 2s and flushing tty
Sending boot image header (512 bytes)...
  0 % [++.+++++++++++++++++
xmodem: Bad message
sudo kwboot -t -B 115200 /dev/ttyUSB0 -b /home/user/Downloads/uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
kwboot version 2022.01+dfsg-2ubuntu2.5
Patching image boot signature to UART
Aligning image header to Xmodem block size
Sending boot message. Please reboot the target.../
Waiting 2s and flushing tty
Sending boot image header (512 bytes)...
 25 % [....                                                                  ]
Done
Sending boot image data (502572 bytes)...
  0 % [..+.+++.++.++.+.+.+.++..+....+++.+.++++.+.+.+++.+.++..+.++.+.+..++++.+]
  0 % [..++++++.+.+..++..........+.+.+.++.+.+.++..+.+.++.+..+.++++.+++.+++...]
  1 % [+..+.....++.+..+..++..+.+.+..+.+++.+++..+.+.+++.+++..+.+..++..+++.+.++]
  2 % [.+.+.+++.+.+++..+.+.+++.+....+.+.+..+++..+...+.++..+++.+++.+.+.++..+++]
  3 % [+.+...++.+..+..++..++++.+.+.+.+....+..++...+.+..+++.+++.+.+..+..+.++.+]
  4 % [.++.+.++.++++..+.+...+.++++...+.+++..++++++.+....+...++...++.+.+...+..]
  5 % [...+..+..++..+.+.+.++.+..++.+...++++.+.++...+....+.+...+.++.+.+.++...+]
  6 % [+++......+++....++.++.......+++.+++.+.++...+...++..+..+......+.+.++..+]
  7 % [..+.+.+..+..+...+..++.+...+.++++.++.++.+..+.+...++..+.+.++...+++..+.++]
  8 % [.+.++.++.++.+.+++++.++.+......+.+...+++.+..+++.++..+.++++.+.+...+.++..]
  8 % [.++.+.+++++.........+++.++.++.+.+.+...+++++++++...+.+....+.+..++++++++]
  9 % [.++++++.+.++.++.+.++.+.+.+++....++..++...+.++.+.++.++++.+++++.+..+..+.]
 10 % [+..++++++.+++..+.++.+++..+...+.+.++.+.++.+.+.+.+++++.++.....+......++.]
 11 % [+.+.+.+++.++.+..+...++++..++..+..+++.+.+....+.+++.+++.++..+...+.++..++]
 12 % [.++..++++...++...++++.+.+.+..+.++.+.++.+.+.+++..++.++.++.++++......+.+]
 13 % [.....+.+..++.++..+.++++++.++.+...++.+++.++...++.+++.+.+++++++.+...+..+]
 13 % [+++..+..+++..+.++++......++.++++...+.++.++.+.+.+++++..+++++++++..+.+.+]
 14 % [+.+++.+.+++++.++.+..+....+..+++.++.+.+.+.......++++.+.+.+.....+.++...+]
 15 % [+.+.++.++++.++.+.+.++.+.+.+.+.++++++.+.....+++++.+.+.+++..+.++.++.++.+]
 16 % [+.....+.+.+.+.++..+.+......+.+..+....+.+.+...+..+..+++.+.++...++......]
 17 % [+++.+.+..++++..+.+.+++..++++++..+++.+++.++.++..+...+.++.++.+.+.+....++]
 17 % [+.++..+...+++..+..+.+.++.+++......+++...+.+++.+...+++.++++.+++.+...+.+]
 18 % [...++..+.+++++..+.+.++.+.+.......+.........++++++.+.+...+.++..++.+.+++]
 19 % [++.+.++.++...+++.+..++.++.++....++++.+...++..+.++.+..+..+.++++.+.+.+..]
 20 % [.++.+.+++.+.+.+++.++++.+.++.+.++.+++++++.+++....+.+.++...+..+++..+.++.]
 21 % [+.+.+++.++.++.++.+++...+++++.+..+...+..+.+.+.+...++.+..+.++..+..+.+.+.]
 22 % [.+..+..+++.+.+.++......+++.++.+.+.+.+.+.+..++.+.+.+..+++++..+...++++++]
 23 % [.+..+.++.+.+...+.+++.+++++.+.+++.+++..++++.+.+++.........+....+.+...++]
 23 % [.++.++..+.+.+.++++....+..+.++.++...+.+...+...++.+...+.+.++++.+++.+.++.]
 24 % [++...+++.+.+.+...++..++.+.++.+++.++.+++++++.++..+++++++.+.+.+++...+.++]
 25 % [+...+.+.......+..+.+++.++.+.++.+.++...++..+.++.+.+.+++...+++.+.+++.+..]
 26 % [.+.++.++.+.+++++.+++.+...++.+.++.+.++....+.++++++++++++++.+.++++.+++.+]
 27 % [.....++.+.++....+.+.++.+++++....++++.+..+.++.+.+...++.+++++++.+...+++.]
 27 % [+.+.++.+...+.........+.++++.++.++++.++.++.+.+.+....+.+..+.+.++++++....]
 28 % [+..+.....+..++.+.+.+...++.+.+....+.+.+...+.+.+++...+....++.+.+.+.+++++]
 29 % [..+..+.+++.+...+.+.+....+++++++.+.+.+..++.+++.+++++++++..+.....++.+...]
 30 % [+.+.++++..+.+.++.+.+.++++.+.....+..++++++.+.++..+.+...++++.+.+..++.+..]
 31 % [..+.+.+.+..+.++.+.....+.+.+.++++...+...+..+.+.++..++.+....++.+...+....]
 32 % [+.+..+.....+++.+.+.++.+..+++..+.+...++.++.+...++.+++++..+..+.++.+..+++]
 33 % [+...+.++.++...++++++.++.+.++......+...+....+.+.+.+.+++.+.+.+.....++...]
 34 % [..+++.....+.+.+..+.+.+.+...++..+.+.+.+.+++....+.++...+++...+.+.++.+.++]
 35 % [+..........+.....+.++.+.++.+.+...+....+...+.++.+.+...++..++...++.++...]
 36 % [+.+.........+...+.+.+.+.+.+.....+...+...+.+++++.+++......+....+.++.+..]
 37 % [......+...++.+..+.+++.+...++.++...+..+...++.+.+.+...+.++..+.+.+...+.+.]
 38 % [+..++.+.+...+.+....+....+.+.+.++.++++...++++...+..++.+.+++.+.+.....+.+]
 39 % [.++++.+....+.+...+.+.+.+..+...+..+.+.....+.....+..++.++.+.+.+.+++.....]
 40 % [+......+++++++.+...+.+++...+..++++.++++..+.+.+.+...+.+..++...+.+++.++.]
 41 % [.+.++.++.++.++.++...+.+.+....+....+.++....++.+++.++.+.++.+++++...+.+.+]
 42 % [.+.+.+.+....+.+.++++.+.++++++.+.+.+.+++.++..++++.++.+.+.+++++.........]
 43 % [+..+...++...+..++.+.+.++++.+++...+.+..+..+.+.++....+.+.+....+.++.++...]
 44 % [+..+....+...++.+++....+.+.+.+..+++.+.++..+..+++++.++.....+.....+.+..+.]
 45 % [+.+..+.+.+++......+..+....+.+.++...+...+...++..+.+...++.+++.+..+.++.+.]
 46 % [+..+....+.+.+..++++.+++..+++++++.++.+...+.+.++.++++.+..+.......+.+.+++]
 47 % [.+.+.+++.++++..+...+.+.+++.+..++...+...+.++...+++...++.+.+.+.+....+..+]
 48 % [.+.+...+....+....+.+..++++..+++++.++++++.....+++.+.++...+.+...++.+...+]
 49 % [.+....+.++.+.++++.++.+.++.+.+.++.+.....+.......+...+..+...+...+.++.+.+]
 50 % [....+..+..+...+...++.+++.++.+..+.+...+.....++....+..+.++.++.++++..++.+]
 51 % [+++...++++...+...++.+.....++.....+.+...+.++.+.+.+..+.+++...+....+.+.+.]
 52 % [+...+++...++++++++++...+.+.++.+.+......++++++.++.++....+...+..++++++++]
 52 % [++.++.+.++.+.++.+....++.+.+.++.+..+..+.+++.++++.++..+..+.+...+.....+.+]
 53 % [+...+.+..+.+.....+....++.+++++.+..+.+.+..+..++....+.++.+.+...+++.+....]
 54 % [+++.+.+.+++....+..+.+++.....+...+.+.+++.+...+.........+.+....+...++..+]
 55 % [++++.++...+....+.+..+...+..+.+.+....+.++..+...+....+.+..+..++....++...]
 57 % [+++.+.+.+.++++.+.+++..+....+.++.++.+.+...+.+..+++.+.+.++++++.++++++.+.]
 57 % [+..+...+...++.++.+++.+.++...+..+..+.++.++...++++...+....++.++.++++.++.]
 58 % [+..+++.+++++...+...+..+.+.+.+.+.+.+.++.+++++++.++.++.+.+...+++.+....+.]
 59 % [..++++.+.+....++...++.+++..+..+...+.+.+++++.++.++++.++.++.++.+++++...+]
 60 % [++.+.+.++.+.+.+...++.+.+.+.+...+.+..+++++.++.+...+.+...++++.+++.+.....]
 61 % [+..+.+.++.+.+...+.+.+.+.++++...+.++..+++++++++.+.+++++...+++.......+++]
 61 % [++++++.+........+.+.+++..++.+.+...+...+...+.++.+.....+.....+.+..+.+.+.]
 63 % [..+.+...+.+++.+.+.+.+....+...+.+...+++++...++.++...++.++.+.+.++.+..+..]
 64 % [++.+.+++.+++.++++..+.+...++.+...+.+...+.+....+.+....+.+........+..+...]
 65 % [...+.+.++..++.++...++...+...++.+...++.++...++++.+.++++++.+..+.+...+.++]
 65 % [++.++++++++.++....+.+..+++.++++.+.....+++.........+.+.....+.++++.+.++.]
 66 % [..+......+....++++...+.....++.++++.++.+..+.+...+.....+....+...+.+...++]
 68 % [+.+++++.+.++.++....+...+.+.+...+++.+.+++.+.+.++..+......+...+.++.++.++]
 68 % [...+.+.+..+++.+.+++.+.+...+...+.+.+.++...+.+.++...++++.+.++.++.+.+.+++]
 69 % [+.+.++....+.....+..++.+...........+..+...+..+.+.++...+....+.++.++++...]
 70 % [++.+.+++.+.+.+.+++++++.+.++.+++.+.+++.+..++...++..+...+.+.++.+++.+.+.+]
 71 % [.++.+.+.+.++.+....+...++.++....+.+.+.+...+....+.+...+.++++.+..+++.+.+.]
 72 % [++......+.++..+++.+......+.+.+.+.+.+.+...+.+..++.+++....++.+.+++.+....]
 73 % [+++...++..+.+...+.+.++.+..+...++.+.+..+.++.+..+.+...++.+++....+++.+.++]
 74 % [...+..+.+...++..+..++++.+++++.+++++++.+++.++.+.++..+..+++.....+.+...++]
 75 % [+.+.+.++...++..+.+.+.+++.++..+..+.+++.+++..+...+.++.+.+++++..+...+.++.]
 76 % [+.+.+.++++.+.+.++..+.+...+.++....+.+...+.+.++...++.+..+.+...+...+...++]
 77 % [...++.++.+++..+.+..+.+++...+...+++...++...+++.+.+.++.++.+..+++.++.+.+.]
 78 % [+..+.+.+.+.+.++.+.+..+.+..+.+.++.+...++.++.++..++.+++++.+..+....+.+.+.]
 79 % [...+...+....+++++.++.+......+.+.++.+++++....+.++++...+++....+........+]
 80 % [++..++...++++++...+.++..+.+.+++.++..+.+.+..+++.+++++.+.+.+.++...+....+]
 80 % [.+.+..+..+.+..+.++.++++.+.+++..+..++.++++...+.+...+.....+..+...+++++++]
 81 % [.+.++++.+.+....+.++..+..+.......+.....++.+++.+....+......+.+...++..++.]
 82 % [+...+..+.++.+.+++.+++.+..+.+.+...+..+.+..+..+.+.+.+.+..+.+..+.+.....++]
 83 % [+++++++...+...+.++.++++..++.++++...++++...+++..+...+.+++....+.+..++.++]
 84 % [....+.+...+.......+..+++.+.+.+.+.+.+.......+.+...++...+......+......+.]
 85 % [++++.+.+....+.....+.+.++.+.+........+.++..+.....+..+..+..+...+.+++.+++]
 87 % [.+.+.....+++.++.+.++.+.++.+.++.+.+.++.....++.+.+..+.++.+..+..+.+.+.++.]
 87 % [.++.+.+.+....+....+.++.....+....+.+.+..+.+...++++.++.+.+...+++++++.+.+]
 88 % [......+.+...+.+.+.+.+.......+.+.+.+..+++..++++.++++.++...++.+..+......]
 89 % [+.++...+.......+.+.+...+...+.++...+...+.+...+...............+.++...+.+]
 91 % [++.+++++..+.+.+.+.+++++.+.+++.+..+.+++.++....+.++..+....+.++.++.+++.++]
 91 % [....++.+++...+....+.++...++..+.++..+.+++.++.+..+..+.+.+.+..+...++.+..+]
 92 % [+.+.+...+..+++++.+.++.....+.+.+...+...+.++++.+++.+.++.+.+.+.++++.+..++]
 93 % [+.+.+...+..++...+.+++....++.+.+..+.+.....+....++.+...+.++..+....+..+.+]
 94 % [+++.+...+.+.+++.++.+.++.+++.+.++.+.+...+..+.++...+...+.+++.+...+...+.+]
 95 % [++.+.+++.+.+.++.+..+...+.+.++.+++......+.+++..+.+...+...++.++.++.+.+..]
 96 % [..++.+....+.+......++...++++.+++++...+.+....+..+.++++++.++.+.++++.+...]
 97 % [.+.+.+.+.+....+....++..+.+...+.+.+.+.+.+.+.+.+.++.+.+.++...+..+..+.+.+]
 98 % [++.+...++.+.+++...+..+.+...+.+..+.+.+++...+.+.++...++.+++.+.+++.....+.]
 99 % [..+...+..+.+..+..+++.++.++.+.+.+.                                     ]
Done
Finishing transfer
xmodem: Bad message

And this is from picocom terminal tab:

sudo picocom -c --b 115200 --f n --p n --d 8 /dev/ttyUSB0
picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : yes
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready
�����_ή��_ކ{;�� @����[���_��

metodi,

Don't run kwboot. Run only picocom only.

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

bodhi,

This is the output of 3 or 5 boot-reboot cycles.

\FFy\C7\FF
\00\00\80\00 \00\00\00\00\00\00\00\00\FF\00\00\00\00\00\9B\D7\00\00\00\00\00\00\00\00\00\00\FB\00\00\00\00\00\00\FF\F5\FF\00\00\00\00\00\00\00\00\FB3\00\00\00\00\FE?:@\00\00\00\00\00\00

Earlier today I ran minicom and that's what I got:

Welcome to minicom 2.8

OPTIONS: I18n                                                                
Port /dev/ttyUSB0, 23:07:17                                                  
                                                                             
Press CTRL-A Z for help on special keys                                      
fc ff fb db 00 00 00 40 08 80 00 00 00 00 00 00 00 80 00 00 00 00 00 00 00 00 ea
 ff 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff fe ff 5f 05 0
0 10 00 00 00 00 00 00 00 00 00 ff af 5b 00 01 00 00 00 00 00 00 00 00 80 00 00 
00 00 00 00 00 00 00 00 00 ff ff 00 04 00 00 00 08 00 00 00 00 00 00 00 ff ff f
f 3f 00 00 04 00 00 00 00 00 00 00 00 00 00 00 ff ec 03 00 00 00 00 00 00 00 00 
00 00 00 00 00 ff ff ff 03 00 06 00 00 00 00 00 00 00 00 ff

On every reboot it adds 32 symbols - 16 groups of two.

How about picocom like you did above?

sudo picocom -c --b 115200 --f n --p n --d 8 /dev/ttyUSB0

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

bodhi,

The first row in my previous post is a copy/paste of the picocom log file.
This morning I ran the command again, but this time I am attaching the file(s) itself.

p.s. I am about to get an FT232RL converter and try if the issues came from the CP2102 converter itself.


UPDATE: Today I get another TTL converter, RS323RL and run all the commands mention above with the same result. I am still able to upload the uboot image file, but it is not loading... Picocom gave (almost) the same reuslt - 00s, but this time I am getting two digits (0s) at a boot.

The log file contains the "data" of 4 boot-reboot cycles:



Edited 2 time(s). Last edit at 03/05/2024 03:33PM by metodi.

I'm still trying to get some meaningful data out of the box, using both converters, but still wigh no luck.
I have a couple of questions:

1 - is it possible the communication settings to be different, like different baud rate, or data bits, or stop bits, etc.? I searched more information on the internet and I found a couple of articles, stating that those 00s I am getting are a sign for bad communication between devices. I tried different settings, slowing down baud, changing parity, etc. but with no luck.

2 - is it possible the device's serial port to be damaged somehow and this to be the reason for my issues loading uboot? I manage to send some data to the NSA, as the watchdog is disabled and the file transfer is successful, but are those clear signs of properly working port?

3 - is it possible to somehow check for faulty RAM? I suppose if my issue is due to a hardware failure it must be the RAM, am I right?

4 - probably not important, but a couple of hours before I found the NSA bricked, there was a power outage. After the power was restored I started the device to checked if everything was running well, and it does.

metodi,

> 1 - is it possible the communication settings to
> be different, like different baud rate, or data
> bits, or stop bits, etc.? I searched more
> information on the internet and I found a couple
> of articles, stating that those 00s I am getting
> are a sign for bad communication between devices.
> I tried different settings, slowing down baud,
> changing parity, etc. but with no luck.

No need to research that. Marvell Kirkwood BootROM requires these parameters. Besides, my home backup server is the NSA325v2 (identical to v1). So I run this very often for the last 8-10 years or so.

picocom -c --b 115200 --f n --p n --d 8 /dev/ttyUSB0

> 2 - is it possible the device's serial port to be
> damaged somehow and this to be the reason for my
> issues loading uboot? I manage to send some data
> to the NSA, as the watchdog is disabled and the
> file transfer is successful, but are those clear
> signs of properly working port?

Sending boot image data (502572 bytes)...
  0 % [..+.+++.++.++.+.+.+.++..+....+++.+.++++.+.+.+++.+.++..+.++.+.+..++++.+]
  0 % [..++++++.+.+..++..........+.+.+.++.+.+.++..+.+.++.+..+.++++.+++.+++...]
  1 % [+..+.....++.+..+..++..+.+.+..+.+++.+++..+.+.+++.+++..+.+..++..+++.+.++]
99 % [..+...+..+.+..+..+++.++.++.+.+.+.                                     ]

Not really. The kwboot transfer had a lot of errors. When you see +++, It means the handshake was not happening as it should, and the next dot (.) means it has recovered from the errors .

However, the good sign is the fact that the watchdog was disabled, which indicated that the watchdog killer command (in the transfered u-boot header) was already executed successfully. Here is where the header was successfully transfered:

Quote

sudo kwboot -t -B 115200 /dev/ttyUSB0 -b /home/user/Downloads/uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
kwboot version 2022.01+dfsg-2ubuntu2.5
Patching image boot signature to UART
Aligning image header to Xmodem block size
Sending boot message. Please reboot the target.../
Waiting 2s and flushing tty
Sending boot image header (512 bytes)...
25 % [.... ]
Done

> 3 - is it possible to somehow check for faulty
> RAM? I suppose if my issue is due to a hardware
> failure it must be the RAM, am I right?

I think the issue is still with the serial port. Use magnifier to see if any thing odd about it. Things like odd color like burning, or pins are not stable. And make sure the serial wires are a good distance from the power cord (or try to shield them somehow, i.e. use a CD Audio Blaster cable for serial connection).

If the issue is RAM, I'm no sure how to recover from that other than a HW mod to replace the RAM.

> 4 - probably not important, but a couple of hours
> before I found the NSA bricked, there was a power
> outage. After the power was restored I started the
> device to checked if everything was running well,
> and it does.

Sometime the damage has occurred by the power surge, but it'd take a few hours running to make it worse to the point that you cannot boot.

I like the fact that the kwboot ran until the end of transfer. There is some hope. Otherwise, if nothing happed and just crickets then you'll need JTAG to unbrick. This box has JTAG header, but unpopulated and you need to solder the header. In case you go with JTAG, no need to buy the debugger if you have an rPI where you can connect the wires and run OpenOCD.

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

Thank you bodhi,

I checked the serial port pins. No odd colors, no sign of burning, no unstable pins. The only odd thing I saw were multiple "wet spots" (I don't know how are these called in English?!) on the back/downside of the whole board. It is like at some moment there were salty water drops that had dried out, but left like tiny white spots?!

Now that I have observed the board more carefully, I think that at some point there were something soldered to the JTAG header. I may be wrong, but as it is unpopulated there should be holes/openings, and not solder marks, right?! As I look at these closely, some of them look like a factory done - (almost) perfectly round, but others are looking like there be some kind of intervention done?! I know that the serial port vcc pin should not be used and never done it, but is there a way to find out if this was ever done? What will be the effect of powering the serial port thru the vcc pin, and what damage can that do the the port itself?
I got this NSA second hand, and as it was working just fine until recently, I have never open it...

metodi,

> I checked the serial port pins. No odd colors, no
> sign of burning, no unstable pins. The only odd
> thing I saw were multiple "wet spots" (I don't
> know how are these called in English?!) on the
> back/downside of the whole board. It is like at
> some moment there were salty water drops that had
> dried out, but left like tiny white spots?!

Not sure what they are!

> Now that I have observed the board more carefully,
> I think that at some point there were something
> soldered to the JTAG header. I may be wrong, but
> as it is unpopulated there should be
> holes/openings, and not solder marks, right?! As I
> look at these closely, some of them look like a
> factory done - (almost) perfectly round, but
> others are looking like there be some kind of
> intervention done?!

Sounds like it has been modified. IIRC, JTAG header pins on this board are perfectly round solder buttons, i.e filled in, not holes. Lots of boards have solder buttons for unpopulated header, even for serial headers.

> I know that the serial port
> vcc pin should not be used and never done it, but
> is there a way to find out if this was ever done?
> What will be the effect of powering the serial
> port thru the vcc pin, and what damage can that do
> the the port itself?

Vcc 3V could fry the serial port. I know for a fact that this board serial port works without the 3V pin connected, so don't connect the 3V unless you are desperate and want to try.

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