What about serial cable ? Is it connected ?
e.g:
Yep; I could interrupt the U-boot pressing esc, but usb reset gave me 0 storage devices found (USB flash is in the front). Will try more and describe my results here. Thanks:)
Maybe you have older/smaller USB flash ?
I have a 16GB FAT32 formatted disk, but who knows - will try another one...
Tried two different USB3 16GB FAT32 and one USB2 1GB FAT formatted, both USB ports with no luck:
NSA310>> usb reset
(Re)start USB...
USB: scanning bus for devices... 1 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
NSA310>> fatload usb 1 0x1000000 u-boot.kwb
** Can't read from device 1 **
** Unable to use usb 1:1 for fatload **
NSA310>> fatload usb 0 0x1000000 u-boot.kwb
** Can't read from device 0 **
** Unable to use usb 0:1 for fatload **
NSA310>>
There are all LEDs on and the On/Off button on the device is not responsive.
You are writing commands in the device firmware shell. These commands must be written in the uboot shell.
Below you are writing it in the uboot shell, which is the correct place.
For some reason the stock bootloader is unable to detect the USB drives you are using. I don't know why, but some people did have issues like that.
You have to transfer the files with tftp, it's a bit more annoying, I'll post instructions below.
If you install successfully with the following instructions I'll update the wiki with this additional method.
Prepare the tftp server and the files you want to transfer as described here: https://openwrt.org/docs/guide-user/troubleshooting/tftpserver?s[]=tftp#tftp_server_on_windows
Set your PC's ethernet port to have fixed IP address 192.168.1.10 and connect it with an ethernet cable to the NSA310 ethernet port.
boot the NSA310 and reach the uboot (bootloader) console by pressing a key as soon as you see the prompt.
You should see
NSA310>>
Now write
setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.10
Then you can begin the file transfer with
tftp 0x1000000 u-boot.kwb
It should show a progress bar and will tell you if the transfer was successful.
If it's good, then you can proceed with the other instructions, to install the OpenWrt uboot
nand erase 0x0 0x100000
nand write 0x1000000 0x00000 0x100000
reset
Then write your device's mac address as written in the sticker under the NSA310 ( the AB:CD:EF:00:00:00 you see below is an example MAC address, please write your device's MAC in the terminal)
setenv ethaddr AB:CD:EF:00:00:00
saveenv
Then, you can try with normal instructions as you have just installed a different uboot, that should be able to read from USB.
usb reset
fatload usb 0 0x2000000 nsa310.bin
If it fails again, you must use tftp again to load OpenWrt firmware too.
write
setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.10
tftp 0x2000000 nsa310.bin
and then proceed with
nand erase.part ubi
nand write 0x2000000 ubi 0x600000
reset
And OpenWrt should be installed.
Thank you very much for the instructions, I will try them and report later.
I have been trying for several hours without success (from two PCs, Win - tftpd32 + Solarwinds, Ubuntu) so the problem seems to be in the NSA310:
NSA310>> setenv ipaddr 192.168.1.1
NSA310>> setenv serverip 192.168.1.10
NSA310>> tftp 0x1000000 u-boot.kwb
Using egiga0 device
TFTP from server 192.168.1.10; our IP address is 192.168.1.1
Filename 'u-boot.kwb'.
Load address: 0x1000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
NSA310>>
Giving up for now, maybe I'll try later.
Thanks for your help anyway!
@ir11: Any update so far?
I had the same issue like you. Using four different USB Sticks which didn't work. After that I used the "oldest" USB stick I found supporting USB 1.1 only and it worked. Unfortunately I didn't manage to test the TFTP method on the stock u-boot (thx @bobafetthotmail for the description). Suprisingly I was not able to get a network connection for TFPT, using uboot.2017.07-tld-1.nsa310...
I updated the flashing instructions, trying to collect all information I pulled from different source on one page Table of Hardware - Zyxel NSA310. As this is more or less my first entry, I am looking forward to your feedback
1 Like
Where does the information that the NSA310b image works on an 310s come from? It would surprise me if that is true, as the 310s is a different NAS, with a different SoC. At least the ZyXEL firmware cannot be exchanged.
1 Like
The 310S has the same SoC of NSA310-320-325 but its hardware config is closer to NSA320-325 (most important thing is that it's not using the silly realtek ethernet and is instead using the SoC's own ethernet controller) and should boot and mostly work with that image, as it worked on Debian back then when they were writing the device tree files for these devices https://forum.doozan.com/read.php?2,22241 and only LEDs and power button don't work (as they used different GPIO pins to operate them).
The Zyxel NAS with different SoCs (Marvell Armada) are those from NAS326 and onwards.
Another possible workaround is to use the Sata port. Format it as FAT32 and place the files in it, then
ide reset
fatload ide 0 0x2000000 nsa310.bin
should load the files from the SATA drive.
So for NSA310S I must use NSA325 OpenWrt Image? I tried NSA310b image (as written in the instructions), but Ethernet interface not working
NSA310b uses different ethernet controller so it will not work.
With NSA325 image ethernet is the same so it should work, LEDs and power button will not work.
And is there a way to get the power button working on NSA310S?
The only way is to add official support for the nsa310s in OpenWrt, as the file that defines what GPIO pins are used as buttons and leds (the dts file) is compiled and integrated in the kernel image.
it's easier than adding support for most other devices as it is more or less a carbon copy of what was done to add NSA325, just take the dts file from other projects that support this device like bodh's Debian https://forum.doozan.com/read.php?2,12096
I could provide better directions than this if someone is interested but I'm not doing it myself as I don't have the time and device to test.
I am interested. I can try compile OpenWRT, but I don't know where I get correct dts file for NSA310S.
It's in the *.patch file (it's a text file) in the linux-5.5.1-kirkwood-tld-1-bodhi.tar.bz2 archive form the forum thread I linked above.
It might be easier than I said, there is no need to add official support, you can just compile for NSA310b and just hijack its dtb file to be for your device instead.
download the sources of OpenWrt, then open the file /openwrt/target/linux/kirkwood/files-5.4/arch/arm/boot/dts/kirkwood-nsa310b.dts (this is the dts file of the NSA 310b), delete all text and paste this text (please copy this from inside a Linux system or a text editor that is using Unix line terminator setting or it will mess up the formatting of the text) so now the dts file is correct for your device.
/*
* Device tree file for the Zyxel NSA 310S NAS box, hacked to disguise itself as a NSA 310b for OpenWrt
*
* Copyright (c) 2015-2016, bodhi <mibodhi@gmail.com>
*
* Based on
* Copyright (c) 2014, Adam Baker <linux@baker-net.org.uk>
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation; either version
* 2 of the License, or (at your option) any later version.
*
* Based upon the board setup file created by Peter Schildmann
*/
/dts-v1/;
#include "kirkwood.dtsi"
#include "kirkwood-6281.dtsi"
/ {
model = "ZyXEL NSA310b";
compatible = "zyxel,nsa310b", "zyxel,nsa310", "marvell,kirkwood-88f6281", "marvell,kirkwood";
memory {
device_type = "memory";
reg = <0x00000000 0x10000000>;
};
chosen {
bootargs = "console=ttyS0,115200";
stdout-path = &uart0;
};
ocp@f1000000 {
pinctrl: pin-controller@10000 {
pinctrl-names = "default";
pmx_sata0: pmx-sata0 {
marvell,pins ; /* NA */
marvell,function = "sata0";
};
pmx_sata1: pmx-sata1 {
marvell,pins ; /* NA */
marvell,function = "sata1";
};
pmx_usb_power: pmx-usb-power {
marvell,pins = "mpp21"; /* OK */
marvell,function = "gpio";
};
pmx_pwr_off: pmx-pwr-off {
marvell,pins = "mpp27"; /* OK */
marvell,function = "gpio";
};
pmx_btn_reset: pmx-btn-reset {
marvell,pins = "mpp24"; /* OK */
marvell,function = "gpio";
};
pmx_btn_copy: pmx-btn-copy {
marvell,pins = "mpp25"; /* OK */
marvell,function = "gpio";
};
pmx_btn_power: pmx-btn-power {
marvell,pins = "mpp26"; /* OK */
marvell,function = "gpio";
};
pmx_led_hdd2_green: pmx-led-hdd2-green {
marvell,pins = "mpp34"; /* OK */
marvell,function = "gpio";
};
pmx_led_hdd2_red: pmx-led-hdd2-red {
marvell,pins = "mpp12"; /* OK */
marvell,function = "gpio";
};
pmx_led_usb_green: pmx-led-usb-green {
marvell,pins = "mpp15"; /* OK */
marvell,function = "gpio";
};
pmx_led_copy_green: pmx-led-copy-green {
marvell,pins = "mpp22"; /* OK */
marvell,function = "gpio";
};
pmx_led_copy_red: pmx-led-copy-red {
marvell,pins = "mpp23"; /* OK */
marvell,function = "gpio";
};
pmx_led_sys_green: pmx-led-sys-green {
marvell,pins = "mpp28"; /* OK */
marvell,function = "gpio";
};
pmx_led_sys_orange: pmx-led-sys-orange {
marvell,pins = "mpp29"; /* OK */
marvell,function = "gpio";
};
pmx_led_hdd1_green: pmx-led-hdd1-green {
marvell,pins = "mpp16"; /* OK */
marvell,function = "gpio";
};
pmx_led_hdd1_red: pmx-led-hdd1-red {
marvell,pins = "mpp13"; /* OK */
marvell,function = "gpio";
};
/*
pmx_buzzer: pmx-buzzer {
marvell,pins = "mpp20";
marvell,function = "gpio";
};
*/
pmx_pwr_sata1: pmx-pwr-sata1 {
marvell,pins = "mpp33";
marvell,function = "gpio";
};
};
serial@12000 {
status = "ok";
};
sata@80000 {
status = "okay";
nr-ports = <2>;
};
rtc@10300 {
status = "disabled";
};
i2c@11000 {
status = "okay";
ht1382: rtc@68 {
compatible = "htk,ht1382";
reg = <0x68>;
};
};
};
regulators {
compatible = "simple-bus";
#address-cells = <1>;
#size-cells = <0>;
pinctrl-names = "default";
pinctrl-0 = <&pmx_usb_power &pmx_pwr_sata1>;
usb0_power: regulator@1 {
compatible = "regulator-fixed";
reg = <1>;
regulator-name = "USB Power";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
regulator-always-on;
regulator-boot-on;
enable-active-high;
gpio = <&gpio0 21 GPIO_ACTIVE_HIGH>;
};
sata1_power: regulator@2 {
compatible = "regulator-fixed";
reg = <2>;
regulator-name = "SATA1 Power";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
regulator-always-on;
regulator-boot-on;
enable-active-high;
gpio = <&gpio1 1 GPIO_ACTIVE_HIGH>;
};
};
gpio_poweroff {
compatible = "gpio-poweroff";
pinctrl-0 = <&pmx_pwr_off>;
pinctrl-names = "default";
gpios = <&gpio0 27 GPIO_ACTIVE_HIGH>;
};
gpio_keys {
compatible = "gpio-keys";
#address-cells = <1>;
#size-cells = <0>;
pinctrl-0 = <&pmx_btn_reset &pmx_btn_copy &pmx_btn_power>;
pinctrl-names = "default";
button@1 {
label = "Power Button";
linux,code = <KEY_POWER>;
gpios = <&gpio0 26 GPIO_ACTIVE_HIGH>;
};
button@2 {
label = "Copy Button";
linux,code = <KEY_COPY>;
gpios = <&gpio0 25 GPIO_ACTIVE_LOW>;
};
button@3 {
label = "Reset Button";
linux,code = <KEY_RESTART>;
gpios = <&gpio0 24 GPIO_ACTIVE_LOW>;
};
};
gpio-leds {
compatible = "gpio-leds";
pinctrl-0 = <&pmx_led_hdd2_green &pmx_led_hdd2_red
&pmx_led_usb_green
&pmx_led_sys_green &pmx_led_sys_orange
&pmx_led_copy_green &pmx_led_copy_red
&pmx_led_hdd1_green &pmx_led_hdd1_red>;
pinctrl-names = "default";
green-sys {
label = "nsa310s:green:sys";
gpios = <&gpio0 28 GPIO_ACTIVE_HIGH>;
linux,default-trigger = "default-on";
};
orange-sys {
label = "nsa310s:orange:sys";
gpios = <&gpio0 29 GPIO_ACTIVE_HIGH>;
};
green-hdd1 {
label = "nsa310s:green:hdd1";
gpios = <&gpio0 16 GPIO_ACTIVE_HIGH>;
};
red-hdd1 {
label = "nsa310s:red:hdd1";
gpios = <&gpio0 13 GPIO_ACTIVE_HIGH>;
};
green-hdd2 {
label = "nsa310s:green:hdd2";
gpios = <&gpio1 2 GPIO_ACTIVE_HIGH>;
};
red-hdd2 {
label = "nsa310s:red:hdd2";
gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
};
green-usb {
label = "nsa310s:green:usb";
gpios = <&gpio0 15 GPIO_ACTIVE_HIGH>;
};
green-copy {
label = "nsa310s:green:copy";
gpios = <&gpio0 22 GPIO_ACTIVE_HIGH>;
linux,default-trigger = "ide-disk";
};
red-copy {
label = "nsa310s:red:copy";
gpios = <&gpio0 23 GPIO_ACTIVE_HIGH>;
};
};
};
&nand {
status = "okay";
chip-delay = <35>;
partition@0 {
label = "uboot";
reg = <0x00c0000 0x0080000>;
};
partition@140000 {
label = "ubi";
reg = <0x0140000 0x7ec0000>;
};
};
&mdio {
status = "okay";
ethphy0: ethernet-phy@1 {
compatible = "marvell,88e1510";
reg = <1>;
};
};
ð0 {
status = "okay";
ethernet0-port@0 {
phy-handle = <ðphy0>;
};
};
&pciec {
status = "okay";
};
&pcie0 {
status = "okay";
};
Save and compile for nsa310b, and you should get an OpenWrt image that will report itself as nsa310b but will be in fact using the correct hardware settings for a nsa310S
EDIT: fixed partitions in dts file
1 Like
I try replace kirkwood-nsa310b.dts file and compile openwrt, but on device booting I have this kernel panic. Do you have any idea what to do about it?
Do you have DTS file for NSA325? I didn't find it in openWRT targets.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.4.24 (fialot@fialot-VirtualBox) (gcc version 8.3.0 (OpenWrt GCC 8.3.0 r12629-6e64039a87)) #0 Mon Mar 16 23:51:48 2020
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] OF: fdt: Machine model: ZyXEL NSA310b
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 64960
[ 0.000000] Kernel command line: console=ttyS0,115200
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 250948K/262144K available (5162K kernel code, 178K rwdata, 1392K rodata, 1024K init, 203K bss, 11196K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] random: get_random_bytes called from start_kernel+0x2d4/0x500 with crng_init=0
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[ 0.000009] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[ 0.000040] Switching to timer-based delay loop, resolution 6ns
[ 0.000130] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.000150] pid_max: default: 32768 minimum: 301
[ 0.000372] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.000393] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.001361] CPU: Testing write buffer coherency: ok
[ 0.002288] Setting up static identity map for 0x100000 - 0x10003c
[ 0.002595] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.006483] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.006511] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.006676] pinctrl core: initialized pinctrl subsystem
[ 0.007761] NET: Registered protocol family 16
[ 0.008266] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.009347] cpuidle: using governor ladder
[ 0.009735] Feroceon L2: Enabling L2
[ 0.009778] Feroceon L2: Cache support initialised.
[ 0.014213] No ATAGs?
[ 0.035901] SCSI subsystem initialized
[ 0.036809] usbcore: registered new interface driver usbfs
[ 0.036867] usbcore: registered new interface driver hub
[ 0.036926] usbcore: registered new device driver usb
[ 0.039714] clocksource: Switched to clocksource orion_clocksource
[ 0.040480] thermal_sys: Registered thermal governor 'step_wise'
[ 0.040742] NET: Registered protocol family 2
[ 0.041341] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.041375] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.041406] TCP bind hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.041439] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.041519] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 0.041542] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 0.041740] NET: Registered protocol family 1
[ 0.041776] PCI: CLS 0 bytes, default 32
[ 0.044570] workingset: timestamp_bits=14 max_order=16 bucket_order=2
[ 0.051636] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.051648] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.062600] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.063588] mvebu-gpio f1010140.gpio: IRQ index 3 not found
[ 0.064011] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 0.064030] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.064043] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.064054] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 0.064168] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[ 0.064205] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 0.065667] PCI: bus0: Fast back to back transfers disabled
[ 0.065683] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.067066] PCI: bus1: Fast back to back transfers enabled
[ 0.067083] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 0.067297] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref]
[ 0.067312] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.067774] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.068431] printk: console [ttyS0] disabled
[ 0.068517] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 10416666) is a 16550A
[ 0.512732] printk: console [ttyS0] enabled
[ 0.517961] sata_mv f1080000.sata: slots 32 ports 2
[ 0.526371] scsi host0: sata_mv
[ 0.530293] scsi host1: sata_mv
[ 0.533603] ata1: SATA max UDMA/133 irq 32
[ 0.537683] ata2: SATA max UDMA/133 irq 32
[ 0.542270] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
[ 0.548592] nand: Eon NAND 128MiB 3,3V 8-bit
[ 0.552864] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 0.560420] Scanning device for bad blocks
[ 0.569590] Bad eraseblock 100 at 0x000000c80000
[ 0.579236] Bad eraseblock 200 at 0x000001900000
[ 0.625347] 9 fixed-partitions partitions found on MTD device orion_nand
[ 0.632026] Creating 9 MTD partitions on "orion_nand":
[ 0.637143] 0x000000000000-0x000000100000 : "uboot"
[ 0.642676] 0x000000100000-0x000000180000 : "uboot_env"
[ 0.648471] 0x000000180000-0x000000200000 : "key_store"
[ 0.654290] 0x000000200000-0x000000280000 : "info"
[ 0.659636] 0x000000280000-0x000000c80000 : "etc"
[ 0.664967] 0x000000c80000-0x000001680000 : "kernel_1"
[ 0.670725] 0x000001680000-0x000004640000 : "rootfs1"
[ 0.676508] 0x000004640000-0x000005040000 : "kernel_2"
[ 0.682304] 0x000005040000-0x000008000000 : "rootfs2"
[ 0.688600] libphy: Fixed MDIO Bus: probed
[ 0.692976] libphy: orion_mdio_bus: probed
[ 0.697073] [Firmware Warn]: /ocp@f1000000/mdio-bus@72004/ethernet-phy@1: Whitelisted compatible string. Please remove
[ 0.713802] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 0.722487] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 5c:f4:ab:2f:ff:63
[ 0.731250] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.737747] ehci-orion: EHCI orion driver
[ 0.741920] orion-ehci f1050000.ehci: EHCI Host Controller
[ 0.747414] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 0.755188] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 0.789729] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 0.796266] hub 1-0:1.0: USB hub found
[ 0.800229] hub 1-0:1.0: 1 port detected
[ 0.804588] usbcore: registered new interface driver usb-storage
[ 0.810700] i2c /dev entries driver
[ 0.815213] watchdog: f1020300.watchdog-timer: driver supplied timeout (4294967295) out of range
[ 0.823985] watchdog: f1020300.watchdog-timer: falling back to default timeout (25)
[ 0.831769] orion_wdt: Initial timeout 25 sec
[ 0.843943] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 0.852013] NET: Registered protocol family 10
[ 0.858176] Segment Routing with IPv6
[ 0.861932] NET: Registered protocol family 17
[ 0.866395] 8021q: 802.1Q VLAN Support v1.8
[ 0.874140] hctosys: unable to open rtc device (rtc0)
[ 1.041022] ata1: SATA link down (SStatus 0 SControl F300)
[ 1.169727] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 1.222190] hub 1-1:1.0: USB hub found
[ 1.226199] hub 1-1:1.0: 4 ports detected
[ 1.371019] ata2: SATA link down (SStatus 0 SControl F300)
[ 1.376697] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 1.384161] Please append a correct "root=" boot option; here are the available partitions:
[ 1.392490] 1f00 1024 mtdblock0
[ 1.392493] (driver?)
[ 1.398997] 1f01 512 mtdblock1
[ 1.398999] (driver?)
[ 1.405512] 1f02 512 mtdblock2
[ 1.405514] (driver?)
[ 1.412029] 1f03 512 mtdblock3
[ 1.412032] (driver?)
[ 1.418541] 1f04 10240 mtdblock4
[ 1.418543] (driver?)
[ 1.425056] 1f05 10240 mtdblock5
[ 1.425058] (driver?)
[ 1.431573] 1f06 48896 mtdblock6
[ 1.431575] (driver?)
[ 1.438083] 1f07 10240 mtdblock7
[ 1.438085] (driver?)
[ 1.444609] 1f08 48896 mtdblock8
[ 1.444611] (driver?)
[ 1.451128] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.459358] Rebooting in 1 seconds..
this is my mistake
[ 0.637143] 0x000000000000-0x000000100000 : "uboot"
[ 0.642676] 0x000000100000-0x000000180000 : "uboot_env"
[ 0.648471] 0x000000180000-0x000000200000 : "key_store"
[ 0.654290] 0x000000200000-0x000000280000 : "info"
[ 0.659636] 0x000000280000-0x000000c80000 : "etc"
[ 0.664967] 0x000000c80000-0x000001680000 : "kernel_1"
[ 0.670725] 0x000001680000-0x000004640000 : "rootfs1"
[ 0.676508] 0x000004640000-0x000005040000 : "kernel_2"
[ 0.682304] 0x000005040000-0x000008000000 : "rootfs2"
these are the original flash partitions and OpenWrt can't boot
Now I wrote the correct flash partitions in the dts so the kernel can find the root filesystem. I fixed the file in the post above, please copy it and try again.