Welcome! Log In Create A New Profile

Advanced

Debian on Zyxel NAS326

Posted by Kirsch 
Re: Zyxel NAS326 - Debian / Boot from USB?
April 14, 2017 12:06AM
Hi.

The answer to first 3 questions is yes.
I think my LED's are all white? :-)
Re: Zyxel NAS326 - Debian / Boot from USB?
April 14, 2017 12:30AM
nielsek Wrote:
-------------------------------------------------------
> Hi.
>
> The answer to first 3 questions is yes.
> I think my LED's are all white? :-)

The 3rd question is

Quote

3. Which command did you use to power down? "poweroff" or "shutdown -h now" ?

So yes to "poweroff" ?

And Ethernet LED is white, did it light up white or not light up at all?

... About other info, can you post it?

Quote

dmesg
ethtool eth0
ifconfig -a
cat /etc/init.d/halt
cat /etc/init.d/reboot

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
April 14, 2017 12:44AM
yes, "poweroff" was used.
Attached first outputs, will let you know late.r
Attachments:
open | download - dmesg.txt (30.7 KB)
open | download - ethtool.txt (928 bytes)
open | download - ifconfig.txt (2.1 KB)
Re: Zyxel NAS326 - Debian / Boot from USB?
April 14, 2017 01:47AM
nielsek,

> yes, "poweroff" was used.

What do you see in dmesg when you power off?

On one terminal, connect serial console, and on 2nd terminal
poweroff
This way you would capture everything that the kernel does during power off.

One thing that I have not figured out is how turn on the ethernet LED light correctly, so I need all the info I can get from a different box to compare with mine. The fact that you did not see the amber or green ethernet LED is a puzzle!

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
April 14, 2017 02:27AM
Strange, but WOL does not work for me anymore. It worked for the first time, but not anymore.
Re: Zyxel NAS326 - Debian / Boot from USB?
April 14, 2017 02:23PM
nielsek Wrote:
-------------------------------------------------------
> Strange, but WOL does not work for me anymore. It
> worked for the first time, but not anymore.


Strange indeed. But that's anoher good hint. Thanks nielsek.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
April 14, 2017 02:40PM
nielsek,

At the moment, I think the MAC address stored in the NIC itself is the problem (or one of the problems) with WOL.

I think it is time for me to seriously look at how to make stock u-boot deal with the DTB correctly.

Stock u-boot can deal with DTB, but its code was an pretty old version so I had to force it not to pass it to the kernel.

Or I need to start building new u-boot for it.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 2 time(s). Last edit at 04/14/2017 02:44PM by bodhi.
Re: Zyxel NAS326 - Debian / Boot from USB?
April 16, 2017 04:05AM
Quote
bodhi
At the moment, I think the MAC address stored in the NIC itself is the problem (or one of the problems) with WOL.
I was thinking the same. There's no way how to find out what is the address and test then?
Re: Zyxel NAS326 - Debian / Boot from USB?
April 16, 2017 02:19PM
nielsek Wrote:
-------------------------------------------------------
>
Quote
bodhi
> At the moment, I think the MAC address stored in t
> he NIC itself is the problem (or one of the proble
> ms) with WOL.
>
> I was thinking the same. There's no way how to fi
> nd out what is the address and test then?

