[BPI-R3 Mini] Boot from NAND fails

mtk_uartboot also works with valid bootloader on local storage, bit it must be active when device is powered on

Can anybody help me actually get the mtk_uartboot to handshake with my device? nothing seems to actually transfer. I’ve tried every combination that I can think of. Maybe my board is just toast?

Try with linux os, with windows/macos not working fine

I tried with linux also.

Please attach more information, too me works correctly on linux

You have to first connect and start mtk_uartboot and then power the board

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

I guess it would also be possible to build a bl2 with RAM_BOOT_UART_DL=1 from my fork of atf, so it can load a kernel and initramfs from the fip (just wait a bit longer then) and start using the initramfs image directly (with airoha firmware included, iproute2, parted, mkfs.xxx etc). But I see I need to fix a few things, before the ram version builds Fixed

Hi everybody, new noob here. :roll_eyes:

I’m a bit overstretched with all the informations I find here in this forum about flashing a BPI-R3mini to stable OpenWrt img. Ist the following manual still a (the) save way to flash Openwrt? https://openwrt.org/toh/sinovoip/bananapi_bpi_r3_mini My plan was to copy the files from USB to partitions of the eMMC and NAND. Is there anything wrong with this idea?

Or is it better to go this way here? https://wiki.fw-web.de/doku.php?id=en:bpi-r3mini:start#fix_bricked_boot Somehow I’m afraid ending up like the TS, but I wont have the skills to get out of these troubles. So any hints to avoid it, would help a lot.

thanks a lot in advance!

Primary you should use the install for mainline openwrt using their install instructions. But if you are not able to do this way (because you cannot boot r3mini) you can fallback to my wiki.

1 Like