[NSA325] Is it dead or just sleeping? (1 reply)

After multiple restarts yesterday* I've tried to boot with my last working kernel (5.14.9) for the final time to get back to a working hardware state. Unfortunately all I've got was the output below. The autoboot timeout just skips. Tried a few times, with and without USB storage and nothing changed.

* Was trying to work around that the 5.17.4 and 5.15.5 kernels installation did not produce initramfs' that passed CRC check on boot. Only unset all the env variables and semi-manually set them to the defaults, taken from https://forum.doozan.com/read.php?3,12381 -> uboot.2016.05-tld-1.environment.bodhi.tar.

So just would like to check if this is known and the next step I should take is unbricking via kwboot, as described here: https://forum.doozan.com/read.php?3,51739,51919#msg-51919

Additionally is there a way to check MTD's for wear? (sans the obvious symptoms, like no devices or write errors)

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)                                                                 
ZyXEL NSA325 2-Bay Power Media Server                                                                               
                                                                                                                    
SoC:   Kirkwood 88F6282_A1                                                                                          
DRAM:  512 MiB                                                                                                      
WARNING: Caches not enabled                                                                                         
NAND:  128 MiB                                                                                                      
In:    serial                                                                                                       
Out:   serial                                                                                                       
Err:   serial                                                                                                       
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0 
NSA325> 
NSA325> 
NSA325> 
NSA325> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0
>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>
> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U
-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Bo
ot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 
2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>> U-Boot 201
7.0>>>> U-Boot 2017.0>>>> U-Boot 2017.0>>>

The output ends with a blinking cursor, but no input is accepted nor output returned. The console starts at some moment pinging (bell) each second, but still no other output.

==== >8 ====

Edit 1

kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.nsa325.mtd0.kwb -p
Sending boot message. Please reboot the target...-
Sending boot image...
@PCww3
       0 % [+xmodem: Operation canceled

Not having much hope.