Support for WavLink WL-WN573HX3

I'm wondering if the Wavlink WL-WN573HX3 will be supported ?
It is a faster wifi wise version of the WavLink WL-WN573HX1
It would be really great if the WL-WN573HX3 is in the process of getting support

I hunted about to see if i can findout what chipsets are used in both, I have yet to find anything about either of them.

HX1 is supposed to be MT - https://techinfodepot.shoutwiki.com/wiki/List_of_802.11ax_Hardware

The WL-WN573HX1 still isn't supported officially. It is in the Snapshots, but no official release. So I wouldn't hold your breath for the HX3.

How did you find HX1 over there? Browser find function doesn't show any match for either "wavlink", "hx1" or "hx3".

Also since HX1 is now supported with 24.10, any hope for HX3? Is the hardware at all similar?

If you got one, you tell us...

I have one. How to get the information? Only possible by opening the hardware and via serial console?

if you want to add it to openwrt, it'll be the only way anyway.

I will check it next week when have some vacation. Hopefully, I don't fall off the roof when I take down the AP from the chimney ... :rofl:

1 Like

I have taken it down today and opened. Everywhere screws instead of glue :slight_smile:

I have some photos to share. Because I am new, I cannot embed the photos in this post.

Find the photos here: WN573HX3

I see the serial console pins and tomorrow I will connect via serial console. Because I am familiar with building ESP32 / Arduino IoT, this should be hopefully an easy task for me.

What are the other pins (4G reset/GND/DP/DM/5v)?

Any good advises "what to respect" when connecting?

First time of doing this with a router/access point and the box is brand new :rofl:

Got the first boot capture and some infos from the u-boot console:
First boot capture:


F0: 102B 0000
FA: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 2400 0041 [0000]
G0: 1190 0000
EC: 0000 0000 [0000]
T0: 0000 022A [010F]
Jump to BL

NOTICE:  BL2: v2.7(release):292bca1-dirty
NOTICE:  BL2: Built : 02:04:54, Jul 12 2023
NOTICE:  WDT: disabled
NOTICE:  DDR3 1866MHZ
NOTICE:  EMI: Using DDR3 settings

dump toprgu registers data: 
1001c000 | 00000000 0000ffe0 00000000 00000000
1001c010 | 00000fff 00000000 00f00000 00000000
1001c020 | 00000000 00000000 00000000 00000000
1001c030 | 003c0003 003c0003 00000000 00000000
1001c040 | 00000000 00000000 00000000 00000000
1001c050 | 00000000 00000000 00000000 00000000
1001c060 | 00000000 00000000 00000000 00000000
1001c070 | 00000000 00000000 00000000 00000000
1001c080 | 00000000 00000000 00000000 00000000

dump drm registers data: 
1001d000 | 00000000 00000000 00000000 00000000
1001d010 | 00000000 00000000 00000000 00000000
1001d020 | 00000000 00000000 00000000 00000000
1001d030 | 00a083f1 000003ff 00100000 00000000
1001d040 | 00000000 00000000 00020303 000000ff
1001d050 | 00000000 00000000 00000000 00000000
1001d060 | 00000002 00000000 00000000 00000000
drm: 500 = 0x8 
[DDR Reserve] ddr reserve mode not be enabled yet
DDR RESERVE Success 0
[EMI] ComboMCP not ready, using default setting
BYTE_swap:0 
BYTE_swap:0 
Window Sum 632, worse bit 6, min window 76
Window Sum 640, worse bit 8, min window 80
Window Sum 504, worse bit 0, min window 62
Window Sum 498, worse bit 8, min window 60
Window Sum 508, worse bit 1, min window 62
Window Sum 500, worse bit 8, min window 60
Window Sum 516, worse bit 1, min window 62
Window Sum 508, worse bit 10, min window 60
Window Sum 522, worse bit 1, min window 62
Window Sum 518, worse bit 8, min window 62
Window Sum 526, worse bit 0, min window 64
Window Sum 528, worse bit 0, min window 64
Window Sum 522, worse bit 8, min window 62
Window Sum 524, worse bit 8, min window 62
NOTICE:  EMI: Detected DRAM size: 256MB
NOTICE:  EMI: complex R/W mem test passed
NOTICE:  CPU: MT7981 (1298MHz)
NOTICE:  BL2: Booting BL31
NOTICE:  BL31: v2.7(release):292bca1-dirty
NOTICE:  BL31: Built : 02:04:56, Jul 12 2023
NOTICE:  Hello BL31!!!


U-Boot 2022.07-rc3-ga7d4f1f1-dirty (Jul 12 2023 - 02:04:02 +0000)

