Possible to flash R3 ubuntu image into eMMC/NAND?

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

I’ve installed packages in WSL and the chroot error has gone. Do you have idea on the next error?

WSL:

sudo apt install qemu-user-static binfmt-support

Docker container:

ubuntu@afe0fd51a26a:~/BPI-Router-Images$ ./buildimg.sh bpi-r3 noble
needed: python3 python3-requests parted qemu-user-static debootstrap binfmt-support
create image for bpi-r3 (arm64) noble 6.12 sdmmc
board  : bpi-r3
kernel : 6.12
device : sdmmc
{'skipubootdownload': '1', 'imgfile': 'bpi-r3_emmc.img.gz', 'kernelfile': 'bpi-r3_6.12.47-main.tar.gz', 'userpackages': '"ethtool iperf3 tcpdump"'}
bpi-r3mini_emmc_bl2.img
...
...
...
bpi-r3_6.12.47-main.tar.gz already exists
-rw-r--r-- 1 ubuntu ubuntu 123 Sep 24 19:21 sourcefiles_bpi-r3.conf
image-file: bpi-r3_emmc.img.gz
kernel-file: bpi-r3_6.12.47-main.tar.gz
checking for needed packages...
$1:arm64
setting arch
$2:noble
isdebian:0,isubuntu:1
setting distro
create chroot 'ubuntu noble' for arm64
/home/ubuntu/BPI-Router-Images/ubuntu_noble_arm64 already exists - aborting
-rw-r--r-- 1 ubuntu ubuntu 7.6M Sep 24 16:29 bpi-r3_emmc.img.gz
ls: cannot access 'noble_arm64.tar.gz': No such file or directory
rootfs file missing
ubuntu@afe0fd51a26a:~/BPI-Router-Images$
50

It seems a script error, perhaps clean the working folder. Perhaps @frank-w knows, I do not use this script.

51

Not good. Installing packages in WSL2 does not help.

Instead, I patched buildchroot.sh and it built further a bit, however, the WSL2/Docker environment is still unable to perform partprobe/loopdev actions:

Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for libc-bin (2.39-0ubuntu8.5) ...
umounting tmpfs...
-rw-r--r-- 1 ubuntu ubuntu 7.6M Sep 24 16:29 bpi-r3_emmc.img.gz
-rw-r--r-- 1 root root 105M Sep 24 21:05 noble_arm64.tar.gz
unpack imgfile (bpi-r3_noble_6.12.47-main_sdmmc.img.gz)...
setting up imgfile to loopdev...
mounting loopdev...
sh: 1: udevadm: not found
Error: Partition(s) 1, 2, 3, 4, 5, 6 on /dev/loop2 have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
sh: 1: udevadm: not found
partprobe failed

real    6m15.139s
user    0m24.980s
sys     0m4.215s
ubuntu@afe0fd51a26a:~/BPI-Router-Images$

I think it really needs a native Linux environment to build.

Here are the output files I can get, but they should be incompleted images and missing the important bpi-r3_noble_6.12.47-main.img.gz which I want to flash into eMMC:

