OpenWrt support for Xiaomi AX3000T

If the assembly supports Winbond, then after installation it lights up the LED on the router white... and if it does not support AN8855, then it turns the router into an unmanaged switch when connected to another router or an Internet provider cable. In your assembly, the LED lights up yellow and there is no movement on the Ethernet interfaces.

And you have a boot log via uart?

No. Yesterday I offered "writers" help in testing, but no one responded and I did not disassemble the router and rent UART. This topic is no longer for developers, but just a tech support thread with answers on which button to press.... I tried everything I found on this topic (firmware), but there is no special result. Maximum Wi-Fi with an unmanaged switch ))))

P.S.
That is, some have already done Winbond support correctly, the same ImmortalWrt even in the stable branch, but with AN8855 support - trouble.... I haven't found it anywhere yet, perhaps because it DOESN'T EXIST.

Hello, I use xiaomiax3000t router, but its firmware version is 1.0.84. After I downgrade to 1.0.47, I cannot connect to the PC through the lan port to access the uboot management page. When can openwrt be used normally with firmware version 1.0.84

Alex, in my build WiFi was not activated as in the official release)
But as I remember, there was the Immortal build with announced an8855 support, sorry haven't seen any feedback.

The author wrote that he has problems with this and is solving them. So it's a no-no there too. It's clear about the disabled Wi-Fi. I wrote how you can see whether the firmware has loaded or not. Yellow LED - it hasn't loaded and when the tested router is connected to another one, there is no link on the ports - it hasn't loaded, soft brick. White LED and there is a link on the ports - it has loaded and there is support - Winbond. But if there is a link and without connecting to another router, then there is already support for AN8855. But I haven't seen anything like that yet, unfortunately.

The firmware image "OpenWrt 23.05.5 (+new spi-nand W25N01KV)" works well on my Xiaomi AX3000T RD23 (Global edition) with a Winbond flash memory. Luci included. Thank you a lot for a building image!
P.S. FW installed via "XMiR-Patcher".

3 Likes

Thanks for your feedback

In my build: Yellow without blinking - started, Blue - wan interface connected. (As on the stock firmware)

Guys, if you have ax3000t with an8855, please take me your full dump of flash (just one dump is nessary;) ). Thanks.

Ser9ei, please explain to me - what's differets between "nmbm-" and "ubootmod-" images? Thank you.

So, it's happened, and the new Windbond NAND chip is already starting to appear on the RD23. Thanks for sharing!

Could you please post the output for the command dmesg | grep nand ?

Also, what was the stock firmware version on your rd23 when you received the router?

Xiaomi AX3000T (Global)
Version 1.0.31

root@OpenWrt:~# logread | grep spi
Mon Sep 16 20:47:49 2024 kern.info kernel: [ 0.858640] spi-nand spi0.0: Winbond SPI NAND was found.
Mon Sep 16 20:47:49 2024 kern.info kernel: [ 0.863954] spi-nand spi0.0: 128 MiB, block size: 128 KiB, page size: 2048, OOB size: 96

1 Like

Thank you.

So, someday the RD23 could appear with the AN8855 switch as well.

1 Like

In the RD03 (CH) revision only, I hope...

This is another version of OpenWrt build (not included in the official source) has only one diff - support single 112MB mtk ubi nmbm layout as in the ImmortalWrt.
For this version I use a different uboot (see 'mtk-uboot-112m-ubi-nmbm' folder by my link.) This is a uboot from mtk sdk and I reused git repository from mr. hanwckf (see details in readme.txt file there).
As for me it's the best choice - bigger firmware size then with stock uboot and mtk uboot has web interface for firmware/uboot upgrade or emergency firmware restore (no web interface in openwrt uboot-mod).

But also a issue - OpenWrt build for this layout will never be in the official repository. You will have to compile this build yourself or use ImmortalWrt.
I like this version and it's been stable on my router since Jan '24.

In the hanwckf’s repository is present multi-layout mtk uboot - user can switch from stock/onewrt-mod/immortal layout (but stock firmware may not support it - I haven't tested this point, only for OpenWrt with stock layout).

Ps
Winbond flash may be supported in this uboot, but has not been tested.

One for IoT devices.

Stock since here I don't have the need for port forwarding. From another site using the same build number but on a different router (Belkin RT3200) those work as expected.

Yes, both for IoT devices as for stuff like a TV, PC, etc.

One router but with roaming enabled and using usteer. So I decide, instead of the device, which band (2.4/5 GHz) to use.

Also, on my build, I have replaced dnsmasq with unbound and odhcpd.
So it is not a 1 to 1 but the setup here has it's own complexity :slight_smile:

Okay. But then there should be a link via Ethernet when connecting to another router or provider cable?
Of course, it's great that, unlike the OpenWrt developers, you are trying to make a normal indication, instead of random blinking and fading... What is all this correspondence for... If you are interested in making support for the AN8855 switch, then I will help as much as I can. If not, then I'm a pass(((
P.S.
It's just that support for the Winbond chip is available in the openWrt SNAPSHOT and the ImmortalWrt stock....

Wifi configuration breaking change!

I've just upgraded from snapshot (a recent from 23.05.4) to stable 23.05.5, and on first reboot my wifi was gone. Actually, /etc/config/wireless format has changed:

from: option path 'platform/soc/18000000.wifi'
to: option path 'platform/18000000.wifi'
(in the 2 sections config wifi-device)

You'd better know... or have an ethernet cable with you!

Led indication is only a sub-product and not the goal.
I have shared firmware only for people who don't want to be as QA for the snapshots build (=unstable dev build).

OK! Let's apologize to each other for wasting our time! But somehow there was no request from the opponent for logs of successful loading and the rest))).
Thanks for the work!