aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot
Commit message (Collapse)AuthorAgeFilesLines
* ath79: fix boardname of GL.iNet GL-AR300MPaul Wassi2018-12-311-1/+2
| | | | | | | | | | This device is called GL-AR300M, therefore rename the board(s) to 'gl-ar300m-nor' and 'gl-ar300m-nand' Signed-off-by: Paul Wassi <p.wassi@gmx.at> [change boardname in uboot envtools as well, don't use wildcards for boardname] Signed-off-by: Mathias Kresin <dev@kresin.me>
* layerscape: add LS1021AIOT board supportBiwen Li2018-12-182-1/+19
| | | | | | | | | | | | | | | | | | | | | | | The LS1021A-IoT gateway reference design based on the QorIQ LS1021A processor is a purpose-built, small footprint hardware platform with a wide array of high-speed connectivity and low-speed serial interfaces to support secure delivery of IoT services for home, business or other commercial location. - Combines standards-based, open source software with a feature-rich IoT gateway design to establish a common, open framework for secured IoT service delivery and management. - Provides a wide assortment of high-speed and serial-based connectivity in a compact, highly secure design. - High efficiency through the use of the Arm-based QorIQ LS1021A embedded processor. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Biwen Li <biwen.li@nxp.com>
* uboot-envtools: fix configuration for I2SE DuckbillsMichael Heimpold2018-12-182-2/+2
| | | | | | | | After changing board names to DT compat string, we also need to adjust the script which generates uboot-env configuration files. Fixes: e880a30549b ("mxs: use generic sysinfo board detection") Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* uboot-envtools: ath79: add support for the Buffalo BHR-4GRV2Stefan Lippers-Hollmann2018-12-181-0/+1
| | | | | | | | | | | According to https://github.com/openwrt/openwrt/pull/1527, support for the Buffalo BHR-4GRV2 in ath79 requires repartitioning from an initramfs image, make this easier by supporting uboot-envtools support out of the box. Build tested, but not runtime tested. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* uboot-envtools: ath79: add support for the Buffalo WZR-HP-AG300HStefan Lippers-Hollmann2018-12-181-0/+3
| | | | | | | | | Port support for the Buffalo WZR-HP-AG300H from the ar71xx target to ath79 as well. Build- and runtime tested on the Buffalo WZR-HP-AG300H. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ramips: drop support for ALLNET ALL0239-3G and Sitecom WL-341 v3Mathias Kresin2018-12-121-1/+0
| | | | | | | | | | | | Beside one exception, no one took care of these two remaining boards still using the legacy image build code during the last two years. Since OpenWrt 14.07 the ALLNET ALL0239-3G image building is broken. The Sitecom WL-341 v3 image build code looks pretty hackish and broken. It's questionable if the legacy image works as all. Signed-off-by: Mathias Kresin <dev@kresin.me>
* uboot-fritz4040: update package to 2018-12-09Christian Lamparter2018-12-114-353/+5
| | | | | | | | | | | | | | | | | This patch updates the uboot-fritz4040 package to the latest version. The portability and private-libgcc patches, as well as the upload-to-f4040.sh script have been added to the upstream repository. Furthermore, the upload-to-f4040 has been updated to take the first parameter as the file it is supposed to flash, otherwise it defaults to the previous "uboot-fritz4040.bin". Furthermore the error messages have been improved and ftp will now dump some "progress information" to the user's console. Also included is support for gcc 8+ and a fix for the obnoxous error that currently breaks the builders: | fritz/src/lzma2eva.c:23:30: fatal error: zlib.h: No such file or directory Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add support for the Netgear WNDAP620 and WNDAP660Christian Lamparter2018-11-261-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the Netgear WNDAP620 and WNDAP660, they are similar devices, but due to the LAN LED configuration, the switch setup and WIFI configuration each gets a different device target. Hardware Highlights WNDAP620: CPU: AMCC PowerPC APM82181 at 1000 MHz DRAM: 128 MB, 2 x 64 MiB DDR2 Hynix H5PS5162GF CPU: AMCC PowerPC APM82181 at 1000 MHz FLASH: 32 MiB, NAND SLC, Hynix HY27US08561A Ethernet: RealTek RTL8363SB 2x2-Port Switch PHY - Only 1 GBit Port (POE) Wifi: Atheros AR9380 minipcie - Dual-Band - 3x3:3 Serial: console port with RJ45 Interface (9600-N-8-1) LEDS: Power, LAN-Activity, dual color LAN-Linkspeed, 2.4GHz, 5GHz LEDs Button: Soft Reset Button Antennae: 3 internal dual-band antennae + 3 x RSMA for external antennaes Hardware Highlights WNDAP660: CPU: AMCC PowerPC APM82181 at 1000 MHz + 2 Heatsinks DRAM: 256 MB, 2 x 128 MiB DDR2 FLASH: 32 MiB, NAND SLC, Hynix HY27US08561A Ethernet: RealTek RTL8363SB 2x2-Port Switch PHY (POE) Wifi1: Atheros AR9380 minipcie - Dual-Band - 3x3:3 Wifi2: Atheros AR9380 minipcie - Dual-Band - 3x3:3 Serial: console port with RJ45 Interface (9600-N-8-1) LEDS: Power, LAN-Activity, 2x dual color LAN-Linkspeed, 2.4GHz, 5GHz LEDs Button: Soft Reset Button Antennae: 6 internal dual-band antennae + 3 x RSMA for external antennaes Flashing requirements: - needs a tftp server at 192.168.1.10/serverip. - special 8P8C(aka RJ45)<->D-SUB9 Console Cable ("Cisco Console Cable"). Note: Both WNDAP6x0 have a MAX3232 transceivers, hence no need for any separate CMOS/TTL level shifters. External Antenna: The antennae mux is controlled by GPIO 11 and GPIO14. Valid Configurations: = Config# = | = GPIO 11 = | = GPIO 14 = | ===== Description ===== 1. | 1 / High | 0 / Low | Use the internal antennae (default) 2. | 0 / Low | 1 / High | Use the external antennae The external antennaes are only meant for the 2.4 GHz band. One-way Flashing instructions via u-boot: 0. connect the serial cable to the RJ45 Console Port Note: This requires a poper RS232 and not a TTL/USB adaptor. 1. power up the AP and interrupt the u-boot process at 'Hit any key to stop autoboot' 2. setup serverip and ipaddr env settings Enter the following commands into the u-boot shell # setenv ipaddr 192.168.1.1 # setenv serverip 192.168.1.10 3. download the factory.img image to the AP Enter the following commands into the u-boot shell # tftp ${kernel_addr_r} openwrt-apm821xx-nand-netgear_wndap660-squashfs-factory.img 4. verfiy image integrity Enter the following commands into the u-boot shell # crc32 $fileaddr $filesize If the calculated crc32 checksum does not match, go back to step 3. 5. flash the image Enter the following commands into the u-boot shell # nand erase 0x110000 0x1bd0000 # nand write ${kernel_addr_r} 0x110000 ${filesize} 6. setup uboot environment Enter the following commands into the u-boot shell # setenv bootargs # setenv fileaddr # setenv filesize # setenv addroot 'setenv bootargs ${bootargs} root=/dev/ubiblock0_0' # setenv owrt_boot 'nboot ${kernel_addr_r} nand0 0x110000; run addroot; run addtty; bootm ${kernel_addr_r}' # setenv bootcmd 'run owrt_boot' # saveenv 7. boot # run bootcmd Booting initramfs instructions via u-boot: Follow steps 0 - 2 from above. 3. boot initramfs Enter the following commands into the u-boot shell # tftp ${kernel_addr_r} openwrt-apm821xx-nand-netgear_wndap660-initramfs-kernel.bin # run addtty # bootm ${kernel_addr_r} Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: MX60(W): enable u-boot environmentChristian Lamparter2018-11-261-0/+3
| | | | | | | | | This patch adds u-boot environment access to the MX60(W) target. "The environment size is one NAND block (128KiB on Buckminster). We allocate four NAND blocks to deal with bad blocks which may exist in the saved environment" Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: MR24: add to uboot-envtoolsChristian Lamparter2018-11-261-0/+4
| | | | | | | | This patch adds the complicated u-boot environment access settings for to the MR24 target. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add uboot-envtools supportChristian Lamparter2018-11-261-0/+18
| | | | | | | | | All apm821xx devices use u-boot and most of them have an accessible u-boot environment. This patch adds the necessary template file, but does not add the uboot-envtools package to any of the targets. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* uboot-mxs: bump to v2018.09Michael Heimpold2018-11-014-130/+72
| | | | | | | Also update the U-Boot BSP patch for I2SE Duckbill devices and remove upstreamed patch for LibreSSL support. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* grub2: fix regression caused by binutils-2.31.1Philip Prindeville2018-10-252-1/+76
| | | | | | | | | | | | | grub-efi no longer works: grub-mkimage: error: relocation 0x4 is not implemented yet. See: http://git.savannah.gnu.org/cgit/grub.git/commit/util?id=842c390469e2c2e10b5aa36700324cd3bde25875 Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>i [PKG_RELEASE increase]
* sunxi: add support for Orange Pi ZeroJulian Haupt2018-10-071-0/+7
| | | | Signed-off-by: Julian Haupt <julian.haupt@hauptmedia.de>
* uboot-lantiq: fix compile with modern host dtcThomas Nixon2018-10-071-0/+19
| | | | | | | | In dtc version 1.4.6 the macro names in header include guards changed, but the build relies on them matching in order to replace selected headers. This is a horrible hack to work around this. Signed-off-by: Thomas Nixon <tom@tomn.co.uk>
* uboot-envtools: adds r7800 uboot env supportAnsuel Smith2018-10-072-1/+4
| | | | | | This fix and adds support for r7800 uboot env Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* uboot-lantiq: fix compatibility with gcc7Martin Schiller2018-09-261-0/+142
| | | | | | | Backport u-boot commit 704f3acfcf55343043bbed01c5fb0a0094a68e8a to fix compatibility with gcc7. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* layerscape: add ls1012afrwy support and drop ls1012afrdmYangbo Lu2018-09-224-18/+18
| | | | | | | | | | | | | | | | | | | | | | | ls1012afrdm was no longer supported in NXP Layerscape SDK. Instead a new board ls1012afrwy was introduced in LSDK. This patch is to drop ls1012afrdm and add ls1012afrwy support. Since only 2MB NOR flash could be used, we just put u-boot and firmware on NOR flash, and put kernel/dtb/rootfs on SD card. The Layerscape FRWY-LS1012A board is an ultra-low-cost development platform for LS1012A Series Communication Processors built on Arm Cortex-A53. This tool refines the FRDM-LS1012A with more features for a better hands-on experience for IoT, edge computing, and various advanced embedded applications. Features include easy access to processor I/O, low-power operation, micro SD card storage, an M2 connector, a small form factor, and expansion board options via mikroBUS Click Module. The MicroBUS Module provides easy expansion via hundreds of powerful modules supporting sensors, actuators, memories, and displays. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add SD card boot supportYangbo Lu2018-09-225-1/+67
| | | | | | | | | NOR/QSPI Flash on Layerscape board only has limited 64MB memory size. Since some boards (ls1043ardb/ls1046ardb/ls1088ardb/ls1021atwr) could support SD card boot, we added SD boot support for them to put all things on SD card to meet large memory requirement. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add armv7 subtarget and ls1021atwr board supportYangbo Lu2018-09-222-1/+17
| | | | | | | | | | | | | | | | | | The NXP TWR-LS1021A module is a development system based on the QorIQ LS1021A processor. - This feature-rich, high-performance processor module can be used standalone or as part of an assembled Tower System development platform. - Incorporating dual Arm Cortex-A7 cores running up to 1 GHz, the TWR-LS1021A delivers an outstanding level of performance. - The TWR-LS1021A offers HDMI, SATA3 and USB3 connectors as well as a complete Linux software developer's package. - The module provides a comprehensive level of security that includes support for secure boot, Trust Architecture and tamper detection in both standby and active power modes, safeguarding the device from manufacture to deployment. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add u-boot environment support for OpenWrt bootYangbo Lu2018-09-228-1/+70
| | | | | | | This patch is to implement u-boot environment txt files to support OpenWrt boot for all layerscape devices. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update u-boot to LSDK-18.06Yangbo Lu2018-09-222-49/+71
| | | | | | | | | | | | | | The u-boot source code had been migrated to codeaurora for LSDK-18.06 release and the future release. This patch is to update u-boot to LSDK-18.06 for both uboot-layerscape and uboot-layerscape-armv8_32b packages. Besides, this patch also introduced some other changes. - Reworked uboot-layerscape makefile to make it more readable. - Define package in uboot-layerscape-armv8_32b for each board. - Fixed u-boot package selection in target image makefile. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: drop uboot-layerscape patchesYangbo Lu2018-09-226-320/+0
| | | | | | | | Dropped uboot-layerscape patches which were environemnt patches. We will make u-boot environment binaries with a txt file for all devices. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* sunxi: build image/uboot for the NanoPi NEO2Jasper Scholte2018-09-221-0/+9
| | | | | | | | The NanoPi NEO2 is a small Allwinner H5 based board available with different DRAM configurations. This board is very similar to the NanoPi NEO PLUS2 Signed-off-by: Jasper Scholte <NightNL@outlook.com>
* uboot-zynq: use a file to modify the default environmentLuis Araneda2018-09-102-0/+3
| | | | | | | | | Follow the strategy of other targets and create a default environment file, uEnv.txt, to configure the behavior of U-Boot. For now, use it to pass bootargs to the kernel Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* uboot-zynq: copy U-Boot images to STAGING_DIRLuis Araneda2018-09-101-0/+9
| | | | | | | | | | | Create a directory inside STAGING_DIR and copy U-Boot output images, so they can be used later when creating the sdcard image Additionally, like others targets, override the default install method to avoid copying the images to bin directory Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* uboot-zynq: automatically select the appropriate variantLuis Araneda2018-09-101-0/+5
| | | | | | | | Select the U-Boot variant automatically based on the current selected device, and hide the package from menuconfig Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* uboot-zynq: remove ZC706 boardLuis Araneda2018-09-101-4/+0
| | | | | | | The board was added when creating the target, but the corresponding device was never defined inside the target Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* imx6: use BUILD_DEVICES in uboot-imx6 for mx6cuboxiFelix Fietkau2018-09-051-0/+2
| | | | | | Fixes build with the default profile Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-imx6: fall back to MMC for SPL if boot mode is invalidFelix Fietkau2018-09-031-0/+26
| | | | | | Fixes boot on Hummingboard Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-imx6: remove obsolete patchFelix Fietkau2018-09-031-87/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-imx6: install images into STAGING_DIR_IMAGEFelix Fietkau2018-09-031-0/+7
| | | | | | Will be used by a new combined image for cubox Signed-off-by: Felix Fietkau <nbd@nbd.name>
* imx6: Initial support for SolidRun CuBox-i devices based on i.MX6 processors ↵Vladimir Vid2018-08-251-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (i1, i2, i2eX, and i4Pro). - Specifications - CuBox i1: - SoC: i.MX6 Solo - Cores: 1 - Memory Size: 512MB - GPU: GC880 - Wifi/Bluetooth: Optional - USB 2.0 ports: 2 - Ethernet: 10/100/1000 Mbps CuBox i2 | i2eX: - SoC: i.MX6 Dual Lite - Cores: 2 - Memory Size: 1GB - GPU: GC2000 - Wifi/Bluetooth: Optional - USB 2.0 ports: 2 - Ethernet: 10/100/1000 Mbps CuBox i4Pro | i4x4: - SoC: i.MX6 Quad - Cores: 4 - Memory Size: 2/4 GB - GPU: GC2000 - Wifi/Bluetooth: Build In - USB 2.0 ports: 2 - Ethernet: 10/100/1000 Mbps Built-in u-boot requires SPL (secondary program loader) to be present on the SD-card regardless of the image type which will be loaded. SPL is generated by the u-boot-mx6cuboxi package which is preselected by the target device and can be found in bin/u-boot-mx6cuboxi directory. Flashing the SPL: dd if=/dev/zero of=/dev/mmcblk0 bs=1M count=4 dd if=bin/targets/imx6/generic/u-boot-mx6cuboxi/SPL of=/dev/mmcblk0 bs=1K seek=1 Preparing the firmware on the SD-card: (echo o; echo n; echo p; echo 1; echo ''; echo ''; echo w) | fdisk /dev/mmcblk0 mkfs.ext4 /dev/mmcblk0p1 mount /dev/mmcblk0p1 /mnt tar -xzf bin/targets/imx6/generic/openwrt-imx6-device-cubox-i-rootfs.tar.gz -C /mnt/ mkdir -p /mnt/boot cp bin/targets/imx6/generic/{*-uImage,*.dtb,*.scr} /mnt/boot/ Generated u-boot.img needs to be placed on the first partition: cp bin/targets/imx6/generic/u-boot-mx6cuboxi/u-boot.img /mnt/ To boot from the SD card: Boot script which sets mmc/dtb parameters and boots the board is automatically sourced. If this does not work for any reason: mmc dev 0; load mmc 0:1 $scriptaddr boot/boot.scr; source $scriptaddr Currently imx6dl-cubox-i.dtb (Dual Lite) and imx6q-cubox-i.dtb (Quad) device trees are available. Tested on i4Pro, MMC, USB (+ HiD), HDMI and ethernet ports are working. Wireless and bluetooth are broken ATM. According to SolidRun forums, BCM4329/BCM4330 firmware is used which works fine on older kernels. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
* uboot-zynq: add support for the zybo z7 boardLuis Araneda2018-08-254-6/+612
| | | | | | | | Backport board support from the upcoming v2018.09 release, and add an additional patch to read the MAC address from flash memory Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* grub2: rebase patchesJo-Philipp Wich2018-08-231-8/+4
| | | | | | | | | Patch 300-CVE-2015-8370.patch was added without proper rebasing on the version used by OpenWrt, make it apply and refresh the patch to fix compilation. Fixes: 7e73e9128f ("grub2: Fix CVE-2015-8370") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* grub2: Fix CVE-2015-8370Rosen Penev2018-08-232-1/+45
| | | | | | | | | | | This CVE is a culmination of multiple integer overflow issues that cause multiple issues like Denial of Service and authentication bypass. More info: https://nvd.nist.gov/vuln/detail/CVE-2015-8370 Taken from Fedora. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* yamonenv: Remove dead URLsRosen Penev2018-08-221-2/+1
| | | | | | uscan errors on the URL as it is no longer available. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* fconfig: Remove dead URLsRosen Penev2018-08-221-2/+1
| | | | | | uscan errors on the URL as it is no longer available. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* apex: Remove dead URL.Rosen Penev2018-08-221-2/+1
| | | | | | | | uscan errors on the URL as it is no longer available. Also switched the download URL to HTTPS. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* uboot-zynq: update to 2018.07Luis Araneda2018-08-133-3/+46
| | | | Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* ath79: add support for OCEDO KoalaDavid Bauer2018-08-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the OCEDO Koala SOC: Qualcomm QCA9558 (Scorpion) RAM: 128MB FLASH: 16MiB WLAN1: QCA9558 2.4 GHz 802.11bgn 3x3 WLAN2: QCA9880 5 GHz 802.11nac 3x3 INPUT: RESET button LED: Power, LAN, WiFi 2.4, WiFi 5, SYS Serial: Header Next to Black metal shield Pinout is 3.3V - GND - TX - RX (Arrow Pad is 3.3V) The Serial setting is 115200-8-N-1. Tested and working: - Ethernet - 2.4 GHz WiFi - 5 GHz WiFi - TFTP boot from ramdisk image - Installation via ramdisk image - OpenWRT sysupgrade - Buttons - LEDs Installation seems to be possible only through booting an OpenWRT ramdisk image. Hold down the reset button while powering on the device. It will load a ramdisk image named 'koala-uImage-initramfs-lzma.bin' from 192.168.100.8. Note: depending on the present software, the device might also try to pull a file called 'koala-uimage-factory'. Only the name differs, it is still used as a ramdisk image. Wait for the ramdisk image to boot. OpenWRT can be written to the flash via sysupgrade or mtd. Due to the flip-flop bootloader which we not (yet) support, you need to set the partition the bootloader is selecting. It is possible from the initramfs image with > fw_setenv bootcmd run bootcmd_1 Afterwards you can reboot the device. Signed-off-by: David Bauer <mail@david-bauer.net>
* sunxi: Added support for Xunlong Orange Pi PC2Antonio Silverio2018-08-091-0/+9
| | | | | | | | | | | | | | | | CPU: H5 High Performance Quad-core 64-bit Cortex-A53 GPU: Mali450 OpenGL ES 2.0/1.1/1.0, OpenVG 1.1, EGL Memory: 1GB DDR3 (shared with GPU) Onboard Storage: TF card (Max. 32GB) / NOR flash(2MB) Onboard Network: 1000M/100M Ethernet RJ45 USB 2.0 Ports: Three USB 2.0 HOST, one USB 2.0 OTG, HOST mode role by default in DTS Buttons: Power Button(SW4) Debug TTL UART: ..DC-IN.. >[GND][RX][TX] ..HDMI.. Signed-off-by: Antonio Silverio <menion@gmail.com>
* uboot-envtools: add ath79 targetDavid Bauer2018-08-081-0/+26
| | | | | | | | This adds uci entries for all ath79 devices for which this already was the case on ar71xx. Additionally we add the OCEDO Koala as there was no support in OpenWRT yet. Signed-off-by: David Bauer <mail@david-bauer.net>
* kirkwood: add support for Iomega Storcenter ix2-200Ademar Arvati Filho2018-07-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Iomega Storcenter ix2-200 is a dual SATA NAS powered by a Marvell Kirkwood SoC clocked at 1GHz. It has 256MB of RAM and 32MB of flash memory, 3x USB 2.0 and 1x 1Gbit/s NIC Specification: - SoC: Marvell Kirkwood 88F6281 - CPU/Speed: 1000Mhz - Flash-Chip: Hynix NAND - Flash size: 32 MiB,erase size:16 KiB,page size:512,OOB size:16 - RAM: 256MB - LAN: 1x 1000 Mbps Ethernet - WiFi: none - 3x USB 2.0 - UART: for serial console Installation instructions - easy steps: 1. download factory.bin and copy into tftp server 2. access uboot environment with serial cable and run ``` setenv mainlineLinux yes setenv arcNumber 1682 setenv console 'console=ttyS0,115200n8' setenv mtdparts 'mtdparts=orion_nand:0x100000@0x000000(u-boot)ro,0x20000@0xA0000(u-boot environment)ro,0x300000@0x100000(kernel),0x1C00000@0x400000(ubi)' setenv bootargs_root 'root=' setenv bootcmd 'setenv bootargs ${console} ${mtdparts} ${bootargs_root}; nand read.e 0x800000 0x100000 0x300000; bootm 0x00800000' saveenv setenv serverip 192.168.1.1 setenv ipaddr 192.168.1.13 tftpboot 0x00800000 factory.bin nand erase 0x100000 $(filesize) nand write 0x00800000 0x100000 $(filesize) run bootcmd ``` 3. access openwrt by dhcp ip address assigned by your router (p.ex: 192.168.1.13) Installation steps nand bad blocks proof: 1. download initramfs-uImage and copy into usb ext2 partition ``` mkfs.ext2 -L ext2 /dev/sdh1 mount -t ext2 /dev/sdh1 /mnt cp initramfs-uImage /mnt/initramfs.bin umount /mnt ``` 2. access uboot environment with serial cable and run ``` setenv mainlineLinux yes setenv arcNumber 1682 setenv console 'console=ttyS0,115200n8' setenv mtdparts 'mtdparts=orion_nand:0x100000@0x000000(u-boot)ro,0x20000@0xA0000(u-boot environment)ro,0x300000@0x100000(kernel),0x1C00000@0x400000(ubi)' setenv bootargs_root 'root=' setenv bootcmd 'setenv bootargs ${console} ${mtdparts} ${bootargs_root}; nand read.e 0x800000 0x100000 0x300000; bootm 0x00800000' saveenv usb reset; ext2load usb 0:1 0x00800000 /initramfs.bin; bootm 0x00800000 ``` 3. log into openwrt and sysupgrade to install into flash ``` sysupgrade -n /tmp/sysupgrade.bin ``` 4. access openwrt by dhcp ip address assigned by your router (p.ex: 192.168.1.13) Signed-off-by: Ademar Arvati Filho <arvati@hotmail.com>
* omap: rename image for sysupgrade compatibilityLucian Cristian2018-07-301-5/+5
| | | | | | for sysupgrade to work we need to change the image name based on dts target name Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* uboot-envtools: add configuration for Traverse LS1043 boards.Mathew McBride2018-07-301-0/+25
| | | | Signed-off-by: Mathew McBride <matt@traverse.com.au>
* grub2: fix packed-not-aligned error on GCC 8Edi Turn2018-07-301-0/+71
| | | | | | Fix the compile error "packed-not-aligned" when using GCC 8. Signed-off-by: Edi Turn <yyxstter@gmail.com>
* uboot-imx: bump to 2018.03 which fixes the build issues with fdt64_t ↵Vladimir Vid2018-07-079-1636/+26
| | | | | | | | | | | redefinitions * change mx6qsabresd to mx6qsabres to match defconfig name * merge wanboard profiles since there is only one defconfig for the target device * move wanboard options from wandboard.h to defconfig * remove legacy patches Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
* uboot-kirkwood: fix malformed boot configurationAlberto Bursi2018-06-278-8/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With current uboot default configuration the bootloader will fail to start the OpenWrt firmware with the following error: ----- unexpected character 'b' at the end of partition Error initializing mtdparts! incorrect device type in ubi Partition ubi not found! Error, no UBI device/partition selected! Wrong Image Format for bootm command Error occured, error code = 112 ----- If the uboot configuration is examined with printenv I can see that mdtparts line (on a nsa310) is wrong: ----- mtdparts=mtdparts=orion_nand:0x0c0000(uboot), 0x80000(uboot_env),0x7ec0000(ubi)bootargs_root= ---- The "bootargs_root=" that was appended to it should not be there. Fix the issue by adding a \0 line terminator at the end of affected lines, mimicking what is also done by uboot upstream. This issue was detected and confirmed on a nsa310, nsa325 and a pogoplug v4, but it's not hardware-specific, so apply the same fix to other devices as well. Note that the issue is with the uboot's integrated boot configuration, which is not used unless the uboot configuration in flash is unavailable (erased or corrupted), which happens only on first time installation, or if the user deletes the uboot configuration when upgrading uboot. People just upgrading from an older uboot without erasing their previous uboot configuration stored in flash would not have noticed this issue. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* uboot-kirkwood: fix whitespacesAlberto Bursi2018-06-278-29/+29
| | | | | | remove whitespaces from the patches Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 03:50:32 +0000