@deema sorry, this was caused by an omission in the commits I had pushed. I forced-pushed an update and also pushed to openwrt.git, the buildbot is munging on it in this moment:
https://buildbot.openwrt.org/master/images/#/builders/44/builds/6
(so in an hour or two we will have images on downloads.openwrt.org)
Update: yet another small bug (caused by uncareful copy&paste on my end), caused the generated U-Boot for eMMC to contain the environment for SDMMC. Fixed now:
Hi, I want make clear. U-boot and bl2 flashing in eMMC only when I pick “Install bootloader and recovery to eMMC.” from SD u-boot menu?
You can do that manually in the U-Boot shell as well. From within Linux you can write to the eMMC, but I haven’t tried writing to the boot0 hardware partition in that way (may require some extra locks to be broken).
Using the option to install to eMMC in the bootloader menu is the easiest way. If you don’t have serial access, you can trigger the installation on the next boot from within OpenWrt running from the SD Card like this:
fw_setenv bootcmd run emmc_init
Buildbot for mt7622 running again:
https://buildbot.openwrt.org/master/images/#/builders/44/builds/8
Once this has completed, there will be images on downloads.openwrt.org containing both, the changes needed to select either SATA or PCIE1 at boot as well as fixed environment for eMMC installation.
I have install new build, but how activate sata support.
I found IT:
fw_setenv bootconf config-mt7622-bananapi-bpi-r64-sata
and reboot.
I had try new build. It work fine. Sata port have work.
Should work as on other images (maybe need to prepare hw-partitions with mmc utils).
root@bpi-r64:~# echo 0 > /sys/block/mmcblk1boot0/force_ro
root@bpi-r64:~# dd if=bl2_emmc.bin of=/dev/mmcblk1boot0
If it does not boot from emmc check/set partition config with mmcutils (needs to be 0x48)
root@bpi-r64:~# ./mmc extcsd read /dev/mmcblk1 | grep 'PARTITION_CONFIG'
Boot configuration bytes [PARTITION_CONFIG: 0x00]
root@bpi-r64:~# ./mmc bootpart enable 1 1 /dev/mmcblk1
root@bpi-r64:~# ./mmc extcsd read /dev/mmcblk1 | grep 'PARTITION_CONFIG'
Boot configuration bytes [PARTITION_CONFIG: 0x48]Hello, i have a bpi-r64 (mt7622) with lede 17 snapshot instaled, i want to move to openwrt last stable 19. But i don’t understand how to install from scratch. Thanks for your reply.
Flash openwrt-mediatek-mt7622-bananapi_bpi-r64-sdcard.img to SD card (by Win32Diskimager for example). Boot from SD and flash loader by command “Install bootloader and recovery to eMMC.”. Reboot from eMMC and load sysupgrade image by tftp server (tftpd64 for example) . More information you can see there
in U-boot how i can change the ip of tftp server ?
By default env var serverip is used.
you can do
printenv serverip
setenv serverip 192.168.0.10
And try again
thanks it’s working 
but now i get this : 
i download the lasted version and it seems to work
Did you follow the OpenWrt guide?
It seems a little complicated. I have not yet tried it as hardware wise the bpi-r2 would be great as an OpenWrt router.
Or does the latest OpenWrt snapshot install normally, without the drama?
Hi. I have solved my trouble with internet. When I power on my BPI with modem, internet appear not immediately with luci, but only after 30-40 sec. I have noted that fist time wan load with IP 192.168.100.2 but some time late it reconnect with IP witch gave modem. To speed up this process I have create script which reboot wan if it’s IP 192.168.100.2:
WANIP=$(/sbin/ifconfig wan | grep 'inet addr:' | cut -d: -f2 | awk '{ print $1}')
BADIP="192.168.100.2"
if [ $WANIP = $BADIP ]
then
logger Wan Stop $WANIP
ifdown wan
sleep 10
ifup wan
logger Wan Start
fi
I putted it to: luci->system->startup->local startup
192.168.100.2 looks like a configured address…imho it will be better to remove this config…i guess you get your public-ip on wan,right?
But it do what I want. Give me internet after start immediately.
I’ve updated the OpenWrt snapshot image for the R64 one more time, now the sdcard.img comes gz compressed and already contains everything, no need to use dd on the command line.
Installation instructions are updated accordingly: