Welcome! Log In Create A New Profile

Advanced

ZyXEL nas326 installation problem

Posted by rkachowski 
Re: ZyXEL nas326 installation problem
November 18, 2017 04:19PM
rkachowski ,

> Thanks a lot for your help. Everything seems to
> work awesomely now - turns out it was just my bad
> partitioning.

Cool!

>
> FWIW: even following the instructions I still have
> to unplug / replug the TX pin, otherwise kwboot is
> stuck on "Sending debug message. Please reboot
> the target...".

You will need to wait a while, perhaps 10 seconds, before the debug handshake finally timed out. This does not happen right away. Basically, the box received the debug message, and then waits for more data, and eventually timed out, and execute stock u-boot in NAND).

This never failed to run for me:
For ARM32 kwboot: 
./kwboot -t -B 115200 /dev/ttyUSB0 -d

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
kekeke
Re: ZyXEL nas326 installation problem
November 20, 2017 07:51AM
bodhi Wrote:
-------------------------------------------------------
> kekeke,
>
> Please post the entire bootlog, from u-boot banner
> until it stopped (a snippet of log is never
> helpful!).


It was almost full:

hecksum verification PASSED
l
 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2013.01-svn48206 (Dec 03 2015 - 02:50:37) Marvell version: 2014_T3.0p6

Board: RD-NAS-88F6820-DDR3
SoC:   MV88F6810 Rev A0
       running 1 CPUs
CPU:   ARM Cortex A9 MPCore (Rev 1) LE
       CPU 0
       CPU    @ 1332 [MHz]
       L2     @ 666 [MHz]
       TClock @ 200 [MHz]
       DDR    @ 666 [MHz]
       DDR 32 Bit Width, FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM:  512 MiB

Map:   Code:			0x1fed0000:0x1ff95e28
       BSS:			0x1ffef2b4
       Stack:			0x1f9cff20
       Heap:			0x1f9d0000:0x1fed0000
       U-Boot Environment:	0x00200000:0x00280000 (NAND)

NAND:  256 MiB
MMC:   mv_sdh: 0
*** Booting kernel from kernel 1 @0x00000000; run bootcmd_custom;  ***
USB2.0 0: Host Mode
USB3.0 0: Host Mode
USB3.0 1: Host Mode
Board configuration detected:
Net:   
|  port  | Interface | PHY address  |
|--------|-----------|--------------|
| egiga0 |   RGMII   |     0x01     |
egiga0 [PRIME]
Hit any key to stop autoboot:  0 

NAND read: device 0 whole chip
Attempt to read outside the flash area
 0 bytes read: ERROR
Booting from SATA ...
AHCI init for unit0
Target spinup took 0 ms.
SATA link 1 timeout.

Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found
scanning bus for devices...
kekeke
Re: ZyXEL nas326 installation problem
November 20, 2017 08:01AM
I tried to run steps manually and it's failing on `run sata_init` step:

Marvell>> printenv
CASset=max
CONTRY_TYPE=FF
FEATURE_BIT=00
MALLOC_len=5
MODEL_ID=B303
MPmode=SMP
PRODUCT_NAME=STG-328
VENDOR_NAME=MitraStar Technology Corp.
autoload=no
baudrate=115200
boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr
bootargs=console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2
bootargs_dflt=$console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel
bootargs_end=:10.4.50.254:255.255.255.0:Armada38x:eth0:none
bootargs_root=root=/dev/nfs rw
bootcmd=nand read 0x2000000 0x00000000; run bootcmd_custom;  0xF00000 && bootz 0x2000000
bootcmd_auto=stage_boot $boot_order
bootcmd_custom=run bootcmd_custom_sata
bootcmd_custom_sata=if run sata_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
bootcmd_fdt=tftpboot 0x2000000 $image_name;tftpboot $fdtaddr $fdtfile;setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_boot=tftpboot 0x2000000 $image_name; setenv bootargs $console $nandEcc $mtdparts $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetConfig video=dovefb:lcd0:$lcd0_params clcd.lcd0_enable=$lcd0_enable clcd.lcd_panel=$lcd_panel; bootz 0x2000000 - $fdtaddr;
bootcmd_fdt_edit=tftpboot $fdtaddr $fdtfile; fdt addr $fdtaddr; setenv bootcmd $bootcmd_fdt_boot
bootcmd_lgcy=tftpboot 0x2000000 $image_name; setenv bootargs $bootargs_dflt; bootm 0x2000000;
bootcmd_stock_1=run set_bootargs_stock; echo Booting from NAND kernel 1 ...; nand read 0x2000000 0x00E00000 0xF00000 && bootz 0x2000000
bootcmd_stock_2=run set_bootargs_stock; echo Booting from NAND kernel 2 ...; nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000
bootdelay=20
cacheShare=no
change_boot_part=0
console=console=ttyS0,115200
core_checksum_1=868590f39fdf3fe14e07e5824a550dd7
core_checksum_2=2773b03df8b32c243f8b84dcefa79efb
curr_bootfrom=1
device_partition=0:1
disaMvPnp=no
eeeEnable=no
enaClockGating=no
enaCpuStream=no
enaFPU=yes
enaMonExt=no
enaWrAllo=no
eth1addr=00:50:43:38:32:25
eth1mtu=1500
eth2addr=00:50:43:38:a6:25
eth2mtu=1500
eth3addr=00:50:43:32:a6:38
eth3mtu=1500
ethact=egiga0
ethaddr=B8:EC:A3:7F:D9:46
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=yes
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
fwversion_1=V5.20(AAZF.1)
fwversion_2=V5.21(AAZF.1)
ide_path=/
image_name=uImage
img_checksum_1=596153a55a196698e2f816f42d2dae47
img_checksum_2=5356a1c083dfd6bc8c74bfd231aa15a6
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
kernel_addr_1=0x00000000; run bootcmd_custom; 
kernel_addr_2=0x08700000
kernel_addr_r=2080000
kernel_mtd_1=3
kernel_mtd_2=5
lcd0_enable=0
lcd0_params=640x480-16@60
lcd_panel=0
load_dtb_addr=0x1000000
load_image_addr=0x02000000
load_initrd_addr=0x2900000
loadaddr=0x02000000
loads_echo=0
modelid_1=B303
modelid_2=B303
mtdids=nand0=armada-nand
mtdparts=mtdparts=armada-nand:2m(u-boot),2m(env),2m(config),15m(kernel1),110m(rootfs1),15m(kernel2),-(rootfs2)
mvNetConfig=mv_net_config=4,(00:50:43:11:11:11,0:1:2:3),mtu=1500
mv_pon_addr=00:50:43:25:a6:38
nandEcc=nfcConfig=4bitecc
netbsd_en=no
netmask=255.255.255.0
netretry=no
next_bootfrom=1
pcieTune=no
pexMode=RC
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
revision_1=50729
revision_2=50984
romfile_checksum_1=9D0A
romfile_checksum_2=A762
rootpath=/srv/nfs/
sata_bootcmd=echo Booting from SATA ...; setenv fdt_skip_update yes; run sata_init; ext2load scsi 0:1 $load_image_addr /boot/zImage; ext2load scsi 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load scsi 0:1 $load_initrd_addr /boot/uInitrd; run sata_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr
sata_delay_reset=0
sata_dma_mode=yes
sata_init=mw.l f1018100 20420000; mw.l f1018140 003ca800; sleep 3; scsi init
sata_set_bootargs=setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"
script_addr_r=3000000
script_name=boot.scr
scsidevs=0
serial_number=
serverip=10.4.50.38
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"
standalone=fsload 0x2000000 $image_name;setenv bootargs $console $nandEcc $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm 0x2000000;
stderr=serial
stdin=serial
stdout=serial
sysimg_mtd_1=4
sysimg_mtd_2=6
usb0Mode=host
usbActive=0
usbType=2
vxworks_en=no
yuk_ethaddr=00:00:00:EE:51:81
zld_checksum_1=845ace22f5de7ac51fbd2ed1338bd28d
zld_checksum_2=102d2dc16f397df0dddc4f1ad6380e52

Environment size: 5163/524284 bytes

Marvell>> printenv fdt_skip_update
fdt_skip_update=yes
Marvell>> run sata_init
AHCI init for unit0
Target spinup took 0 ms.
SATA link 1 timeout.

Error: SCSI Controller(s) 1B4B:9215 1B4B:9235 not found
scanning bus for devices...
kekeke
Re: ZyXEL nas326 installation problem
November 20, 2017 08:24AM
It seems that I'm not alone with this issue: https://forum.doozan.com/read.php?2,35995,36092,quote=1#REPLY
But the only conclusion I can do from this is that it's not >2TB HDD size issue because I have old 250GB WD HDD (WD2500AAKS).
Re: ZyXEL nas326 installation problem
November 20, 2017 04:09PM
kekeke,

> 250GB WD HDD (WD2500AAKS).

That could be it. I have tested a few different HDDs on this box, and they don't always initialize correctly. Certain HDD will initialize upon power up, but randomly failed to initiialize upon warm reboot.

So it is not what you doing is wrong. This stock u-boot is quite flaky with HDDs. I am looking for way to force it to initialze the disks reliably.

I'd like you to try this test.

Power up, interrupt serial console and

mw.l f1018100 20420000
mw.l f1018140 003ca800
sleep 5
scsi init
scsi init
scsi init

Repeat the "scsi init" a few times like that. See if eventually it will be initialized.

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



Edited 1 time(s). Last edit at 11/20/2017 04:31PM by bodhi.
Re: ZyXEL nas326 installation problem
November 20, 2017 07:48PM
kekeke,

If it hangs, insert this disk to the 2nd slot and try again.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: ZyXEL nas326 installation problem
November 21, 2017 02:10AM
kekeke,

Let's try this

mw.l f1018100 20420000
mw.l f1018140 003ca800
scsi reset

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: ZyXEL nas326 installation problem
November 21, 2017 06:23PM
kekeke
Re: ZyXEL nas326 installation problem
November 21, 2017 09:51PM
bodhi Wrote:
-------------------------------------------------------
> kekeke,
>
> See this post:
>
> https://forum.doozan.com/read.php?2,32146,42779#msg-42779
To summarize: I tried what you suggested above, but it didn't help. Anyway, thank you, I will wait for the news!
Re: ZyXEL nas326 installation problem
November 22, 2017 06:52PM
kekeke,

Did you try power up like heiko did (instead of rebooting only):

https://forum.doozan.com/read.php?2,36069,42854#msg-42854

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

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: