[Tutorial] Build, customize and use MediaTek open-source U-Boot and ATF

ericwoud · November 4, 2022, 12:06pm

Still trying to get ATF v2.7 to reboot on R64… See above.

Do you guys think there is a kernel/dts patch that I’m missing, which will cause the kernel not to reboot, when starting from ATF v2.7?

Perhapse a Mhz setting in the operating-points? Or perhapse the L2 cache patch in dts? Anyone knows?

frank-w · December 27, 2022, 8:10am

Sorry for late response…maybe this:

https://lore.kernel.org/all/[email protected]/T/#rdf4176e65da050b8125edf90ab2f0753147bff90

Do you use the ddr_flyby option for r64 (in my r64 atf repo i do not use it afaik)? I try to integrate weijis current state into my uboot repo to have one atf branch for r64 and r3…

@ericwoud can you confirm that it fixes your issue?

@dangowrt can you please repost this fix?

@hackpascal daniel mentioned that this should be fixed in TF-A too…have you done this already? it looks like we have similar issue on r3/mt7986…reboot hangs in uboot and it cannot access sdcard (but i have not tried your new source from here as i struggle with correct flags)

tried to use the new TF-A code for bpi-r3 (and created gpt with sgdisk instead of flashing the broken gpt img)

F0: 102B 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 103F 0000
F3: 1001 0000 [0200]
F3: 1001 0000
F6: 300C 0028
F5: 480C 0000
00: 1005 0000
FA: 1040 0000
FA: 1040 0000 [0200]
F9: 103F 0000
F3: 1001 0000 [0200]
F3: 1001 0000
F6: 300C 0028
01: 102A 0001
02: 1005 0000
BP: 2000 00C0 [0001]
EC: 0000 0000 [3000]
T0: 0000 0182 [010F]
System halt!

built u-boot.bin from 2022-10-r3 branch, switched to mtk-atf branch, build it and created image with createimg command (using values 100 for boot and 6144 for root to have same sectors as my current gpt created by your py2-script)

github.com

frank-w/u-boot/blob/mtk-atf/build.sh

#!/bin/bash
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-

board="bpi-r3"
#board="bpi-r64"
device="sdmmc"
#device="emmc"
#device="spim_nand"
#device="spim_nor"

#https://forum.banana-pi.org/t/tutorial-build-customize-and-use-mediatek-open-source-u-boot-and-atf/13785/
mkimg="USE_MKIMAGE=1 MKIMAGE=./tools/mkimage"

if [[ -e build.conf ]];then
       . build.conf
fi

case $device in
	"spi-nand") device="spim_nand";;

This file has been truncated. show original

partitiontable looks good for me:

non-working:

Number  Start (sector)    End (sector)  Size       Code  Name
   1              34            8191   4.0 MiB     8300  bl2
   2            8192            9215   512.0 KiB   8300  u-boot-env
   3            9216           13311   2.0 MiB     8300  factory
   4           13312           17407   2.0 MiB     8300  fip
   5           17408          222207   100.0 MiB   8300  boot
   6          222208        12805120   6.0 GiB     8300  rootfs

working (from py2 gpt-img):

Number  Start (sector)    End (sector)  Size       Code  Name
   1              34            8191   4.0 MiB     8300  bl2
   2            8192            9215   512.0 KiB   8300  u-boot-env
   3            9216           13311   2.0 MiB     8300  factory
   4           13312           17407   2.0 MiB     8300  fip
   5           17408          222207   100.0 MiB   8300  kernel
   6          222208        12805120   6.0 GiB     8300  rootfs

content of bl2-partition looks a bit different (maybe caused by mkimage usage?):

non-working:

00000000  53 44 4d 4d 43 5f 42 4f  4f 54 00 ff 01 00 00 00  |SDMMC_BOOT......|
00000010  00 02 00 00 ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00000200  42 52 4c 59 54 00 00 00  01 00 00 00 00 4a 00 00  |BRLYT........J..|
00000210  88 51 03 00 42 42 42 42  08 00 01 00 00 06 00 00  |.Q..BBBB........|
00000220  88 51 03 00 ff ff ff ff  ff ff ff ff ff ff ff ff  |.Q..............|
00000230  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00000600  4d 4d 4d 01 38 00 00 00  46 49 4c 45 5f 49 4e 46  |MMM.8...FILE_INF|
00000610  4f 00 00 00 01 00 00 00  01 00 05 01 00 0d 20 00  |O............. .|
00000620  88 07 03 00 88 0d 03 00  00 03 00 00 20 00 00 00  |............ ...|
00000630  00 03 00 00 01 00 00 00  4d 4d 4d 01 0c 00 01 00  |........MMM.....|
00000640  01 00 00 00 4d 4d 4d 01  14 00 02 00 00 00 00 00  |....MMM.........|
00000650  10 00 00 00 80 00 00 00  4d 4d 4d 01 14 02 03 00  |........MMM.....|
00000660  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

working (old bpi-atf source):

00000000  53 44 4d 4d 43 5f 42 4f  4f 54 00 ff 01 00 00 00  |SDMMC_BOOT......|
00000010  00 02 00 00 ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00000200  42 52 4c 59 54 00 00 00  01 00 00 00 00 06 00 00  |BRLYT...........|
00000210  88 fd 02 00 42 42 42 42  08 00 01 00 00 06 00 00  |....BBBB........|
00000220  88 fd 02 00 ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000230  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00000600  4d 4d 4d 01 38 00 00 00  46 49 4c 45 5f 49 4e 46  |MMM.8...FILE_INF|
00000610  4f 00 00 00 01 00 00 00  01 00 05 01 00 0d 20 00  |O............. .|
00000620  88 f7 02 00 88 fd 02 00  00 03 00 00 20 00 00 00  |............ ...|
00000630  00 03 00 00 01 00 00 00  4d 4d 4d 01 0c 00 01 00  |........MMM.....|
00000640  01 00 00 00 4d 4d 4d 03  64 00 07 00 90 11 00 00  |....MMM.d.......|
00000650  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|

mhm, flashed old bl2/fip to the new parttable, and got same system-halt…so maybe i miss something in gpt (flags??)…old gpt with new atf works…so anything i miss in gpt-creation

took me some time to read out the information, but it looks like the legacy bootable flag is needed…do not know yet how to set it with sgdisk, but gdisk prints this when i read the working gpt

Expert command (? for help): a       
Partition number (1-6): 1
Known attributes are:
0: system partition
1: hide from EFI
2: legacy BIOS bootable
60: read-only
62: hidden
63: do not automount

Attribute value is 0000000000000004. Set fields are:
2 (legacy BIOS bootable)

seems that was the problem…got it set by this

sudo sgdisk --attributes=1:set:2 ${LDEV}

after that bl2 got loaded

ericwoud · December 27, 2022, 7:57pm

I’ve tried the opp 3000000 fix before, did not work. I just tried it again, to make sure, but it does not help.

I am building with DDR3_FLYBY=1

The only thing I change is the branch I build, everything else is exactly the same. v2.7 hangs at reboot while v2.4 does not.

So _gitbranch=“mtksoc” Hangs at reboot

And _gitbranch=“mtksoc-20210508” Does not hang at reboot.

On the R64 that is. And I don’t hang at u-boot, but it hangs totally not restarting from the very first visible byte on the uart output. Sounds like a different hang then the one you were experiencing.

frank-w · December 29, 2022, 2:10pm

tried this ATF on r64 (needed some time to get it working due to the strange MBR/GPT mix)…

at least after booting into uboot and issue “reset” board boots into uboot again…so i guess it is a linux setting breaking reboot in ATF (similar to the Patch from Daniel i’m pointing above). do not have a rootfs on my new card…i hope i find time to check this.

at least uboot 2022-10 with this ATF is completely build in my github for r64/r3 including sd-card images (bootchain only, no rootfs)

https://github.com/frank-w/u-boot/tree/2022-10-bpi (+ mtk-atf branch)

huangya · January 3, 2023, 11:43am

@hackpascal

Below command should miss the CROSS_COMPILE option.

make -f Makefile PLAT= BOOT_DEVICE= BL33=<path-to-u-boot.bin> all fip

ENABLE_JTAG=

This option is valid only when PLAT is mt7981/mt7988

Typo? I think it’s mt7986 instead of mt7988. Here is the grep output of ATF code.

% grep ENBLE_JTAG . -r
./plat/mediatek/mt7981/platform.mk:ENABLE_JTAG          ?=      0
./plat/mediatek/mt7981/platform.mk:ifeq ($(ENABLE_JTAG), 1)
./plat/mediatek/mt7981/platform.mk:CPPFLAGS             +=      -DENABLE_JTAG
./plat/mediatek/mt7981/platform.mk:$(call MAKE_DEP,bl2,mt7981_gpio,ENABLE_JTAG)
./plat/mediatek/mt7981/drivers/gpio/mt7981_gpio.c:#ifdef ENABLE_JTAG
./plat/mediatek/mt7986/platform.mk:ENABLE_JTAG          ?=      0
./plat/mediatek/mt7986/platform.mk:ifeq ($(ENABLE_JTAG), 1)
./plat/mediatek/mt7986/platform.mk:CPPFLAGS             +=      -DENABLE_JTAG
./plat/mediatek/mt7986/platform.mk:$(call MAKE_DEP,bl2,mt7986_gpio,ENABLE_JTAG)
./plat/mediatek/mt7986/drivers/gpio/mt7986_gpio.c:#ifdef ENABLE_JTAG

Have you tested the JTAG in the BPI-R3? I compiled the ATF with option ENABLE_JTAG=1.

ericwoud · January 21, 2023, 11:43am

I’ve tried

 		opp-300000000 {
 - 			opp-hz = /bits/ 64 <30000000>;
 -			opp-microvolt = <950000>;
 +			opp-hz = /bits/ 64 <300000000>;
 +			opp-microvolt = <1000000>;
  		};

As here

Suggests that it may get stuck without this patch. This patch also does not work. Reboot in ATF 2.7 still gets stuck in my build on the R64.

I’ve also tried totally removing the opp-300000000 node, but it makes no difference.

ericwoud · February 21, 2023, 1:43pm

I have have tried out the 2 branches of mtksoc and mtksoc-20210508. I converted them to patches. After some changes to the patches I could apply the patches to the same commit of the original ATF repo. And even then the mtksoc version still did not reboot on the R64. This for me had ruled out that this is an ATF upgrade problem. It is somewhere in the newest series of commits in the mtksoc branch. Something not compatible with R64 (when it reboots with psci?).

Anyway, I now have created a minimal fork of mtksoc/mtksoc-20210508 combined, specifically for bpir64. It is rebased to the newest ATF firmware of today, and it reboots

https://github.com/ericwoud/arm-trusted-firmware/tree/bpir64

frank-w · February 21, 2023, 8:24pm

Have you compared the rebased working version with the original with the issue?

ericwoud · February 22, 2023, 9:03am

I have kept the change from original ATF as minimal as possible. I have only applied the following commits (from 2021 v2.4 branch and 2022 v2.7 branch)

2022: build_macros.mk: add support to use prebuilt libraries
2022: mmc: do not check mmc_csd.spec_vers for eMMC
2022: mediatek: common: add MediaTek SD/eMMC controller driver
2022: mediatek: common: add generic high-speed UART console driver
2021: mediatek: mt7622: add initial BL2/BL31 support
2021: mediatek: mt7622: add DDR initialization support

There were some changes to the SPSR code, so the 64-bit U-Boot/Kernel support is moved inside the initial BL2/BL31 support commit, as it was necessary for rebasing.

So there are a lot of differences from the v2.7 branch of openwrt.

I’ve also added my own changes to the branch as well, but if you just build it, it can be used as if my patches are not applied and have it start (a 64 bit) U-Boot.

PS: I’ve ordered a R3 and I plan to add this one to my fork of ATF as well.I believe I can have it start a initrd directly from atf (as with R64 already possible). Then from the initrd load an image to ram and then switch from sd to emmc. Then finally flash the emmc from ramdisk. This way no need to use nand as an in between step… In theory…

frank-w · February 22, 2023, 10:03am

Maybe @hackpascal can look at the diff and find reboot-breaking change?

You want to switch sd to emmc while system is running? How do you want to trigger kernel looking for device change of mmc controller with different dts-setting? I don’t think this can work…

ericwoud · March 3, 2023, 1:11pm

@frank-w: I’m looking at the bl1 -> bl2 sequence. I’ve noticed that for R3 you do not write any header:

github.com

frank-w/u-boot/blob/760f1effb8022e64f7abdeea9ed32a134be3ea8d/build.sh#L122


				rootend=$(( ${rootstart} + (${rootsize}*1024*2) ))
				sudo sgdisk -o ${LDEV}
				sudo sgdisk -a 1 -n 1:34:8191 -A 1:set:2 -t 1:8300 -c 1:"bl2"		${LDEV}
				#sudo sgdisk --attributes=1:set:2 ${LDEV}
				sudo sgdisk -a 1 -n 2:8192:9215		-t 2:8300 -c 2:"u-boot-env"	${LDEV}
				sudo sgdisk -a 1 -n 3:9216:13311	-t 3:8300 -c 3:"factory"	${LDEV}
				sudo sgdisk -a 1 -n 4:13312:17407	-t 4:8300 -c 4:"fip"		${LDEV}
				sudo sgdisk -a 1024 -n 5:17408:${bootend} -t 5:8300 -c 5:"boot"		${LDEV}
				sudo sgdisk -a 1024 -n 6:${rootstart}:${rootend} -t 6:8300 -c 6:"rootfs" ${LDEV}


				#sudo dd if=gpt_${device}_100m6g.img of=$LDEV conv=notrunc,fsync #1> /dev/null 2>&1
				#try to repair MBR/GPT
				#sudo sgdisk --backup=bpi-r3_sgdisk.gpt /dev/sdb
				#sudo sgdisk --load-backup=bpi-r3_sgdisk.gpt /dev/sdb
				#re-read part table
				sudo losetup -d $LDEV
				sudo losetup -P $LDEV $IMGDIR/$IMGNAME.img 1> /dev/null #2>&1


				#sudo partprobe $LDEV #1> /dev/null 2>&1
				sudo dd if=build/${PLAT}/release/bl2.img of=${LDEV}p1 conv=notrunc,fsync #1> /dev/null 2>&1
				sudo dd if=build/${PLAT}/release/fip.bin of=${LDEV}p4 conv=notrunc,fsync #1> /dev/null 2>&1

It is commented out…

Does the R3 not require any header? Is it enough the set legacy boot bit of the bl2 partition in GPT table?

Before you mentioned this as the start of sector 0:

frank-w:

00000000 53 44 4d 4d 43 5f 42 4f 4f 54 00 ff 01 00 00 00 |SDMMC_BOOT......| 
00000010 00 02 00 00 ff ff ff ff ff ff ff ff ff ff ff ff |................| 
00000020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff |................|

Which does seem like a header. Or did it turn out this was not necessary?

frank-w · March 3, 2023, 1:41pm

The line you mention was the binary gpt i flashed before (created by python2 script in mtk-code).

It is enough creating the gpt with bootable bl2 and writing the right bl2 binary (there is a bin and an img file) there

ericwoud · March 15, 2023, 4:53pm

On the BPI-R3, there is a small side affect when only switching switch D down (and leaving the rest up).

In this combination, it is possible to load the bl2 from sector 34 an up on the EMMC, from /dev/mmcblk0. The difference is that mmcblk0boot0 is not being used. bl2 gets written together with the rest of the image.

This way the entire image needs only written to 1 device (similar to SDMMC).

In the makefile, change all declarations:

BROM_HEADER_TYPE	:=
to
BROM_HEADER_TYPE	?=

and then build an emmc atf image, passing BOOT_DEVICE=emmc and BROM_HEADER_TYPE=sdmmc on the make command line.

Elijah · June 21, 2023, 7:41am

On the BPI-R3, add new spi nand Flash(QE bit set 0 off default). but NMBM don’t support, all block be sacnned bad block, also i add spim driver .C file’s .init struct setting, not work again. Could you take me how to fix it?

startup err log: …

spi nand driver file’s init struct:

NMBM LA data(By Acute logic analyzer): (That show nmbm set ecc off, and not set QE bit =1)

QE bit by spec.:

spi nand driver files: xtxtech.c (5.6 KB)

Elijah · June 26, 2023, 1:59am

I get it, Add “arm-trusted-firmware/drivers/mtd/nand/spi_nand.c” new line 127,Flash ID, then QE enble set.

But one new conundrum has emerged, Error log stop that “NOTICE: NMBM has been initialized in read-only mode”

frank-w · June 27, 2023, 3:58pm

is there some ATF/uboot-code for mt7988?

hackpascal · June 27, 2023, 6:04pm

in progress. i’m preparing the atf code now.

Elijah · July 10, 2023, 3:37am

Hi, i use "snfi" config for uboot & atf, but dont working, is my configs error?<br/>
<br/>
<b>err info(powerup from spim, flash ecc config):</b><br/>
<br/>
[2023/7/10 10:50:07] F0: 102B 0000<br/>
[2023/7/10 10:50:07] FA: 1040 0000<br/>
[2023/7/10 10:50:07] FA: 1040 0000 [0200]<br/>
[2023/7/10 10:50:07] F9: 0000 0000<br/>
[2023/7/10 10:50:07] V0: 0000 0000 [0001]<br/>
[2023/7/10 10:50:07] 00: 0000 0000<br/>
[2023/7/10 10:50:07] BP: 2400 0041 [0000]<br/>
[2023/7/10 10:50:07] G0: 1190 0000<br/>
[2023/7/10 10:50:07] EC: 0000 0000 [1000]<br/>
[2023/7/10 10:50:07] T0: 0000 021E [010F]<br/>
[2023/7/10 10:50:07] Jump to BL<br/>
[2023/7/10 10:50:07] <br/>
[2023/7/10 10:50:07] NOTICE:  BL2: v2.7(release):v2.4-rc0-2957-g753934848-dirty<br/>
[2023/7/10 10:50:07] NOTICE:  BL2: Built : 10:15:50, Jul 10 2023<br/>
[2023/7/10 10:50:07] NOTICE:  WDT: disabled<br/>
[2023/7/10 10:50:08] NOTICE:  CPU: MT7986 (2000MHz)<br/>
[2023/7/10 10:50:08] NOTICE:  EMI: Using DDR4 settings<br/>
[2023/7/10 10:50:08] NOTICE:  EMI: Detected DRAM size: 2048MB<br/>
[2023/7/10 10:50:08] NOTICE:  EMI: complex R/W mem test passed<br/>
[2023/7/10 10:50:08] NOTICE:  SPI_NAND parses attributes from parameter page.<br/>
[2023/7/10 10:50:08] NOTICE:  SPI_NAND Detected ID 0xef<br/>
[2023/7/10 10:50:08] NOTICE:  Page size 2048, Block size 131072, size 134217728<br/>
[2023/7/10 10:50:08] NOTICE:  Initializing NMBM ...<br/>
[2023/7/10 10:50:10] NOTICE:  NMBM management region starts at block 960 [0x07800000]<br/>
[2023/7/10 10:50:10] NOTICE:  NMBM has been initialized in read-only mode<br/>
[2023/7/10 10:50:11] NOTICE:  BL2: Booting BL31<br/>
[2023/7/10 10:50:11] NOTICE:  BL31: v2.7(release):v2.4-rc0-2957-g753934848-dirty<br/>
[2023/7/10 10:50:11] NOTICE:  BL31: Built : 10:15:51, Jul 10 2023<br/>
[2023/7/10 10:50:11] <br/>
[2023/7/10 10:50:11] <br/>
[2023/7/10 10:50:11] U-Boot 2022.10-rc3-10199-gcac27537e1-dirty (Jul 10 2023 - 10:14:58 +0800)<br/>
[2023/7/10 10:50:11] <br/>
[2023/7/10 10:50:11] CPU:   MediaTek MT7986<br/>
[2023/7/10 10:50:11] Model: mt7986-rfb<br/>
[2023/7/10 10:50:11] DRAM:  2 GiB<br/>
[2023/7/10 10:50:11] Core:  47 devices, 18 uclasses, devicetree: separate<br/>
[2023/7/10 10:50:11] <br/>
[2023/7/10 10:50:11] Initializing NMBM ...<br/>
[2023/7/10 10:50:11] spi-nand: spi_nand spi_nand@1: Winbond SPI NAND was found.<br/>
[2023/7/10 10:50:11] spi-nand: spi_nand spi_nand@1: 128 MiB, block size: 128 KiB, page size: 2048, OOB size: 64<br/>
[2023/7/10 10:50:11] Could not find a valid device for nmbm0<br/>
[2023/7/10 10:50:12] NMBM management region starts at block 960 [0x07800000]<br/>
[2023/7/10 10:50:12] Signature has been written to block 1023 [0x07fe0000]<br/>
[2023/7/10 10:50:12] Main info table has been written to block 960<br/>
[2023/7/10 10:50:12] Backup info table has been written to block 963<br/>
[2023/7/10 10:50:12] NMBM has been successfully created<br/>
[2023/7/10 10:50:12] <br/>
[2023/7/10 10:50:12] MMC:   mmc@11230000: 0<br/>
[2023/7/10 10:50:12] Loading Environment from MTD... *** Warning - bad CRC, using default environment<br/>
[2023/7/10 10:50:12] <br/>
[2023/7/10 10:50:12] In:    serial@11002000<br/>
[2023/7/10 10:50:12] Out:   serial@11002000<br/>
[2023/7/10 10:50:12] Err:   serial@11002000<br/>
[2023/7/10 10:50:13] Net:   <br/>
[2023/7/10 10:50:13] Warning: ethernet@15100000 (eth0) using random MAC address - ba:4d:d1:8b:8b:19<br/>
[2023/7/10 10:50:13] eth0: ethernet@15100000<br/>
[2023/7/10 10:50:17]   *** U-Boot Boot Menu ***<br/>
      1. Startup system (Default)<br/>
      2. Upgrade firmware<br/>
      3. Upgrade ATF BL2<br/>
      4. Upgrade ATF FIP<br/>
      5. Upgrade single image<br/>
      6. Load image<br/>
      0. U-Boot console<br/>
  Press UP/DOWN to move, ENTER to select, ESC/CTRL+C to quit<br/>
