Totolink A7100RU support

what are the chances to provide openwrt support for this router. the stock firmware is somehow limited but it has great coverage.

No one knows without technical specifications (used SOC, flash type and size, RAM size, wireless chipsets) - and even then there may be nasty surprises when it sits on your desk.

at least I haven't found technical data about within a couple of minutes searching.

I also found somewhere that it has MT7621A chip.

(from the link above)
2 dual core processor with 880MHz, 256MB memory and 16MB Flash. Gigabit WAN port, two LAN ports

While mt7621a should make it rather straight forward, this SOC is a bit low-end for 802.11ax and other tasks expected from a modern router.

Understood. Without going into specific brand, what chip should I aim at?

At this point, mt7622b+mt7915e - but there is a catch, some vendors do enable secure boot for mt7622, so not all devices will be easily flashable…

The Linksys E8450/ Belkin RT3200 does not (and therefore is supported), the TP-LINK TL-XDR3230 does (and it's unclear if it can be supported).


many thanks!

Let's say I would like to add this device on my own. Are there any tutorials that I can look into to start with?

so I managed to connect to this device using serial.
It turnes out that it runs on openwrt actually, but some old version (14.07)

I tried to follow the tutorial but for some reason I cannot get GPIO's

cat /sys/kernel/debug/gpio gives no output

Anyway - if I understand correctly , in order to provide proper support I need to create dts file, right?
Having access to whole filesystem and dmesg provides me enough information to achieve that ?

I managed to build an image based on similar router. I loaded it to RAM from uboot and got a question. With stock firmware I have this message in dmesg

[    2.468000] 0x000000000000-0x000001000000 : "ALL"
[    2.480000] 0x000000000000-0x000000030000 : "Bootloader"
[    2.492000] 0x000000030000-0x000000040000 : "Config"
[    2.500000] 0x000000040000-0x000000050000 : "Factory"
[    2.512000] 0x000000050000-0x000000f80000 : "firmware"
[    2.524000] 0x0000001d5aab-0x000000f80000 : "rootfs"
[    2.532000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[    2.560000] mtd: partition "rootfs_data" created automatically, ofs=0xc50000, len=0x330000
[    2.576000] 0x000000c50000-0x000000f80000 : "rootfs_data"
[    2.588000] 0x000000f80000-0x000001000000 : "custom-info"

so I translated that to dts file like this:

&spi0 {
        status = "okay";

        flash@0 {
                compatible = "jedec,spi-nor";
                reg = <0>;
                spi-max-frequency = <40000000>;

                partitions {
                        compatible = "fixed-partitions";
                        #address-cells = <1>;
                        #size-cells = <1>;

                        partition@0 {
                                label = "u-boot";
                                reg = <0x0 0x30000>;

                        partition@30000 {
                                label = "u-boot-env";
                                reg = <0x30000 0x40000>;

                        factory: partition@40000 {
                                label = "factory";
                                reg = <0x40000 0x50000>;

                        partition@50000 {
                                compatible = "denx,uimage";
                                label = "firmware";
                                reg = <0x50000 0xf80000>;
//                      partition@1d5aab {
//                              compatible = "";
//                              label = "rootfs";
//                              reg = <0x1d5aab 0xf8000>;

but after building image in dmesg I can see this:

[    5.534424] Creating 4 MTD partitions on "spi0.0":
[    5.543968] 0x000000000000-0x000000030000 : "u-boot"
[    5.554929] 0x000000030000-0x000000070000 : "u-boot-env"
[    5.566508] 0x000000040000-0x000000090000 : "factory"
[    5.577515] 0x000000050000-0x000000fd0000 : "firmware"
[    5.588837] 2 uimage-fw partitions found on MTD device firmware
[    5.600655] Creating 2 MTD partitions on "firmware":
[    5.610547] 0x000000000000-0x000000185aab : "kernel"
[    5.621380] 0x000000185aab-0x000000f80000 : "rootfs"
[    5.632218] mtd: device 5 (rootfs) set to be root filesystem
[    5.643595] 1 squashfs-split partitions found on MTD device rootfs
[    5.655921] 0x000000c00000-0x000000f80000 : "rootfs_data"

does this make sense? Sizes seems diffrent.