Differences

This shows you the differences between two versions of the page.

--- en:bpi-r3:uboot [2023/04/06 19:05] – [nor flash] frank
+++ en:bpi-r3:uboot [2024/04/07 09:39] (current) – [writing emmc] frank
@@ Line 69: / Line 69: @@
   BPI-R3> run newboot
-  #using spi dt-overlay
+  #using dt-overlay config
   BPI-R3> setenv bootconf "#conf-sd-nor" #conf-sd-nor=sd base dts + nor dt overlay
@@ Line 172: / Line 172: @@
 and use the resulting u-boot.bin.xz as BL33
+==== kernel/initrd ====
+currently untested...
+<code>
+label = "recovery"; //initrd max 10MB
+reg = <0x180000 0xa80000>;
+label = "fit"; //kernel max 20MB
+reg = <0xc00000 0x1400000>;
+</code>
+<code>
+MT7986> sf probe
+SF: Detected w25q256 with page size 256 Bytes, erase size 4 KiB, total 32 MiB
+MT7986> sf erase 0x180000 0xa80000
+SF: 11010048 bytes @ 0x180000 Erased: OK
+MT7986> fatload usb 0:1 ${loadaddr} rootfs_bpi-r3.cpio.zst
+9501203 bytes read in 798 ms (11.4 MiB/s)
+MT7986> sf write ${loadaddr} 0x180000 ${filesize}
+device 0 offset 0x180000, size 0x90fa13
+SF: 9501203 bytes @ 0x180000 Written: OK
+MT7986> sf erase 0xc00000 0x1400000
+SF: 20971520 bytes @ 0xc00000 Erased: OK
+MT7986> fatload usb 0:1 ${loadaddr} bpi-r3-6.1.itb
+8424540 bytes read in 708 ms (11.3 MiB/s)
+MT7986> sf write ${loadaddr} 0xc00000 ${filesize}
+device 0 offset 0xc00000, size 0x808c5c
+SF: 8424540 bytes @ 0xc00000 Written: OK
+</code>
+loading it:
+<code>
+MT7986> setenv useinitrd 'setenv root "/dev/ram0 rw";setenv bootopts "${bootopts} initrd=${rdaddr},20M";'
+MT7986> sf read ${rdaddr} 0x180000 0xa80000
+device 0 offset 0x180000, size 0xa80000
+SF: 11010048 bytes @ 0x180000 Read: OK
+MT7986> sf read ${kaddr} 0xc00000 0x1400000
+device 0 offset 0xc00000, size 0x1400000
+SF: 20971520 bytes @ 0xc00000 Read: OK
+MT7986> setenv bootnor 'run useinitrd;run setbootconf; run buildargs; bootm ${kaddr}${bootconf};'
+MT7986> run bootnor
+</code>
 ===== usb =====
@@ Line 213: / Line 258: @@
 </code>
 ===== writing emmc =====
+:!: newest atf for mediatek needs gpt with fip partition so it must be created first (maybe copy first 1M from sdcard to emmc).
 get emmc/gpt information:
@@ Line 360: / Line 407: @@
 now flash bl2 to boot0 block and fip to fip partition
+short way using my environment:
+<code>
+MT7986> setenv bl2file 2023.04/bpi-r3_emmc_bl2.img
+MT7986> setenv fipfile 2023.04/bpi-r3_emmc_fip.bin
+MT7986> run wremmc
+bl2file=2023.04/bpi-r3_emmc_bl2.img
+bytes read in 20 ms (9.3 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=2023.04/bpi-r3_emmc_fip.bin
+bytes read in 58 ms (10.6 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
+</code>
+manual way:
+<hidden>
 <code>
 BPI-R3> mmc dev 0
@@ Line 386: / Line 454: @@
 BPI-R3>
 </code>
+</hidden>
 If boot from emmc does not work,maybe bootbus needs to be changed to 0: