I have a new Zyxel NSA320. It is unmodified. At the uboot prompt I printenv and save all environment variables. Next I pulled code from https://github.com/psch2/uboot-nsa320, compiled and used kwboot to load new uboot. No problems so far. Now if I reload all environment variables I saved and boot the kernel loads but does not execute. Any ideas?

NSA320> boot

NAND read: device 0 offset 0xc80000, size 0xa00000
10485760 bytes read: OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-2.6.31.8
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5909960 Bytes = 5.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

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

rray : 1. I'm not sure, but it may be that psch2's uboot code doesn't have the required L2cache disable feature in it. That is one issue that must be brought up (although it is clear that you are just trying to boot a 2.6.31.8 kernel, not 3.2 or higher).

2. Another is that _if_ you are trying to run a UBoot image loaded into RAM, it probably won't work. Though some got it to work in previous/older versions of U-Boot, it was never really/truly supported.

3. We can't see your env variables, specifically the ones w/ the bootargs, so we can't tell if your console stuff is set up correctly.

4. Did you fix your ethaddr in U-Boot? W/o that, stuff may not work very well.

5. Does your router's log say anything regarding a DHCP request?

6. Are you aware of how udev in linux gets twitchy about trying to boot a device when a MAC/ethaddr has been changed? You may want to look in /etc/udev/rules.d/ for some sort of persistent net rules file. If I change MAC address, I usually delete that file, otherwise IIRC udev disables your ethernet.

=====================================================

• davy's Github Repo's rescue-dg

First let me say this all may seem a bit useless but to me it is more about the how and why than just following a recipe. Thanks for your patience. The version of uboot that comes installed on my nsa320 will not boot from usb. I wish to be able to boot from usb device and retain the original Zyxel installed software, except for uboot. Why, just because I should be able to. If I use kwboot to load your uboot from quickstart I can boot from usb but not the original software in nand. I tried booting from nand using your uboot while running wireshark and saw no activity from the nsa320. Below is the data from the Zyxel uboot. As you can see the cache is on in this version. Has anyone hooked up jtag to a nsa320?

__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Mar 23 2011 - 16:09:39) Marvell version: 3.4.19

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

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 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)
//--- stateButtonBit = 3, recovery ---//
Kernel address is 0xc80000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0, egiga1 [PRIME]
Hit any key to stop autoboot: 0
NSA320>> 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
bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000
bootdelay=2
baudrate=115200
loads_echo=0
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=DD01
PRODUCT_NAME=NSA-320
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=ZyXEL Communications Corp.
run_diag=yes
ethaddr=C8:6C:87:F8:3D:84
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=0xc80000
pcieTune=no
ethact=egiga1

Environment size: 1557/131068 bytes

Hi,

rray have you progressed in installing usbboot-enabled u-boot into the nsa320 ? I'm also interested in this. I'd like to boot full system from usb and keep the HDDs only for data.

I'm not sure ... are you both looking for a newer UBoot for the NSA320? I made one back in Spring of this year (2012), and it boots from USB, from SATA, from TFTP and from NAND. If you are already aware of this and want something newer or with a wider feature set, then disregard, and good luck to you.

If you do want to use the one I already created, then see this : http://forum.doozan.com/read.php?2,7806

=====================================================

• davy's Github Repo's rescue-dg

Hi davygravy,

I'm aware of your solution and I'm not looking for a new u-boot (just for a working one). I was trying to find somewhat more detailed tutorial on how to install custom linux distro into my NSA320.

As I don't have a prepared serial cable with a level shifter currently - I was hoping to find some easier method maybe via the usb_key_func.sh. If I'm not mistaken the procedure from your package requires a serial connection to issue the commands to u-boot (section 3)? Am I correct?

Have a look at the installation package for the device @ Arch Linux ARM. It should be easy enough to modify to use a Debian rootfs in it's place.