AVM FRITZ!Box 7530

Under Construction!
This page is currently under construction. You can edit the article to help completing it.

Write a short, relevant description of the device. Include a technical overview, but avoid marketing buzzwords/useless stuff. Two to four sentences is about right. A picture is good, too. Edit the page to see how to add pictures.

FIXME Any text with a light background (like this one) provides instructions for creating the Details Page. When you have filled in correct/useful information (instead of any template that's there) remove the instructions, as well as the <WRAP> that encloses it.

AVM FritzBox 7530 AVM FritzBox 7530

FIXME

  1. This is an empty template that suggests the information that should be present on a well-constructed Device Page. This means, that you have to fill it with life and information.
  2. There are several “fixme” tags with text on a light background (like this text) throughout this template. As you fill in the page, remove those tags so that people can judge its completeness.
  3. When there are no more “fixme” tags left, delete this one too, along with the <WRAP> that encloses it.
  • Please include only model specific information, omit bla,bla and put everything generic into separate articles
  • If you have no time to write certain stuff, link to docs
  • base-system should lead the way, do not explain this again
  • DO NOT provide a complete howto here! Instead groom the general documentation.
ModelVersionSoCCPU MHzFlash MBRAM MBWLAN HardwareWLAN2.4WLAN5.0100M portsGbit portsModemUSB
FRITZ!Box 7530Qualcomm IPQ4019716128NAND256Qualcomm IPQ4019b/g/na/n/ac-4xDSL1x 3.0
  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"

FIXME The instructions below are for Broadcom devices and only serve as an example.
Remove / modify them if they do not apply to this particular device!

This section deals with

  • How you install OpenWrt from a device freshly opened
  • The steps required such as reset to factory defaults if the device has already been configured

Note: Reset router to factory defaults if it has been previously configured.

  • Browse to http://192.168.1.1/Upgrade.asp
  • Upload .bin file to router
  • Wait for it to reboot
  • Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed.

Specific values needed for tftp

FIXME Enter values for “FILL-IN” below

Bootloader tftp server IPv4 address FILL-IN
Bootloader MAC address (special) FILL-IN
Firmware tftp image Latest OpenWrt release (NOTE: Name must contain “tftp”)
TFTP transfer window FILL-IN seconds
TFTP window start approximately FILL-IN seconds after power on
TFTP client required IP address FILL-IN

generic.sysupgrade

FIXME These are generic instructions. Update with your router's specifics.

  • 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

If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line. There are two command line methods for upgrading:

  • sysupgrade
  • mtd

Note: It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.

sysupgrade

  • Login as root via SSH on 192.168.1.1, then enter the following commands:
cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
sysupgrade /tmp/xxx.abc

mtd

If sysupgrade does not support this router, use mtd.

  • Login as root via SSH on 192.168.1.1, then enter the following commands:
cd /tmp
wget http://downloads.openwrt.org/snapshots/trunk/XXX/xxx.abc
mtd write /tmp/xxx.abc linux && reboot

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

generic.debrick

Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

FIXME Please fill in real values for this device, then remove the EXAMPLEs

The default network configuration is:

Interface Name Description Default configuration
br-lan EXAMPLE LAN & WiFi EXAMPLE 192.168.1.1/24
vlan0 (eth0.0) EXAMPLE LAN ports (1 to 4) EXAMPLE None
vlan1 (eth0.1) EXAMPLE WAN port EXAMPLE DHCP
wl0 EXAMPLE WiFi EXAMPLE Disabled

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

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.

Switch Ports

Port Switch port
CPU (eth0) 0
LAN 1 1
LAN 2 2
LAN 3 3
LAN 4 4

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.

FIXME Please fill in real values for this device, then remove the EXAMPLEs

The AVM FRITZ!Box 7530 has the following buttons:

BUTTON Event
EXAMPLE Reset reset
EXAMPLE Secure Easy Setup ses
EXAMPLE No buttons at all. -
General
Brand AVM
Model FRITZ!Box 7530
Versions
Device Type WiFi Router
Availability Available 2019
Comments - general See also https://boxmatrix.info/wiki/FRITZ!Box_7530
OpenWrt Support
Supported Since Commit https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=95b0c07a618fe5fd93a26931152ced483bba143b
Supported Since Release 19.07.0
Supported Current Release 19.07.5
Unsupported
Hardware
Bootloader U-Boot
Target ipq40xx
System-On-Chip
CPU MHz 716
Flash MB 128NAND
RAM MB 256
Network
Ethernet 100M ports -
Ethernet Gbit ports 4
Switch Qualcomm Atheros QCA8075
Modem xDSL
VLAN Yes
Comments - network ports
Wireless
WLAN 2.4GHz b/g/n
WLAN 5.0GHz a/n/ac
WLAN Hardware Qualcomm IPQ4019
Detachable Antennas -
Comments - WLAN
Interfaces
USB ports 1x 3.0
SATA ports -
Serial Yes
JTAG ¿
Comments - USB & SATA ports
Misc
LED count 6
Button count 3
Power supply 12 VDC, 1.5 A
Links
Forum Topic URL
WikiDevi URL https://wikidevi.wi-cat.ru/AVM_FRITZ!Box_7530
OEM device homepage URL https://avm.de/produkte/fritzbox/fritzbox-7530/
Firmware OEM Stock URL https://avm.de/service/downloads/?product=fritzbox-7530
Firmware OpenWrt Install URL http://downloads.openwrt.org/releases/19.07.5/targets/ipq40xx/generic/openwrt-19.07.5-ipq40xx-generic-avm_fritzbox-7530-initramfs-fit-uImage.itb
Firmware OpenWrt Upgrade URL http://downloads.openwrt.org/releases/19.07.5/targets/ipq40xx/generic/openwrt-19.07.5-ipq40xx-generic-avm_fritzbox-7530-squashfs-sysupgrade.bin
Edit the underlying data View/Edit data

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!

FIXME Describe what needs to be done to open the device, e.g. remove rubber feet, adhesive labels, screws, …

  • To remove the cover and open the device, do a/b/c

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

Serial connection parameters
for AVM FRITZ!Box 7530
115200, 8N1

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

COPY HERE THE BOOTLOG WITH THE ORIGINAL FIRMWARE


COPY HERE THE BOOTLOG ONCE OPENWRT IS INSTALLED AND RUNNING


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

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2020/12/10 21:19
  • by kipper