Adding OpenWrt support for Xiaomi AX3600 (Part 1)

thanks for the heads up, I was able to to it using tftpd method though so all good, and I know better not to use the webui now :slight_smile:

one issue I'm seeing is that with wifi I can reach the internet just fine, but not wired.

both ethernet and wifi ports are on the same bridge and get dhcp IPs but when opening even just https://1.1.1.1 it works via wireless but not wired... I can reach the http one though and see it redirecting to https... so I wonder if this is a packet size thing... but then why would it work on wireless?

2 Likes

btw, I heard from some guys, it is not so dangerous as it could e imagined to connect 3v3 USB-TTLs to 1v8 UARTs, and, (quoting) "it wil just be a bit more heated, but will still work".

Aren't they lie?

I don't need UART for now, but isn't the power coming from the router it self and your just connecting the tx/rx? or am I wrong?

That is incorrect, other have already killed their ax3600 by using 3.3V based usb2serial adapters. You might be lucky, once, but don't expect it to work and not end up in smoke signals.

A 1.8V compliant usb2serial device based on the FTDI FT232RL can be bought for around 10 USD/ EUR (slightly less if you're lucky), don't waste a >70 USD/ EUR device because of this.

I would also be rather careful. Of course, there may be SoCs that do not just blow up but this ultimately depends on the IO cell design and in particular the ESD protection diode used therein.

Anyway, such 1.8 volt capable (and 3.3 and 5 volt switchable) FTDI USB to serial TTL adapters can be had for less than 5 bucks on AX.

I ran some experiments while updating three AX3600 to the 29-Nov IPQ807x-5.10-backports. All units are accessible via WiFi only.

  • GUI sysupgrade - proceeded OK, but failed to update first time on unit A
    (i.e. stayed on old version - not softbricking or anything like that)
  • "wifi down; sysupgrade ..." worked OK first time once on unit A, then failed first time on unit B.
  • "wifi down; sleep 3; sysupgrade ..." worked OK first time on both unit B and C.

Not 100% conclusive, but a solid indication of what @kirdes pointed out. In the past I'd generally needed to repeat the GUI method 2-5 times before successfully updating.

Edit: @Gingernut, yes, I'm an idiot! Of course, the sysupgrade that was active during this experiment was that of the old/source running version of IPQ807x-5.10-backports, not the 29-Nov destination.

2 Likes

From what I've observed, and another user, from latest release GUI sysupgrade now works fine first time without the need for any other interaction.

1 Like

You also also can add two Si diodes (0.7V) in series (1.4V) to TX of the adapter so the voltage drops from 3.3 to about 1.9 volt.

@robimarko @Ansuel

Saw this commit over at codeaurora that adds the needed he_bss_color option and sets it to a random value on every radio bring up when AX is enabled.

https://source.codeaurora.org/quic/qsdk/oss/system/feeds/wlan-open/commit/mac80211/files/lib/netifd/wireless/mac80211.sh?h=NHSS.QSDK.11.5.0.5.r511&id=73b0402e558a52c15c9c6079c956079599736000

Gave it a whirl and seems to work as said.

Hi I wanna to ask mine Redmi AX6 brick before and today I tried to use FT232 to debrick but I found that when I boot, both Internet and System light is not up and also not get a reply from serial. Is that totally broken already ? Thanks

Not sure if any of that "capable" TTLs are realy useful, but I've already ordered this one: https://www.aliexpress.com/item/4000216010101.html
It should be ok, I hope, since it has 1v8 switch on board

2 Likes

I've same situation with my D2.
Most probably, there is dead flash.

In my case, I plan to unsolder it, reflash with original fw dump, and solder it back.
But D2 have SOP8-sized flash chip, so it it pretty possible.

Unlike that, I found AX3600 have unsolderable (at least in-home) flash chip.
Not sure about AX6, but as it is sibling to AX3600 model, I guess, there is same situation.
So, most probably you're done :man_shrugging:

3 Likes

Hi Robimarko: i installed your latest build and i like it very much. its very responsive and i wanted to install banip addon. But while installing it , some required dependency package is missing(kmod-ipt-ipset) i am not able to find this package anywhere on the internet for ax3600.

Can you tell me how and where i can download it and install it please?

Thanks in advance

At some point you will have to rebuild OpenWrt with this patchset yourself. These prebuilt snapshots are intended to assist development, to allow easy testing with a 'known-good' (recent-) base, but they can't replace OpenWrt as a whole. The minute you depend on additional kernel modules, you will have to build the necessary dependencies (as part of the whole image) yourself - or wait for official support.

please tell me which architecture atleast this ax3600 belongs to. i am not able to find ipq807x generic package of kmod-ipt-ipset... any lhelp to findout where i can get this file ?

Nowhere.

You need to build it yourself.

While the generic packages are aarch64_cortex-a53, kernel modules are not generic (ipq807x) and specific to this build of the day; OpenWrt doesn't cover ipq807x yet.

Does the prerelease in https://github.com/robimarko/openwrt/releases include fixes for AX ? I tried to read back but I'm a bit confused if that's supposed to be fixed or not, and I'm facing strange issues where most of my devices get DHCP fine but won't reach the internet.

It has nothing to do with distance because I can always connect fine on my laptop (macOS) and I've already tried without using AX, and I was never using 160, just 80...

I'm also experiencing the same in most my Ethernet connected devices, and some just start working from time to time, so it seems like I'm bumping into something else.

Are there any specific logs I can look into that might hint to the cause?

FWIW the device is using about 70% memory

You can look at your syslog to see if there is the same Ethernet port kernel panic I get.

@dchard Well, it seems that they figured out that keeping regulatory info in FW and BDF-s is not that smart (At least partially).
So they have added a file just containing regulatory info, so far only for QCA6390 and WCN6855 but I hope they do this for others as well.
https://patchwork.kernel.org/project/linux-wireless/patch/20211202083616.15406-1-quic_wgong@quicinc.com/

6 Likes