Maybe I am doing something wrong, but when I try to flash the firmware on my WR1300 V3.0 I get this error...
what am I doing wrong? unfortunately I couldn't find the page dedicated to v3 (it's always an afterword to v2) so I'm not sure if I'm doing things the right way, any help?
Two observations:
You can't upgrade directly from the original firmware to OpenWrt, you have to necessarily go through the intermediate firmware that the Cudy people have.
The process is simple:
Yes! I forgot to close the thread, but my case was that the firmware offered by Cudy was not available for 2 days so I was in trouble to figure out which firmware we are talking about. Thank you!
Sorry for bumping an older thread. I am running the 23.05 openwrt that I compiled myself (same result with snapshot) on WR1300 V3
However my 5G wifi would only allow up to 3dbm tx, which is pretty bad.
iwinfo phy1-ap0 txpowerlist
0 dBm ( 1 mW)
1 dBm ( 1 mW)
2 dBm ( 1 mW)
* 3 dBm ( 1 mW)
and:
iwinfo phy1-ap0 info
phy1-ap0 ESSID: "openwrt-5"
Access Point: F4:A4:54:85:C4:CC
Mode: Master Channel: 40 (5.200 GHz) HT Mode: VHT80
Center Channel 1: 42 2: unknown
Tx-Power: 3 dBm Link Quality: unknown/70
Signal: unknown Noise: -90 dBm
Bit Rate: unknown
Encryption: mixed WPA/WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11ac/b/g/n
Hardware: 14C3:7663 14C3:7663 [MediaTek MT7613BE]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy1
Am I doing something wrong? I am running out of ideas, which is why I decided to come here and ask around as to what might be wrong with this picture 
It works fine when im right next to it, but if I go in a different room - that baby is slowing itself down significantly.
Thank you for any help or advice you can provide!
The issue with v3 (I have one) is that their calibration data is wrong so the driver defaults to 3dBm.
I have successfully injected the v2 eeprom data in a v3 device, and it works completely fine.
To do so, you'll need to inject it in the driver either by patching the driver or the dts and compile your own. I'm not sure what the correct way to fix this is so I didn't send a patch upstream.
The way I did it it (which is not a proper way to do it) was:
Yup, that did it.
I wonder what needs to be patched on openwrt side to make this less of a hacky way to fix 5GHz WiFi..
Hi Zekica,
I've been working on getting an older build of OpenWRT up and running on the Cudy WR1300 v3 hardware and I'm very close, but I'm running into this same issue with the 5Ghz Txpower. I'm running off OpenWRT 19.07 but I'm happy to patch as required to get this power issue resolved.
Can you provide a scrubbed version of the eeprom patch?
iwinfo phy1-ap0 txpowerlist
0 dBm ( 1 mW)
1 dBm ( 1 mW)
2 dBm ( 1 mW)
* 3 dBm ( 1 mW)
iw phy phy1 info
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2304 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: 0
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports AP-side u-APSD.
Device supports T-DLS.
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
Band 2:
Capabilities: 0x1ff
RX LDPC
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: No restriction (0x00)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x338001fa):
Max MPDU length: 11454
Supported Channel Width: 160 MHz, 80+80 MHz
RX LDPC
short GI (80 MHz)
short GI (160/80+80 MHz)
TX STBC
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Frequencies:
* 5180 MHz [36] (3.0 dBm)
* 5200 MHz [40] (3.0 dBm)
* 5220 MHz [44] (3.0 dBm)
* 5240 MHz [48] (3.0 dBm)
* 5260 MHz [52] (3.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (3.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (3.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (3.0 dBm) (no IR, radar detection)
* 5500 MHz [100] (3.0 dBm) (no IR, radar detection)
* 5520 MHz [104] (3.0 dBm) (no IR, radar detection)
* 5540 MHz [108] (3.0 dBm) (no IR, radar detection)
* 5560 MHz [112] (3.0 dBm) (no IR, radar detection)
* 5580 MHz [116] (3.0 dBm) (no IR, radar detection)
* 5600 MHz [120] (3.0 dBm) (no IR, radar detection)
* 5620 MHz [124] (3.0 dBm) (no IR, radar detection)
* 5640 MHz [128] (3.0 dBm) (no IR, radar detection)
* 5660 MHz [132] (3.0 dBm) (no IR, radar detection)
* 5680 MHz [136] (3.0 dBm) (no IR, radar detection)
* 5700 MHz [140] (3.0 dBm) (no IR, radar detection)
* 5720 MHz [144] (3.0 dBm) (no IR, radar detection)
* 5745 MHz [149] (3.0 dBm) (no IR)
* 5765 MHz [153] (3.0 dBm) (no IR)
* 5785 MHz [157] (3.0 dBm) (no IR)
* 5805 MHz [161] (3.0 dBm) (no IR)
* 5825 MHz [165] (3.0 dBm) (no IR)
* 5845 MHz [169] (disabled)
* 5865 MHz [173] (disabled)
valid interface combinations:
* #{ IBSS } <= 1, #{ managed, AP, P2P-client, P2P-GO } <= 4,
total <= 4, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Supported extended features:
* [ VHT_IBSS ]: VHT-IBSS
* [ RRM ]: RRM
* [ SET_SCAN_DWELL ]: scan dwell setting
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
The eeprom patch was a wrong way to fix this. For older versions of OpenWrt just patch the v2 .dts:
&pcie1 with &pcie0&pcie0 with &pcie1That should be enough for any version except main/snapshot. There additional changes were needed for supporting the new nvram cells subsystem - this is already merged.
Hi Zekica,
We have already done that, here is the .dts file section
&pcie0 {
wifi@0,0 {
compatible = "mediatek,mt76";
reg = <0x0000 0 0 0 0>;
mediatek,mtd-eeprom = <&factory 0x0000>;
mtd-mac-address = <&bdinfo 0xDE00>;
ieee80211-freq-limit = <2400000 2500000>;
led {
led-sources = <0>;
led-active-low;
};
};
};
&pcie1 {
wifi@0,0 {
compatible = "mediatek,mt76";
reg = <0x0000 0 0 0 0>;
mediatek,mtd-eeprom = <&factory 0x8000>;
mtd-mac-address = <&bdinfo 0xDE00>;
mtd-mac-address-increment = <1>;
ieee80211-freq-limit = <5000000 6000000>;
};
};
The board boots and the readio is detected, but we are stuck with 3dbm of transmit power for the 5Ghz radio which is pretty much unusable. Is there anything that I'm misisng here as to why that would be the case? There aren't any obvious error messages
Here is the patch I used originally, and can be useful if your device doesn't have the correct 5GHz calibration data in eeprom.
Thanks,
I had found it in another thread and had tested it in our system, I confirmed it was loading with some debug output and I'm still having the same problem with the low power on the 5Ghz radio. I was hoping there was possibly a change there that I didn't have from the posted one.
I appreciate the help, back to digging