Openwrt trunk now officially supports the required 233 for Banana Pi BPI-R4 + BE14 Wifi module

No,mt7530 driver is involved for switch part

Ah, you are right. My bad.

I’ve not been using the MTK feeds for a while, OpenWRT runs stable from the 24.10 branch. But the documentation for that feed is outdated for they created a directory for the 24.10 branch that should be used instead of the main content.

I used the instructions for master (and replace the path with the 24.10 but I still have a limit of 6dbm and is unclear if this is not supported yet, some bug or even a different version of the board. I also checked the eeprom and is my understanding it loads the mt7996_eeprom_233_2i5i6i.bin and the MD5 matches the upstream / MTK version.

OpenWRT Issue wifi txpower value is very low Ā· Issue #17489 Ā· openwrt/openwrt Ā· GitHub

Yeah, saw it later, the 24.10 content directory’s patches don’t apply on the 24.10 branch. Manually fixing the conflict, then building for ā€˜mt7988a-rfb’, with the new 233 firmware in OP, the bpi-r4 doesn’t boot. Not sure what happened, don’t have serial yet.

EDIT: Is there some place that builds these MTK SDK bpi-r4 images in a standardized manner? Frankly I don’t have time to figure out why somebody’s flaky patches don’t apply on the the branch they’re intended for. Currently, this feels like a waste of time, because each person will produce subtly different builds, and there’s zero point of reference.

@frank-w are you running a Banana Pi R4 with the the BE14?

I have be14 installed and did basic steps like starting hostapd,not more yet as i’m busy with different things.

And i work on mainline kernel in debian and not openwrt.

1 Like

Cool, thanks for the update. Since I’m blocked with openwrt I may actually give a go to Debian.

I build an image using GitHub - frank-w/BPI-Router-Images and I get a similar limitation but this time I get an error message from the module

NOTE: This are logs from a Debian image

   13.287851] mt7996e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20240809122254a

[   13.492882] mt7996e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20240809122249
[   13.540892] mt7996e 0000:01:00.0: DSP Firmware Version: ____000000, Build Time: 20240809121650
[   13.582032] mt7996e 0000:01:00.0: WA Firmware Version: ____000000, Build Time: 20240809122214
[   13.979603] mt7996e 0000:01:00.0: registering led 'mt76-phy0'
[   14.048117] mt7996e 0000:01:00.0: registering led 'mt76-phy1'
[   14.098110] mt7996e 0000:01:00.0: registering led 'mt76-phy2'
[   14.177746] mt7996e 0000:01:00.0: vgaarb: pci_notify
[   53.706304] mt7996e 0000:01:00.0: Message 001a0034 (seq 6) timeout
[   76.106294] mt7996e 0000:01:00.0: Message 00120012 (seq 7) timeout
[   98.506295] mt7996e 0000:01:00.0: Message 00120012 (seq 8) timeout
[  120.906303] mt7996e 0000:01:00.0: Message 00120012 (seq 9) timeout
[  143.306297] mt7996e 0000:01:00.0: Message 00120012 (seq 10) timeout
[  165.706296] mt7996e 0000:01:00.0: Message 00120012 (seq 11) timeout
[  188.106297] mt7996e 0000:01:00.0: Message 00120012 (seq 12) timeout
[  210.506302] mt7996e 0000:01:00.0: Message 00120012 (seq 13) timeout

Tried 24.10.0-rc5 bananapi_bpi-r4-sdcard.img.gz. Dmesg: dmesg_bpi-r4_24.10-rc5.log.txt (93.8 KB) And BE at 320MHz works!

@SSIV Are you also able to set the tx_power to something more than 6/7 dBm?

Driver default is 23 dBm in JP region.

Which WiFi card do you have? I have a Banana PI BE14 v1.0 and mine is limited to 6 / 7dBm

Thank you for sharing, I have exactly the same kit. Do you know which version of the Wifi card do you have? mine is v1.0

Same BPI-R4-NIC-BE14 revision here: v1.0. Was unsure at first, but luckily filmed my assembly of the bpi-r4, so it’s definitely v1.0.

I have the same equipment and like @bananas I’m limited to 6/7dBm even though my region (US) (and iw reg get) say I should be able to go up to 30 for 2.4Ghz and 23-30 for 5Ghz (and 12dBm for 6Ghz, although the 6Ghz doesnt appear to work at all and limits itself to 5dBm). I’ve tried openwrt 24.10-rc4 , rc5 & rc6 and openwrt snapshot from Jan 1 2025. iw phy0.0-ap0 set txpower fixed ā€œnumberā€ does work, it just maxes out at 6dBm , and similarly the iw command on 5Ghz works, but up to 7dBm.

Before settling on this 24.10-rc6 setup, I’ve tried:

I don’t know whether the Tx-Power ceiling changed in any way during this firmware hopping, but I can set 2.4/5/6GHz to 23dBm (~200mW) respectively. However, I’m currently running in 5GHz/6GHz mode with Tx-Power limited to 9dBm (7mW), because these puny toy-like antennas the bpi-r4 came with aren’t made for such high Tx-Power anyway.

Any chance that the mt7996e wifi driver or the BE14 hardware itself decreases tx power based on overheating or insufficient power? (I’ve used multiple 12V and currently using a 19V power supply, so I doubt it’s power), and the system cpu never hits 122 degrees Fahrenheit, so I doubt it’s overheating, but I’m grasping at straws here to try to explain why the txpower never goes above 6 and 7 dBm on 2.4Ghz and 5Ghz respectively.

It shouldnt matter, but I’m using the sdcard to boot, are you too? Or did you move to the NAND or eMMC?

And lastly, there’s no extra power connection the BE14 needs, right? The V00 connector is supposed to be unused?

Would be interesting to get to the bottom of this. Some musings:

  • Baseus GaN3 Pro 100W is 20V USB-PD capable. Could be a factor, but frankly not sure.
  • Using sdcard to boot. Will move to nvme booting once setup doesn’t require surgical gloves.
  • Temps are steady at ~60C after several days. Not particularly amazing.
  • No extra power connections going to the BE14, apart from what’s already being pulled from pcie.
  • Attaching pics of the overall setup, nothing out of the ordinary that I can see.
1 Like