aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm63xx/image
Commit message (Collapse)AuthorAgeFilesLines
* treewide: use wpad-basic-wolfssl as defaultPetr Štetiar2020-08-201-5/+5
| | | | | | | | | | | | | | | In order to support SAE/WPA3-Personal in default images. Replace almost all occurencies of wpad-basic and wpad-mini with wpad-basic-wolfssl for consistency. Keep out ar71xx from the list as it won't be in the next release and would only make backports harder. Build-tested (build-bot settings): ath79: generic, ramips: mt7620/mt76x8/rt305x, lantiq: xrx200/xway, sunxi: a53 Signed-off-by: Petr Štetiar <ynezz@true.cz> [rebase, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: add support for the Sercomm H500-sDaniel González Cabanelas2020-06-071-1/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sercomm H500-s is an xDSL dual band wireless router based on Broadcom BCM63167 SoC. Hardware: SoC: Broadcom BCM63167 CPU: BMIPS4350 V8.0, 400 MHz, 2 cores Flash: NAND 128 MiB RAM: DDR3 128 MiB Ethernet: 4x 10/100/1000 Mbps Switch: BCM53134S Wireless: 802.11b/g/n: BCM435f (integrated) 802.11ac: Quantenna QT3740BC (onboard SoC) USB: 1x 2.0 LEDs/Buttons: 11x / 2x Flash instruction, web UI: 1. Reset to defaults using the reset button if the admin password is unknown 2. Login into the web UI as admin. Address: http://192.168.0.1 User: admin Password: VF-ESVodafone-H-500-s or l033i-h500s 3. Go to Settings -> Firmware Update, and select the Openwrt factory firmware 4. Update the firmware. 5. Wait until it finish, the device will reboot with Openwrt installed on the alternative image partitions keeping the stock firmware in the former. Notes: - The patch also adds support for the lowi version. Only the factory firmware is different. - The integrated Wifi in the Broadcom Soc isn't still supported. - The Quantenna 802.11ac wifi works ok, but needs to be configured with the Quantenna client application. It can't be configured with Luci nor any iw command since it's a separated subsystem linked via ethernet. - The BCM53134S external switch is managed via MDIO which isn't supported in this target. Therefore it will behave as a dumb switch. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* bcm63xx: image: support device-specific load addressÁlvaro Fernández Rojas2020-06-071-12/+10
| | | | | | | Some CFEs are located at the address currently used for relocation and lzma loader load address, so we need to provide a way to override it. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: don't add the CFE to the sercomm factoryDaniel González Cabanelas2020-06-071-12/+0
| | | | | | | | | | | | | | | There is no need to include the CFE bootloader in the Sercomm factory images. There might be a case when this could be useful: - We are running the stock firmware on the first Sercomm image - The second partition storing the botloader was erased (unlikely) Even in this case flashing an image without a bootlader is harmless. Don't include the bootloader in the factory image creation and rid of the risk of flashing factory images with an untested bootloader partition. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* bcm63xx: lzma-loader: allow bigger ramdisksÁlvaro Fernández Rojas2020-06-032-4/+6
| | | | | | | | | | | | | | | | Some (older) CFEs are loaded at 0x80401000 and ramdisks are loaded at 0x80010000, which means that ramdisk size limit is 0x3F1000 (almost 4M). Therefore, current ramdisks (~4MB) are overwritting CFE in these devices, which results in a crash. This commit changes the address where ramdisks are loaded to 0x80a00000, which is the same address where kernel is loaded when booting from the flash. Therefore, lzma-loader will now be loaded at 0x80a00000, but it will still decompress the kernel at 0x80010000. Tested with huawei,hg556a-b, which has its CFE loaded at 0x80401000. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: ad1018: remove cfe.bin image supportÁlvaro Fernández Rojas2020-06-032-27/+1
| | | | | | | | | | | | Apparently, Sercomm allows loading a BCM WFI image via CFE, but this image destroys "serial" and "protect" nand partitions, which is wrong. It will also set both bootflags to the same value, which causes booting issues with cferam (cferom will alternatively boot from cferam1 or cferam2 each time the device is rebooted). Now that OEM Sercomm images are supported it's time to remove this hacky cfe.bin image support. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: stop using legacy lzma for all devicesÁlvaro Fernández Rojas2020-06-031-54/+59
| | | | | | | | | BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vg-8050: switch to bcm-wfi-splitÁlvaro Fernández Rojas2020-06-021-1/+1
| | | | | | | Allows to keep a backup firmware in case active firmware is corrupted. Also fix hsspi address warning. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vr-3032u: switch to bcm-wfi-splitÁlvaro Fernández Rojas2020-06-021-1/+1
| | | | | | Allows to keep a backup firmware in case active firmware is corrupted. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: order devices alphabeticallyÁlvaro Fernández Rojas2020-06-021-10/+10
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: add CFE_WFI_VERSION values for each deviceÁlvaro Fernández Rojas2020-06-021-1/+5
| | | | | | CFE_WFI_VERSION should be defined per device instead of using a generic value. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: sercomm: switch to sercomm-load scriptÁlvaro Fernández Rojas2020-06-021-5/+6
| | | | | | | xxd is not a valid dependency and shouldn't be used. Fixes buildbot failure. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: ad1018: support Sercomm factory imagesÁlvaro Fernández Rojas2020-06-021-1/+11
| | | | | | | This images can be flashed from the official firmware, as opposed to CFE images, which can only be flashed from CFE and require opening the case. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: support Sercomm firmwaresÁlvaro Fernández Rojas2020-06-022-0/+67
| | | | | | Add support for Sercomm factory firmwares (AES 256 CBC encrypted). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm63xx: add support for ADB P.DG A4001N A-000-1A1-AXDaniele Castro2020-05-221-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ADB P.DG A4001N A-000-1A1-AX a.k.a. Telecom Italia ADSL2+ Wi-Fi N (AGPWI) has the same PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. OpenWrt's ADB P.DG A4001N image is made for the ADB P.DG A4001N A-000-1A1-AE. It has different LEDs configuration and flash size/layout w.r.t the ADB P.DG A4001N A-000-1A1-AX. Hardware: * Board ID: 96328avng * SoC: Broadcom BCM6328 * RAM DDR2-800: 32 Mbyte - winbond W9725G6KB-25 * Serial flash: 16 Mbyte - MXIC MX25L 12845EMI-10G * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43224/5 Wireless Network Adapter (rev 01) * LEDs: 2x Power, 2x ADSL, 2x Internet, 2x Wi-Fi, 2x Service * Buttons: 1x Reset, 1x WPS (named WiFi/LED) * UART: 1x TTL 115200n8, TX NC RX, on J5 connector (short R192 and R193) NC GND NC Installation via CFE: * Stock CFE has to be overwriten with one for 96328avng boards that can upload .bin images with no signature check (cfe-A4001N-V0000_96328avng.bin) * connect a serial port to the board * Stop the boot process after power on by pressing enter * set static IP 192.168.1.2 and subnet mask 255.255.255.0 * navigate to http://192.168.1.1/ * upload the OpenWrt image file Signed-off-by: Daniele Castro <danielecastro@hotmail.it> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: WIP: add Huawei HG253s v2 supportÁlvaro Fernández Rojas2020-05-211-0/+22
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: support CFE partition tagsÁlvaro Fernández Rojas2020-05-212-0/+22
| | | | | | | | Introduce support for generating JFFS2 CFE partition tags. This is used in NAND devices in order to verify the integrity of the JFFS2 partition. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: lzma-loader: rely on CHIP_ID for UART addressÁlvaro Fernández Rojas2020-05-205-83/+32
| | | | | | | | lzma-loader uart output wasn't working on BCM3380/BCM6362 because these SoCs have the same processor ID. Let's use CHIP_ID for establishing the UART base address. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: lzma-loader: remove unused definitionsÁlvaro Fernández Rojas2020-05-202-22/+1
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: add CVG834G CHIP_IDÁlvaro Fernández Rojas2020-05-201-1/+1
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: rename CFE_CHIP_ID to CHIP_IDÁlvaro Fernández Rojas2020-05-203-101/+101
| | | | | | Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add unmodded SERCOMM AD1018 supportÁlvaro Fernández Rojas2020-05-192-0/+43
| | | | | | | | | Until now only HW modded SPI flash version was supported. BCM6328 with 64M RAM and 128M NAND. More info: https://openwrt.org/toh/sercomm/ad1018 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add Comtrend VG-8050 supportÁlvaro Fernández Rojas2020-05-191-0/+17
| | | | | | | | BCM63169 with 128M RAM, 128M NAND and BCM53125 switch. Switch is connected by HSSPI to CS5. More info: https://openwrt.org/toh/comtrend/vg8050 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add NETGEAR DGND3700v2 supportÁlvaro Fernández Rojas2020-05-191-0/+17
| | | | | | | | BCM6362 with 64M RAM, 32M NAND and BCM53125 switch. Switch is connected by MMAP, which is currently unsupported (no VLANs). More info: https://openwrt.org/toh/netgear/dgnd3700v2 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add support for Comtrend VR-3032uÁlvaro Fernández Rojas2020-05-181-0/+18
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: smp: add NAND supportÁlvaro Fernández Rojas2020-05-182-0/+123
| | | | | | NAND controller is present on BCM6328, BCM6362, BCM6368 and BCM63268. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: remove unused definitionÁlvaro Fernández Rojas2020-05-141-2/+1
| | | | | | KERNEL_ENTRY isn't used by lzma-loader. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: loader-lzma: use default lzmaÁlvaro Fernández Rojas2020-05-122-10/+6
| | | | | | Specific CFE LZMA parameters aren't needed for LZMA Loader. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: rename LOADADDR to KERNEL_LOADADDRÁlvaro Fernández Rojas2020-05-121-9/+8
| | | | | | Also remove KERNEL_ENTRY, since it's the same as KERNEL_LOADADDR Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAMJonas Gorski2020-04-121-0/+11
| | | | | | | | | | | Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* treewide: gather DEVICE_VARS into one placeSungbo Eo2020-03-211-5/+6
| | | | | | | | | | | Place DEVICE_VARS assignments at the top of the file or above Device/Default to make them easier to find. For ramips, remove redundant values already present in parent file. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* brcm63xx: rename target to bcm63xxAdrian Schmutzler2020-02-1421-0/+3408
This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 04:36:17 +0000