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.