ubuntu@afe0fd51a26a:~/BPI-Router-Images$ ll
total 7853664
drwxr-xr-x 6 ubuntu ubuntu       4096 Sep 24 21:11 ./
drwxr-x--- 1 ubuntu ubuntu       4096 Sep 24 21:12 ../
drwxr-xr-x 8 ubuntu ubuntu       4096 Sep 24 15:25 .git/
drwxr-xr-x 3 ubuntu ubuntu       4096 Sep 24 15:25 .github/
-rw-r--r-- 1 ubuntu ubuntu         48 Sep 24 15:25 .gitignore
-rw-r--r-- 1 ubuntu ubuntu       1532 Sep 24 15:25 README.md
-rw-r--r-- 1 ubuntu ubuntu   99280305 Sep 24 15:35 bpi-r3_6.12.47-main.tar.gz
-rw-r--r-- 1 ubuntu ubuntu    7865152 Sep 24 16:29 bpi-r3_emmc.img.gz
-rw-r--r-- 1 ubuntu ubuntu 7818182656 Sep 24 21:05 bpi-r3_noble_6.12.47-main_sdmmc.img
-rw-r--r-- 1 ubuntu ubuntu    7123336 Sep 24 16:27 bpi-r3_sdmmc.img.gz
-rwxr-xr-x 1 ubuntu ubuntu       4519 Sep 24 20:57 buildchroot.sh*
-rwxr-xr-x 1 ubuntu ubuntu       9315 Sep 24 15:25 buildimg.sh*
drwxr-xr-x 8 ubuntu ubuntu       4096 Sep 24 15:25 conf/
-rwxr-xr-x 1 ubuntu ubuntu        751 Sep 24 15:25 config.sh*
-rw-r--r-- 1 ubuntu ubuntu       9581 Sep 24 15:25 downloadfiles.py
-rwxr-xr-x 1 ubuntu ubuntu        329 Sep 24 15:25 getfirmware.sh*
-rwxr-xr-x 1 ubuntu ubuntu       1301 Sep 24 15:25 image.sh*
-rw-r--r-- 1 root   root    109595707 Sep 24 21:05 noble_arm64.tar.gz
-rw-r--r-- 1 ubuntu ubuntu        123 Sep 24 20:59 sourcefiles_bpi-r3.conf
drwxr-xr-x 2 root   root         4096 Sep 24 20:59 ubuntu_noble_arm64/
ubuntu@afe0fd51a26a:~/BPI-Router-Images$
52

@frank-w @ericwoud

If I have to continue building with WSL2/Docker, it is probably not able to build my own rootfs, right?

If so, how can I copy the rootfs from the SD card so I do not need to debootstrap one as suggested?

Without my own rootfs, can I still make use of my uboot (bpi-r3_sdmmc.img.gz) and kernel (bpi-r3_6.12.47-main.tar.gz)?

53

You can just copy rootfs from sdcard…it is basicly same…but copy it as root with full permissions…you can boot initrd in sdcard mode (so you can pack rootfs with tar and gzip from initrd without it be in use) and the put board in nand or emmc mode but also boot initrd and unpack to root partition…but your error above looks like your emmc is not recognized correctly or gpt is somehow strange…maybe you need to do the sgdisk fix to update backup gpt to primary one

sudo sgdisk --backup=bpi-r3_sgdisk.gpt /dev/sdb
sudo sgdisk --load-backup=bpi-r3_sgdisk.gpt /dev/sdb

But use the real device (mmcblk0) and also do this from initrd.

I have only tested buildscript in native ubuntu system. Afaik docker can no cross arch…so it always is host arch (i guess x86_64). No idea about WSL,not yet used it :stuck_out_tongue:

But why not using my already built images on gdrive.

54

I used your gpt, bl2 and fip but don’t know why it still get stucked before loading kernel:

BPI-R3> gpt read mmc 0
Partition 1:
Start 0MiB, size 0MiB
Block size 512, name gpt
Type U-Boot, bootable 0
UUID df7a38f6-9df4-11ec-a1e0-1c1b0d6d28f5
Type GUID 0fc63daf-8483-4772-8e79-3d69d8477de4

Partition 2:
Start 4MiB, size 0MiB
Block size 512, name u-boot-env
Type U-Boot, bootable 0
UUID 19a4763a-6b19-4a4b-a0c4-8cc34f4c2ab9
Type GUID 0fc63daf-8483-4772-8e79-3d69d8477de4

Partition 3:
Start 4MiB, size 2MiB
Block size 512, name factory
Type U-Boot, bootable 0
UUID 8142c1b2-1697-41d9-b1bf-a88d76c7213f
Type GUID 0fc63daf-8483-4772-8e79-3d69d8477de4

Partition 4:
Start 6MiB, size 2MiB
Block size 512, name fip
Type U-Boot, bootable 0
UUID 18de6587-4f17-4e08-a6c9-d9d3d424f4c5
Type GUID 0fc63daf-8483-4772-8e79-3d69d8477de4