[2023/7/10 10:50:17] *** Upgrading ATF BL2 ***<br/>
[2023/7/10 10:50:17] <br/>
[2023/7/10 10:50:17] Available load methods:<br/>
[2023/7/10 10:50:17]     0 - TFTP client (Default)<br/>
[2023/7/10 10:50:17]     1 - Xmodem<br/>
[2023/7/10 10:50:17]     2 - Ymodem<br/>
[2023/7/10 10:50:17]     3 - Kermit<br/>
[2023/7/10 10:50:17]     4 - S-Record<br/>
[2023/7/10 10:50:17] <br/>
[2023/7/10 10:50:19] Select (enter for default): <br/>
[2023/7/10 10:50:19] <br/>
[2023/7/10 10:50:20] Input U-Boot's IP address: 192.168.1.1<br/>
[2023/7/10 10:50:22] Input TFTP server's IP address: 192.168.1.254<br/>
[2023/7/10 10:50:23] Input IP netmask: 255.255.255.0<br/>
<b>[2023/7/10 10:50:38] Input file name: bl2_snfi_20230710.img</b><br/>
[2023/7/10 10:50:38] <br/>
[2023/7/10 10:50:38] Using ethernet@15100000 device<br/>
[2023/7/10 10:50:38] TFTP from server 192.168.1.254; our IP address is 192.168.1.1<br/>
[2023/7/10 10:50:38] Filename 'bl2_snfi_20230710.img'.<br/>
[2023/7/10 10:50:38] Load address: 0x46000000<br/>
[2023/7/10 10:50:38] Loading: ################<br/>
[2023/7/10 10:50:38] 	 1.2 MiB/s<br/>
[2023/7/10 10:50:38] done<br/>
[2023/7/10 10:50:38] Bytes transferred = 225184 (36fa0 hex)<br/>
[2023/7/10 10:50:38] Saving Environment to MTD... Erasing on MTD device 'u-boot-env'... OK<br/>
[2023/7/10 10:50:38] Writing to MTD device 'u-boot-env'... OK<br/>
[2023/7/10 10:50:38] OK<br/>
[2023/7/10 10:50:38] <br/>
[2023/7/10 10:50:38] *** Loaded 225184 (0x36fa0) bytes at 0x46000000 ***<br/>
[2023/7/10 10:50:38] <br/>
[2023/7/10 10:50:38] Erasing 'bl2' from 0x0, size 0x40000 ... OK<br/>
[2023/7/10 10:50:38] Writing 'bl2' from 0x46000000 to 0x0, size 0x36fa0 ... OK<br/>
[2023/7/10 10:50:38] <br/>
[2023/7/10 10:50:38] *** ATF BL2 upgrade completed! ***<br/>
[2023/7/10 10:50:42] MT7986> <br/>
[2023/7/10 10:50:42] MT7986> <br/>
[2023/7/10 10:50:43] MT7986> <br/>
<b>[2023/7/10 10:50:48] MT7986> mtkautoboot </b><br/>
[2023/7/10 10:50:50]   *** U-Boot Boot Menu ***<br/>
      1. Startup system (Default)<br/>
      2. Upgrade firmware<br/>
      3. Upgrade ATF BL2<br/>
      4. Upgrade ATF FIP<br/>
      5. Upgrade single image<br/>
      6. Load image<br/>
      0. U-Boot console<br/>
  Press UP/DOWN to move, ENTER to select, ESC/CTRL+C to quit<br/>
[2023/7/10 10:50:50] *** Upgrading ATF FIP ***<br/>
[2023/7/10 10:50:50] <br/>
[2023/7/10 10:50:50] Available load methods:<br/>
[2023/7/10 10:50:50]     0 - TFTP client (Default)<br/>
[2023/7/10 10:50:50]     1 - Xmodem<br/>
[2023/7/10 10:50:50]     2 - Ymodem<br/>
[2023/7/10 10:50:50]     3 - Kermit<br/>
[2023/7/10 10:50:50]     4 - S-Record<br/>
[2023/7/10 10:50:50] <br/>
[2023/7/10 10:50:51] Select (enter for default): <br/>
[2023/7/10 10:50:51] <br/>
[2023/7/10 10:50:51] Input U-Boot's IP address: 192.168.1.1<br/>
[2023/7/10 10:50:52] Input TFTP server's IP address: 192.168.1.254<br/>
[2023/7/10 10:50:53] Input IP netmask: 255.255.255.0<br/>
<b>[2023/7/10 10:51:07] Input file name: fip_snfi_20230710.bin</b><br/>
[2023/7/10 10:51:07] <br/>
[2023/7/10 10:51:07] Using ethernet@15100000 device<br/>
[2023/7/10 10:51:07] TFTP from server 192.168.1.254; our IP address is 192.168.1.1<br/>
[2023/7/10 10:51:07] Filename 'fip_snfi_20230710.bin'.<br/>
[2023/7/10 10:51:07] Load address: 0x46000000<br/>
[2023/7/10 10:51:22] Loading: #T T ##################################################<br/>
[2023/7/10 10:51:22] 	 49.8 KiB/s<br/>
[2023/7/10 10:51:22] done<br/>
[2023/7/10 10:51:22] Bytes transferred = 747273 (b6709 hex)<br/>
[2023/7/10 10:51:22] Saving Environment to MTD... Erasing on MTD device 'u-boot-env'... OK<br/>
[2023/7/10 10:51:22] Writing to MTD device 'u-boot-env'... OK<br/>
[2023/7/10 10:51:22] OK<br/>
[2023/7/10 10:51:22] <br/>
[2023/7/10 10:51:22] *** Loaded 747273 (0xb6709) bytes at 0x46000000 ***<br/>
[2023/7/10 10:51:22] <br/>
[2023/7/10 10:51:22] Erasing 'fip' from 0x380000, size 0xc0000 ... OK<br/>
[2023/7/10 10:51:22] Writing 'fip' from 0x46000000 to 0x380000, size 0xb6709 ... OK<br/>
[2023/7/10 10:51:22] <br/>
[2023/7/10 10:51:22] *** ATF FIP upgrade completed! ***<br/>
[2023/7/10 10:51:22] <br/>
[2023/7/10 10:51:22] Erasing 'environment' from 0x100000, size 0x20000 ... OK<br/>
<b>[2023/7/10 10:51:31] MT7986> reset</b><br/>
[2023/7/10 10:51:31] resetting ...<br/>
[2023/7/10 10:51:31] <br/>
[2023/7/10 10:51:31] F0: 102B 0000<br/>
[2023/7/10 10:51:31] FA: 1040 0000<br/>
[2023/7/10 10:51:31] FA: 1040 0000 [0200]<br/>
[2023/7/10 10:51:31] F9: 3903 0041<br/>
[2023/7/10 10:51:31] F3: 1001 0000 [0200]<br/>
[2023/7/10 10:51:31] F3: 1001 0000<br/>
[2023/7/10 10:51:31] F6: 102C 0000<br/>
[2023/7/10 10:51:31] F5: 1026 0000<br/>
[2023/7/10 10:51:31] 00: 1005 0000<br/>
[2023/7/10 10:51:31] FA: 1040 0000<br/>
[2023/7/10 10:51:31] FA: 1040 0000 [0200]<br/>
[2023/7/10 10:51:31] F9: 3903 0041<br/>
[2023/7/10 10:51:31] F3: 1001 0000 [0200]<br/>
[2023/7/10 10:51:31] F3: 1001 0000<br/>
[2023/7/10 10:51:31] F6: 102C 0000<br/>
[2023/7/10 10:51:31] 01: 102A 0001<br/>
[2023/7/10 10:51:31] 02: 1005 0000<br/>
[2023/7/10 10:51:31] BP: 2000 00C0 [0001]<br/>
[2023/7/10 10:51:31] EC: 0000 0000 [1000]<br/>
[2023/7/10 10:51:31] T0: 0000 00BA [010F]<br/>
<b>[2023/7/10 10:51:31] System halt!</b><br/>
[2023/7/10 10:51:31] <br/>
<br><br/>
<br><br/>
<b>compile process：</b><br><br/>