There are several MAC addresses defined in u-boot env. Perhaps one of them is the one stored in the NIC. I recall there is one of the Zyxel boxes (can't remember which) that can only WOL by using the Marvell MAC address (the NIC chip is Marvell), but not by the Zyxel MAC address.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
April 17, 2017 06:26AM
bodhi Wrote:
-------------------------------------------------------
> @everybody,
>
> I need someone to test the new kernel WOL patches
> in 4.10.9-mvebu-tld-1 on your box. Please try:
>
>
> ethtool -s eth0 wol g
>


ethtool -s eth0 wol g
Cannot set new wake-on-lan settings: Operation not supported
  not setting wol

but this new kernel and patch fixes another issue:

Someone has to replace his NAS326 because the NAND gets corrupt ant it doesn't boot anymore..
The replacement from ZyXEL has issues when using the rootfs (kernel 4.9).
The ethernet device is coming up but DHCP timeouts (as seen on NSA310s / NSA320s).
Setting up the network staticly changes nothing.
rebooting directly from ZyXEL OS to Debian .. same thing ..
"cold" boot .. same thing ...

He tried the new uploaded kernel and now it's working as it should.
Re: Zyxel NAS326 - Debian / Boot from USB?
April 17, 2017 02:22PM
pengu,

>
> ethtool -s eth0 wol g
> Cannot set new wake-on-lan settings: Operation not
> supported
> not setting wol

That meant you have not applied all the patches. Have you tried running kernel 4.10.9-mvebu-tld-1?

> but this new kernel and patch fixes another issue:
>
> He tried the new uploaded kernel and now it's work
> ing as it should.

Cool! but his ethernet problem might have been the lack of /etc/network/interfaces hwaddress.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 03:17AM
Patches applied ... but see here ..

[1598111.263448] mvneta: mvneta_ethtool_set_wol phy_id = 0x0 
[1598111.268973] mvneta f1070000.ethernet eth0: The PHY does not support set_wol, was CONFIG_MARVELL_PHY enabled?

but CONFIG_MARVELL_PHY is enabled.

cat .config | grep  CONFIG_MARVELL_PHY 
CONFIG_MARVELL_PHY=y
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 05:40AM
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 09:02AM
Well I have decided to move from stock OS to debian on my NAS326 using Method "A" in the corresponding thread. But not luck, it keeps booting back to stock OS all the time. I have tried different USB Ports and different USB sticks as well without any success. rootfs has been extracted as root (not sudo). Also verified multiple times the envs being set correct. Only difference to the guide is that I used gtkterm instead of kwboot to enter the envs but I guess that should not make a difference, or? kwboot did not detect anything and spinning forever. I'm clueless.



Edited 1 time(s). Last edit at 05/03/2017 09:56AM by sebr.
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 11:14AM
sebr,

> Only difference to the guide is that I
> used gtkterm instead of kwboot to enter the envs b
> ut I guess that should not make a difference, or?

To enter envs, it does not matter which program you are using.

Please post the entire serial console log where you attempt to do section A, with listing of modified u-boot envs before boot.


> kwboot did not detect anything and spinning foreve
> r. I'm clueless.

Post the terminal session log where you execute kwboot. And also which type of the PC/Mac system OS where you run kwboot.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 12:41PM
See attached logfile.

I used kwboot that came with ubuntu (16.04 x86). There are no error messages it just spinning forever. But that is only a minor problem since I can connect via terminal to the device without issues.



Edited 1 time(s). Last edit at 05/03/2017 01:02PM by sebr.
Attachments:
open | download - nas326.txt (22.7 KB)
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 01:18PM
sebr,

Your executed commands

Marvell>>  setenv curr_bootfrom 1
Marvell>> setenv next_bootfrom 1
Marvell>> setenv load_dtb_addr 0x1000000
Marvell>> setenv load_initrd_addr 0x2900000
Marvell>> setenv load_image_addr 0x02000000
Marvell>> setenv usb_init 'mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start'
Marvell>> setenv set_bootargs_stock 'setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"'
Marvell>> setenv bootcmd_stock_1 'run set_bootargs_stock; echo Booting from NAND kernel 1 ...; nand read 0x2000000 0x00E00000 0xF00000 && bootz 0x2000000'
Marvell>> setenv bootcmd_stock_2 'run set_bootargs_stock; echo Booting from NAND kernel 2 ...; nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000'
Marvell>> setenv usb_set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"'
Marvell>> setenv usb_bootcmd 'echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr'
Marvell>> setenv bootcmd_custom 'if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi'setenv kernel_addr_1 '0x00000000; run bootcmd_custom; '
Marvell>> saveenv


Instruction:

setenv curr_bootfrom 1
setenv next_bootfrom 1
setenv load_dtb_addr 0x1000000
setenv load_initrd_addr 0x2900000
setenv load_image_addr 0x02000000
setenv usb_init 'mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start'
setenv set_bootargs_stock 'setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:rootfs1 rw rootdelay=2"'
setenv bootcmd_stock_1 'run set_bootargs_stock; echo Booting from NAND kernel 1 ...; nand read 0x2000000 0x00E00000 0xF00000 && bootz 0x2000000'
setenv bootcmd_stock_2 'run set_bootargs_stock; echo Booting from NAND kernel 2 ...; nand read 0x2000000 0x08700000 0xF00000 && bootz 0x2000000'
setenv usb_set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"'
setenv usb_bootcmd 'echo Booting from USB ...; setenv fdt_skip_update yes; run usb_init; ext2load usb 0:1 $load_image_addr /boot/zImage; ext2load usb 0:1 $load_dtb_addr /boot/dts/armada-380-zyxel-nas326.dtb; ext2load usb 0:1 $load_initrd_addr /boot/uInitrd; run usb_set_bootargs; bootz $load_image_addr $load_initrd_addr $load_dtb_addr'
setenv bootcmd_custom 'if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi'
setenv kernel_addr_1 '0x00000000; run bootcmd_custom; '
saveenv

You've missed the bold line above.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 02:13PM
Thank you very much :-)

Unfortunately still no luck, see this

Hit any key to stop autoboot:  3  2  1  0 

NAND read: device 0 whole chip
Attempt to read outside the flash area
 0 bytes read: ERROR
Booting from USB ...
(Re)start USB...
USB0:   Port (usbActive) : 0	Interface (usbType = 2) : USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
*  kernel: cmdline image address = 0x02000000
Bad Linux ARM zImage magic!
Erasing Nand...
Writing to Nand... done
*** change boot partition to kernel2 ***
resetting ...
\00
Then back to stock OS again.

UPDATE: Now finally got it to boot. I used various Toshiba and Lexar USB sticks and they failed to get detected for whatever reason. Sandisk solved the problem.



Edited 1 time(s). Last edit at 05/03/2017 02:28PM by sebr.
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 03:25PM
bodhi Wrote:
-------------------------------------------------------
> pengu,
>
>
> > [1598111.263448] mvneta: mvneta_ethtool_set_wol
> ph
> > y_id = 0x0
>
> This meant you have missed some configs.


yeah .. now it's working

[  389.958644] m88e1318_get_wol: phy_id = 0x1410dd1 OK
[  389.963557] mvneta: mvneta_ethtool_set_wol phy_id = 0x1410dd1 
[  389.971942] m88e1318_set_wol: phy_id = 0x1410dd1 OK
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 11:44PM
sebr Wrote:

> UPDATE: Now finally got it to boot. I used various
> Toshiba and Lexar USB sticks and they failed to ge
> t detected for whatever reason. Sandisk solved the
> problem.

Cool :)

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 03, 2017 11:48PM
pengu & sebr,

Please try WOL to see if you see the same behavior that I and others have seen.

I dont expect it to work. But it's good to compare notes on behavior to confirm. We should observe the ethernet LED during shutdown, and then try WOL with all ether addresses that are defined in the stock u-boot envs.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 04, 2017 08:05AM
Unfortunately WoL not working. No LED is staying on after issuing the poweroff command. Seems like PHY is shut down completely. None of the ethaddr found in u-boot is able to wake the box up. Also not the current one (Marvell default?).
Re: Zyxel NAS326 - Debian / Boot from USB?
May 04, 2017 09:30AM
Re: Zyxel NAS326 - Debian / Boot from USB?
May 04, 2017 01:11PM
Could somebody pls give feedback about the SMB speeds that you guys get with the latest rootfs and kernel?
Read AND write speed are ~60 MB/s only, with many ups and downs. Tested with an ext4 Volume on the internal bay and GBit Network.
That is far below the file transfer speed with stock os. I have tried a few samba tweaks but that not made any big difference.
Speed of the disks is not the limiting factor:
root@nas326:/srv/dev-disk-by-id-md-name-NAS326-2# dd if=/dev/zero of=tempfile bs=1M count=1024
1024+0 Datensätze ein
1024+0 Datensätze aus
1073741824 Bytes (1,1 GB) kopiert, 7,47945 s, 144 MB/s
root@nas326:/srv/dev-disk-by-id-md-name-NAS326-2# dd of=/dev/zero if=tempfile bs=1M count=1024
1024+0 Datensätze ein
1024+0 Datensätze aus
1073741824 Bytes (1,1 GB) kopiert, 6,9247 s, 155 MB/s