Partition 5:
Start 8MiB, size 32MiB
Block size 512, name kernel
Type U-Boot, bootable 0
UUID 971f7556-ef1a-44cd-8b28-0cf8100b9c7e
Type GUID 0fc63daf-8483-4772-8e79-3d69d8477de4

Partition 6:
Start 40MiB, size 256MiB
Block size 512, name rootfs
Type U-Boot, bootable 0
UUID 309a3e76-270b-41b2-b5d5-ed8154e7542b
Type GUID 0fc63daf-8483-4772-8e79-3d69d8477de4

success!
BPI-R3> fatload usb 0:1 $loadaddr BananaPi/gpt_emmc_100m6g.img
17408 bytes read in 2 ms (8.3 MiB/s)
BPI-R3> mmc erase 0x0 0x400;mmc write ${loadaddr} 0x0 0x400
MMC erase: dev # 0, block # 0, count 1024 ... 1024 blocks erased: OK
MMC write: dev # 0, block # 0, count 1024 ... 1024 blocks written: OK
BPI-R3> setenv bl2file BananaPi/bpi-r3_emmc_bl2.img
BPI-R3> setenv fipfile BananaPi/bpi-r3_emmc_fip.bin
BPI-R3> run wremmc
bl2file=BananaPi/bpi-r3_emmc_bl2.img
200793 bytes read in 16 ms (12 MiB/s)
MMC erase: dev # 0, block # 0, count 1024 ... 1024 blocks erased: OK
MMC write: dev # 0, block # 0, count 1024 ... 1024 blocks written: OK
fipfile=BananaPi/bpi-r3_emmc_fip.bin
280749 bytes read in 21 ms (12.7 MiB/s)
MMC erase: dev # 0, block # 13312, count 4096 ... 4096 blocks erased: OK
MMC write: dev # 0, block # 13312, count 4096 ... 4096 blocks written: OK
BPI-R3> res
resetting ...

F0: 102B 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 103F 0000
F3: 1006 0033 [0200]
F3: 4001 00E0 [0200]
F3: 0000 0000
V0: 0000 0000 [0001]
00: 0000 0000
BP: 2400 0041 [0000]
G0: 1190 0000
EC: 0000 0000 [2000]
T0: 0000 021F [010F]
Jump to BL

NOTICE:  BL2: v2.12.0(release):a385740df-bpi-r3-emmc
NOTICE:  BL2: Built : 10:50:35, Aug 20 2025
NOTICE:  WDT: [40000000] Software reset (reboot)
NOTICE:  CPU: MT7986 (2000MHz)
NOTICE:  EMI: Using DDR4 settings
NOTICE:  EMI: Detected DRAM size: 2048MB
NOTICE:  EMI: complex R/W mem test passed
NOTICE:  BL2: Booting BL31
NOTICE:  BL31: v2.12.0(release):a385740df-bpi-r3-emmc
NOTICE:  BL31: Built : 10:50:38, Aug 20 2025


U-Boot 2025.07-bpi-geacd36c56c9c-dirty (Aug 20 2025 - 10:50:10 +0000)

CPU:   MediaTek MT7986
Model: BananaPi BPi-R3
DRAM:  2 GiB
Core:  48 devices, 22 uclasses, devicetree: separate
MMC:   mmc@11230000: 0
Loading Environment from MMC... Reading from MMC(0)... *** Warning - bad CRC, using default environment

In:    serial@11002000
Out:   serial@11002000
Err:   serial@11002000
=> board_late_init...
Net:   MediaTek MT7531

Warning: ethernet@15100000 (eth0) using random MAC address - 62:fa:12:db:0d:ab
eth0: ethernet@15100000
Hit any key to stop autoboot:  0


  *** U-Boot Boot Menu ***

      1. Enter kernel-name to boot from SD/EMMC.
      2. Boot kernel from TFTP.
      3. Boot from SD/EMMC.
      4. Boot kernel from NVME.
      Exit


  Press UP/DOWN to move, ENTER to select, ESC to quit



