[R2Pro] Debian Bullseye / Ubuntu 22.04

frank-w · May 25, 2022, 4:55am

Hi,

i’ve created 2 basic images (only bootchain + rootfs, no network setup)

uboot 2022.04-bpi
linux 5.18.0-bpi-r2pro-main
(barebox 2022-05 incl. iodomain fix)

user:root, pw:bananapi

example-configuration for wan-port (eth0)

date -s '2022-05-23 21:50:00 CEST'
ip addr add 192.168.0.18/24 dev eth0
ip link set eth0 up
ip route add default via 192.168.0.10
# only do once (resolv.conf is persistent)
cp /etc/resolv.conf{,.bak}
echo "nameserver 192.168.0.10" > /etc/resolv.conf

https://drive.google.com/drive/folders/1pnTxSquZL-7n0xx4Bx1xJl7LqEKfa71Y?usp=sharing

the -basic is without rootfs and can be used as base for own linux distribution (deboostrap + set rootpw)

have included phy and dsa driver for switch which can be switched by using other dtb (default dsa driver) in uboot (extlinux.conf)

banada · October 3, 2022, 9:27am

Hello is this image support emmc? Best Regards

frank-w · October 3, 2022, 10:41am

Not out of the box,but you can use it as base,flash atf/uboot after and configure uboot/linux for emmc (pointing to the other mmc device)

banada · October 3, 2022, 3:34pm

I ask for alternatively can we use this image without using maskroom button .

frank-w · October 3, 2022, 3:45pm

Maskrom needs to be only done once to boot mainline bootchain from sd because emmc contsins broken bootchain from factory

banada · October 3, 2022, 3:58pm

could you explain how can configure uboot/linux for emmc? I wantto develop a image on sd card and transfer it into emmc ?Is it possible? Best Regards

frank-w · October 3, 2022, 5:07pm

2022-04 from my uboot-repo supports r2pro (in newer versions it is broken). Atf is only binary blob. Seems r2pro had same atf/uboot for emmc,so you can try writing it to emmc (boot0 not needed).

Seems I had already added a check in uboot for emmc/sd

Only need to change fstab in linux to point to emmc instead sd

github.com

frank-w/u-boot/blob/2022-04-bpi/include/configs/rk3568_bpi-r2-pro.h#L24


#define BOOTENV_R2P \
	"board=bpi-r2pro\0" \
	"device=mmc\0" \
	"partition_sd=1:2\0" \
	"partition_emmc=0:2\0" \
	"bootenv=uEnv.txt\0" \
	"checkenv=test -e ${device} ${partition} ${bootenv}\0" \
	"importenv=env import -t ${scriptaddr} ${filesize}\0" \
	"loadbootenv=if fatload ${device} ${partition} ${scriptaddr} ${bootenv};then run importenv;else echo \"fatload (${bootenv}) failed\";fi\0" \
	"checksd=fatinfo ${device} ${partition_sd}\0" \
	"selectmmc=if run checksd; then echo Boot from SD ; setenv partition ${partition_sd};else echo Boot from eMMC; setenv partition ${partition_emmc} ; fi;\0" \
	"reloadmenu=run selectmmc;if run checkenv; then run loadbootenv; else echo file not found; fi;bootmenu;\0" \
	RUNBOOTMENU \
	"bootmenu_0=1. Run extlinux.=run distro_bootcmd\0" \
	"bootmenu_default=0\0"


#endif

But i’m unsure if distroboot handles sd/emmc currently. Only made basic tests with emmc as it is tricky booting from sd after emmc is flashed.

Seems bootorder is hardcoded in uboot for distroboot.

github.com

ARM-software/u-boot/blob/master/doc/README.distro#L280


-------------------------


<config_distro_bootcmd.h> defines $bootcmd and many helper command variables
that automatically search attached disks for boot configuration files and
execute them. Boards must provide configure <config_distro_bootcmd.h> so that
it supports the correct set of possible boot device types. To provide this
configuration, simply define macro BOOT_TARGET_DEVICES prior to including
<config_distro_bootcmd.h>. For example:


------------------------------------------------------------
#ifndef CONFIG_SPL_BUILD
#define BOOT_TARGET_DEVICES(func) \
        func(MMC, mmc, 1) \
        func(MMC, mmc, 0) \
        func(USB, usb, 0) \
        func(PXE, pxe, na) \
        func(DHCP, dhcp, na)
#include <config_distro_bootcmd.h>
#endif
------------------------------------------------------------