ca7324134d
Ruckus R500 datasheet: https://webresources.ruckuswireless.com/datasheets/r500/ds-ruckus-r500.html Specifications: SoC: 720Mhz QCA9558 RAM: 256MB Storage: 64MB of FLASH (SPI NOR - S25FL512S) 1x AR8327 GB switch Ethernet: 1x1000M port #3 on AR8327, 1x1000M (802.3at POE), port #5 on AR8327 Wireless: QCA988X HW2.0 802.11ac AR9550 2.4GHz 802.11b/g/n 5x GPIO LED 1x GPIO Reset Button 1x DC Jack 12v 1x UART, 3.3v, 115200 1x TPM, SLB9645TT12 2x Beamforming antennas configured via 74LV164 MAC addresses: 1. art 0x807E | Factory bridged | f0:3e:90:XX:XX:80 | 2. art 0x66 | eth0 | f0:3e:90:XX:XX:83 | (port 5, cpu port 6) - PoE port 3. art 0x6c | eth1 | f0:3e:90:XX:XX:84 | (port 3, cpu port 0) - non PoE port Serial console: 115200-8-N-1 on internal H4 header. Pinout: H1 ----------- |1|x|3|4|5| ----------- Pin 1 is near the "H4" marking. 1 - RX x - no pin 3 - VCC (3.3V) 4 - GND 5 - TX JTAG: Connector H2, similar to MIPS eJTAG, standard, unpoulated. H9 ---------------------- |2 |4 |6 |8 |10|12|14| ---------------------- |1 |3 |5 |7 |9 |11|13| ---------------------- 3 - TDI 5 - TDO 7 - TMS 9 - TCK 2,4,6,8,10 - GND 14 - Vref 1,11,12,13 - Not connected I²C: connector H2, near power LED, unpopulated: ------ |1|2|3 ------ H2 1 - SCL 2 - SDA 3 - GND Installation: Serial Port/TFTP 1. Setup tftp server on the local network 2. Connect to UART with TTL 3. Interupt U-boot process with Ctrl-C 4. Setup appropriate ipaddr and serverip in setenv: - setenv ipaddr 192.168.1.1 - setenv serverip 192.168.1.2 5. On TFTP Server - copy openwrt-ath79-generic-ruckus_r500-initramfs-kernel.bin to /srv/tftp 6. On R500 boot into initrd image - tftpboot 0x81000000 openwrt-ath79-generic-ruckus_r500-initramfs-kernel.bin - bootm 0x81000000 7. On TFTP server - scp -O openwrt-ath79-generic-ruckus_r500-squashfs-sysupgrade.bin root@192.168.1.1:/tmp 8. Ensure the boot command is set before flashing the image: fw_setenv bootcmd 'bootm 0xbf1c0000' 9. On R500 - sysupgrade /tmp/openwrt-ath79-generic-ruckus_r500-squashfs-sysupgrade.bin 10. If not done in 8; set boot command from U-boot shell itself: - setenv bootcmd bootm 0xbf1c0000 - saveenv - reset This patch adapted from https://github.com/victhor393/openwrt-ruckus-r500/tree/ruckus-r500-master Signed-off-by: Damien Mascord <tusker@tusker.org> - Heavily refactored the device tree - Extended commit message - Documented onboad connectors - Refactored MAC and calibration data setups to use nvmem-layout - Made both network interfaces LAN ports and bridge them, this makes more sense for an access point and is consistent with the rest of Ruckus APs. - Enable lzma-loader for compressed initramfs - Enabled the optional internal USB port - Added missing LEDs and according pinctrl settings - Added reserved memory region used for bootloader communication - Added the bit-banged I²C bus and onboard TPM - Refactored boot scheme and flash layout to match earlier Ruckus devices and maximize usable space for user data. Quirks: - H7 is the physical presence switch for the SLB9645TT12 TPM. TODO: - Link state reporting on the Ethernet ports doesn't work and both ports report "up" due to limitation of swconfig ar8327 driver. With DSA conversion, this shall be rectified. - Locate 2nd shift register (U7) controlling beamforming antennas, probably on ath10k GPIOs which are currently unsupported in the driver. For this, there is a device tree node describing that - but explicitly disabled. - At the moment of adding support, there is an endianness bug in the TPM driver causing it to not detect the TPM module because of ID mismatch. Signed-off-by: Lech Perczak <lech.perczak@gmail.com> Link: https://github.com/openwrt/openwrt/pull/17550 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
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 -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo 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
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0