eMMC always booting to TFTP

Banana Pi Router design BPI-R3/R3 Mini(MT7986)
1

Hey, I am trying to install OpenWRT 25.03.3 on BPI R3 on the eMMC

I used to have the firmware installed on SD card but due to a statistical reboot problem I had to move my firmware to the eMMC.

At first I didn’t have uboot at all on my eMMC, so I installed openwrt 25.03 on sd, the moved it to nand, When I tried to move it again to emmc it didn’t succeed:

I followed the following tutorial in order to install emmc:

but when finished I got the following data on serial adapter when trying to boot from eMMC:

F0: 102B 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 103F 0000
F3: 1006 0033 [0200]
F3: 4001 00E0 [0200]
F3: 4002 0000
F6: 102C 0000
F5: 1026 0000
00: 1005 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 103F 0000
F3: 4001 00E0 [0200]
F3: 4002 0000
F6: 102C 0000
01: 102A 0001
02: 1005 0000
BP: 2000 00C0 [0001]
EC: 0000 0000 [2000]
T0: 0000 0103 [010F]
System halt!

since the stage of installing bootloader on eMMC tutorial didn’t succeed, I tried to use the following option from the bootloader (I was in SPI-NAND mode): Install bootloader, recovery and production to eMMC.

I switched to eMMC and luckily everything booted up and waited for TFTP! I’ve downloaded “Kernel” target from Openwrt’s firmware selector and managed to boot it via tftp, and then, while on eMMC mode tried to install openwrt using sysupgrade target.

Unfortunately, regardless of what I’m doing I can’t manage to boot from the eMMC directly, and it always tries to boot from TFTP. Anyone have any ideas what is failing here? Thank you

This is the (forever) pending to tftp boot log that I get now:

* spi-nand0
  - device: spi_nand@1
  - parent: spi@1100a000
  - driver: spi_nand
  - type: NAND flash
  - block size:        0x20000 bytes
  - page size:         0x800 bytes
  - OOB size:          64 bytes
  - OOB available:     24 bytes
  - 0x000000000000-0x000008000000 : "spi-nand0"
          - 0x000000000000-0x000000080000 : "bl2"
          - 0x000000080000-0x000000380000 : "factory"
          - 0x000000380000-0x000000580000 : "fip"
          - 0x000000580000-0x000008000000 : "ubi"
Using ethernet@15100000 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.1
Filename 'openwrt-mediatek-filogic-bananapi_bpi-r3-initramfs-recovery.itb'.
Load address: 0x46000000
2

Based on output above you miss bl2 or partconfig is wrong (boot0 not set to bootable)

3

hey Frank thank you for the answer do you refer to the 1st log or the second?

because right now I only see the second one, the TFTP log (ever since I ran the Install bootloader, recovery and production to eMMC.)

I am able to boot with no issue from NAND, anything I can run to try fixing bl2 / partconfig?

4

I thought second output was from nand,sorry.

I would look if the flag_recovery is set

https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/boot/uboot-mediatek/patches/430-add-bpi-r3.patch;h=cbcda89119516d719b59cee46433f7c4d04a899f;hb=HEAD#l1059

Maybe there is something in pstore or the production image is broken.

Based on this you can try reflashing the production image or something else