AVM FRITZ!Box 7520 / 7530

The FRITZ!Box 7520 and 7530 are AC1200 Dual-Band WiFi Routers (up to 1.2Gbps). They have 4x 1G LAN ports, a DSL/VDSL port up to 300Mb, and a USB 3.0 port.

The FRITZ!Box 7520 is the same hardware platform as the 7530, but its OEM software reduces the speed of 2x LAN ports and the USB port. Those limits do not apply to OpenWRT.

Product Page (English): https://en.avm.de/products/fritzbox/fritzbox-7530/technical-data/

Source Code: FRITZ!Box 7520 and FRITZ!Box 7530

root@fritzbox:~# cat /proc/cpuinfo

model name      : ARMv7 Processor rev 5 (v7l) - Quad Core CPU
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm

Hardware        : Generic DT based system
Revision        : 0000
Serial          : 0000000000000000

1. Grab the uboot for the Device from the u-boot-fritz7530 subdirectory. Place it in the same directory as the eva_ramboot.py script.
2. Assign yourself the IP address 192.168.178.10/24. Connect your Computer to one of the boxes LAN ports.
3. Connect Power to the Box. As soon as the LAN port of your computer shows link, load the U-Boot to the box using following command.
   

   > ./eva_ramboot.py --offset 0x85000000 192.168.178.1 uboot-fritz7530.bin

4. The U-Boot will now start. Now assign yourself the IP address 192.168.1.70/24. Copy the OpenWrt initramfs (!) image to a installed TFTP server root directory on our Computer and rename it to FRITZ7530.bin.
5. The Box will now put the file (a pull request every 5 seconds) and boot OpenWrt into RAM. This can take up to two minutes.
6. Copy the U-Boot and the OpenWrt sysupgrade (!) image to the Box using scp, like
   

scp /tmp/uboot-fritz7530.bin root@192.168.1.1:/tmp/
scp /tmp/avm_fritzbox-7530-squashfs-sysupgrade.bin  root@192.168.1.1:/tmp/

SSH into the Box and first write the Bootloader to both previous kernel partitions.

mtd write /tmp/uboot-fritz7530.bin uboot0
mtd write /tmp/uboot-fritz7530.bin uboot1

1. Remove the AVM filesystem partitions to make room for our kernel + rootfs + overlayfs.
   

   ubirmvol /dev/ubi0 --name=avm_filesys_0
   ubirmvol /dev/ubi0 --name=avm_filesys_1

2. Flash OpenWrt peristently using sysupgrade.
   

   sysupgrade -n /tmp/avm_fritzbox-7530-squashfs-sysupgrade.bin

dev:    size   erasesize  name
mtd0: 00080000 00020000 "SBL1"
mtd1: 00080000 00020000 "MIBIB"
mtd2: 00080000 00020000 "QSEE"
mtd3: 00040000 00020000 "CDT"
mtd4: 00080000 00020000 "QSEE_B"
mtd5: 00040000 00020000 "urlader0"
mtd6: 00040000 00020000 "urlader1"
mtd7: 00840000 00020000 "nand-tffs"
mtd8: 00400000 00020000 "uboot0"
mtd9: 00400000 00020000 "uboot1"
mtd10: 06d00000 00020000 "ubi"

See Installation

• Browse to http://192.168.1.1/cgi-bin/luci/mini/system/upgrade/ LuCI Upgrade URL
• Upload image file for sysupgrade to LuCI
• Wait for reboot

• Login as root via SSH on 192.168.1.1, then enter the following commands:

cd /tmp
wget https://downloads.openwrt.org/releases/21.02.0-rc2/targets/ipq40xx/generic/openwrt-21.02.0-rc2-ipq40xx-generic-avm_fritzbox-7530-squashfs-sysupgrade.bin
sysupgrade /tmp/openwrt-21.02.0-rc2-ipq40xx-generic-avm_fritzbox-7530-squashfs-sysupgrade.bin

If no Internet or WAN configured use WinScp''. and upload the file to /tmp

• 1st Login as root via WinScp on 192.168.1.1, then browse to /tmp and upload the openwrt-21.XX.XX-ipq40xx-generic-avm_fritzbox-7530-squashfs-sysupgrade.bin file
• 2nd Login as root via SSH on 192.168.1.1, then enter the following commands:

cd /tmp
sysupgrade /tmp/openwrt-21.02.0-rc2-ipq40xx-generic-avm_fritzbox-7530-squashfs-sysupgrade.bin

For debrick and / or factory image recovery use the AVM Recovery Tool.

The default network configuration as of 21.02.0-rc2

This device has one ethernet interface with 4 LAN ports. It does not have a fifth eth port for WAN like FB4040

eth0 is connected to the 4 LAN ports as well as the CPU. VLANs can be configured the standard OpenWrt way. The table below shows how they are displayed and numbered in LUCI.

A working VLAN setup is shown in the image below. This uses LAN 1 as a trunk port that receives tagged VLAN traffic from the network. LAN 2 and LAN 3 are members of VLAN 42 (used for the “Internal” network), LAN 4 is connected to VLAN 99 (used for a “Guest” network)

When configuring the VLANs it is very important to bind the LUCI network interfaces to the correct physical interfaces before applying the settings. Otherwise you will be locked out of the device and need to reflash it!

Go to LUCI→Network→Interfaces and check the “Physical Settings” for each one. Following the example above “Internal” would be connected to eth0.42 and “Guest” to eth0.99. When everything works as expected, corresponding WIFI networks can be added as a bridge here later on.

It has been mentioned in the forums that with this SoC, VLAN IDs 1 and 2 are treated specially by the hardware driver (https://forum.openwrt.org/t/vlans-on-ipq40xx-alternative-config-for-fritzbox-4040/41832/6) so it is probably best to avoid VLAN ID 1 and 2 if possible. This may change with updated hardware drivers.

→ hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

Front:
Insert photo of front of the casing

Back:
Insert photo of back of the casing

Backside label:
Insert photo of backside label

Note: This will void your warranty!

Main PCB:
Insert photo of PCB

→ port.serial general information about the serial port, serial port cable, etc.

How to connect to the Serial Port of this specific device:
Insert photo of PCB with markings for serial port

→ port.jtag general information about the JTAG port, JTAG cable, etc.

How to connect to the JTAG Port of this specific device:
Insert photo of PCB with markings for JTAG port

Space for additional notes, links to forum threads or other resources.

• …

How to add tags