Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| inbox:toh:sinovoip:bananapi_bpi-r4 [2024/06/04 22:44] – [Installation] better wording and ordering attila-lendvai | inbox:toh:sinovoip:bananapi_bpi-r4 [2024/11/21 07:31] – Add information how to enable WO firmware dpawlik | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| {{page> | {{page> | ||
| - | Banana Pi BPI-R4 | + | Banana Pi BPI-R4 uses the MediaTek MT7988A (Filogic 880), a 1.8GHz |
| {{media: | {{media: | ||
| Line 61: | Line 61: | ||
| Installing to eMMC is possible by first installing to NAND, then copy from the NAND to eMMC. This is because the sdcard and the eMMC cannot be both accessed at the same time. The sdcard takes priority and " | Installing to eMMC is possible by first installing to NAND, then copy from the NAND to eMMC. This is because the sdcard and the eMMC cannot be both accessed at the same time. The sdcard takes priority and " | ||
| - | If you don't want to, or cannot use the serial console, then you can instruct the bootloader to perform installation on the next reboot using the bootloader environment | + | You may also instruct the bootloader to perform |
| + | |||
| + | [[wp> | ||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| Line 119: | Line 121: | ||
| </ | </ | ||
| ***/ | ***/ | ||
| - | |||
| ===== Hardware ===== | ===== Hardware ===== | ||
| + | |||
| + | |||
| ==== Info ==== | ==== Info ==== | ||
| ^ Architecture | ^ Architecture | ||
| Line 148: | Line 151: | ||
| </ | </ | ||
| ***/ | ***/ | ||
| + | |||
| + | ==== BPI-R4-NIC-BE14 ==== | ||
| + | One of the greatest advantages of this device is the cooperation of the main processor (MT7988) with the WiFi module (**MT7996**). | ||
| + | The **BPI-R4-NIC-BE14** module is often described as a board with MT7996 processor, but this is actually a marketing shorthand used by MediaTek | ||
| + | for its Wireless module series. The MT7996 refers to an entire chipset package consisting of multiple components: MT7995AV+MT7976CN+MT7977IAN. | ||
| + | |||
| + | <WRAP BOX> | ||
| + | **Important**: | ||
| + | </ | ||
| + | |||
| + | Before you mount the module to the router, remember to switch the " | ||
| + | |||
| + | {{media: | ||
| + | |||
| + | After that, the 12V LED lights up when turned **ON**. | ||
| + | |||
| + | === Wireless Offload === | ||
| + | |||
| + | Before explaining the WO firwmare goal, it is worth to mention about **WED** - **W**ireless **E**thernet **D**ispatch. (Special thanks | ||
| + | for Dangowrt for the explaination). | ||
| + | |||
| + | The WED term stems from the original implementation which is part of MT7622 and offloads | ||
| + | forwarding from Ethernet to Wireless, ie. WiFi TX is offloaded only. Hence packets received on Ethernet | ||
| + | are dispatched to Wireless, hence the name. More recent versions (MT7986, MT7981 and later SoC) do | ||
| + | support also taking care of the traffic received on the Wireless interface. | ||
| + | |||
| + | The " | ||
| + | offloading firmware is required. | ||
| + | |||
| + | WED means offloading traffic forwarding from/to Wireless. It works with the existing | ||
| + | flow-offloading aka. HWNAT engine of MediaTek SoCs, just like for forwarding Ethernet traffic. | ||
| + | Newer SoCs need firmware to perform WED, and that is called WO firmware. Because WED is now bidirectional, | ||
| + | MediaTek started to use the more generic term WO instead of WED, which suggests a unidirectional | ||
| + | nature as it has been the case on MT7622. Today, the two terms (WED and WO) mean the same feature. | ||
| + | |||
| + | The " | ||
| + | |||
| + | <WRAP BOX> | ||
| + | **Important**: | ||
| + | |||
| + | |||
| + | To set 2GB RAM limit, you need to execute on the router: | ||
| + | < | ||
| + | fw_setenv bootargs " | ||
| + | </ | ||
| + | |||
| + | To go back to previous settings, execute on the router: | ||
| + | < | ||
| + | fw_setenv bootargs " | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | After you change RAM size (temporary workaround), | ||
| + | |||
| + | < | ||
| + | echo " | ||
| + | </ | ||
| + | |||
| + | Then **reboot** the router to apply changes. When it comes back, results should be as below: | ||
| + | |||
| + | < | ||
| + | $ cat / | ||
| + | Y | ||
| + | $ cat / | ||
| + | Y | ||
| + | </ | ||
| + | |||
| + | |||
| + | === Module BPI-R4-NIC-BE14 photo === | ||
| + | |||
| + | {{media: | ||
| + | |||
| + | === 6GHz wireless network === | ||
| + | |||
| + | The topic of 6GHz networking is often duplicated on the official OpenWrt forum, so before | ||
| + | configuring your network, make sure: | ||
| + | |||
| + | * if you are using Windows 10, using the 6GHz network is not possible on this system, | ||
| + | * make sure you have the latest drivers, | ||
| + | * verify the Wi-Fi [[https:// | ||
| + | * there are only few contries where the 320MHz width can be used | ||
| + | |||
| + | <WRAP BOX> | ||
| + | **NOTE**: Sometimes the latest drivers may not achieve satisfactory speeds. It is worth trying sometimes to use **AX** mode than **BE** mode. | ||
| + | </ | ||
| + | |||
| + | ==== Testing speed locally ==== | ||
| + | There are many tools to check the speed between the host and the router. The most commonly | ||
| + | used, " | ||
| + | " | ||
| + | convenient method for testing (by default the service should be available on port :8989). | ||
| ==== Photos ==== | ==== Photos ==== | ||
| Line 176: | Line 270: | ||
| ===== Bootlogs ===== | ===== Bootlogs ===== | ||
| + | |||
| ==== OEM bootlog ==== | ==== OEM bootlog ==== | ||
| <WRAP bootlog> | <WRAP bootlog> | ||
| Line 800: | Line 895: | ||
| [ | [ | ||
| [ | [ | ||
| - | + | </ | |
| - | + | ||
| - | BusyBox v1.33.2 (2023-06-04 07:30:12 UTC) built-in shell (ash) | + | |
| - | + | ||
| - | _______ | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | |__| W I R E L E S S F R E E D O M | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | === WARNING! ===================================== | + | |
| - | There is no root password defined on this device! | + | |
| - | Use the " | + | |
| - | in order to prevent unauthorized SSH logins. | + | |
| - | -------------------------------------------------- | + | |
| - | root@OpenWrt:/# | + | |
| </ | </ | ||
| Line 1425: | Line 1503: | ||
| [ | [ | ||
| [ | [ | ||
| - | |||
| - | |||
| - | |||
| - | BusyBox v1.36.1 (2024-02-18 08:56:45 UTC) built-in shell (ash) | ||
| - | |||
| - | _______ | ||
| - | | ||
| - | | ||
| - | | ||
| - | |__| W I R E L E S S F R E E D O M | ||
| - | | ||
| - | | ||
| - | | ||
| - | === WARNING! ===================================== | ||
| - | There is no root password defined on this device! | ||
| - | Use the " | ||
| - | in order to prevent unauthorized SSH logins. | ||
| - | -------------------------------------------------- | ||
| - | root@OpenWrt:/# | ||
| </ | </ | ||
| </ | </ | ||