for ATF:

make clean
make CROSS_COMPILE="~/BPI-R3-OPENWRT-V21.02.3-main/staging_dir/toolchain-aarch64_cortex-a53_gcc-8.4.0_musl/bin/aarch64-openwrt-linux-" -f Makefile PLAT=“mt7986” BOOT_DEVICE=“snand” BL33="~/mt7986av_dir_home/uboot_files/u-boot-snfi-xtxtect-"$(date +’%Y%m%d’)".bin" NAND_TYPE=“hsm:2k+128” NMBM=“1” DRAM_USE_DDR4=“1” all fip

for UBOOT:
make clean
make mt7986_snfi_nand_rfb_defconfig
make CROSS_COMPILE="~/BPI-R3-OPhttps://forum.banana-pi.org/t/tutorial-build-customize-and-use-mediatek-open-source-u-boot-and-atf/13785/38ENWRT-V21.02.3-main/staging_dir/toolchain-aarch64_cortex-a53_gcc-8.4.0_musl/bin/aarch64-openwrt-linux-"

frank-w · July 10, 2023, 5:01am

Which board do you use? BPI-R3 has no snfi…“only” spim-nand and nor

Elijah · July 10, 2023, 6:18am

Thx. i used BPI-R3 v1.1, i testing mtk soc ecc now, that i try use ‘flash hw ecc’s atf&boot’ + ‘mtk soc ecc’s kernel&rootfs’ .