[BPI-R64] Debian Bullseye image

Hi,

i’ve created a Bullseye image for BPI-R64 (new bootchain, used the last debian buster as base)

  • uboot 2020.10
  • linux kernel 5.15.0
  • user/pw: root/bananapi

Configuration is similar to Bullseye for BPI-R2 (used same systemd-files for network)

  • wan: 192.168.0.18/24
  • lanports bridged with IPv4 192.168.1.1/24 (dnsmasq as dhcp-server on lanbr0)

https://drive.google.com/drive/folders/1oP7jy1KrrIOifvImo2nQ59wx3_9hHkgk?usp=sharing

bpi-r64_bullseye_newatf_5.15_incomplete.img.gz
bpi-r64_bullseye_newatf_5.15_incomplete.img.gz.md5
2 Likes

if you want dhcp on wan, change /etc/systemd/network/11-wan.network and activate DHCP=ipv4 by removing the # at beginning of line and disable the static config below

1 Like

Hello, tried the image. It stopped on boot SD/EMMC:

## Error: "fit" not defined
** No partition table - mmc 1 **
BPI-R64>

this is maybe caused by some sdcards and new bootchain (Opensource ATF)

i guess you see something like this on loading uboot:

CPU:   MediaTek MT7622
Model: mt7622-bpi-r64
DRAM:  1 GiB
WDT:   Started with servicing (60s timeout)
MMC:   [email protected]: 0, [email protected]: 1
In:    [email protected]
Out:   [email protected]
Err:   [email protected]
Net:
Warning: [email protected] (eth0) using random MAC address - 12:60:ce:66:26:91
eth0: [email protected]
Hit any key to stop autoboot:  0
unable to read ssr
unable to read ssr
unable to select a mode
mmc_init: -524, time 600
Boot from eMMC

it is discussed here with mtk (together with a dram init issue in bl2 too causing reboot issues due to low voltage)

it appear immediately after menu:

`
....
3. Boot from SD/EMMC
.....

`

Menu is shown after the errors i’ve posted.

** No partition table - mmc 1 **

Looks like gpt cannot be read from sdcard…you boot from sdcard,right? Image is not prepared for emmc…for this it needs some adjustments

that’s right, from a sdcard

have you (maybe similar) errors after loading uboot (before the menu) like i’ve posted?

i suggest to use another sdcard (vendor), made good experiences with sandisk.

one other problem can be that an old gpt partition table exists (backup at the end of sdcard), but the you get an error/warning on starting uboot that main gpt does not match backup one…here you can dd the last sector of sdcard with if=/dev/zero. another way is to fix gpt with pc, but gparted overwrites the bootsector on fixing backup-gpt, so you need to reflash the first ~2MB of image to sdcard again

is there way to pause loading before menu to read if there is the error?

you can press any key before menu is loaded, pressing a key directly before menu is shown, cancels it

most serial terminals (like putty or minicom) can scroll back so you should see the error

that is the loading:

 `
F0: 102B 0000
F5: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 0400 0041 [0000]
G0: 1190 0000
T0: 0000 0328 [000F]
Jump to BL

NOTICE:  BL2: v2.2(release):CI-BUILD-20201124_181406-d407ab2-3-g8a75849
NOTICE:  BL2: Built : 11:14:54, Nov 29 2020
NOTICE:  BL2: Booting BL31
NOTICE:  BL31: v2.2(release):CI-BUILD-20201124_181406-d407ab2-3-g8a75849
NOTICE:  BL31: Built : 11:14:57, Nov 29 2020


U-Boot 2020.10-bpi (Nov 29 2020 - 11:04:35 +0100)

CPU:   MediaTek MT7622
Model: mt7622-bpi-r64
DRAM:  1 GiB
WDT:   Started with servicing (60s timeout)
MMC:   [email protected]: 0, [email protected]: 1
In:    [email protected]
Out:   [email protected]
Err:   [email protected]
Net:   
Warning: [email protected] (eth0) using random MAC address - 4e:29:86:dc:02:0a
eth0: [email protected]
Hit any key to stop autoboot:  0 
BPI-R64> 

`

mhm, looks good. strange that you fall into it…also no warning about gpt mismatch, but maybe this comes up only on access

you can try this in uboot-console (when menu is shown, last entry):

run selectmmc;run loadenv;
`
BPI-R64> run selectmmc;run loadenv;
switch to partitions #0, OK
mmc1 is current device
Boot from SD
*** ERROR: Can't read MBR header ***
find_valid_gpt: *** ERROR: Invalid GPT ***
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
error!
*** ERROR: Can't read GPT Entries ***
GPT: Failed to allocate memory for PTE
find_valid_gpt: *** ERROR: Invalid GPT ***
*** ERROR: Can't read GPT header ***
find_valid_gpt: *** ERROR: Invalid Backup GPT ***
** Invalid partition 1 **
BPI-R64>
`

ok, so maybe caused by invalid backup-gpt

you have gparted installed?

sudo gparted /dev/sdX # your sdcard-device, gparted asks you to fix the gpt
sudo dd if=imgfile of=/dev/sdX bs=1M count=2

maybe gdisk also works, but have not tried yet, how large is your sdcard? it should be at least 8GB

yes, this helped, thanks a lot. the image boots very quickly, great!

the problem card was 32G

card that boots - 16G

Which step makes it work? Fixing backup-gpt or replace card?

I changed to smaller 16G SD card

32G CD card - gparted fix the error, but dd bs=1M count=2 returns the error back

Mhm,gparted breaks bootsector in my case while repairing backup gpt…strage that restoring it does not work in your case…maybe block was to large…i had used the bpi-r64_sdmmc.img from my atf-repo (which contains bootheaders including uboot/fip)

Hello all,

Who can help me with a very simple question? I bought the BPI-R64 (old version) but I can’t find a description of the power supply anywhere. I would very much like to know where the PLUS pole is. Is it on the inside or is it on the outside of the jack plug?

Thank you very much and see you soon …

Pluspole is inside,same for r2

IMG_20211201_171709