aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu/image
Commit message (Collapse)AuthorAgeFilesLines
* mvebu: add support for WRT32X (venom)Michael Gray2018-05-141-0/+10
| | | | | | | | | | | | | | | | | | Linksys WRT32X (Venom) is identical in hardware to the WRT3200ACM with a different flash layout and boots zImage rather than uImage. Specification: - Marvell Armada 385 88F6820 (2x 1.8GHz) - 256MB of Flash - 512MB of RAM - 2.4GHz (bgn) and 5GHz (an+ac wave 2) - 4x 1Gbps LAN + 1x 1Gbps WAN - 1x USB 3.0 and 1x USB 2.0/eSATA (combo port) Flash instruction: Apply factory image via web-gui. Signed-off-by: Michael Gray <michael.gray@lantisproject.com>
* mvebu: add support for MACCHIATObin (cortex-a72)Damir Samardzic2018-03-313-0/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add initial support for Marvell MACCHIATObin, cortex-a72 based Marvell ARMADA 8040 Community board. Comes in two forms: Single Shot and Double Shot. Specifications: - Quad core Cortex-A72 (up to 2GHz) - DDR4 DIMM slot with optional ECC and single/dual chip select support - Dual 10GbE (1/2.5/10GbE) via copper or SFP 2.5GbE (1/2.5GbE) via SFP 1GbE via copper - SPI Flash - 3 X SATA 3.0 connectors - MicroSD connector - eMMC - PCI x4 3.0 slot - USB 2.0 Headers (Internal) - USB 3.0 connector - Console port (UART) over microUSB connector - 20-pin Connector for CPU JTAG debugger - 2 X UART Headers - 12V input via DC Jack - ATX type power connector - Form Factor: Mini-ITX (170 mm x 170 mm) More details at http://macchiatobin.net Booting from micro SD card: 1. reset U-Boot environment: env default -a saveenv 2. prepare U-Boot with boot script: setenv bootcmd "load mmc 1:1 0x4d00000 boot.scr; source 0x4d00000" saveenv or manually: setenv fdt_name armada-8040-mcbin.dtb setenv image_name Image setenv bootcmd 'mmc dev 1; ext4load mmc 1:1 $kernel_addr $image_name;ext4load mmc 1:1 $fdt_addr $fdt_name;setenv bootargs $console root=/dev/mmcblk1p2 rw rootwait; booti $kernel_addr - $fdt_addr' saveenv Signed-off-by: Damir Samardzic <damir.samardzic@sartura.hr>
* mvebu: clearfog-pro: set new DTB name in boot-scriptJosua Mayer2018-03-311-0/+4
| | | | | | | The DTB for Clearfog Pro has been renamed in mainline. However U-Boot hasn't picked up that change yet :(, so we need to hardcode it for now. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: unset uboot build by defaultMathias Kresin2018-03-152-1/+2
| | | | | | | | Initialise the UBOOT variable by default. Otherwise it will be unintended inherit to following images if set and causes an uboot build where not required. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: new subtarget cortex A53Tomasz Maciej Nowak2018-03-103-2/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces new subtarget for Marvell EBU Armada Cortex A53 processor based devices. The first device is Globalscale ESPRESSObin. Some hardware specs: SoC: Marvell Armada 3700LP (88F3720) dual core ARM Cortex A53 processor up to 1.2GHz RAM: 512MB, 1GB or 2GB DDR3 Storage: SATA interface µSD card slot with footprint for an optional 4GB EMMC 4MB SPI NOR flash for bootloader Ethernet: Topaz Networking Switch (88E6341) with 3x GbE ports Connectors: USB 3.0 USB 2.0 µUSB port connected to PL2303SA (USB to serial bridge controller) for UART access Expansion: 2x 46-pin GPIO headers for accessories and shields with I2C, GPIOs, PWM, UART, SPI, MMC, etc MiniPCIe slot Misc: Reset button, JTAG interface Currently booting only from µSD card is supported. The boards depending on date of dispatch can come with various U-Boot versions. For the newest version 2017.03-armada-17.10 no manual intervention should be needed to boot OpenWrt image. For the older ones it's necessary to modify default U-Boot environment: 1. Interrupt boot process to run U-Boot command line, 2. Run following commands: (for version 2017.03-armada-17.06 and 2017.03-armada-17.08) setenv bootcmd "load mmc 0:1 0x4d00000 boot.scr; source 0x4d00000" saveenv (for version 2015.01-armada-17.02 and 2015.01-armada-17.04) setenv bootargs "console=ttyMV0,115200 root=/dev/mmcblk0p2 rw rootwait" setenv bootcmd "ext4load mmc 0:1 ${fdt_addr} armada-3720-espressobin.dtb; ext4load mmc 0:1 ${kernel_addr} Image; booti ${kernel_addr} - ${fdt_addr}" saveenv 3. Poweroff, insert SD card with OpenWrt image, boot and enjoy. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: Add subtarget for Cortex A9 buildHauke Mehrtens2018-03-102-153/+166
| | | | | | This is in preparation for adding a subtarget for the Cortex A53 later. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: add support for Turris OmniaRyan Mounce2018-03-101-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds support for the Turris Omnia and builds an eMMC sysupgrade image in the same format as the SolidRun ClearFog. An initramfs image in the simple yet Omnia-specific 'medkit' image format is also built in order to ease the initial flashing process. Notable hardware support omissions are support for switching between SFP cage and copper PHY, and RGB LED control. Due to a current limitation of DSA, only 1/2 CPU switch uplinks are used. Specifications: - Marvell Armada 385 1.6GHz dual-core ARMv7 CPU - 1GB DDR3 RAM - 8GB eMMC Flash - 5x Gigabit LAN via Marvell 88E6176 Switch (2x RGMII CPU ports) - 1x switchable RJ45 (88E1514 PHY) / SFP SGMII WAN - 2x USB 3.0 - 12x dimmable RGB LEDs controlled by independent MCU - 3x Mini PCIe slots - Optional Compex WLE200N2 Mini PCIe AR9287 2x2 802.11b/g/n (2.4GHz) - Optional Compex WLE900VX Mini PCIe QCA9880 3x3 802.11ac (2.4 / 5GHz) - Optional Quectel EC20 Mini PCIe LTE modem Flash instructions: If the U-Boot environment has been modified previously (likely manually via serial console), first use serial to reset the default environment. => env default -a => saveenv Method 1 - USB 'medkit' image w/o serial - Copy openwrt-mvebu-turris-omnia-sysupgrade.img.gz and omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz to the root of a USB flash drive formatted with FAT32 / ext2/3/4 / btrfs / XFS. Note that the medkit MUST be named omnia-medkit*.tar.gz - Disconnect other USB devices from the Omnia and connect the flash drive to either USB port. - Power on the Omnia and hold down the rear reset button until 4 LEDs are illuminated, then release. - Wait approximately 2 minutes for the Turris Omnia to flash itself with the temporary image, during which LEDs will change multiple times. - Connect a computer to a LAN port of the Turris Omnia with a DHCP client - (if necessary) ssh-keygen -R 192.168.1.1 - ssh root@192.168.1.1 $ mount /dev/sda1 /mnt $ sysupgrade /mnt/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself and you can remove the flash drive. Method 2 - TFTP w/ serial - Extract omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz and copy dtb + zImage to your TFTP server (rename if desired) - Connect Turris Omnia WAN port to DHCP-enabled network with TFTP server - Connect serial console and interrupt U-Boot => dhcp => setenv serverip <tftp_server_ip_here> => tftpboot 0x01000000 zImage => tftpboot 0x02000000 dtb => bootz 0x01000000 - 0x02000000 - OpenWrt will now boot from ramdisk - Download openwrt-mvebu-turris-omnia-sysupgrade.img.gz to /tmp/ $ sysupgrade /tmp/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* mvebu: unify boot.scr creationTomasz Maciej Nowak2018-03-023-13/+8
| | | | | | | Unify boot.scr generation so Makefile for device image generation won't grow without a reason. Also make boot-scr step optional. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: make sdcard bootloader option configurableTomasz Maciej Nowak2018-03-022-10/+21
| | | | | | | Remove the necessity for boot loader from SD card image creation process and make it configurable. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: fix partition type and signature for sdcardTomasz Maciej Nowak2018-03-022-4/+7
| | | | | | | | | | | Previously the partition signature was assigned from provided type. Now both are corrected wherein signature is always generated from SOURCE_DATE_EPOCH. With that the root file system can be identified by PARTUUID string, without relying on static declaration of device node. This commit also does some cosmetics, removing trailing whitespace and replacing spaces with tab. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: remove redefinition of image name for clearfogTomasz Maciej Nowak2018-03-021-2/+0
| | | | | | | | The IMAGE_NAME redefinition causes overwriting of generated SD card image when multiple root file system types are selected. In result only single SD card image is generated. This commit fixes this behaviour. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: clearfog: use partition uuid for root= bootargJosua Mayer2018-03-022-12/+14
| | | | | | | | | | | U-Boot already knows where it found the boot.scr, and figuring out the partition UUID becomes trivial at this point. This change allows booting OpenWrt from whatever storage it has been flashed to: SD card, eMMC, USB disk or SATA disk. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> [replace lede with openwrt, redact commit message] Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mwlwifi: add and use individual firmware packagesJohnny S. Lee2018-02-261-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | As each mvebu device only uses one of the firmwares provided by mwlwifi package, it makes sense to put them in separate packages and only install the one that is needed. Current mwlwifi version's firmware sizes and usages by devices: 88W8864.bin 118776 caiman, mamba, cobra, shelby 88W8897.bin 489932 (none) 88W8964.bin 449420 rango Changes by this commit: * indicate in title that mwlwifi also is driver for 88W8897 and 88W8964 * remove mwlwifi package's firmware installation rules * add 3 new individual firmware packages (all depends on kmod-mwlwifi): - mwlwifi-firmware-88w8864 - mwlwifi-firmware-88w8897 - mwlwifi-firmware-88w8964 * add firmware package to mvebu devices' DEVICE_PACKAGES accordingly Signed-off-by: Johnny S. Lee <_@jsl.io> [Add the used FW files to the PACKAGES of default image] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: fix sysupgrade from 17.04 for clearfog proJonas Gorski2018-02-111-0/+1
| | | | | | | | | When clearfog was renamed to clearfog pro, it broke sysupgrade from 17.04 as the new images now get rejected as incompatible. Fix this by adding the legacy boardname to the compatible devices. Fixes: ec4a8c6dee81 ("mvebu: ClearFog renamed upstream to ClearFog Pro") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* treewide: add only one device when appending to TARGET_DEVICESLuis Araneda2017-12-121-5/+19
| | | | | | | | | This will avoid some conflicts when doing a git rebase or merge, specially when adding support to a new device. Signed-off-by: Luis Araneda <luaraneda@gmail.com> [drop brcm47xx changes which rename the images] Signed-off-by: Mathias Kresin <dev@kresin.me>
* merge: targets: update image generation and targetsZoltan HERPAI2017-12-082-4/+4
| | | | Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* mvebu: clean up ClearFog Base package selectionRyan Mounce2017-10-151-6/+2
| | | | | | | | | | It is unclear why so many packages are selected for ClearFog Base compared to its big brother, and there is no reason to not append metadata for Base. Tidy this up as the only hardware difference between Base/Pro is the presence of a switch and a different board name / device tree. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* mvebu: WRT3200ACM: add bluetooth moduleHenryk Heisig2017-09-171-1/+1
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* mvebu: clearfog: include DTB for all variants in imageJosua Mayer2017-05-301-3/+5
| | | | | | | Installing all armada-388-clearfog-* DTBs in the same sdcard image, it now becomes much easier to swap sdcards between different device variants. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: update boot-script to use generic variablesJosua Mayer2017-05-302-10/+44
| | | | | | | | | | | U-Boot provides standard variables for load addresses, and filesystem-agnostic load-commands. Furthermore thanks to distro-boot, the device and partition from which the system boots is known. The new boot-script makes use of all this information. Tested on the only board that uses this boot-script: Clearfog Pro Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: add ClearFog Base supportMarko Ratkaj2017-05-142-0/+27
| | | | | | | | | | Add support for SolidRun ClearFog Base board. The base model is a smaller version of ClearFog Pro without the DSA switch, replacing it with a second copper gigabit port, and only one PCIe socket. Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
* mvebu: ClearFog renamed upstream to ClearFog ProMarko Ratkaj2017-05-142-7/+7
| | | | | | The conventional model is now known as the "Clearfog Pro" Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
* mvebu: wrt3200acm enable SDIO interfaceHenryk Heisig2017-03-111-0/+1
| | | | | | add mwifiex-sdio package to wrt3200acm Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* mvebu: append metadata to clearfog sd card imagesJonas Gorski2017-02-131-1/+1
| | | | | | | | | | | | | | Fixes the following issue: root@LEDE:/# sysupgrade /tmp/lede-mvebu-armada-388-clearfog-sdcard.img.gz Saving metaconfig... Image metadata not found Use sysupgrade -F to override this check when downgrading or flashing to vendor firmware Image check 'fwtool_check_image' failed. root@LEDE:/# Acked-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* mvebu: put u-boot images into image staging directoryJo-Philipp Wich2017-01-271-1/+1
| | | | | | | | | | | | Do not put the u-boot images into the kernel build directory as this directory might get removed after kernel updates while the u-boot packages InstallDev recipe is not getting re-executed because it is still considered current, leading to image build failures later on due to missing u-boot images. To ensure that built bootloader images persist over kernel version updates in the buildroot, put them into the new STAGING_DIR_IMAGE directory. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* uboot-mvebu: switch to u-boot.mkFelix Fietkau2017-01-241-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: remove the clearfog-bundleFelix Fietkau2017-01-131-13/+1
| | | | | | It is obsoleted by proper SD card image support Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: fix image validation errorMathias Kresin2016-12-041-2/+2
| | | | | | | | The name from the Device define will be used in the metadata. Due to typo/different spelling, this name might not match the one exported in /lib/mvebu.sh. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: fix typo in image metadata supportMathias Kresin2016-11-271-2/+2
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: use image metadata for firmware validationFelix Fietkau2016-11-241-1/+4
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add support for the Linksys WRT3200ACM (Rango)Imre Kaloz2016-10-241-1/+9
| | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mvebu: add sysupgrade support for clearfogJonas Gorski2016-09-261-1/+1
| | | | | | | | Add and enable sysupgrade support for clearfog boards, based on how the brcm2708 target does it. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add switch node to clearfogJonas Gorski2016-09-261-1/+1
| | | | | | | | Add a switch node to clearfog to probe and initialize it on Clearfog Pro. This make the switch work and allows using all six switch ports. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: make hidden and be m for clearfog to fix IB failing to add itJonas Gorski2016-09-261-1/+1
| | | | | | | | | | | | | Uboot-mvebu isn't a real package, which will break the image builder when it tries to install it during the packing step. Instead of cleafog selecting it through its default packages, make it default to m if the clearfog profile is selected. This will ensure it is always build, but never added to the rootfs. This fixes creating images for clearfog with IB. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* uboot-mvebu: also install into KDIR to ensure it packaged in IBJonas Gorski2016-09-261-1/+1
| | | | | | | | The clearfog image requires u-boot, so package it into KDIR to make sure it is available in imageBuilder. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* image: remove padding parameter from append-kernel/append-rootfsMathias Kresin2016-09-131-2/+2
| | | | | | | | | | | 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>
* image: add KERNEL_SIZE to the default device varsMathias Kresin2016-09-131-2/+0
| | | | | This reverts commit ec37a565878fd79d4127cbb843c17ce3b8dc97c0 and fixes the underlying issue.
* build: drop UBI EOF marker from images by defaultFelix Fietkau2016-09-121-0/+1
| | | | | | | | Only add them where they are actually required. Should help with compatibility issues with stock U-Boot images that access UBI Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: fix OpenBlocks AX3 imageMathias Kresin2016-09-111-1/+1
| | | | | | | | The KERNEL_SIZE variable is unset and no padding is applied. This looks like a typo to me since the ubinized image need to be aligned to the flash blocksize. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: use ext4/f2fs overlay filesystem for solidrun clearfogFelix Fietkau2016-09-102-14/+11
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: enable ext4, f2fs and loop device supportFelix Fietkau2016-09-101-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image: use k as unit suffix for blocksizeMathias Kresin2016-09-041-4/+4
| | | | | | | 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>
* mvebu: use ptgen instead of fdisk to make the clearfog image script more ↵Felix Fietkau2016-09-021-55/+17
| | | | | | portable Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add sdcard image creation scriptJosua Mayer2016-09-023-2/+153
| | | | | | | | | | | | | | | | Added gen_mvebu_sdcard_img.sh to facilitate creating an fixed-size sdcard image, adding the bootloader and populating it with actual data. Added the required rules for creating a 4GB sdcard image according to this layout: p0: boot (fat32) p1: rootfs (squashfs) p2: rootfs_data (ext4) This should be generic to any mvebu boards that can boot from block storage. Added the new sdcard image to the Clearfog image profile. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [cleanup]
* mvebu: clearfog: require uboot-mvebu-clearfogJosua Mayer2016-09-021-0/+1
| | | | | | | | | The u-boot variant for the clearfog is provided by the uboot-mvebu-clearfog, and not by the generic uboot-mvebu packae. Make sure the clearfog variant is selected when building for it. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: rework ClearFog bundle.tar.gz generationJo-Philipp Wich2016-08-141-12/+6
| | | | | | | Instead of introducing a fake filesystem type, move the tar generation step directly into the image build step. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mvebu: add ClearFog .tar.gz bundleJo-Philipp Wich2016-08-131-0/+26
| | | | | | | | | | The previous image building code rework removed the rootfs.tar.gz with embedded kernel and dtb build artifact which is required to build suitable SD images. Reintroduce a .tar.gz artifact locally which embeds kernel and dtb, similar to how the old code handled it. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* build: rename sysupgrade-nand to sysupgrade-tarJo-Philipp Wich2016-07-291-1/+1
| | | | | | | Now that the "sysupgrade-nand" step is used by non-NAND targets as well, rename it to "sysupgrade-tar" to make it more generic. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mvebu: limit image builds to profile selectionFelix Fietkau2016-07-261-0/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: switch to the new image build codeFelix Fietkau2016-07-211-229/+127
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 12:49:05 +0000