Check Point V-80 (Quantum Spark 1590 Appliance) is an Appliance, based on Armada 8040 (88F8040). Specification: - SoC : Marvell Armada 8040 (88F8040) - RAM : DDR4 2 GiB (4x 512 MiB chip) - Flash : eMMC 4 GiB - Ethernet : 10x 10/100/1000 Mbps - LAN 1-8 : Marvell 88E6393X - WAN : Marvell 88E1512 - DMZ : Marvell 88E1512 (RJ-45/SFP combo) - LEDs/Keys (GPIO): 11x/1x - UART : "CONSOLE" port (USB 1.1 Type-C) - chip : Silicon Labs CP2102N - port : ttyS0 - settings : 115200bps 8n1 - HW Monitoring : 2x nuvoTon NCT7802Y - USB : USB 3.0 Type-A - Power : 12 VDC, 3.3 A - plug : DC Plug 2.5/5.5 mm (inner/outer) Flash instruction (common): 1. Boot V-81 normally 2. Login to the vendor CLI (default: admin/admin) and login to the Linux CLI by `expert` command 3. Update U-Boot environment variables by the following commands fw_setenv bootcmd_ow_usb 'usb start; load usb 0:1 ${loadaddr} boot.scr && source ${loadaddr}' fw_setenv bootcmd_ow_sd 'load mmc 0:1 ${loadaddr} boot.scr && source ${loadaddr}' fw_setenv bootcmd_ow_emmc 'run set_mmc_internal; mmc read ${loadaddr} ${prim_header_mmc_blk} 4 && source ${loadaddr}' fw_setenv bootcmd 'run bootcmd_ow_usb; run bootcmd_ow_sd; run bootcmd_ow_emmc; run bootcmd_part${activePartition};' Attention: don't forget single quatations of values to prevent expansion of variables 4. Turn off the device Flash instruction (USB-boot/SD-boot): 1. Extract and burn (squashfs|ext4)-sdcard.img.gz to USB storage or MicroSD card 2. Connect that storage to V-81 3. Turn on V-81 and it will be booted with OpenWrt in that USB storage Flash instruction (eMMC-boot): 1. Copy initramfs image, dtb and bootsctipt to the USB storage with renaming initramfs.bin -------> Image dtb -----------------> armada-8040-v-81.dtb bootscript (.scr) ---> boot.scr 2. Connect that storage to the USB 3.0 port on V-81 3. Turn on V-81 and it will be booted with OpenWrt initramfs image in that USB storage 4. Upload (squashfs|ext4)-sysupgrade.gz to V-81 5. Perform sysupgrade with the uploaded image 6. Wait ~100 seconds to complete flashing Reverting to stock firmware: 1. Turn on V-81 and interrupt booting by Ctrl + C 2. Select "4. Restore to Factory Defaults (local)" 3. Wait ~180 seconds to complete restoring and rebooting Notes: - The partition table in the internal eMMC has single partition, but "blkdevparts=" parameter will be passed from the bootloader and that definition will be used instead. - The port-side LED pairs of RJ-45/SFP ports on V-81 are switched by a GPIO pin of pin7 on &cp0_gpio2. (High(1): RJ-45, Low(0): SFP) This needs to be switched manually. - The MicroSD card slot is too unstable and the following messages are printed without "marvell,xenon-phy-slow-mode;" property. [ 97.060851] mmc0: error -84 whilst initialising SD card [ 97.137049] mmc0: error -84 whilst initialising SD card [ 97.214315] mmc0: error -84 whilst initialising SD card ... - There are no detailed information about maximum power consumption limit of the SFP port or optional DSL-SFP modules sold officially. But the power requirement of almost DSL-SFP modules are 3.3V/700mA, so set the maximum value of the SFP port to 2000 mW (Power Level III). - Do not insert a MicroSD card before turning of the device when OpenWrt installation. The stock firmware deletes all files in the first partition automatically, to use it as a storage for logs. MAC addresses: LAN: 00:1C:7F:xx:xx:FA (mmcblk1boot0, ethaddr (text)) WAN: 00:1C:7F:xx:xx:F9 (mmcblk1boot0, eth2addr (text)) DMZ: 00:1C:7F:xx:xx:FB (mmcblk1boot0, eth1addr (text)) Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> Link: https://github.com/openwrt/openwrt/pull/16904 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> |
||
---|---|---|
.devcontainer/ci-env | ||
.github | ||
.vscode | ||
config | ||
include | ||
LICENSES | ||
package | ||
scripts | ||
target | ||
toolchain | ||
tools | ||
.gitattributes | ||
.gitignore | ||
BSDmakefile | ||
Config.in | ||
COPYING | ||
feeds.conf.default | ||
Makefile | ||
README.md | ||
rules.mk |
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -a
to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -a
to install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfig
to select your preferred configuration for the toolchain, target system & firmware packages. -
Run
make
to build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg
. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrt
on oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-devel
on oftc.net.
License
OpenWrt is licensed under GPL-2.0