[BPI-R3] Debian Bullseye Image

Banana Pi Router design BPI-R3/R3 Mini(MT7986)
82

Debian Linux 6.6.36-bpi-r3-main on aarch64.

cat /proc/partitions
major minor  #blocks  name

  31        0      20480 mtdblock0
  31        1      10752 mtdblock1
  31        2        512 mtdblock2
  31        3        512 mtdblock3
  31        4        256 mtdblock4
  31        5        256 mtdblock5
 179        0    7634944 mmcblk0
 179        1       4079 mmcblk0p1
 179        2        512 mmcblk0p2
 179        3       2048 mmcblk0p3
 179        4       2048 mmcblk0p4
 179        5     102400 mmcblk0p5
 179        6    6758400 mmcblk0p6
 179        8       4096 mmcblk0boot0
 179       16       4096 mmcblk0boot1
83

Mhm,my nvme is detected with same kernel version

84

Can I have an incompatible SSD?

IMG_20240723_171945
IMG_20240723_1719451552×688 287 KB

85

Possibly,you can look in bootlog via dmesg,but this is unrelated to image so please create separate thread

86

Hello. I would like to boot R3 mini from NVMe. I think I more or less understand the bootchain (thanks for Frank & Eric). Right now I cannot see NVMe from uboot. Tried different versions (openwrt, frank-w’s prebuilt images) booted from a pendrive, but pcie enum output is empty. Linux (openwrt busybox and this debian image) successfully probe and recognize the NVMe. Is there something I miss? Thanks!

87

pcie enum and nvme scan commands normally bring no output…but we had added some debug output.

Just run these 2 commands and look with nvme info or pci if something is found

https://wiki.fw-web.de/doku.php?id=en:bpi-r3mini:start#pcie_nvme

How did you run my image from usb? I guess you mean chainloading u-boot.bin,right?

88

I run it with chainloading as in your wiki.

fatload usb 0:1 $loadaddr u-boot-fw.bin
go $loadaddr

this boots your prebuilt u-boot, specifically the U-Boot 2024.10-bpi-g8fbd1da0163f-dirty from your gh releases.

Then I run the commands and there is no nvme:

BPI-R3M> pci enum
BPI-R3M> nvme info
BPI-R3M> pci
89

You miss “nvme scan” but imho pci should show it

90

Thanks, yes I missed nvme scan but with that version it is the same.

But this might be a regression. Downloaded and tried other versions:

  • U-Boot 2024.04-bpi-g285dd4d9e-dirty (Jul 21 2024): works
  • U-Boot 2024.07-bpi-g80d10f258-dirty (Sep 02 2024): works
  • U-Boot 2024.10-bpi-gfc06f80d0b82-dirty (Oct 12 2024): not works
  • U-Boot 2024.10-bpi-gc9eae044eee7-dirty (Oct 15 2024 ): not works
  • U-Boot 2024.10-bpi-gbaedb28ae9a8-dirty (Nov 03 2024): not works

So apparently something (in my case at least) wrong with every version starting with 2024.10. I can live with the 2024.07 however you might find this info useful.

The output when works:

BPI-R3M> pci enum
detected a card at 0x11280000
BPI-R3M> nvme scan
BPI-R3M> nvme info
Device 0: Vendor: 0x1344 Rev: V3MA002  Prod: 232046F6A954
            Type: Hard Disk
            Capacity: 488386.3 MB = 476.9 GB (1000215216 x 512)
1 Like
91

seems like i missed the dts changes in 2024-10…

pushed, pipeline should have built a binary soon, try to apply to 2025-01 too, also something to check because of clock changes (but seems already correct)…dts imho needs to be fixed to new clock names

92

Thanks for acting promptly! Unfortunately the same as before:

BPI-R3M> version
U-Boot 2024.10-bpi-gaefc17162b36-dirty (Jan 06 2025 - 11:00:40 +0000)

BPI-R3M> pci enum
BPI-R3M> nvme scan

No need to hurry, I’ll check 2025.01 as well when its done. Thanks for the efforts!

93

pci enum and nvme scan normally have no output…you have to use nvme info to have output…should work now

We should get 2024-10 working first as 2025-01 contains many clock changes,but afair i tested with pcie too.

94

tested on r3mini (as i have no nvme ready for my test-r3 boards), and there it works

BPI-R3M> version                                                                                                                                    
U-Boot 2024.10-bpi-00033-gaefc17162b36-dirty (Jan 06 2025 - 13:37:47 +0100)                                                                         
                                                                                                                                                    
BPI-R3M> pci enum                                                                                                                                   
BPI-R3M> nvme scan                                                                                                                                  
BPI-R3M> nvme info                                                                                                                                  
Device 0: Vendor: 0x1c5c Rev: 80002C00 Prod: ND94N163610404F0R                                                                                      
            Type: Hard Disk                                                                                                                         
            Capacity: 244198.3 MB = 238.4 GB (500118192 x 512)                                                                                      
BPI-R3M>
1 Like
95

Indeed, it works as expected, sorry for the noise. I did not realized for first read that the output of the pci enum and nvme scan just intended for debug purposes in your fork and the upstream behavior is different (no output). It looks like the following now:

BPI-R3M> pci enum
BPI-R3M> nvme scan
BPI-R3M> nvme info
Device 0: Vendor: 0x1344 Rev: V3MA002  Prod: 232046F6A954
            Type: Hard Disk
            Capacity: 488386.3 MB = 476.9 GB (1000215216 x 512)
BPI-R3M> version
U-Boot 2024.10-bpi-gaefc17162b36-dirty (Jan 06 2025 - 11:00:40 +0000)
96

but thanks for pointing to it…looks like i have to rebuild my images on gdrive as they are using the old 2024-10 uboot with pcie dts nodes missing, but i want to test r2pro image first. So this will take some time.

first updated r3mini ram-images that were also affected :wink:

started re-building r3/r4 images