4e46ae1f69
NETGEAR ReadyNAS Duo v2 is a NAS based on Marvell kirkwood SoC.
Specification:
- Processor Marvell 88F6282 (1.6 GHz)
- 256MB RAM
- 128MB NAND
- 1x GBE LAN port (PHY: Marvell 88E1318)
- 1x USB 2.0
- 2x USB 3.0
- 2x SATA
- 3x button
- 5x leds
- serial on J5 connector accessible from rear panel
(115200 8N1) (VCC,TX,RX,GND) (3V3 LOGIC!)
Installation by USB + serial:
- Copy initramfs image to fat32 usb drive
- Connect pendrive to USB 2.0 front socket
- Connect serial console
- Stop booting in u-boot
- Do:
usb reset
setenv bootargs 'console=ttyS0,115200n8 earlyprintk'
setenv bootcmd 'nand read.e 0x1200000 0x200000 0x600000;bootm 0x1200000'
saveenv
fatload usb 0:1 0x1200000 openwrt-kirkwood-netgear_readynas-duo-v2-initramfs-uImage
bootm 0x1200000
- copy sysupgrade image via ssh.
- run sysupgrade
Installation by TFTP + serial:
- Setup TFTP server and copy initramfs image
- Connect serial console
- Stop booting in u-boot
- Do:
setenv bootargs 'console=ttyS0,115200n8 earlyprintk'
setenv bootcmd 'nand read.e 0x1200000 0x200000 0x600000;bootm 0x1200000'
saveenv
setenv serverip 192.168.1.1
setenv ipaddr 192.168.1.2
tftpboot 0x1200000 openwrt-kirkwood-netgear_readynas-duo-v2-initramfs-uImage
bootm 0x1200000
- copy sysupgrade image via ssh.
- run sysupgrade
Known issues:
- Power button and PHY INTn pin are connected to the same GPIO. It
causes that every network restart button is pressed in system.
As workaround, button is used as regular BTN_1.
For more info please look at file:
RND_5.3.13_WW.src/u-boot/board/mv_feroceon/mv_hal/usibootup/usibootup.c
from Netgear GPL sources.
Tested-by: Raylynn Knight <rayknight@me.com>
Tested-by: Lech Perczak <lech.perczak@gmail.com>
Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
77 lines
1.7 KiB
Diff
77 lines
1.7 KiB
Diff
--- a/arch/arm/boot/dts/kirkwood-netgear_readynas_duo_v2.dts
|
|
+++ b/arch/arm/boot/dts/kirkwood-netgear_readynas_duo_v2.dts
|
|
@@ -19,6 +19,13 @@
|
|
reg = <0x00000000 0x10000000>;
|
|
};
|
|
|
|
+ aliases {
|
|
+ led-boot = &led_power;
|
|
+ led-failsafe = &led_power;
|
|
+ led-running = &led_power;
|
|
+ led-upgrade = &led_power;
|
|
+ };
|
|
+
|
|
chosen {
|
|
bootargs = "console=ttyS0,115200n8 earlyprintk";
|
|
stdout-path = &uart0;
|
|
@@ -115,7 +122,7 @@
|
|
&pmx_led_blue_backup >;
|
|
pinctrl-names = "default";
|
|
|
|
- power_led {
|
|
+ led_power: power_led {
|
|
label = "status:blue:power_led";
|
|
gpios = <&gpio0 31 GPIO_ACTIVE_LOW>;
|
|
default-state = "keep";
|
|
@@ -129,11 +136,13 @@
|
|
disk1_led {
|
|
label = "status:blue:disk1_led";
|
|
gpios = <&gpio0 23 GPIO_ACTIVE_LOW>;
|
|
+ linux,default-trigger = "ata1";
|
|
};
|
|
|
|
disk2_led {
|
|
label = "status:blue:disk2_led";
|
|
gpios = <&gpio0 22 GPIO_ACTIVE_LOW>;
|
|
+ linux,default-trigger = "ata2";
|
|
};
|
|
|
|
backup_led {
|
|
@@ -150,7 +159,13 @@
|
|
|
|
power-button {
|
|
label = "Power Button";
|
|
- linux,code = <KEY_POWER>;
|
|
+ /* Power button and INT pin from PHY are both connected
|
|
+ * to this GPIO. Every network restart causes PHY restart
|
|
+ * and button is pressed. It's difficult to use it as
|
|
+ * KEY_POWER without changes in kernel (or netifd) so
|
|
+ * the button is configured as regular one.
|
|
+ */
|
|
+ linux,code = <BTN_1>;
|
|
gpios = <&gpio1 15 GPIO_ACTIVE_LOW>;
|
|
};
|
|
|
|
@@ -208,18 +223,13 @@
|
|
};
|
|
|
|
partition@200000 {
|
|
- label = "uImage";
|
|
+ label = "kernel";
|
|
reg = <0x0200000 0x600000>;
|
|
};
|
|
|
|
partition@800000 {
|
|
- label = "minirootfs";
|
|
- reg = <0x0800000 0x1000000>;
|
|
- };
|
|
-
|
|
- partition@1800000 {
|
|
- label = "jffs2";
|
|
- reg = <0x1800000 0x6800000>;
|
|
+ label = "ubi";
|
|
+ reg = <0x0800000 0x7800000>;
|
|
};
|
|
};
|
|
|