Banana Pi BPI-RV2 OpenWrt support

Banana PI RISC-V Design BPI-RV2 (Siflower SF21H8898)
1

OpenWrt snapshot support is already available at

https://downloads.openwrt.org/snapshots//targets/siflower/sf21/

2

Hi,

please see my post Banana Pi BPI-RV2 Risc-V gateway board design with Siflower SF21H8898 chip design - #12 by grrguu

To fix USB for OpenWrt snapshot please add the following diff to OpenWrt:

diff --git a/target/linux/siflower/dts/sf21h8898_bananapi_bpi-rv2.dtsi b/target/linux/siflower/dts/sf21h8898_bananapi_bpi-rv2.dtsi
index aa309e37c1..6904cf3048 100644
--- a/target/linux/siflower/dts/sf21h8898_bananapi_bpi-rv2.dtsi
+++ b/target/linux/siflower/dts/sf21h8898_bananapi_bpi-rv2.dtsi
@@ -185,6 +185,7 @@
 
 &usb {
        status = "okay";
+       vbus-supply = <&usb_vbus>;
 };
 
 &dpns {

Still looking into how to fix NVMe. Maybe the issue is related to power regulator, too ? The following is missing in OpenWrt Snapshot sf21h8898-bpi-rv2.dtsi

	m2keyb_pwren: regulator@1 {
		compatible = "regulator-fixed";
		regulator-name = "m2keyb_pwren";
		regulator-min-microvolt = <3300000>;
		regulator-max-microvolt = <3300000>;
		gpio = <&gpio 38 GPIO_ACTIVE_HIGH>;
		enable-active-high;
		regulator-always-on;
	};

…but adding the above alone does not bring NVMe up. Any hints ?

Thank you for your help.

3

Hi @sinovoip and thank you very much for your products! Already have BPI-F3 and happy with it!

I just received my BPI-RV2. It seems I cannot find full uboot source code tree of it. Can you please point me to it? I could not find it anywhere.

Thanks!

4

Do you looking for this?

5

I’ve been here and even successfully built openwrt from this repo but still not able to find any u-boot. This source tree contains build recipe only for OpenSBI with related patches, but u-boot is missing from there

6

After getting a B-key to M-key adapter I could test some other NVMe.

The issue experienced is only with the B-key NVMe, it’s not detected at all. This B-Key NVMe does work in x86 PC fine.

Not working: B-Key KIOKIA KBG50ZNS512G NVMe SSD

Using M-key NVMe via adapter the NVMe is detected (stock OpenWrt and OpenWrt snapshot):

root@bpirv2:~# lspci
0000:00:00.0 PCI bridge: Device 1a0a:abcd (rev 01)
0001:00:00.0 PCI bridge: Device 1a0a:abcd (rev 01)
0001:01:00.0 Non-Volatile memory controller: Sandisk Corp PC SN530 NVMe SSD (DRAM-less) (rev 01)
root@bpirv2:~# hdparm -t /dev/nvme0n1

/dev/nvme0n1:
Timing buffered disk reads: 1144 MB in  3.00 seconds = 380.88 MB/sec
root@bpirv2:~# hdparm -T /dev/nvme0n1

/dev/nvme0n1:
Timing cached reads:   1908 MB in  2.00 seconds = 953.73 MB/sec

root@bpirv2:~# lspci
0000:00:00.0 PCI bridge: Device 1a0a:abcd (rev 01)
0001:00:00.0 PCI bridge: Device 1a0a:abcd (rev 01)
0001:01:00.0 Non-Volatile memory controller: Sandisk Corp SanDisk Ultra 3D / WD Blue SN550 NVMe SSD (rev 01)
root@bpirv2:~# hdparm -t /dev/nvme0n1

/dev/nvme0n1:
Timing buffered disk reads: 1108 MB in  3.00 seconds = 369.30 MB/sec
root@bpirv2:~# hdparm -T /dev/nvme0n1

/dev/nvme0n1:
Timing cached reads:   1820 MB in  2.00 seconds = 909.89 MB/sec

So this is good news! Perhaps this is related to max W the PCIe slot can handle ? The older NVMe seem to draw more power…