This does not work for me because the initial installation says to use a factory image and the Techdata page only lists a sysupgrade file.
I have a working serial console access
I can log in as root on the stock firmware
I can watch the boot messages of the Linux kernel
I can enter the ADAM2 bootloader and flash files onto the Fritz!Box.
Simply flashing the sysupgrade image fails as expected.
Extracting the sysupgrade tar archive and flashing the resulting kernel and root files to the corresponding devices also results in a failing boot (my notes say something like "kernel boots, but root device is not found", I could retry if a boot log is needed).
I can restore all the damage I did by flashing with the AVM recovery tool , so I am quite comfortable to flash wildly and just see what happens
I don't dare to touch to replace the boot loader by try and error, because recovering from that will be harder (I don't do JTAG yet).
So I am able to flash and I even have serial console access, but where do I go from here?
I think I have to replace the ADAM2 bootloader by uboot, but why and how and what next to install an image?
Are there any related systems from where I can adapt the steps I'll have to do?
https://wiki.openwrt.org/toh/avm/fritz.box.wlan.7360 contains more verbose information, how much of that applies to the 3370 is another question (there may be differences between spi-nor flash or nand flash).
#!/bin/sh
ftp -n 192.168.178.1<<EOT
user adam2 adam2
debug
bin
passive
quote MEDIA FLSH
put /"your path"/bin/lantiq/openwrt-lantiq-xrx200-FRITZ3370.eva.align.128k mtd1
put /"your path"/bin/lantiq/openwrt-lantiq-xrx200-FRITZ3370-jffs2-128k.image.eva mtd0
quit
EOT
seems to have kinda worked for MatrixCoder.
I was a little irritated by the notion to install uboot, but the files for the FB3370 distributed by lede suggest that.
The last OpenWRT release for this FB offers the files used above instead.
I found some time and tested the above mentioned patches. The file system/flash layout information seems to be wrong, hence the bootloop.
Here is a bootlog: https://pastebin.com/0ziQ0A9S
Not yet. Since I'm not a developer I have to do a lot by trial and error.
I can only guess that the (very limited) EVA bootloader doesn't check for ECC errors, that would explain all the errors like the one below, once mtd1 gets attached (that doesn't explain why the flashing of the kernel works, though). ubi0 error: ubi_io_read: error -77 (ECC error) while reading 64 bytes from PEB 0:512, read 64 bytes
Does anyone know how to build the filesystem image with --space-fixup? (explanation)
There's the CONFIG_TARGET_UBIFS_FREE_SPACE_FIXUP option in include/image.mk, which I have set in my .config, but is there any way to check if this gets applied to the produced eva images? A build with V=s doesn't reveal if this option was used.
#!/bin/sh
ftp -n 192.168.178.1<<EOT
user adam2 adam2
debug
bin
passive
quote MEDIA FLSH
put /"your path"/bin/lantiq/openwrt-lantiq-xrx200-FRITZ3370.eva.align.128k mtd1
put /"your path"/bin/lantiq/openwrt-lantiq-xrx200-FRITZ3370-jffs2-128k.image.eva mtd0
quit
EOT
Looks like the ECC-on-die patch got mainlined for Linux 4.14, this makes things easier:
start with a current git master and apply the most recent versions of mkresins FB3370 patches (do NOT use the ones I linked above, these patches are a moving target), build with kernel 4.14 and use "on-die" ECC mode:
I found the time to compile it and set it up Wifi and the switch including VLAN seem to work fine so far. I didn't test the DSL interface since I don't use DSL anymore.
Edit: Looks like a lot of network io performance was lost, caps at ~55 mbit/s.
Edit2: Today a few commits got pushed from a staging repo to the main repo which add support for the FB3370! link
You can enable kernel 4.14 on lantiq and test flowoffload, in my tests I go from ~80-85 MBit/s to 96 MBit/s on a BT Business Hub 5 type A (SMP enabled).
would you be willing to share some details how you proceeded?
Have you build the image yourself, or you uses latest 18.x. release from openwrt and loaded over WebGUI of FritzBox?
Sorry for stupid questions, just having a spare 3370, HW rev.5 with the UrLoader 2186 with 30 seconds limitation on adam2, so any hints, or help would be very appreciated! Tried it with 15.x, with 17, and 18.x. image, no luck. Would be amazing to have openwrt on that box.
Since commit 0b62fe5e OpenWrt can be installed using the eva/adam2 bootloader. Within the same HW revision 5 of the Fritz!Box 3370 different NAND flash chips are used and the correct image has to be chosen. Please read the detailed commit message before trying an install.