Stock env for Zyxel NSA310

Hello all,

is here somebody who has backup of the original env from stock firmware Zyxel NSA310?

Thanks for any advice.

> is here somebody who has backup of the original
> env from stock firmware Zyxel NSA310?

I don't have this, try searching the forum? And perhaps others can help.

I'm also curious to see what it looks like (i.e. is there network-related info?).

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

I have reseted env connected to NSA310 with UART: resetenv (Return all environment variable to default.)

Here is default stock environments from my NSA310:

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
bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000
bootdelay=2
baudrate=115200
loads_echo=0
ethaddr=00:19:CB:00:51:81
eth1addr=00:19:CB:00:51:82
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=DA01
PRODUCT_NAME=NSA-310
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=ZyXEL Communications Corp.
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
ethprime=egiga1
netbsd_en=no
vxworks_en=no
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;
disaMvPnp=no
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
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
hddPowerCtrl=no
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
kernel_addr=0x4640000
pcieTune=no
ethact=egiga1

jurop,

> I have reseted env connected to NSA310 with UART:
> resetenv (Return all environment
> variable to default.)

It looks good. However, there is no guarantee that these internal envs are the same as one stored in flash. Usualy, the envs on flash is more up-to-date.

But it should boot the box OK.

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

bodhi Wrote:
-------------------------------------------------------
>
> It looks good. However, there is no guarantee that
> these internal envs are the same as one stored in
> flash. Usualy, the envs on flash is more
> up-to-date.
>
> But it should boot the box OK.

It is possible get the env from the flash?

NSA310 has started correct but in UART i can not boot from TFTP and any ping. I have set ipaddr, gatewayip, serverip.

jurop,

> It is possible get the env from the flash?

Not likely, but let's try this.

Cold start (recycle power), interrupt count down and

printenv

and post the entire serial console log here.

> NSA310 has started correct but in UART i can not
> boot from TFTP and any ping. I have set ipaddr,
> gatewayip, serverip.

IIRC, I don't think this stock u-boot has network capability. You could try the latest Debian rootf on USB, see this post:

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

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

bodhi Wrote:
-------------------------------------------------------
> jurop,
>
> > It is possible get the env from the flash?
>
> Not likely, but let's try this.
>
> Cold start (recycle power), interrupt count down
> and
>

> printenv
>

> and post the entire serial console log here.
>
> > NSA310 has started correct but in UART i can
> not
> > boot from TFTP and any ping. I have set ipaddr,
> > gatewayip, serverip.
>
> IIRC, I don't think this stock u-boot has network
> capability. You could try the latest Debian rootf
> on USB, see this post:
>
> https://forum.doozan.com/read.php?2,139998


I tried to create a USB according to the instructions and the kernel panicked:

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done.
Begin: Running /scripts/nfs-premount ... done.
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no devices to configure
ipconfig: no dev[ 189.313695][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 189.322663][ T1] CPU: 0 UID: 0 PID: 1 Comm: init Not tainted 6.18.10-kirkwood-tld-1 #4 NONE a0f4bd7277a1fb453850e5ebd33a1d95fce82224
[ 189.334997][ T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[ 189.341999][ T1] Call trace:
[ 189.342014][ T1] unwind_backtrace from show_stack+0x10/0x14
[ 189.351236][ T1] show_stack from vpanic+0xc0/0x29c
[ 189.356423][ T1] vpanic from panic+0x28/0x2c
[ 189.361080][ T1] panic from do_exit+0x204/0x8ec
[ 189.366007][ T1] do_exit from sys_exit_group+0x0/0x14
[ 189.371457][ T1] sys_exit_group from sys_exit_group+0x10/0x14
[ 189.377604][ T1] sys_exit_group from ret_fast_syscall+0x0/0x44
[ 189.383838][ T1] Exception stack(0x90819fa8 to 0x90819ff0)
[ 189.389626][ T1] 9fa0: 006575a0 00000004 00000002 00000000 00000002 00657190
[ 189.398555][ T1] 9fc0: 006575a0 00000004 00000001 000000f8 00000000 76effd80 00000000 005544a8
[ 189.407481][ T1] 9fe0: 00555acc 7ecee9e8 004ce8c4 76e02544
[ 189.413271][ T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 ]---
ices to configure
/init: .: line 384: can't open '/run/net-*.conf': No such file or directory


Is it wrong made a boot usb or is it a wrong u-boot env configuration?

jurop,


> Is it wrong made a boot usb or is it a wrong
> u-boot env configuration?

The USB rootfs was not prepared correctly.

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

Latest released kernel: linux-6.18.10-kirkwood-tld-1-bodhi.tar.bz2 (15 Feb 2026)
Latest released rootfs: Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (01 Nov 2023)

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 redo the rootfs following the instruction at 01 Nov 2023 section.

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