Table of Contents
BananaPi R4
Hardware
- MediaTek MT7988A (Filogic 880)
- MT7530 switch builtin (1 cpu-port with 4GBit/s + 1Gbit/s user-ports)
- 4G RAM
- 8GB eMMC flash
- 128MB SPI-NAND Flash
- either 2x SFP+ (10GBit/s USXGMII) or 1SFP+ and 2g5 rj45 with PoE (link)
- Wifi7 with additional module connected to the 2 PCIe slots at bottom of board
- BPI-R4-NIC-BE19 (no public sale): MT7996 + MT7975 (2.4G) + MT7977A (6G) + MT7977B (5G)
- BPI-R4-NIC-BE14: MT7995AV + MT7976CN + MT7977IAN
- powersupply 12V/5A required when using wifi card,2A (like on other BPi Routers) is not enough
v00:
v1.0:
Changes between v0 and v1 (pm): https://forum.banana-pi.org/t/bpi-r4-linux-bootup/15926/59
v1.1:
thermal
cat /sys/class/thermal/thermal_zone0/temp
Uses lvts driver
Thermalpad size: https://forum.banana-pi.org/t/banana-pi-bpi-r4-heatsink-and-case-design/16638/53
testing fan
by default first trip point is set to 40°C and second is 85°C…for testing the fan it is a bit high when using a passive heatsink. so just set first to 35 and second to 45.
root@bpi-r4-v11:/sys/class/thermal/thermal_zone0 # cat trip_point_4_temp 40000 root@bpi-r4-v11:/sys/class/thermal/thermal_zone0 # cat trip_point_3_temp 85000 root@bpi-r4-v11:/sys/class/thermal/thermal_zone0 # echo 45000 > trip_point_3_temp root@bpi-r4-v11:/sys/class/thermal/thermal_zone0 # echo 35000 > trip_point_4_temp root@bpi-r4-v11:/sys/class/thermal/thermal_zone0
Network
GMAC0 (4GBit/s) is connected internally to mt7530 switch variant where the 4 user-Ports are exposed as rj45 on board (1xWan,3xLan).
The SFP(+) cages are connected to SerDes lanes of GMAC1 and GMAC2, and those can be switched between SGMII/1000Base-X/2500Base-X mode for 10M/100M/1000M/2500M (via mtk-pcs-lynxi, just like on MT7622 and MT7986) and USXGMII/10GBase-KR for 5000M and 10000M.
Supported interface modes for the SFP+ cages of the R4 are: SGMII, 1000Base-X, 2500Base-X, 5GBase-R, 10GBase-R, USXGMII
So 1.25Gbps (= 1000Base-X or SGMII) and 3.125Gbps (= 2500Base-X) SFP modules can work fine with the R4.
Sfp-connections
| USB-A | SFP1-WAN | SFP2-LAN | 4xRJ-45 | 12V | USB-C |
|---|---|---|---|---|---|
| USXGMII0 | USXGMII1 | GSW | |||
| eth2 | eth1 | eth0 |
Forward 10g should work with ppe patch,but input needs rss+lro.
https://forum.banana-pi.org/t/bpi-r4-not-getting-full-10gbps-speed-on-wan/18134/30
full 10G will need RSS+LRO implemented in mtk ethernet driver and enabled (not yet working):
ethtool -K eth2 lro on # enable hw_lro ethtool -k eth2 | grep large large-receive-offload: on iperf3 -bidir -c 192.168.90.10
RSS: https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-feeds/+/18f46a84d87308a4f56f9176ca166dc75c38bb20%5E%21/ LRO: https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-feeds/+/ddc366751fad05dade79b09932a999c5d5ae890c%5E%21/#F0
NETSYS: V2 for mt7986 (bpi-r3) V3 for mt7988 (bpi-r4)
Daniel tells me that lro should be enabled via userspace with
ethtool -N $ifname flow-type tcp4 dst-ip $lan_ip loc 0
Wifi
wifi is realized with daughter board (Network Interface Card) in the 2 mPCIe-Slots at bottom of the board.
Wifi-Module needs 12V…v1 uses sw4 in on-position, v0 used devicetree-overlay which enables the WIFI_PWR_EN regulator. Be careful with this setting when using different card in mPCIe slots!
kernel-module: mt7996e.ko
Newer wifi card with reduced antenna-count (6 instead of 14):
https://forum.banana-pi.org/t/banana-pi-bpi-r4-bpi-be14-wi-fi7-nic-module/17182
newer card currently has timeout on 3rd wifi interface (6.8-netnext), i guess we need another firmware file for the mt7977ia frontend
wifi config (inprogress untested):
PCIE
2x1Lane (M.2 slots) and 2x2lane. the 2x2lane is for wifi (mPCIe slots).
USB
Sim slots
- CN16(M.2 KEY) – SIM1
- CN12 (mPCIE) – SIM2
- CN14 (mPCIE) – SIM3
Bootswitch
| A | B | |
|---|---|---|
| nand | 0 | 1 |
| eMMC | 1 | 0 |
| SD | 1 | 1 |
switch down is “1”, so both down booting from sdcard (v0 had both up to boot from sdcard)
v0:
GPIO
PWM
How to get pwm6 working:
https://forum.banana-pi.org/t/bpi-r4-cpu-fan-setup/17362/102
echo "pwm6_0 pwm" > /sys/kernel/debug/pinctrl/1001f000.pinctrl-pinctrl_moore/pinmux-select # Enable PWM function on the pin group pwm6_0 (GPIO62) echo 100000 > /sys/class/pwm/pwmchip0/period # Set freq to 10 kHz (100000 ns period) echo 40000 > /sys/class/pwm/pwmchip0/duty_cycle # Set duty cycle to 40% (40000 ns active) echo 1 > /sys/class/pwm/pwmchip0/enable # Run PWM
eeprom
BPI-R4 has an eeprom on i2c-mux channel 0
[ 1.515672] at24 2-0057: 256 byte 24c02 EEPROM, writable, 1 bytes/write
write-mode (wp-gpio is linked to green led):
# echo 0 > /sys/devices/platform/gpio-leds/leds/green:status/brightness root@bpi-r4-v11:~ # echo "test" > /sys/bus/i2c/devices/2-0057/eeprom root@bpi-r4-v11:~ # hexdump -C /sys/bus/i2c/devices/2-0057/eeprom 00000000 74 65 73 74 0a ff ff ff ff ff ff ff ff ff ff ff |test............| 00000010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................| * 00000100 root@bpi-r4-v11:~ # echo 1 > /sys/devices/platform/gpio-leds/leds/green:status/brightness root@bpi-r4-v11:~
rtc
Battery connection looks like charging circuit for ml2032. You should not connect non-rechargeable battery like cr2032.
https://forum.banana-pi.org/t/bpi-r3-bpi-r4-does-the-bpi-r3-r4-have-a-rtc/17763/36
Connector is JST with 1.25mm pitch
RTC time will survive software reboot
# dmesg | grep rtc [ 1.479923] rtc-pcf8563 2-0051: low voltage detected, date/time is not reliable. [ 1.487390] rtc-pcf8563 2-0051: registered as rtc0 [ 1.493378] rtc-pcf8563 2-0051: low voltage detected, date/time is not reliable. [ 1.500771] rtc-pcf8563 2-0051: hctosys: unable to read the hardware clock root@bpi-r4-v11:~ # date -s "2024-04-27 09:55 CEST" Sat Apr 27 07:55:00 UTC 2024 root@bpi-r4-v11:~ # hwclock -w root@bpi-r4-v11:~ # hwclock -r 2024-04-27 07:56:23.979830+00:00 root@bpi-r4-v11:~ # reboot ... root@bpi-r4-v11:~ # dmesg | grep rtc [ 1.480067] rtc-pcf8563 2-0051: registered as rtc0 [ 1.486061] rtc-pcf8563 2-0051: setting system clock to 2024-04-27T07:56:53 ) root@bpi-r4-v11:~ # date Sat Apr 27 08:00:46 UTC 2024 root@bpi-r4-v11:~
uboot/ATF
currently use these:
and bootup "my" kernel like this:
MT7988> setenv fit 6.5.0-rc1-mt7988.itb
MT7988> setenv kaddr 0x48000000
MT7988> fatload mmc 0:5 ${kaddr} ${fit}
4970220 bytes read in 417 ms (11.4 MiB/s)
MT7988> bootm ${kaddr}
kaddr 0x46000000 works too, if uncompressed kernelimage is smaller than 32M (fit size of 14M was too large)
in newer u-boot i have set kaddr to 0x46000000 (fit loadaddr 0x44000000, rdaddr 0x48000000)
ram-boot with mtk_uartboot tool:
./mtk_uartboot -s /dev/ttyUSB4 --aarch64 --payload bpi-r4_ram_bl2.bin --fip bpi-r4_ram_fip.bin
8GB RAM
to use 8GB of ram bl2 code needs to be changed
https://forum.banana-pi.org/t/bpi-r4-successfully-upgraded-8gb-ram-on-bpi-r4/17882/44?u=frank-w
phy-variant
right kernel devicetrees have to be loaded
example for 6.15-rc:
bootconf=#conf-base-2g5#ov-sd fit=6.15.0-rc1.itb 9625136 bytes read in 645 ms (14.2 MiB/s) ## Loading kernel from FIT Image at 46000000 ... Using 'conf-base-2g5' configuration ... Using 'ov-sd' configuration Trying 'fdt-ov-sd' fdt subimage
firmware has to be downloaded and installed to /lib/firmware/mediatek/
then module has to be loaded (currently not autoloaded in debian and result in crash if not loaded and interface set to up).
root@bpi-r4-8G:~# modprobe mtk-2p5ge [ 27.798327] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges: [ 27.805664] mtk-pcie-gen3 11280000.pcie: Parsing ranges property... [ 27.811970] mtk-pcie-gen3 11280000.pcie: IO 0x0020000000..0x00201fffff -> 0x0020000000 root@bpi-r4-8G:~[ 27.821056] mtk-pcie-gen3 11280000.pcie: MEM 0x0020200000..0x0027ffffff -> 0x0020200000 # root@bpi-r4-8G:~# ip link set eth1 up [ 40.141879] MediaTek MT7988 2.5GbE PHY mdio-bus:0f: Firmware date code: 0/0/0, version: 0.0 [ 41.492639] MediaTek MT7988 2.5GbE PHY mdio-bus:0f: Firmware loading/trigger ok. [ 41.500970] mtk_soc_eth 15100000.ethernet eth1: PHY [mdio-bus:0f] driver [MediaTek MT7988 2.5GbE PHY] (irq=POLL) [ 41.511319] mtk_soc_eth 15100000.ethernet eth1: configuring for phy/internal link mode root@bpi-r4-8G:~# [ 44.697996] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx root@bpi-r4-8G:~# ip a a 192.168.0.19/24 dev eth1 root@bpi-r4-8G:~# ping 192.168.0.11 PING 192.168.0.11 (192.168.0.11) 56(84) bytes of data. 64 bytes from 192.168.0.11: icmp_seq=1 ttl=64 time=0.339 ms 64 bytes from 192.168.0.11: icmp_seq=2 ttl=64 time=0.169 ms ^C --- 192.168.0.11 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1012ms rtt min/avg/max/mdev = 0.169/0.254/0.339/0.085 ms
maybe put it in /etc/modules
echo "mtk-2p5ge" >> /etc/modules
tftp
BPI-R4> setenv bootfile 6.5.0-rc1-mt7988-r4.itb BPI-R4> run bootnetfit
openwrt image
using bin/targets/mediatek/filogic/openwrt-mediatek-filogic-bananapi_bpi-r4-initramfs-recovery.itb
BPI-R4> usb start
BPI-R4> ls usb 0:1 r4
./
../
7929856 openwrt-mediatek-filogic-bananapi_bpi-r4-initramfs-recovery.itb
1 file(s), 2 dir(s)
BPI-R4> fatload usb 0:1 0x50000000 r4/openwrt-mediatek-filogic-bananapi_bpi-r4-initramfs-recovery.itb
7929856 bytes read in 672 ms (11.3 MiB/s)
BPI-R4> bootm 0x50000000#config-mt7988a-bananapi-bpi-r4#mt7988a-bananapi-bpi-r4-sd
to get the bootconfigs (after #) we can use dumpimage from uboot-tools, see https://www.gibbard.me/linux_fit_images/
openwrt source
mtk-sdk
related ethernet (and other) patches for 6.6 in openwrt 24.10:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=tree;f=target/linux/generic/pending-6.6
debian/ubuntu image building
basicly i have 3 github-repos for this…
- my u-boot repo creates the bootchain (atf bl2+uboot fip+partitions+creating base image), so look for details in this ci-pipeline (.github/workflows/build.yaml) and build.sh in uboot branch and mtk-atf branch
- my kernel-repo (BPI-Router-Linux) contains the linux kernel also built via ci pipeline and build.sh
- my images repo collects these 2 binaries (base-image and kernel-package) and make a full image with rootfs (also ci available in gdrive branch)
prebuilt images on my gdrive: https://drive.google.com/drive/folders/1A5S7_82Bg4EYxjzdQ5FKyBw9Qi2C3uK-?usp=drive_link
some more information and using ubi for nand are here: https://gist.github.com/BtbN/9e5878d83816fb49d51d1f76c42d7945
Webgui (cockpit): https://forum.banana-pi.org/t/bpi-r4-sd-debian-bookworm-bullseye-images-on-kernel-6-8-0-dango/17487/43
flash via this command to sdcard:
gunzip -c bpi-r4_sdmmc.img.gz | sudo dd bs=1M status=progress conv=notrunc,fsync of=/dev/sdX
linux
https://www.kernel.org/doc/html/v6.1/admin-guide/kernel-parameters.html
3GB Ram limit not needed anymore as ethernet driver now uses 36bit addressing
kernel
debug
# mount -t debugfs none /sys/kernel/debug/ # cat /sys/kernel/debug/gpio # cat /sys/kernel/debug/pinctrl/pinctrl-handles # cat /sys/kernel/debug/regulator/regulator_summary # cat /sys/kernel/debug/clk/clk_summary #enable debug for driver probe # echo 'file dd.c +p'>/sys/kernel/debug/dynamic_debug/control # echo 'file core.c +p'>/sys/kernel/debug/dynamic_debug/control # echo '11230000.mmc' > /sys/bus/platform/drivers/mtk-msdc/unbind # echo '11230000.mmc' > /sys/bus/platform/drivers/mtk-msdc/bind
interface config
ip link set lan0 up ip a a 192.168.0.19/24 dev lan0 ip r a default via 192.168.0.10 date -s "2023-08-23 19:37 CEST" #stats ip -s link show dev eth2 ethtool -S eth2
DNS needs to be set in /etc/resolv.conf or in systemd like this:
mkdir -p /etc/systemd/resolved.conf.d/ cp /etc/systemd/resolved.conf /etc/systemd/resolved.conf.d/TEST.conf echo "DNS = 192.168.0.10" >> /etc/systemd/resolved.conf.d/TEST.conf systemctl restart systemd-resolved.service
modules in initrd:
mount /dev/mmcblk0p6 /mnt mkdir /lib/modules mkdir /lib/firmware mount -o bind /mnt/lib/modules /lib/modules mount -o bind /mnt/lib/firmware /lib/firmware modprobe mt7996e
openwrt
upstream
same as for r3
https://forum.banana-pi.org/t/banana-pi-r3-bsp-source-code/14257/2
but select BananaPi BPI-R4 of course :)
i had to do a “make distclean” after “git pull” followed by the documented steps
# Update the feeds ./scripts/feeds update -a ./scripts/feeds install -a make menuconfig #select "Target System (MediaTek Ralink ARM)" => "Subtarget (Filogic 8x0 (MT798x))" => "Target Profile (Bananapi BPi-R4)" make -j$(nproc)
then write the sdcard image…
gunzip -c bin/targets/mediatek/filogic/openwrt-mediatek-filogic-bananapi_bpi-r4-sdcard.img.gz | sudo dd bs=1M status=progress conv=notrunc,fsync of=/dev/sdX
Resize rootfs: https://forum.banana-pi.org/t/bpi-r3-mini-how-to-extend-emmc-overlayfs/17732/43
Patch adding uboot
downstream (sdk)
- clone openwrt master
- add this to feeds.conf.default: “src-git mtksdk https://git01.mediatek.com/openwrt/feeds/mtk-openwrt-feeds”
- scripts/feeds update -f mtksdk
- make menuconfig:
- Target System (MediaTek Ralink ARM)
- Subtarget (Filogic 8×0 (MT798x))
- Target Profile (MediaTek MT7988a nand rfb) #here i see no sd-variant
adding additional options:
CONFIG_PACKAGE_f2fs-tools=y CONFIG_PACKAGE_e2fsprogs=y CONFIG_PACKAGE_dosfstools=y CONFIG_PACKAGE_resize2fs=y CONFIG_PACKAGE_nano=y CONFIG_PACKAGE_iperf3=y #CONFIG_PACKAGE_netcat CONFIG_PACKAGE_tcpdump=y CONFIG_BUSYBOX_CUSTOM=y CONFIG_BUSYBOX_CONFIG_TELNET=y
*-initramfs-kernel.bin is not the production image we’re using. We only use it for testing purpose since it contains rootfs and won’t read the flash.
*-sysupgrade.bin is the actual production image. It’s a tar ball for nand/emmc/sd boards. It contains separate kernel and rootfs that will be written to ubi volume for nand, or the partitions defined for sd/emmc.
#tar -xf bin/targets/mediatek/filogic/openwrt-mediatek-filogic-mediatek_mt7988a-rfb-nand-squashfs-sysupgrade.bin sysupgrade-mediatek_mt7988a-rfb-nand/kernel #dumpimage -l sysupgrade-mediatek_mt7988a-rfb-nand/kernel dumpimage -l openwrt-24.10.0-mediatek-filogic-bananapi_bpi-r4-initramfs-recovery.itb tftpboot 0x50000000 openwrt-mediatek-filogic-bananapi_bpi-r4-initramfs-recovery.itb bootm 0x50000000#config-mt7988a-bananapi-bpi-r4#mt7988a-bananapi-bpi-r4-sd
Gentoo
Known Issues
- Card in M.2 slot causes i2c issues (sfp not detected): https://forum.banana-pi.org/t/bpi-r4-nvme-i2c/17152/2
- pcie2 and some others (offloading with 4G, multiple ppe, rss/lro) not yet working (https://forum.banana-pi.org/t/banana-pi-bpi-r4-wifi-7-router-board-with-mediatek-mt7988a-filogic-880-4g-ram-and-8g-emmc/15757/241)
- Wifi range/throughput currently bad with mainline (openwrt) code. Seems like eeprom issue. https://forum.banana-pi.org/t/bpi-r4-wifi-range/19418/236?u=frank-w