newer r2 have a boot switch (above sdcard) which tries the sd before if on position 1 and emmc first in position 0…then the other device.
it looks like emmc is loaded first, right…try bootswitch in other position. for uboot-issue on emmc, i guess image of openwrt is broken…which openwrt-version do you use?
This problem is discussed multiple times in this forum. Imho only some special images store settings. Most are ramfs only. But as i do not use openwrt i cannot help here…
I guess openwrt there uses mtd partitions (defined in dts of uboot and for kernel in cmdline). You write kernel with mtd command…
After kernel load fails you were dropped to uboot console where you can try different things. At least show environment (where bootmenu is defined) with “printenv”. In these you can look whats called in order and how kernel gets loaded…i guess something like load kerneldata from mtd (maybe using mmc read with block offset of mtd partition) into memory and then call this memoryaddress with bootm. Maybe you can boot from sdcard and show mtd partitions with the mtd command you’ve used for writing
Hi, i have done some experiments with OPENWRT 19.07.05
The instruction on OPENWRT Site is not correct.
After creating the openWRT Image after this instruction you have to write the image file openwrt-mediatek-mt7623-bpi_bananapi-r2-squashfs-img.gz after extraction on a SD Card. Now you can boot from this card and you und you have a option, that you can copy the image to eMMC from uBoot.
This is very good.
OPENWRT 19.07. is running very good. VLAN Tagging is working.
Now i have the problem, that i cannot install new packages. OPENWRT say, that it is a incompatible architecture by installing keepalived and kmod-macvlan
Assumeing /dev/sdx is your sd card, is “write the image file on a sd card” means gzip -d -c openwrt-mediatek-mt7623-bpi_bananapi-r2-squashfs-img.gz | sudo dd out=/dev/sdx?