KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
openwrtv4/target/linux/kirkwood/image/Makefile

140 lines
3.8 KiB
Makefile
Raw Normal View History

add preliminary Marvell Kirkwood support SVN-Revision: 15556
2009-05-02 12:48:42 +00:00
#
kirkwood: fix initramfs images Signed-off-by: Luka Perkov <luka@openwrt.org> SVN-Revision: 38296
2013-10-03 02:50:02 +00:00
# Copyright (C) 2009-2013 OpenWrt.org
add preliminary Marvell Kirkwood support SVN-Revision: 15556
2009-05-02 12:48:42 +00:00
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
image: fix jffs2(_nand) image generation Variables dependend on JFFS2_BLOCKSIZE and NANDBLOCK_SIZE are used for template generation, so need to be present before inclusion of image.mk in target image Makefiles. So move all declarations to before any includes. Fixes: r42878 ("image.mk: clean up and parallelize mkfs calls") Signed-off-by: Jonas Gorski <jogo@openwrt.org> SVN-Revision: 46564
2015-08-05 13:55:52 +00:00
include $(TOPDIR)/rules.mk
include $(INCLUDE_DIR)/image.mk
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
KERNEL_LOADADDR:=0x8000
define Device/Default
kirkwood: clean up profiles, move to image makefile Adds support for per-device rootfs Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-12-22 16:26:27 +00:00
PROFILES := Default
targets: add kernel image dependencies on device tree files Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48146
2016-01-06 18:39:06 +00:00
KERNEL_DEPENDS = $$(wildcard $(DTS_DIR)/$$(DEVICE_DTS).dts)
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
KERNEL := kernel-bin | append-dtb | uImage none
KERNEL_NAME := zImage
kirkwood: install kernel binaries into bin/ for use with external storage Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-05-23 12:38:20 +00:00
KERNEL_SUFFIX := -uImage
kirkwood: cleanup image build code Drop NAND_BLOCKSIZE, UBI_OPTS and UBIFS_OPTS. They are either used by not supported filesystems or by the legacy image build code. Add common used options/images to the default build code and override the options where necessary. Don't export the kernel image, it isn't required by any board. While at it, change the file extension for the sysupgrade images to bin. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-27 23:25:41 +00:00
KERNEL_IN_UBI := 1
kirkwood: add DEVICE_VAR KERNEL_IN_UBI for kernel as volume in ubi images depending on KERNEL_IN_UBI, the image.mk will create a ubi volume for the kernel Signed-off-by: Alexander Couzens <lynxis@fe80.eu> SVN-Revision: 49009
2016-03-14 17:06:08 +00:00
PAGESIZE := 2048
SUBPAGESIZE := 512
image: use k as unit suffix for blocksize Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-04 06:56:05 +00:00
BLOCKSIZE := 128k
kirkwood: cleanup image build code Drop NAND_BLOCKSIZE, UBI_OPTS and UBIFS_OPTS. They are either used by not supported filesystems or by the legacy image build code. Add common used options/images to the default build code and override the options where necessary. Don't export the kernel image, it isn't required by any board. While at it, change the file extension for the sysupgrade images to bin. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-27 23:25:41 +00:00
IMAGES := sysupgrade.bin factory.bin
kirkwood: use image metadata Append and enforce image metadata. Remove the device specific image checks, they are replaced by image metadata. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 08:22:45 +00:00
IMAGE/sysupgrade.bin := sysupgrade-tar | append-metadata
kirkwood: cleanup image build code Drop NAND_BLOCKSIZE, UBI_OPTS and UBIFS_OPTS. They are either used by not supported filesystems or by the legacy image build code. Add common used options/images to the default build code and override the options where necessary. Don't export the kernel image, it isn't required by any board. While at it, change the file extension for the sysupgrade images to bin. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-27 23:25:41 +00:00
IMAGE/factory.bin := append-ubi
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
SUPPORTED_DEVICES := $(subst _,$(comma),$(1))
kirkwood: clean up redundant variables in the image building code Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-07-19 14:38:25 +00:00
endef
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
define Device/cisco_on100
DEVICE_TITLE := Cisco Systems ON100
DEVICE_DTS := kirkwood-on100
DEVICE_PACKAGES := kmod-i2c-mv64xxx
KERNEL_SIZE := 5376k
KERNEL_IN_UBI := 0
UBINIZE_OPTS := -E 5
IMAGE/factory.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-ubi
BOARD_NAME := on100
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
endef
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
TARGET_DEVICES += cisco_on100
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
define Device/cloudengines_pogoe02
DEVICE_TITLE := Cloud Engines Pogoplug E02
DEVICE_DTS := kirkwood-pogo_e02
BOARD_NAME := pogo_e02
SUPPORTED_DEVICES += pogo_e02
linux/kirkwood: migrate goflexhome/goflexnet to new ubi style Also using the new image build step format Signed-off-by: Alexander Couzens <lynxis@fe80.eu> SVN-Revision: 49013
2016-03-14 17:06:12 +00:00
endef
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
TARGET_DEVICES += cloudengines_pogoe02
linux/kirkwood: migrate goflexhome/goflexnet to new ubi style Also using the new image build step format Signed-off-by: Alexander Couzens <lynxis@fe80.eu> SVN-Revision: 49013
2016-03-14 17:06:12 +00:00
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
define Device/cloudengines_pogoplugv4
DEVICE_TITLE := Cloud Engines Pogoplug V4
DEVICE_DTS := kirkwood-pogoplug-series-4
DEVICE_PACKAGES := kmod-usb3
linux/kirkwood: migrate goflexhome/goflexnet to new ubi style Also using the new image build step format Signed-off-by: Alexander Couzens <lynxis@fe80.eu> SVN-Revision: 49013
2016-03-14 17:06:12 +00:00
endef
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
TARGET_DEVICES += cloudengines_pogoplugv4
define Device/iom_iconnect-1.1
DEVICE_TITLE := Iomega Iconnect
DEVICE_DTS := kirkwood-iconnect
BOARD_NAME := iconnect
SUPPORTED_DEVICES += iconnect
endef
TARGET_DEVICES += iom_iconnect-1.1
linux/kirkwood: migrate goflexhome/goflexnet to new ubi style Also using the new image build step format Signed-off-by: Alexander Couzens <lynxis@fe80.eu> SVN-Revision: 49013
2016-03-14 17:06:12 +00:00
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
define Device/linksys_audi
kirkwood: clean up profiles, move to image makefile Adds support for per-device rootfs Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-12-22 16:26:27 +00:00
DEVICE_TITLE := Linksys EA3500 (Audi)
kirkwood: support for buttons in Audi and Viper Both these devices have a wps and a reset button on GPIO pins, which need kmod-gpio-button-hotplug package to work. Add this package to their default package config. Troubleshooted and tested on a Viper. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
2018-05-09 20:38:20 +00:00
DEVICE_PACKAGES := kmod-mwl8k swconfig wpad-mini kmod-gpio-button-hotplug
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
DEVICE_DTS := kirkwood-linksys-audi
KERNEL_SIZE := 2624k
kirkwood: cleanup image build code Drop NAND_BLOCKSIZE, UBI_OPTS and UBIFS_OPTS. They are either used by not supported filesystems or by the legacy image build code. Add common used options/images to the default build code and override the options where necessary. Don't export the kernel image, it isn't required by any board. While at it, change the file extension for the sysupgrade images to bin. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-27 23:25:41 +00:00
KERNEL_IN_UBI := 0
kirkwood: only add UBI EOF markers for devices that need it Fixes issues where the second-stage u-boot already uses UBI. Signed-off-by: Felix Fietkau <nbd@nbd.name>
2017-01-11 13:03:46 +00:00
UBINIZE_OPTS := -E 5
image: remove padding parameter from append-kernel/append-rootfs Using pad-to instead of passing the optional padding to append-kernel or append-rootfs. It could be that the value of a variable is passed. In case the variable is empty no error is thrown. Furthermore the purpose of the extra parameter is hard to get without reading the code. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-11 17:05:20 +00:00
IMAGE/factory.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-ubi
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
BOARD_NAME := linksys-audi
SUPPORTED_DEVICES += linksys-audi
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
endef
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
TARGET_DEVICES += linksys_audi
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
define Device/linksys_viper
kirkwood: clean up profiles, move to image makefile Adds support for per-device rootfs Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-12-22 16:26:27 +00:00
DEVICE_TITLE := Linksys E4200v2 / EA4500 (Viper)
kirkwood: support for buttons in Audi and Viper Both these devices have a wps and a reset button on GPIO pins, which need kmod-gpio-button-hotplug package to work. Add this package to their default package config. Troubleshooted and tested on a Viper. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
2018-05-09 20:38:20 +00:00
DEVICE_PACKAGES := kmod-mwl8k swconfig wpad-mini kmod-gpio-button-hotplug
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
DEVICE_DTS := kirkwood-linksys-viper
KERNEL_SIZE := 2688k
kirkwood: cleanup image build code Drop NAND_BLOCKSIZE, UBI_OPTS and UBIFS_OPTS. They are either used by not supported filesystems or by the legacy image build code. Add common used options/images to the default build code and override the options where necessary. Don't export the kernel image, it isn't required by any board. While at it, change the file extension for the sysupgrade images to bin. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-27 23:25:41 +00:00
KERNEL_IN_UBI := 0
kirkwood: only add UBI EOF markers for devices that need it Fixes issues where the second-stage u-boot already uses UBI. Signed-off-by: Felix Fietkau <nbd@nbd.name>
2017-01-11 13:03:46 +00:00
UBINIZE_OPTS := -E 5
image: remove padding parameter from append-kernel/append-rootfs Using pad-to instead of passing the optional padding to append-kernel or append-rootfs. It could be that the value of a variable is passed. In case the variable is empty no error is thrown. Furthermore the purpose of the extra parameter is hard to get without reading the code. Signed-off-by: Mathias Kresin <dev@kresin.me>
2016-09-11 17:05:20 +00:00
IMAGE/factory.bin := append-kernel | pad-to $$$$(KERNEL_SIZE) | append-ubi
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
BOARD_NAME := linksys-viper
SUPPORTED_DEVICES += linksys-viper
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
endef
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
TARGET_DEVICES += linksys_viper
kirkwood: generate factory images for Linksys EA[34]500 This is done with the new image generation system and board names. It also generates a sysupgrade.tar image. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 47432
2015-11-10 00:16:35 +00:00
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
define Device/raidsonic_ib-nas62x0
DEVICE_TITLE := RaidSonic ICY BOX IB-NAS62x0
DEVICE_DTS := kirkwood-ib62x0
BOARD_NAME := ib62x0
SUPPORTED_DEVICES += ib62x0
kirkwood: convert iconnect, ib62x0 and pogoplug_e02 to the new image build code Update the correspoding u-boot configs to stop relying on kernel-in-rootfs, which was removed a while back Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-12-22 14:07:38 +00:00
endef
kirkwood: sort occurrences of boardame alphabetically This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-01-08 22:49:22 +00:00
TARGET_DEVICES += raidsonic_ib-nas62x0
define Device/seagate_dockstar
DEVICE_DTS := kirkwood-dockstar
DEVICE_TITLE := Seagate FreeAgent Dockstar
BOARD_NAME := dockstar
SUPPORTED_DEVICES += dockstar
endef
TARGET_DEVICES += seagate_dockstar
define Device/seagate_goflexnet
DEVICE_TITLE := Seagate GoFlexNet
DEVICE_DTS := kirkwood-goflexnet
BOARD_NAME := goflexnet
SUPPORTED_DEVICES += goflexnet
endef
TARGET_DEVICES += seagate_goflexnet
define Device/seagate_goflexhome
DEVICE_TITLE := Seagate GoFlexHome
DEVICE_DTS := kirkwood-goflexhome
BOARD_NAME := goflexhome
SUPPORTED_DEVICES += goflexhome
endef
TARGET_DEVICES += seagate_goflexhome
kirkwood: convert iconnect, ib62x0 and pogoplug_e02 to the new image build code Update the correspoding u-boot configs to stop relying on kernel-in-rootfs, which was removed a while back Signed-off-by: Felix Fietkau <nbd@nbd.name>
2016-12-22 14:07:38 +00:00
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
define Device/zyxel_nsa310b
kirkwood: add ZyXEL NSA310b The ZyXEL NSA310 device is a Kirkwood based NAS: - SoC: Marvell 88F6702 1200Mhz - SDRAM memory: 256MB DDR2 400Mhz - Gigabit ethernet: Realtek (over pcie) - Flash memory: 128MB - 1 Power button - 1 Power LED (blue) - 5 Status LED (green/red) - 1 Copy/Sync button - 1 Reset button - 2 SATA II port (1 internal and 1 external) - 2 USB 2.0 ports (1 front and 1 back) - Smart fan The stock u-boot cannot read ubi so it should be replaced with the LEDE/OpenWRT's u-boot or with a u-boot from here https://github.com/mibodhi/u-boot-kirkwood This device's boot ROM supports "kwboot" tool (in mainline u-boot, built automatically if CONFIG_KIRKWOOD is declared) that sends an uboot image to the board over serial connection, it is very easy to unbrick. The stock bootloader can use usb and read from FAT filesystems, so the installation process is simple, place the uboot file on a USB flashdrive formatted as FAT (here it is "openwrt-kirkwood-nsa310.bin", then connect TTL to the board and write the following commands in the bootloader console: usb reset fatload usb 0 0x1000000 openwrt-kirkwood-nsa310.bin nand write 0x1000000 0x00000 0x100000 reset Now you are rebooting in the new u-boot, write this in its console to install the firmware: usb reset fatload usb 0 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin nand erase.part ubi nand write 0x2000000 ubi 0x600000 If your firmware file is bigger than 6 MiBs you should write its size in hex instead of 0x600000 above, or remove that number entirely (it will take a while in this case). If you are using another uboot that can read ubi, set mtdparts like this mtdparts=mtdparts=orion_nand:0x00c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi) And set your bootcmd to be like this bootcmd=run setenv bootargs; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000 Then you can install the firmware as described above. After you installed (or configured) the u-boot for booting the firmware, write the device's mac address in the ethaddr u-boot env. The MAC address is usually on a sticker under the device (one of the two codes is the serial), it should begin with "107BEF" as it is assigned to ZyXEL. write in the u-boot console (use your MAC address instead of the example) setenv ethaddr 10:7B:EF:00:00:00 saveenv to save the mac address in the u-boot. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
2017-01-23 19:34:29 +00:00
DEVICE_TITLE := ZyXEL NSA310b
DEVICE_DTS := kirkwood-nsa310b
DEVICE_PACKAGES := kmod-r8169 kmod-gpio-button-hotplug kmod-hwmon-lm85
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
BOARD_NAME := nsa310b
kirkwood: add ZyXEL NSA310b The ZyXEL NSA310 device is a Kirkwood based NAS: - SoC: Marvell 88F6702 1200Mhz - SDRAM memory: 256MB DDR2 400Mhz - Gigabit ethernet: Realtek (over pcie) - Flash memory: 128MB - 1 Power button - 1 Power LED (blue) - 5 Status LED (green/red) - 1 Copy/Sync button - 1 Reset button - 2 SATA II port (1 internal and 1 external) - 2 USB 2.0 ports (1 front and 1 back) - Smart fan The stock u-boot cannot read ubi so it should be replaced with the LEDE/OpenWRT's u-boot or with a u-boot from here https://github.com/mibodhi/u-boot-kirkwood This device's boot ROM supports "kwboot" tool (in mainline u-boot, built automatically if CONFIG_KIRKWOOD is declared) that sends an uboot image to the board over serial connection, it is very easy to unbrick. The stock bootloader can use usb and read from FAT filesystems, so the installation process is simple, place the uboot file on a USB flashdrive formatted as FAT (here it is "openwrt-kirkwood-nsa310.bin", then connect TTL to the board and write the following commands in the bootloader console: usb reset fatload usb 0 0x1000000 openwrt-kirkwood-nsa310.bin nand write 0x1000000 0x00000 0x100000 reset Now you are rebooting in the new u-boot, write this in its console to install the firmware: usb reset fatload usb 0 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin nand erase.part ubi nand write 0x2000000 ubi 0x600000 If your firmware file is bigger than 6 MiBs you should write its size in hex instead of 0x600000 above, or remove that number entirely (it will take a while in this case). If you are using another uboot that can read ubi, set mtdparts like this mtdparts=mtdparts=orion_nand:0x00c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi) And set your bootcmd to be like this bootcmd=run setenv bootargs; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000 Then you can install the firmware as described above. After you installed (or configured) the u-boot for booting the firmware, write the device's mac address in the ethaddr u-boot env. The MAC address is usually on a sticker under the device (one of the two codes is the serial), it should begin with "107BEF" as it is assigned to ZyXEL. write in the u-boot console (use your MAC address instead of the example) setenv ethaddr 10:7B:EF:00:00:00 saveenv to save the mac address in the u-boot. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
2017-01-23 19:34:29 +00:00
endef
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
TARGET_DEVICES += zyxel_nsa310b
kirkwood: add ZyXEL NSA310b The ZyXEL NSA310 device is a Kirkwood based NAS: - SoC: Marvell 88F6702 1200Mhz - SDRAM memory: 256MB DDR2 400Mhz - Gigabit ethernet: Realtek (over pcie) - Flash memory: 128MB - 1 Power button - 1 Power LED (blue) - 5 Status LED (green/red) - 1 Copy/Sync button - 1 Reset button - 2 SATA II port (1 internal and 1 external) - 2 USB 2.0 ports (1 front and 1 back) - Smart fan The stock u-boot cannot read ubi so it should be replaced with the LEDE/OpenWRT's u-boot or with a u-boot from here https://github.com/mibodhi/u-boot-kirkwood This device's boot ROM supports "kwboot" tool (in mainline u-boot, built automatically if CONFIG_KIRKWOOD is declared) that sends an uboot image to the board over serial connection, it is very easy to unbrick. The stock bootloader can use usb and read from FAT filesystems, so the installation process is simple, place the uboot file on a USB flashdrive formatted as FAT (here it is "openwrt-kirkwood-nsa310.bin", then connect TTL to the board and write the following commands in the bootloader console: usb reset fatload usb 0 0x1000000 openwrt-kirkwood-nsa310.bin nand write 0x1000000 0x00000 0x100000 reset Now you are rebooting in the new u-boot, write this in its console to install the firmware: usb reset fatload usb 0 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin nand erase.part ubi nand write 0x2000000 ubi 0x600000 If your firmware file is bigger than 6 MiBs you should write its size in hex instead of 0x600000 above, or remove that number entirely (it will take a while in this case). If you are using another uboot that can read ubi, set mtdparts like this mtdparts=mtdparts=orion_nand:0x00c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi) And set your bootcmd to be like this bootcmd=run setenv bootargs; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000 Then you can install the firmware as described above. After you installed (or configured) the u-boot for booting the firmware, write the device's mac address in the ethaddr u-boot env. The MAC address is usually on a sticker under the device (one of the two codes is the serial), it should begin with "107BEF" as it is assigned to ZyXEL. write in the u-boot console (use your MAC address instead of the example) setenv ethaddr 10:7B:EF:00:00:00 saveenv to save the mac address in the u-boot. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
2017-01-23 19:34:29 +00:00
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
define Device/zyxel_nsa325
kirkwood: add ZyXEL NSA325 device This patch add ZyXEL NSA325 2-Bay Media Server The ZyXEL NSA325 device is a Kirkwood based NAS: - SoC: Marvell 88F6702 1600Mhz - SDRAM memory: 512MB DDR2 400Mhz - Gigabit ethernet: Marvell Alaska - Flash memory: 128MB - 1 Power button - 1 Power LED (blue) - 5 Status LED (green/red) - 1 Copy/Sync button - 1 Reset button - 2 SATA II ports (internal) - 2 USB 2.0 ports (back) - 1 USB 3.0 port (front) - Fan (fixed speed) - hardware watchdog in a mcu Basically a bigger, more powerful version of NSA310, installation is the same as they share the same flash layout. A notable difference is that there is a hardware watchdog in a mcu on the board, which is disabled by default in the LEDE u-boot. The watchdog is also disabled with a GPIO activation through raw register change when kwbooting or it would reset the board before the new uboot was transferred. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> Signed-off-by: Felix Fietkau <nbd@nbd.name> [remove dead code]
2017-02-06 10:40:52 +00:00
DEVICE_TITLE := ZyXEL NSA325 (v1 and v2)
DEVICE_DTS := kirkwood-nsa325
DEVICE_PACKAGES := kmod-gpio-button-hotplug kmod-rtc-pcf8563 kmod-usb3
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
BOARD_NAME := nsa325
kirkwood: add ZyXEL NSA325 device This patch add ZyXEL NSA325 2-Bay Media Server The ZyXEL NSA325 device is a Kirkwood based NAS: - SoC: Marvell 88F6702 1600Mhz - SDRAM memory: 512MB DDR2 400Mhz - Gigabit ethernet: Marvell Alaska - Flash memory: 128MB - 1 Power button - 1 Power LED (blue) - 5 Status LED (green/red) - 1 Copy/Sync button - 1 Reset button - 2 SATA II ports (internal) - 2 USB 2.0 ports (back) - 1 USB 3.0 port (front) - Fan (fixed speed) - hardware watchdog in a mcu Basically a bigger, more powerful version of NSA310, installation is the same as they share the same flash layout. A notable difference is that there is a hardware watchdog in a mcu on the board, which is disabled by default in the LEDE u-boot. The watchdog is also disabled with a GPIO activation through raw register change when kwbooting or it would reset the board before the new uboot was transferred. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> Signed-off-by: Felix Fietkau <nbd@nbd.name> [remove dead code]
2017-02-06 10:40:52 +00:00
endef
kirkwood: sync image filename with boardname Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-12-28 09:39:19 +00:00
TARGET_DEVICES += zyxel_nsa325
kirkwood: add ZyXEL NSA325 device This patch add ZyXEL NSA325 2-Bay Media Server The ZyXEL NSA325 device is a Kirkwood based NAS: - SoC: Marvell 88F6702 1600Mhz - SDRAM memory: 512MB DDR2 400Mhz - Gigabit ethernet: Marvell Alaska - Flash memory: 128MB - 1 Power button - 1 Power LED (blue) - 5 Status LED (green/red) - 1 Copy/Sync button - 1 Reset button - 2 SATA II ports (internal) - 2 USB 2.0 ports (back) - 1 USB 3.0 port (front) - Fan (fixed speed) - hardware watchdog in a mcu Basically a bigger, more powerful version of NSA310, installation is the same as they share the same flash layout. A notable difference is that there is a hardware watchdog in a mcu on the board, which is disabled by default in the LEDE u-boot. The watchdog is also disabled with a GPIO activation through raw register change when kwbooting or it would reset the board before the new uboot was transferred. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> Signed-off-by: Felix Fietkau <nbd@nbd.name> [remove dead code]
2017-02-06 10:40:52 +00:00
add preliminary Marvell Kirkwood support SVN-Revision: 15556
2009-05-02 12:48:42 +00:00
$(eval $(call BuildImage))
Reference in a new issue Copy permalink