CPU:   MediaTek MT7981
Model: mt7981-rfb
DRAM:  256 MiB
Core:  34 devices, 13 uclasses, devicetree: embed
Loading Environment from nowhere... OK
In:    serial@11002000
Out:   serial@11002000
Err:   serial@11002000
Net:   
Warning: ethernet@15100000 (eth0) using random MAC address - 0e:b1:cd:6c:b6:6e
eth0: ethernet@15100000
UBOOT WN573HX3
gpio: pin 9 (gpio 9) value is 1
gpio: pin 13 (gpio 13) value is 0
ethernet@15100000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
do_winstar_upgrade lookup of <NULL> failed, check setup
*** U-Boot Boot Menu ***Press UP/DOWN to move, ENTER to select, ESC/CTRL+C to quit1. Startup system (Default)2. Upgrade firmware3. Upgrade ATF BL24. Upgrade ATF FIP5. Upgrade single image6. Load image0. U-Boot consoleHit any key to stop autoboot: 2 Hit any key to stop autoboot: 1 SF: Detected fm25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Reading from 0x180000 to 0x46000000, size 0x100 ... OK
Reading from 0x180000 to 0x46000000, size 0x3337c0 ... OK
## Loading kernel from FIT Image at 46000000 ...
   Using 'config@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  ARM64 OpenWrt Linux-5.4.194
     Type:         Kernel Image
     Compression:  lzma compressed
     Data Start:   0x460000e8
     Data Size:    3337664 Bytes = 3.2 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x48080000
     Entry Point:  0x48080000
     Hash algo:    crc32
     Hash value:   733bc683
     Hash algo:    sha1
     Hash value:   046b1faa39740bf28ad5dd533f8872ee5716c5d1
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading fdt from FIT Image at 46000000 ...
   Using 'config@1' configuration
   Trying 'fdt@1' fdt subimage
     Description:  ARM64 OpenWrt mt7981-spim-nor-rfb device tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x4632efec
     Data Size:    17055 Bytes = 16.7 KiB
     Architecture: AArch64
     Hash algo:    crc32
     Hash value:   3548558c
     Hash algo:    sha1
     Hash value:   5e3c969b06349f5f64a954e97d5c5359e089fa08
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Booting using the fdt blob at 0x4632efec
   Uncompressing Kernel Image
   Loading Device Tree to 000000004f7f2000, end 000000004f7f929e ... OK

Starting kernel ...
......
Login timed ouMeshLink login: 

Furthermore, some more information from the u-boot console:

  *** U-Boot Boot Menu ***

      1. Startup system (Default)
      2. Upgrade firmware
      3. Upgrade ATF BL2
      4. Upgrade ATF FIP
      5. Upgrade single image
      6. Load image
      0. U-Boot console

  
  Press UP/DOWN to move, ENTER to select, ESC/CTRL+C to quit


....

MT7981> printenv

baudrate=115200
bootdelay=2
bootmenu_0=Startup system (Default)=mtkboardboot
bootmenu_1=Upgrade firmware=mtkupgrade fw
bootmenu_2=Upgrade ATF BL2=mtkupgrade bl2
bootmenu_3=Upgrade ATF FIP=mtkupgrade fip
bootmenu_4=Upgrade single image=mtkupgrade simg
bootmenu_5=Load image=mtkload
ethact=ethernet@15100000
ethaddr=92:ef:f1:8f:ba:d1
fdtcontroladdr=4ffcdf40
ipaddr=192.168.10.1
loadaddr=0x46000000
netmask=255.255.255.0
serverip=192.168.10.100
stderr=serial@11002000
stdin=serial@11002000
stdout=serial@11002000

Environment size: 511/126972 bytes

MT7981> version
U-Boot 2022.07-rc3-ga7d4f1f1-dirty (Jul 12 2023 - 02:04:02 +0000)

aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
GNU ld (GNU Binutils for Ubuntu) 2.34

Find the full logs (length of this post is limited) here:

uboot_console
wavlink_wn573hx3_boot_capture.txt

This makes fun. Do you have any idea what is the next step to get this device supported and running 'real' openwrt? As far as I can see, there is already running a vendor modified openwrt version.


Because I am limited of 3 replies as a new user, I add my reply here:

Thank you for the link. I was able to patch and build a basic image (OpenWrt 24.10-SNAPSHOT, r28579-cf3988c266). A quick boot with tftpboot was successfully. Network (ethernet) is working. Now I will read and learn how to build a full functional image (e.g. including luci and other packages) on my own.

There is already a pending PR for this device.

1 Like

status' closed, so not very pending any more ?

The box is on the roof again and running my custom OpenWRT 24.10 snapshot! Hooray! Thanks to all for helping me, especially hurrian for pointing me to the PR.
This was helping a lot! The whole procedure was not exactly like described in the PR, but in the end, flashing the firmware went smoothly.

There is no serial console access necessary. After booting my kernel via tftpboot, to make sure it is running, I flashed the *-sysupgrade.bin image (build with the local openwrt-imagebuilder) with the firmware upgrade WebUI from Wavlink. Of course, there was running a serial console in parallel. :wink:

I will do some deeper testing in the next week, to see if all is running nice and smooth.