Bricked Zyxel NSA320S - need help, please

Can I revive (reanimate) the NSA320S, please provide some tutorial that will allow me to create a pendrive or upload Debian via com to the NSA320S memory. This is how I disassembled it to its first parts. I need to do this with a computer with Windows 11 Pro to use

petecom,

> I need to do this with a computer with
> Windows 11 Pro to use

You'll need a Linux system to unbrick this box. You can run Ubuntu USB live on your Intel box. Or install Virtualbox. I would strongly recommend installing Virtualbox or VMWarePlay (if this work) because you will need some Linux environment to administer/troubleshoot/rescue this box easily.

See this post for how to run kwboot to load the NSA310s/320s u-boot image over UART (serial port).

https://forum.doozan.com/read.php?3,51739,51919#msg-51919

Make sure you can run the new u-boot over UART (post the kwboot boot log here for confirmation).

After that, you can go ahead and create a new Debian rootfs on USB thumbdrive using Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (01 Nov 2023). This must be done on Linux.

And then plug the USB rootfs to the box. Run kwboot again. Let it boot automatically, it should boot into the Debian rootfs on USB. If it does not then post the entire boot log (copy whatever is on the terminal) here.

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

You'll need a Linux system to unbrick this box.

In Windows 11:
1) Connect to your computer with Windows 11 to USB port --> AZDelivery CP2102 HW-598 USB auf Serial Adapter CP2102
2) Install Drivers and check number of COM port (devmgmt.msc)
3) Install Software Putty on Windows 11
4) Run Putty on COM Terminal COM# (installed on Windows) and Baudrate (115200)

1) Put another USB in Front USB port with kernel

2) Open in Putty

3) Power on the Zyxel NSA320S


and what next....????

petecom,

> You'll need a Linux system to unbrick this box.
>
> In Windows 11:
> 1) Connect to your computer with Windows 11 to USB
> port --> AZDelivery CP2102 HW-598 USB auf Serial
> Adapter CP2102
> 2) Install Drivers and check number of COM port
> (devmgmt.msc)
> 3) Install Software Putty on Windows 11
> 4) Run Putty on COM Terminal COM# (installed on
> Windows) and Baudrate (115200)

Putty is a terminal program, not a Linux system. Ubuntu, Arch, Debian,... is a Linux system.

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

Hello,
Small steps forward...
This is how my NSA320S is currently running
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: DB6702A-GMtech LE

U-Boot 1.1.4 (Sep 3 2013 - 16:27:22) Marvell version: 3.6.0

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFB00

Soc: 88F6702 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 400Mhz , TClock = 166Mhz

DRAM (DDR2) CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0xc80000.

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0
(Re)start USB...
USB: scanning bus for devices...
USB device not responding, giving up (status=20)
2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: WDC WD5000LPCX-24C6HT0 Firm: 02.01A02 Ser#: WD-WX91A54A3Z1R
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
## Booting image at 00800000 ...
Bad Magic Number
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - ide 0:1 **
## Booting image at 00800000 ...
Bad Magic Number

NAND read: device 0 offset 0xc80000, size 0xa00000

Bad block at 0xc80000 in erase block from 0xc80000 will be skipped
Reading data from 0x169f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8
Created: 2016-03-11 9:09:36 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5730420 Bytes = 5.5 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................................................................................................................................................................................................................................. done, booting the kernel.

and doesn't react to anything

Poniżej polecenie printenv

bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootdelay=2
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
nandEcc=1bit
PRODUCT_NAME=STG-326
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=MitraStar Technology Corp.
run_diag=yes
devices=usb
bootargs_console=console=ttyS0,115200
bootargs_mtdpartitions=mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
init_eth=phyWrite 1 0x16 0x3;phyWrite 1 0x10 0x1017;phyWrite 1 0x11 0x4408;phyWrite 1 0x16 0;phyWrite 1 0x4 0x1e1;phyWrite 1 0x9 0x300;phyWrite 1 0x10 0x3860;phyWrite 1 0x0 0x9140
init_sata=mw.l f1010104 c70e0ffd;ide reset
bootcmd_sata=setenv bootargs ${bootargs_console} ${bootargs_mtdpartitions} netconsole=6665@${ipaddr}/eth0,6666@${serverip}/ root=/dev/md0 ro;ext2load ide 0:1 0x800000 /uimage;bootm 0x800000
bootcmd_nand=setenv bootargs ${bootargs_console} ${bootargs_mtdpartitions} root=/dev/nfs rw init=/init;nand read.e 0x2000000 ${kernel_addr} 0xa00000; bootm 0x2000000
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethact=egiga0
netmask=255.255.255.0
serverip=192.168.72.100
MODEL_ID=DD01
ethaddr=28:28:5D:16:09:06
ipaddr=192.168.72.112
init_usb=mw.l f1010100 1361c000;usb reset
bootcmd_usb=setenv bootargs ${bootargs_console} ${bootargs_mtdpartitions} netconsole=6665@${ipaddr}/eth0,6666@${serverip}/;fatload usb 0 0x800000 /uimage;fatload usb 0 0xf00000 /uinitrd;bootm 0x800000 0xf00000
bootcmd=run init_eth;run init_usb;run init_sata;run bootcmd_usb;run bootcmd_sata;run bootcmd_nand
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
kernel_addr=0xc80000
pcieTune=no

I would like to ask for support and advice...

It's completely unresponsive again, I don't know what I did wrong, but I'm asking for help...

"I'm asking for help..."

I've posted above:

https://forum.doozan.com/read.php?3,139043,139047#msg-139047

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

That's all I understood from the instructions...
You then write something about executing dpkg -i from *.deb but where what and how on a virtual machine, on a pendrive, exactly where?

Then you say rootfs make a uimage, someone writes that they named the partition rootfs (I know you can)

I would like some logic in the instructions, assuming that the world does not end on Debian - there are also other distributions...

So I would like a little... patience.

I do it because from your descriptions, when you read them, a baby can do it (ha, ha, ha - the same as with other topics and installations)

petecom,

> That's all I understood from the instructions...
> You then write something about executing dpkg -i
> from *.deb but where what and how on a virtual
> machine, on a pendrive, exactly where?

When you create the rootfs the first time, there is no dpkg involved. You need to to read the instruction.

https://forum.doozan.com/read.php?2,12096

Quote

Note: If this is your first time installation, then you only need rootfs Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (this has kernel linux-6.5.7-kirkwood-tld-1 already installed). Please scroll down to 01 Nov 2023 section for download link and installation instruction.

So there is no kernel installation needed the first time. Only later when you want to install the latest kernel version, then you will go through the steps (including running dpkg).

> Then you say rootfs make a uimage, someone writes
> that they named the partition rootfs (I know you
> can)

Yes, it is when you format the USB drive with a single partition, and then format that partition as Ext3, when can label it rootfs at the same time.


> I would like some logic in the instructions,
> assuming that the world does not end on Debian -
> there are also other distributions...

You can run other distros. But each distro rootfs /boot structure is slightly different. Here we concentrate on Debian.

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