Port to AVM FRITZ!Box 3490

[andyboeh]

A quote from one of the posts that I asked you to read:

@andyboeh

The wasp_uploader needs to be included in the Lantiq target, the wasp_downloader needs to be included in the ath79 target. Then you need to pull ath_tgt_fw1.fw from an AVM firmware and place it into /opt/wasp along with the ath79 initramfs image. Then you can start the upload script with /opt/wasp/upload-wasp.sh. If everything goes well, you can trigger the script from /etc/rc.local.

Edit: To sum up:

• ath_tgt_fw1.fw needs to go to /opt/wasp, not to /lib/firmware
• ath_tgt_fw2.fw is not needed - this is replaced by the ath79 openwrt image
• to start WiFi, you somehow need to load the ath79 image. This is done by running /opt/wasp/upload-wasp.sh

What we didn't discuss yet is how you configure WiFi: The ath79 target has no access to the flash memory, thus configuration within this target is not persistent. To overcome this limitation, the Lantiq stores the configuration files in /opt/wasp/files. The WiFi configuration is thus in /opt/wasp/files/etc/config/wireless, the network in /opt/wasp/files/etc/config/network. If you change any configuration file, you need to delete the file /opt/wasp/config.tar.gz and re-run /opt/wasp/upload-wasp.sh.

The file /opt/wasp/config.tar.gz serves as an overlay that is extracted on the ath79 target to the root filesystem (-> configuration files). Additionally, it contains a script /opt/wasp/files/usr/bin/wasp_script that is executed during the ath79 boot. By default, it disables the DHCP server on the ath79 target which makes no sense.

By default, the ath79 target uses a static IP address of 192.168.1.2, it can be changed in /opt/wasp/files/etc/config/network.

Upon first start of /opt/wasp/upload-wasp.sh all configuration files are created! I suggest to start with the default configuration for the first time and then continue with configuring the device.

If you want to install additional packages on the ath79 target, you need to place all its files on the lantiq target into /opt/wasp/files and re-create the config.tar.gz file - as it will be extracted to the root folder without further checks, it can contain binaries as well.

Technically, the ath79 target has a boot hook that waits for the upload of the file config.tar.gz by the stage 2 firmware upload.

Edit 2: I pushed a fix for the wrong include in the dts file to my branch, thanks for reporting. I suppose mine built successfully because I didn't clean before running make.