Also network is not the bottleneck:
root@nas326:/srv/dev-disk-by-id-md-name-NAS326-2# iperf -c 192.168.0.100 -P 1 -i 1 -p 5001 -w 1.0M -f M -t 10
------------------------------------------------------------
Client connecting to 192.168.0.100, TCP port 5001
TCP window size: 0.31 MByte (WARNING: requested 1.00 MByte)
------------------------------------------------------------
[  3] local 192.168.0.138 port 52842 connected with 192.168.0.100 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec   112 MBytes   112 MBytes/sec
[  3]  1.0- 2.0 sec   112 MBytes   112 MBytes/sec
[  3]  2.0- 3.0 sec   112 MBytes   112 MBytes/sec
[  3]  3.0- 4.0 sec   112 MBytes   112 MBytes/sec
[  3]  4.0- 5.0 sec   112 MBytes   112 MBytes/sec
[  3]  5.0- 6.0 sec   112 MBytes   112 MBytes/sec
[  3]  6.0- 7.0 sec   112 MBytes   112 MBytes/sec
[  3]  7.0- 8.0 sec   112 MBytes   112 MBytes/sec
[  3]  8.0- 9.0 sec   112 MBytes   112 MBytes/sec
[  3]  9.0-10.0 sec   112 MBytes   112 MBytes/sec
[  3]  0.0-10.0 sec  1120 MBytes   112 MBytes/sec



Edited 3 time(s). Last edit at 05/04/2017 02:02PM by sebr.
Re: Zyxel NAS326 - Debian / Boot from USB?
May 04, 2017 11:02PM
sebr,

Compare your smb.conf with what we have in the Wiki:

Quote

Samba

Samba smb.conf for a simple set up
HowTo setup Samba/CIFS shares

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 05, 2017 06:48AM
bodhi, I checked that already and trimmed my smb.conf according to the instructions. Also played around with socket options without any difference in terms of read or write speed.
While testing the raw performance of the disk using dd and iperf for network I observed the system with htop and cpu was continously maxed out. I wonder if this is the normal behavior that raw disk I/O (dd) put such heavy load on the cpu?!
I did some more testing with FTP. Large files upload to the NAS with ~78 MB/s and download from the NAS to PC with ~86 MB/s. Even the FTP results are far below the stock SMB speeds.



Edited 1 time(s). Last edit at 05/05/2017 04:25PM by sebr.
Re: Zyxel NAS326 - Debian / Boot from USB?
May 08, 2017 10:47AM
sebr,

> While testing the raw performance of the disk usin
> g dd and iperf for network I observed the system w
> ith htop and cpu was continously maxed out. I wond
> er if this is the normal behavior that raw disk I/
> O (dd) put such heavy load on the cpu?!

I would not worry about this. In a test using iperf or dd, those processes should max out the CPU since nothing else that CPU-intensive is running.

I have not paid attention to the performance tuning for Samba and NFS. I expect that some forum members will investigate and contribute with their setup. So far no one has :) I guess I should revisit this at some time in the future.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 08, 2017 12:29PM
SAMBA performance .. it needs some tweaking on Kirkwood boxes ... here .. one line is enough ...

        min receivefile size = 128k

103 mb/s read ... 98 mb/s write ... (windows 10)
a little more on my Gentoo Linux box