## Error: "initrd" not defined
EXT_CSD[179], PARTITION_CONFIG:
BOOT_ACK: 0x1
BOOT_PARTITION_ENABLE: 0x1 (boot0)
PARTITION_ACCESS: 0x0 (user)
emmc available
jedec_spi_nor spi_nor@0: unrecognized JEDEC id bytes: ff, ef, aa
Failed to initialize SPI flash at 0:0 (error -2)
NAND available
emmc nand
fit=bpi-r3.itb
Can't set block device
BPI-R3>

Next, I’ve built an ubuntu noble image by using your Images repo, and flashed eMMC via initrd:

# gunzip -c bpi-r3_noble_6.12.47-main_sdmmc.img.gz | dd bs=512 conv=notrunc,fsync of=/dev/mmcblk0
15269888+0 records in
15269888+0 records out
#

Boot eMMC with ubuntu noble installed:

Ubuntu 24.04.3 LTS bpi-r3 ttyS0

bpi-r3 login: root
Password:

Login incorrect
bpi-r3 login: root
Password:
Welcome to Ubuntu 24.04.3 LTS (GNU/Linux 6.12.47-bpi-r3-main aarch64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/pro

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

root@bpi-r3:~# pwd
/root
root@bpi-r3:~# cd /
root@bpi-r3:/# ls
bin                etc                lost+found  proc  sbin.usr-is-merged  usr
bin.usr-is-merged  home               media       root  srv                 var
boot               lib                mnt         run   sys
dev                lib.usr-is-merged  opt         sbin  tmp
root@bpi-r3:/#
root@bpi-r3:/# cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.3 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
root@bpi-r3:/#

Some questions here:

  1. How can I make your gpt, bl2 and fip work after flashing the eMMC?

  2. The ubuntu noble image is generated by using your pre-built u-boot bpi-r3_emmc.img.gz with my Linux bpi-r3_6.12.47-main.tar.gz. My u-boot built bpi-r3_sdmmc.img.gz instead. How can I build one for emmc like yours?

  3. The ubuntu noble image is missing executable such as ifconfig and iwconfig. How can I get them build-in? Is it needed to customize Linux packages or just append from userpackages in sourcefiles_bpi-r3.conf?

  4. Your Images repo script does not support specific flags for emmc and nand, right?

Thanks.

55

Strange,…have you tried the sgdisk fix above?

The fixed gpt images are an older way and should not be used anymore. I create partitions in my uboot repo in mtk_atf_2025 branch via sgdisk as this is more portable and can be adjusted if needed.

Regarding ifconfig and iwconfig…these are deprecated long time ago and “new” commands are ip (iproute2) and iw

What do you mean with flags for emmc and nand? Building images for these? I started sone time ago,but there are some depencies that have to be fixed for it…afair uboot already creates emmc base image already for r3 and r4,but i have to download the right file when building the image. Nand is currently separate branch “nand” which creates an ubinized image that have to be flashed to ubi mtd partition (bl2 is separate) this contains fip,kernel initrd and config.

56

For sgdisk, is this how it is used? (I can pend this problem as I am now able to build an ubuntu image myself.)

# sgdisk --backup=bpi-r3_sgdisk.gpt /dev/mmcblk0
Warning! Main partition table overlaps the first partition by 34 blocks!
You will need to delete this partition or resize it in another utility.
The operation has completed successfully.
#

So ip and iw commands should be modern. How can I install iproute2 in image? Have to customize Linux packages or append iproute2 from sourcefiles_bpi-r3.conf?

How to build bpi-r3_emmc.img.gz from u-boot repo? I just got bpi-r3_sdmmc.img.gz instead.

To continue the above statement, “Flags for emmc/nand” means to adjust the “device” variable as emmc/nand from build.conf in your u-boot repo. Then users would run “./build.sh createimg” to generate a bpi-r3_*.img.gz file. Now I can only generate bpi-r3_sdmmc.img.gz. Any ways to generate for other types?

I’ll take a look into the Images repo - “nand” branch.

Thanks.

57

Uboot repo already creates emmc base image

It only has to be filled with rootfs and kernel (what my images repo did).you can set the ubootfile in the sourcefiles_bpi-r3.conf to skip download.see readme in images repo

Iproute2 is already installed

58 
ubuntu@afe0fd51a26a:~/u-boot$ ./build.sh createimg
ver:2025.07,ubranch:bpi
emmc not supported
ubuntu@afe0fd51a26a:~/u-boot$ cat build.conf 
uploaduser=$USER
uploadserver=r2
uploaddir=/var/lib/tftp

#board=bpi-r2
#board=bpi-r64
#board=bpi-r2pro
board=bpi-r3
#board=bpi-r3mini
#board=bpi-r4

device=emmc
#device=spi-nand
#device=spi-nor
ubuntu@afe0fd51a26a:~/u-boot$ find -name *.img.gz
./bpi-r3_sdmmc.img.gz
ubuntu@afe0fd51a26a:~/u-boot$ git branch
* 2025-07-bpi
ubuntu@afe0fd51a26a:~/u-boot$

emmc not supported

So your “2025-07-bpi” branch does not support for creating emmc base image. Your upstream branch is “mtk-atf-2025”?

Besides, in Images repo, which kind of packages can be added into? For instance, memtester and net-snmp ok?

image

59

You are aware that you can install any package, once running from that image? Using:

sudo apt install
60

The base image is created by atf code after uboot is built. See pipeline above… First compile uboot with device=emmc and then atf with same and run build.sh createimg to ger the base image.

For images repo i meant this

skipubootdownload=1
imgfile=bpi-r4_sdmmc.img.gz

To use the emmc base image.

But basicly you can pass all packages found by apt,but i do not add them by default…only thinking adding basic network packages like ethtool

61

Thanks. It works after I connect the board to WAN.

62

@ericwoud @frank-w

Do you know how to flash back the NAND into Openwrt firmware? As I have Ubuntu installed in eMMC while the NAND is not bootable individually.

At the very beginning, I flashed both NOR & NAND like this:

mtd erase /dev/mtd0
dd if=mtk-bpi-r3-NAND-WAN1-RJ45-20220720-single-image.bin of=/dev/mtdblock0

After these days I modified the NAND, their partitions became different.

My Openwrt NOR:

root@OpenWrt:/# cat proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00010000 "BL2"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 000b0000 00010000 "Factory"
mtd3: 00080000 00010000 "FIP"
mtd4: 00e00000 00010000 "firmware"
root@OpenWrt:/#

My Ubuntu eMMC with NAND access:

root@bpi-r3:/# cat proc/mtd
dev:    size   erasesize  name
mtd0: 07a80000 00020000 "ubi"
mtd1: 00200000 00020000 "fip"
mtd2: 00280000 00020000 "reserved"
mtd3: 00100000 00020000 "bl2"
root@bpi-r3:/#

I think it has to be flashed to BL2 but it can’t:

root@bpi-r3:/mnt# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 07a80000 00020000 "ubi"
mtd1: 00200000 00020000 "fip"
mtd2: 00280000 00020000 "reserved"
mtd3: 00100000 00020000 "bl2"
root@bpi-r3:/mnt#
root@bpi-r3:/mnt# sudo dd if=mtk-bpi-r3-NAND-WAN1-RJ45-20220720-single-image.bin of=/dev/mtdblock3
dd: writing to '/dev/mtdblock3': Operation not permitted
1+0 records in
0+0 records out
0 bytes copied, 0.000141153 s, 0.0 kB/s
root@bpi-r3:/mnt# flash_erase /dev/mtd3 0 0
flash_erase: error!: /dev/mtd3
             error 13 (Permission denied)
root@bpi-r3:/mnt#
63

This is defined in the devicetree of the system that is booting. Not sure if this is the same on the openwrt version you want to use.

Also in this devicetree, this partition is set as read-only. You’ll need to remove this from the dts, or write to the partition from U-Boot

Also, if you want to write to mtd on linux, the dts may be missing properties to nand, which I don’t know if @frank-w added that to the dts in the Ubuntu image you are using. See:

64

For R3 i have not added mtd partitions afaik

65

Here you have the partitions.

Including the read-only property.

Edit:

In some cases I saw you also added the ubi-volumes to the dts(o). That I believe is abundant, as the setup of the ubi-volumes is already stored on the ubi-partition. Also defining them in the dts(o) would be the second definition of the ubi-volumes and, when not corresponding, may lead to errors.

66

The desired Openwrt devicetree partition is different to that of my NAND partition. It should be the same as the Openwrt NOR:

root@OpenWrt:/# cat proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00010000 "BL2"
mtd1: 00010000 00010000 "u-boot-env"
mtd2: 000b0000 00010000 "Factory"
mtd3: 00080000 00010000 "FIP"
mtd4: 00e00000 00010000 "firmware"
root@OpenWrt:/#

Previously, I flashed Openwrt single-image to the NOR /dev/mtdblock0 which should be referring to the “BL2”, right?

Do you have experience on flashing Openwrt images to NAND from u-boot?

67

No I try to always use linux

68

I have just re-flashed the entire NAND with Openwrt single image from u-boot. It does work.

BPI-R3> run useusb
USB is stopped. Please issue 'usb start' first.
starting USB...
xhci-mtk xhci@11200000: hcd: 0x0000000011200000, ippc: 0x0000000011203e00
xhci-mtk xhci@11200000: ports disabled mask: u3p-0x0, u2p-0x0
xhci-mtk xhci@11200000: u2p:2, u3p:1
Register 300010f NbrPorts 3
Starting the controller
USB XHCI 1.10
Bus xhci@11200000: 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
            System Volume Information/
   200072   bl2_emmc.img
    17408   gpt_emmc_100m6g.img
 16546559   rootfs_arm64.cpio.zst
 27956672   mtk-bpi-r3-NOR-WAN1-RJ45-20220720-single-image.bin
 69584284   mtk-bpi-r3-EMMC-WAN1-RJ45-20220720-single-image.img
 38666240   mtk-bpi-r3-NAND-WAN1-RJ45-20220720-single-image.bin
  9699328   openwrt-mediatek-filogic-bananapi_bpi-r3-initramfs-recovery.itb
  9518220   bpi-r3.itb
 99280305   bpi-r3_6.12.47-main.tar.gz
  7865152   bpi-r3_emmc.img.gz
   200793   bpi-r3_emmc_bl2.img
   280749   bpi-r3_emmc_fip.bin
 727753804   bpi-r3_noble_6.12.47-main_sdmmc.img.gz
   209616   bpi-r3_spim-nand_bl2.img
   279581   bpi-r3_spim-nand_fip.bin
            WAP7633/

15 file(s), 2 dir(s)

BPI-R3> mtd list
jedec_spi_nor spi_nor@0: unrecognized JEDEC id bytes: ff, ef, aa
List of MTD devices:
* spi-nand0
  - device: spi_nand@1
  - parent: spi@1100a000
  - driver: spi_nand
  - path: /spi@1100a000/spi_nand@1
  - type: NAND flash
  - block size: 0x20000 bytes
  - min I/O: 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"
BPI-R3> mtd erase spi-nand0
jedec_spi_nor spi_nor@0: unrecognized JEDEC id bytes: ff, ef, aa
Erasing 0x00000000 ... 0x07ffffff (1024 eraseblock(s))
BPI-R3> fatload usb 0:1 $loadaddr mtk-bpi-r3-NAND-WAN1-RJ45-20220720-single-image.bin
38666240 bytes read in 2766 ms (13.3 MiB/s)
BPI-R3> mtd write spi-nand0 $loadaddr 0x0 0x8000000
jedec_spi_nor spi_nor@0: unrecognized JEDEC id bytes: ff, ef, aa
Writing 134217728 byte(s) (65536 page(s)) at offset 0x00000000
BPI-R3>