BPI-R4 Support

[Yon2068]

Is your feature request related to a problem? Please describe.
I am trying to create an image for the BPI-R4, but so far I have encountered errors. Is it possible to create this image or not?

[Ysurac]

I only support hardware that I own. Else it's difficult to test.
What error did you get when you compiled it ?

[Yon2068]

I only support hardware that I own. Else it's difficult to test. What error did you get when you compiled it ?

curl: (22) The requested URL returned error: 404
Download failed.
No more mirrors to try - giving up.
make[3]: *** [Makefile:110: /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/dl/rustc-1.78.0-src.tar.gz] Error 2
make[3]: Leaving directory '/media/yon/p0/omr/openmptcprouter/feeds/openmptcprouter/rust'
time: package/feeds/openmptcprouter/rust/host-compile#7.71#10.49#5050.80
ERROR: package/feeds/openmptcprouter/rust [host] failed to build.
make[2]: *** [package/Makefile:175: package/feeds/openmptcprouter/rust/host/compile] Error 1
make[2]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source'
make[1]: *** [package/Makefile:171: /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/staging_dir/target-aarch64_cortex-a53_musl/stamp/.package_compile] Error 2

[Yon2068]

I only support hardware that I own. Else it's difficult to test. What error did you get when you compiled it ?

make[8]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5/gettext-tools'
make[7]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5/gettext-tools'
make[6]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5/gettext-tools'
make[6]: Entering directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5'
make[7]: Entering directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5'
make[7]: Nothing to be done for 'install-exec-am'.
make[7]: Nothing to be done for 'install-data-am'.
make[7]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5'
make[6]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5'
make[5]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5'
make[4]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5'
ln -sf msgfmt /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/staging_dir/hostpkg/bin/gmsgfmt
mkdir -p /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/staging_dir/hostpkg/stamp
touch /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5/.built
touch /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/staging_dir/hostpkg/stamp/.gettext-full_installed
find /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/build_dir/hostpkg/gettext-0.22.5 -mindepth 1 -maxdepth 1 -not '(' -type f -and -name '.*' -and -size 0 ')' -print0 | xargs -r -0 rm -rf
make[3]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/package/libs/gettext-full'
time: package/libs/gettext-full/host-compile#1092.76#563.53#1578.64
make[2]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source'
make[1]: *** [package/Makefile:171: /media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/staging_dir/target-aarch64_cortex-a53_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory '/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source'
make: *** [/media/yon/p0/omr/openmptcprouter/myplatform/6.6/source/include/toplevel.mk:248：world]

---

I encountered a new error during a recompilation

[BlueWaterCrystal]

Have you tried compiling for kernel 6.1?

I had trouble compiling 6.6 for BPI-R3 but got 6.1 to compile.

I don't know about the R4 but for the R3 I had to disable ramdisk, otherwise, it wouldn't create the SD card image.
Additionally, I had to create a non-root user and near the end, I used make -j1 for the rest of the build.

This is the command I used to generate the platform:
OMR_TARGET="BPI-R3" OMR_FEED_SRC="master" OMR_KERNEL="6.1" ./build.sh

[Yon2068]

Have you tried compiling for kernel 6.1?

I had trouble compiling 6.6 for BPI-R3 but got 6.1 to compile.

I don't know about the R4 but for the R3 I had to disable ramdisk, otherwise, it wouldn't create the SD card image. Additionally, I had to create a non-root user and near the end, I used for the rest of the build.make -j1

This is the command I used to generate the platform: OMR_TARGET="BPI-R3" OMR_FEED_SRC="master" OMR_KERNEL="6.1" ./build.sh

---

Thanks for your suggestion; I will try again.

[Yon2068]

Have you tried compiling for kernel 6.1?

I had trouble compiling 6.6 for BPI-R3 but got 6.1 to compile.

I don't know about the R4 but for the R3 I had to disable ramdisk, otherwise, it wouldn't create the SD card image. Additionally, I had to create a non-root user and near the end, I used for the rest of the build.make -j1

This is the command I used to generate the platform: OMR_TARGET="BPI-R3" OMR_FEED_SRC="master" OMR_KERNEL="6.1" ./build.sh

---

When nearing the end, is the command make -j1 used because there are errors at that stage, and should I use make -j1 -k to let it continue compiling?

[BlueWaterCrystal]

Have you tried compiling for kernel 6.1?
I had trouble compiling 6.6 for BPI-R3 but got 6.1 to compile.
I don't know about the R4 but for the R3 I had to disable ramdisk, otherwise, it wouldn't create the SD card image. Additionally, I had to create a non-root user and near the end, I used for the rest of the build.make -j1
This is the command I used to generate the platform: OMR_TARGET="BPI-R3" OMR_FEED_SRC="master" OMR_KERNEL="6.1" ./build.sh

When nearing the end, is the command make -j1 used because there are errors at that stage, and should I use make -j1 -k to let it continue compiling?

I think some components just don't like being built in parallel and end up failing the build.
If the build machine has all the required dependencies installed, make -j$(nproc) should work during the whole build.

I believe when I switched to 6.1, if there were errors it at least gave an explanation, which was mostly missing dependencies
vs 6.6 which didn't seem to give many answers and was more of some sort of compatibility issue.

[Yon2068]

Have you tried compiling for kernel 6.1?

I had trouble compiling 6.6 for BPI-R3 but got 6.1 to compile.

I don't know about the R4 but for the R3 I had to disable ramdisk, otherwise, it wouldn't create the SD card image. Additionally, I had to create a non-root user and near the end, I used make -j1 for the rest of the build.

This is the command I used to generate the platform: OMR_TARGET="BPI-R3" OMR_FEED_SRC="master" OMR_KERNEL="6.1" ./build.sh

---

Thank you, I successfully compiled it this time. I'm going to test it now.

[Yon2068]

Have you tried compiling for kernel 6.1?
I had trouble compiling 6.6 for BPI-R3 but got 6.1 to compile.
I don't know about the R4 but for the R3 I had to disable ramdisk, otherwise, it wouldn't create the SD card image. Additionally, I had to create a non-root user and near the end, I used for the rest of the build.make -j1
This is the command I used to generate the platform: OMR_TARGET="BPI-R3" OMR_FEED_SRC="master" OMR_KERNEL="6.1" ./build.sh

When nearing the end, is the command make -j1 used because there are errors at that stage, and should I use make -j1 -k to let it continue compiling?

I think some components just don't like being built in parallel and end up failing the build. If the build machine has all the required dependencies installed, make -j$(nproc) should work during the whole build.

I believe when I switched to 6.1, if there were errors it at least gave an explanation, which was mostly missing dependencies vs 6.6 which didn't seem to give many answers and was more of some sort of compatibility issue.

---

I used the balenaEtcher tool on my Mac to flash openmptcprouter-v0.61rc2-master-c9c2c4e2-r0+24843-acf40c022e-mediatek-filogic-mediatek_mt7988a-rfb-sdcard.img.gz, but the BPI-R4 has no response upon boot. What should I do?

[BlueWaterCrystal]

Was there a target for BPI-R4?

I would Imagine the suffix of the file would be
mediatek-filogic-bananapi_bpi-r4-sdcard instead of mediatek-filogic-mediatek_mt7988a-rfb-sdcard

I'm guessing there is some other sbc that uses the same CPU but has a different device tree and so on.

bananapi_bpi-r4:
https://github.com/openwrt/openwrt/blob/23ac1ad9515588321970985859b2ee0cc8243f91/target/linux/mediatek/image/filogic.mk#L411

mediatek_mt7988a-rfb:
https://github.com/openwrt/openwrt/blob/23ac1ad9515588321970985859b2ee0cc8243f91/target/linux/mediatek/image/filogic.mk#L890C15-L890C35

[Yon2068]

Was there a target for BPI-R4?

I would Imagine the suffix of the file would be mediatek-filogic-bananapi_bpi-r4-sdcard instead of mediatek-filogic-mediatek_mt7988a-rfb-sdcard

I'm guessing there is some other sbc that uses the same CPU but has a different device tree and so on.

bananapi_bpi-r4: https://github.com/openwrt/openwrt/blob/23ac1ad9515588321970985859b2ee0cc8243f91/target/linux/mediatek/image/filogic.mk#L411

mediatek_mt7988a-rfb: https://github.com/openwrt/openwrt/blob/23ac1ad9515588321970985859b2ee0cc8243f91/target/linux/mediatek/image/filogic.mk#L890C15-L890C35

---

I can't find the option for Bananapi BPi-R4 in the Target Profile, but it is indeed available in the OpenWRT compilation.

[Ysurac]

I use a custom target/linux/mediatek/image/filogic.mk, I think BPI-R4 is missing, you can replace it with the one from openwrt in the link from @BlueWaterCrystal

[Ysurac]

I've updated filogik.mk on my repo, so you should be able to compile for BPI-R4 now.

[Yon2068]

I've updated filogik.mk on my repo, so you should be able to compile for BPI-R4 now.

---

Thank you! I have replaced the target/linux/mediatek/image/filogic.mk file and am currently compiling. However, I will pull the code again and recompile once more.

[Yon2068]

Collected errors:

• pkg_hash_check_unresolved: cannot find dependency kmod-thermal for kmod-hwmon-pwmfan
• pkg_hash_fetch_best_installation_candidate: Packages for kmod-hwmon-pwmfan found, but incompatible with the architectures configured
• opkg_install_cmd: Cannot install package kmod-hwmon-pwmfan.
• resolve_conffiles: Existing conffile /media/yon/p0/omr2/openmptcprouter/BPI-R4/6.6/source/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/etc/config/glorytun is different from the conffile in the new package. The new conffile will be placed at /media/yon/p0/omr2/openmptcprouter/BPI-R4/6.6/source/build_dir/target-aarch64_cortex-a53_musl/root-mediatek/etc/config/glorytun-opkg.
  make[2]: *** [package/Makefile:99: package/install] Error 255
  make[2]: Leaving directory '/media/yon/p0/omr2/openmptcprouter/BPI-R4/6.6/source'
  make[1]: *** [package/Makefile:172: /media/yon/p0/omr2/openmptcprouter/BPI-R4/6.6/source/staging_dir/target-aarch64_cortex-a53_musl/stamp/.package_install] Error 2
  make[1]: Leaving directory '/media/yon/p0/omr2/openmptcprouter/BPI-R4/6.6/source'
  make: *** [/media/yon/p0/omr2/openmptcprouter/BPI-R4/6.6/source/include/toplevel.mk:248：world

---

I'm stuck here.
This is a similar case I found: openwrt/openwrt#16400.
What should I do now?

[Ysurac]

Check that CONFIG_THERMAL is set to yes via make kernel_menuconfig in BPI-R4/6.6/source directory (use the key "/" to search).

[Yon2068]

Error: ../dts/mt7988d-smartrg-SDG-8733A.dts:114.1-15 Label or path aqr_green_led not found
Error: ../dts/mt7988d-smartrg-SDG-8733A.dts:118.1-16 Label or path aqr_orange_led not found
Error: ../dts/mt7988d-smartrg-SDG-8733A.dts:122.1-15 Label or path aqr_white_led not found
FATAL ERROR: Syntax error parsing input tree
make[5]: *** [Makefile:43: /media/yon/p0/omr3/openmptcprouter/BPI-R4/6.6/source/build_dir/target-aarch64_cortex-a53_musl/linux-mediatek_filogic/image-mt7988d-smartrg-SDG-8733A.dtb] Error 1

I found the missing file in the dts folder of OpenWrt, and I copied it to the source/target/linux/mediatek/dts directory. However, I noticed that it gets automatically deleted during compilation. What should I do?

[Ysurac]

git pull. It was fixed yesterday.

[Yon2068]

git pull. It was fixed yesterday.

Thank you, I successfully compiled it, but after starting, the network card light is off, and I can't access 192.168.100.1. The onboard green indicator light came on, and the RST button is responsive; the green light goes off and then turns back on (possibly rebooting).

[Ysurac]

As it's not a supported platform, difficult to help as I don't have the device.
You can try to connect a serial USB cable to check the boot screen ( https://wiki.banana-pi.org/Getting_Started_with_BPI-R4 )

[Yon2068]

[    2.379335] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[    2.384649]  mmcblk0: p1 p2 p3 p4 p5 p6 p7
[    2.390893] mtk-pcie-gen3 11280000.pcie:       IO 0x0020000000..0x00201fffff -> 0x0020000000
[    2.403412] mtk-pcie-gen3 11280000.pcie:      MEM 0x0020200000..0x0027ffffff -> 0x0020200000
[    2.751567] mtk-pcie-gen3 11280000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[    2.760378] mtk-pcie-gen3: probe of 11280000.pcie failed with error -110
[    2.767460] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[    2.774777] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[    2.781042] mtk-pcie-gen3 11290000.pcie:       IO 0x0028000000..0x00281fffff -> 0x0028000000
[    2.789478] mtk-pcie-gen3 11290000.pcie:      MEM 0x0028200000..0x002fffffff -> 0x0028200000
[    3.131563] mtk-pcie-gen3 11290000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[    3.140344] mtk-pcie-gen3: probe of 11290000.pcie failed with error -110
[    3.147211] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges:
[    3.154522] mtk-pcie-gen3 11300000.pcie: Parsing ranges property...
[    3.160781] mtk-pcie-gen3 11300000.pcie:       IO 0x0030000000..0x00301fffff -> 0x0030000000
[    3.169214] mtk-pcie-gen3 11300000.pcie:      MEM 0x0030200000..0x0037ffffff -> 0x0030200000
[    3.511570] mtk-pcie-gen3 11300000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[    3.520349] mtk-pcie-gen3: probe of 11300000.pcie failed with error -110
[    3.527211] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges:
[    3.534519] mtk-pcie-gen3 11310000.pcie: Parsing ranges property...
[    3.540778] mtk-pcie-gen3 11310000.pcie:       IO 0x0038000000..0x00381fffff -> 0x0038000000
[    3.549210] mtk-pcie-gen3 11310000.pcie:      MEM 0x0038200000..0x003fffffff -> 0x0038200000
[    3.891565] mtk-pcie-gen3 11310000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[    3.900344] mtk-pcie-gen3: probe of 11310000.pcie failed with error -110
[    4.293051] clk: Disabling unused clocks
[    4.297613] Waiting for root device /dev/fit0...
[   14.682967] platform 15020000.switch: deferred probe pending
[   14.688624] platform 15100000.ethernet: deferred probe pending

Here is TTL information. What should I do?

[Ysurac]

Seems to be similar to openwrt/openwrt#14767
Current OpenWRT snapshot is working ?

[Yon2068]

Seems to be similar to openwrt/openwrt#14767 Current OpenWRT snapshot is working ?

---

Yes, the current OpenWrt snapshot is working fine.

[Ysurac]

Without same TTL messages ?
Can you do also a uci show network and ip a on OpenWRT image ?

[Yon2068]

Without same TTL messages ? Can you do also a and on OpenWRT image ?uci show network``ip a

---

I am using the official OpenWRT image, which can boot normally: https://downloads.openwrt.org/snapshots//targets/mediatek/filogic/openwrt-mediatek-filogic-bananapi_bpi-r4-sdcard.img.gz

[Yon2068]

Without same TTL messages ? Can you do also a and on OpenWRT image ?uci show network``ip a

---

root@OpenWrt:~# uci show network
network.loopback=interface
network.loopback.device='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.globals=globals
network.globals.ula_prefix='fd35:1493:650a::/48'
network.@device[0]=device
network.@device[0].name='br-lan'
network.@device[0].type='bridge'
network.@device[0].ports='lan1' 'lan2' 'lan3' 'eth1'
network.lan=interface
network.lan.device='br-lan'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.lan.ip6assign='60'
network.@device[1]=device
network.@device[1].name='br-wan'
network.@device[1].type='bridge'
network.@device[1].ports='wan' 'eth2'
network.@device[2]=device
network.@device[2].name='wan'
network.@device[2].macaddr='d2:c3:9a:92:64:a6'
network.@device[3]=device
network.@device[3].name='eth2'
network.@device[3].macaddr='d2:c3:9a:92:64:a6'
network.wan=interface
network.wan.device='br-wan'
network.wan.proto='dhcp'
network.wan6=interface
network.wan6.device='br-wan'
network.wan6.proto='dhcpv6'
root@OpenWrt:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1504 qdisc mq state UP qlen 1000
    link/ether d2:c3:9a:92:64:a5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d0c3:9aff:fe92:64a5/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-lan state DOWN qlen 1000
    link/ether 96:f8:5e:d1:8a:f8 brd ff:ff:ff:ff:ff:ff
4: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master br-wan state DOWN qlen 1000
    link/ether d2:c3:9a:92:64:a6 brd ff:ff:ff:ff:ff:ff
5: wan@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-wan state LOWERLAYERDOWN qlen 1000
    link/ether d2:c3:9a:92:64:a6 brd ff:ff:ff:ff:ff:ff
6: lan1@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state LOWERLAYERDOWN qlen 1000
    link/ether d2:c3:9a:92:64:a5 brd ff:ff:ff:ff:ff:ff
7: lan2@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state LOWERLAYERDOWN qlen 1000
    link/ether d2:c3:9a:92:64:a5 brd ff:ff:ff:ff:ff:ff
8: lan3@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-lan state LOWERLAYERDOWN qlen 1000
    link/ether d2:c3:9a:92:64:a5 brd ff:ff:ff:ff:ff:ff
9: br-lan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000
    link/ether d2:c3:9a:92:64:a5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global br-lan
       valid_lft forever preferred_lft forever
    inet6 fd35:1493:650a::1/60 scope global tentative noprefixroute 
       valid_lft forever preferred_lft forever
10: br-wan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000
    link/ether d2:c3:9a:92:64:a6 brd ff:ff:ff:ff:ff:ff
root@OpenWrt:~# 

[Yon2068]

root@OpenWrt:~# uname -a
Linux OpenWrt 6.6.52 #0 SMP Thu Sep 19 21:11:58 2024 aarch64 GNU/Linux

[Yon2068]

The official kernel 6.6.52 is working properly. How can I use the 6.6.52 kernel?
@Ysurac

[itsgps]

@Ysurac roughly where are you located - I would be more than willing to supply you with an BPI-R4 unit. I just bought one thinking I could use it for network bonding, initially thinking Speedify would do the trick, but I am hating the concept of the Per Month price associated with it, so OpenMPT seems a far better option. Plus I may eventually have a need for more than one of these...so would be more than happy to ship this one to you, or buy another and drop-ship it - since right now I can't do much with the current unit other than fiddle around with OpenWRT...Tried booting with R64 image and it seems a no-go...

In the meantime I will build some test solutions using the X86 images for some 4 Port Qotom Mini-PCs I have which will also eventually be used in production, and link them to my VPS to do some testing.

Unless there is simply a means to use OpenWRT itself on the BPI-R4 - and install OpenMPT as a Package just like how Speedify installs ?!

[Ysurac]

For my address, it's in legal notice: https://www.openmptcprouter.com/about
OpenMPTCProuter can't be a simple package for OpenWRT, there is some kernel patch and many fork.

[loriszigliani]

I need help when i compile for platform BPI-R4 with kernel 6.6, show this error:

from this command "make kernel_menuconfig":
ERROR: toolchain/binutils failed to build.
make: *** [/home/loriszigliani/openmptcprouter/BPI-R4/6.6/source/include/toplevel.mk:248: toolchain/install] Error 1 from this command "make kernel_menuconfig"

on command "make -j1"
screenlog.txt

ERROR: package/kernel/bpf-headers failed to build.
make -r world: build failed. Please re-run make with -j1 V=s or V=sc for a higher verbosity level to see what's going on
make: *** [/home/loriszigliani/openmptcprouter/BPI-R4/6.6/source/include/toplevel.mk:248: world] Error 1