What is the max wireless transmit power for this router?
Driver maxs out at 28 dBm for me (5 GHz). I don't have the hardware to test the practical power though.
Weird, I am limited to 23 dBm… What could be causing this?
What region and channel?
When tried driver default and world its limited to 20dBm. When I set it to Singapore, it increases to 23dBm. I use channel 36.
That's correct: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/tree/db.txt
country SG: DFS-FCC
(5150 - 5250 @ 80), (200 mW), AUTO-BW
200 mW = 23.01 dBm
2 Likes
In the region of Panama will be more. 26, and sometimes possibly 28.
Thanks changed channel and now getting 26
The 500 mW (26 dBm) range is DFS in Singapore.
(5470 - 5730 @ 160), (500 mW), DFS
Only bother with DFS ranges if you're going to use 160 MHz width and/or the other frequencies have interference.
Note that, the larger channels use a larger frequency range, which in turn have smaller wavelengths; the extra allowed power in the larger ranges account for that.
Pick your channel/frequency range according to your local interference. For one, you can use LuCI's channel analysis to figure out interferences from nearby APs.
If, for whatever reason, you just want to max out at 28 dBm (which probably isn't even the real practical power), select channel 149 or above, it's non-DFS and allow for up to 1000 mW (30 dBm)
(5725 - 5850 @ 80), (1000 mW)
1 Like
More dBs nine out of ten times won't improve your WiFi quality.
A better placement of the router and selecting a WiFi band with the least interference are other avenues to look into.
Hello, I need your help.
Xiaomi AX3000T router
Winbond NAND
Successfully flashed with snapshot first time
Poorly configured
Reset via uart
Successfully flashed with snapshot second time but after reboot this:
Hit any key to stop autoboot: 0
detect button reset released!
Reading from 0x0 to 0x4f7ff2cc, size 0x4 ... OK
Reading from 0x0 to 0x4f7ff2cc, size 0x4 ... OK
Saving Environment to MTD... Erasing on MTD device 'nmbm0'... OK
Writing to MTD device 'nmbm0'... OK
OK
[Dual Image] Booting System 1, sys1_failed = 0, sys2_failed = 5
ubi0: attaching mtd10
ubi0: scanning is finished
ubi0: attached mtd10 (name "ubi1", size 34 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 272, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 0
ubi0: available PEBs: 249, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
Reading from volume 'kernel' to 0x46000000, size 0x0 ... *** Cannot find volume 'kernel' ***
resetting ...
F0: 102B 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 2400 0041 [0000]
G0: 1190 0000
EC: 0000 0000 [1000]
T0: 0000 024B [010F]
Jump to BL
NOTICE: BL2: v2.6(release):9548a30134d-dirty
NOTICE: BL2: Built : 02:27:18, Jan 24 2024
NOTICE: WDT: disabled
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 | 00a003f1 000000ff 00100000 00000000
1001d040 | 00027e71 000200a0 00020303 000000ff
1001d050 | 00000000 00000000 00000000 00000000
1001d060 | 00000002 00000000 00000000 00000000
drm: 500 = 0xc
[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 612, worse bit 0, min window 76
Window Sum 612, worse bit 8, min window 76
Window Sum 538, worse bit 4, min window 66
Window Sum 510, worse bit 15, min window 60
Window Sum 542, worse bit 0, min window 66
Window Sum 524, worse bit 15, min window 60
Window Sum 544, worse bit 0, min window 66
Window Sum 526, worse bit 15, min window 60
Window Sum 524, worse bit 15, min window 62
Window Sum 530, worse bit 11, min window 62
NOTICE: EMI: Detected DRAM size: 256MB
NOTICE: EMI: complex R/W mem test passed
NOTICE: CPU: MT7981 (1300MHz)
NOTICE: SPI_NAND parses attributes from parameter page.
NOTICE: SPI_NAND Detected ID 0xef
NOTICE: Page size 2048, Block size 131072, size 134217728
NOTICE: Initializing NMBM ...
NOTICE: Signature found at block 1023 [0x07fe0000]
NOTICE: First info table with writecount 0 found in block 960
NOTICE: Second info table with writecount 0 found in block 963
NOTICE: NMBM has been successfully attached in read-only mode
NOTICE: BL2: Booting BL31
NOTICE: BL31: v2.6(release):9548a30134d-dirty
NOTICE: BL31: Built : 02:27:18, Jan 24 2024
NOTICE: Hello BL31!!!
In: serial@11002000
Out: serial@11002000
Err: serial@11002000
Net: eth0: ethernet@15100000
*** U-Boot Boot Menu ***
1. Startup system (Default)
2. Startup firmware0
3. Startup firmware1
4. Upgrade firmware
5. Upgrade ATF BL2
6. Upgrade ATF FIP
7. Upgrade single image
8. Load image
I successfully flashing the kernel at 0x46000000 several times but after reboot the router shows the above information.
Flashing the kernel at 0x48000000 as shown in debrick instruction doesn't work.
Is there any way of knowing looking at the box if the devices comes with the 1.0.84 firmware version with the hardware revision?
The release date must be before 07.24
@aloner What's the problem exactly? That's the stock bootloader menu. It will select the default option after a few seconds, if none of them have been selected manually.
@ChristianWS From the box alone, no. Not sure if there is any visible info from the device itself though.
You can always open the box, plug the router in, access http://192.168.31.1, and check the firmware version at the bottom of the status page. If it's 1.0.84, you can put it back in the box and return.
This bug https://github.com/openwrt/openwrt/issues/14415 is unfortunately back to haunt us, at least with WED enabled.
Hi, here I've bricked another Xiaomi AX3000T for my first time flashing OpenWrt. Details are as below:
router model: RD23 with ESMT nand flash
stock firmware ver: 1.0.49 (INT)
flashed OpenWrt ver: 23.5.05
I flashed the firmware following the instructions on official site(API RCE method), and it was successful at first, but bricked after an power outage. The router led blink really slow and cable connection would be no effect at all, just as this thread -Xiaomi AX3000T bricked(no rapid blink)- mentioned too. The problem seem can be solved by installing UBoot, but currently I have no tool to reset it via UART.
Does many people facing the same problem and fixed through UBoot installation too? Scared of bricking the whole router thoroughly.
Returning will not be an option, I'm buying locally from a guy who sells the Chinese version. He had two in stock that were bought in July, so I'm hoping they don't have the 1.0.84 firmware.
I've tried buying from AliExpress but it couldn't pass customs.
The wording used in this thread implies the 1.0.84 version will eventually be supported. One even implied you can just build OpenWRT with the hardware revision support
Seems like at this point, we will need to highly recommend flashing a different bootloader in the wiki. Most of these bricks seem to be on RD23 though.
This was recommended as a replacement for OpenWrt U-Boot and it apparently supports the stock layout too: What's your favourite cheap LEDE/OpenWrt device? - #735 by erayrafet
I don't use it myself though, so I can't vouch for it.
Like in the thread you linked (more specifically my post in it), did you do the steps mentioned in Basic Configuration?
2 Likes
The problem that router can't boot the system kernel (I don't know what it's called). If I select "Start system (default)", it goes back to the bootloader menu. I can only boot the system kernel after flashing, and after rebooting I can't.
Have you tried these?
2. Startup firmware0
3. Startup firmware1