samba --version
Version 4.5.8-Debian

lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 9.0 (stretch)
Release:	9.0
Codename:	stretch



Edited 1 time(s). Last edit at 05/08/2017 12:32PM by pengu.
Re: Zyxel NAS326 - Debian / Boot from USB?
May 08, 2017 12:46PM
pengu Wrote:
-------------------------------------------------------
> SAMBA performance .. it needs some tweaking on Kir
> kwood boxes ... here .. one line is enough ...
>
>
> min receivefile size = 128k
>
>
> 103 mb/s read ... 98 mb/s write ... (windows 10)
> a little more on my Gentoo Linux box
>
>
> samba --version
> Version 4.5.8-Debian
> 
> lsb_release -a
> No LSB modules are available.
> Distributor ID:	Debian
> Description:	Debian GNU/Linux 9.0 (stretch)
> Release:	9.0
> Codename:	stretch
>

Cool :) thanks Pengu.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Zyxel NAS326 - Debian / Boot from USB?
May 08, 2017 03:49PM
Hi all!

I tried to follow the instructions (Part B: setup without a serial console) but I feel I messed things up as the NAS326 doesn't boot either with (Debian) or without (stock) an attached USB stick.

The output of fw_printenv after the modifications are here:
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 0x00E00000 0xF00000 && bootz 0x2000000
bootcmd_auto=stage_boot $boot_order
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;
bootdelay=3
cacheShare=no
console=console=ttyS0,115200
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
ethmtu=1500
ethprime=egiga0
fdt_addr=2040000
fdt_skip_update=no
fdtaddr=0x1000000
fdtfile=armada-38x-modular.dtb
ide_path=/
image_name=uImage
initrd_name=uInitrd
ipaddr=10.4.50.170
kernel_addr=${kernel_addr_1}
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
loadaddr=0x02000000
loads_echo=0
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
pcieTune=no
pexMode=RC
pxe_files_load=:default.arm-armadaxp-db:default.arm-armadaxp:default.arm
pxefile_addr_r=3100000
ramdisk_addr_r=2880000
rootpath=/srv/nfs/
sata_delay_reset=0
sata_dma_mode=yes
script_addr_r=3000000
script_name=boot.scr
serverip=10.4.50.38
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
fwversion_1=V5.20(AAZF.1)
fwversion_2=V5.20(AAZF.1)
revision_1=50729
revision_2=50729
modelid_1=B303
modelid_2=B303
core_checksum_1=868590f39fdf3fe14e07e5824a550dd7
core_checksum_2=868590f39fdf3fe14e07e5824a550dd7
zld_checksum_1=845ace22f5de7ac51fbd2ed1338bd28d
zld_checksum_2=845ace22f5de7ac51fbd2ed1338bd28d
romfile_checksum_1=9D0A
romfile_checksum_2=9D0A
img_checksum_1=596153a55a196698e2f816f42d2dae47
img_checksum_2=596153a55a196698e2f816f42d2dae47
curr_bootfrom=1
next_bootfrom=1
ethaddr=B8:EC:A3:52:00:9D
serial_number=S170Y04009547
curr_bootfrom=1
next_bootfrom=1
load_dtb_addr=0x1000000
load_initrd_addr=0x2900000
load_image_addr=0x02000000
usb_init=mw.l f1018100 20420000; mw.l f1018140 003E8800; sleep 3; usb start
set_bootargs_stock=setenv bootargs "console=ttyS0,115200 ubi.mtd=4,2048 rootfstype=ubifs root=ubi0:root
fw_setenv bootcmd_stock_1 run set_bootargs_stock
bootcmd_custom=if run usb_bootcmd; then; else if run bootcmd_stock_1; then; else run bootcmd_stock_2; reset; fi; fi
kernel_addr_1=0x00000000; run bootcmd_custom; 
change_boot_part=1

Any ideas how to proceed? Do I need to setup a serial console?

Thanks,
Johannes
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: