Hi Ti,
We are using AM65x EVM board and try to modify u-boot with eMMC and SD card boot.
We want to know how to modify uEnv.txt either in eMMC or SD card.
Can we add "setenv mmcdev 0" and "setenv bootpart 0:2" in uEnv.txt in eMMC and add "setenv mmcdev 1" and "setenv bootpart 1:2" in uEnv.txt in SD card?
Will uEnv.txt be referenced in AM65x? We use the prebuild uEnv.txt you provided.
If not, how can we achieve this?
Thanks.
Eric
Hi Dwarakesh R.
As you told, I add the line "uenvcmd=setenv mmcdev 0;setenv bootpart 0:2" into my uEnv.txt as attached screen shot.
However, no matter I set "mmcdev 1 and bootpart 1:2" or "mmc dev 0 and bootpart 0:2", I always get the logs almost the same.
The difference is only the speed.
I'm not sure if it's right.
Or could you let me know how can I make sure uEnv.txt has beed executed? via logs or anything else?
Thanks.
Eric
Hi Eric,
So you want uboot to be booted from the same location(SDCard I believe and also uEnv.txt from SDCard), whatever you have configured in boot switch and want kernel and filesystems to come from either eMMC or SDCard ?
One suggestion is to make uenvcmd as a single line. I see two uenvcmd in uEnv.txt, merge them and have as single line command separated with semi-colon(and also add mmc rescan command as below example I have given)
Also as I mentioned earlier you can print using echo e.g.
uenvcmd=if run check_psdk_setup;then echo " " ................;setenv mmcdev 0;setenv bootpart 0:2; mmc rescan; echo Eric's uenvcmd is ${uenvcmd}; echo Eric's bootcmd is ${bootcmd}
Hi Dwarakesh R,
Yes, no matter where I boot uboot, I want to put two uEnv.txt in both eMMC and SD card.
In uEnv.txt in eMMC, I want to load filesystem from eMMC.
In uEnv.txt in SD, I want to load it from SD.
That's why I want to have 2 uEnv.txt to set different filesystem load location.
I modified uEnv.txt again for example and put it into my SD card.
Please help to check if anything mistake.
However, I cannot see any echo log from console below.
So, I doubt if uEnv.txt been loaded or not.
Or it's not work in AM65x EVM board?
▒
U-Boot SPL 2019.01-gd938690-dirty (May 26 2020 - 10:55:49 +0800)
SYSFW ABI: 2.7 (firmware rev 0x0013 '19.9.0-v2019.09 (Terrific Llama')
Trying to boot from MMC2
Starting ATF on ARM64 core...
NOTICE: BL31: v2.2(release):ti2019.05-rc1
NOTICE: BL31: Built : 03:29:45, Jan 5 2020
I/TC:
I/TC: OP-TEE version: ti2019.05-rc1-dev (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 Sun Jan 5 03:28:58 UTC 2020 aarch64
I/TC: Initialized
U-Boot SPL 2019.01-gd938690-dirty (May 26 2020 - 10:54:36 +0800)
Detected: AM6-IDKAPPEVM rev E4
Trying to boot from MMC2
U-Boot 2019.01-gd938690-dirty (May 26 2020 - 10:54:36 +0800)
SoC: AM654 PG 1.0
Model: Texas Instruments AM654 Base Board
Board: AM6-COMPROCEVM rev E4
DRAM: 4 GiB
MMC: sdhci@4f80000: 0, sdhci@04FA0000: 1
Loading Environment from MMC... OK
In: serial
Out: serial
Err: serial
Detected: AM6-IDKAPPEVM rev E4
Net: eth3: pruss1_eth, eth2: pruss0_eth, eth0: cpsw_nuss@046000000, eth1: pruss2_eth
Hit any key to stop autoboot: 0
=>
=> print
arch=arm
args_all=setenv optargs earlycon=ns16550a,mmio32,0x02800000 ${mtdparts}
args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}
args_ubi=setenv bootargs console=${console} ${optargs} rootfstype=ubifs root=ubi0:rootfs rw ubi.mtd=ospi.rootfs
baudrate=115200
board=am65x
board_name=am65x
board_rev=E4
board_serial=0129
board_software_revision=01
boot=mmc
boot_fit=0
boot_rprocs=if test ${dorprocboot} -eq 1 && test ${boot} = mmc; then rproc init;run boot_rprocs_mmc;fi;
boot_rprocs_mmc=env set rproc_id;env set rproc_fw;for i in ${rproc_fw_binaries} ; do if test -z "${rproc_id}" ; then env set rproc_id $i;else env set rproc_fw $i;run rproc_load_and_boot_one;env set rproc_id;env set rproc_fw;fi;done
bootargs=androidboot.serialno=${serial#} console=ttyS2,115200 androidboot.console=ttyS2 androidboot.hardware=am65xevmboard
bootcmd=run check_dofastboot; run findfdt; run check_android; if test $is_android -eq 1; then run emmc_android_boot; fi; setenv mmcdev 0; setenv bootpart 0:2; run envboot; run init_${boot}; run boot_rprocs; run get_kern_${boot}; run get_fdt_${boot}; run get_overlay_${boot}; run run_kern
bootdelay=2
bootdir=/boot
bootenvfile=uEnv.txt
bootpart=1:2
bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
check_android=setenv mmcdev 0; env delete boot_start; part start mmc ${mmcdev} boot boot_start; if test "$boot_start" = ""; then env set is_android 0; else env set is_android 1; fi; env delete boot_start
check_dofastboot=if test ${dofastboot} -eq 1; then echo Boot fastboot requested, resetting dofastboot ...;setenv dofastboot 0; env save; echo Booting into fastboot ...; fastboot 0; fi
console=ttyS2,115200n8
cpu=armv8
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;tiboot3.bin.raw raw 0x0 0x400 mmcpart 1;tispl.bin.raw raw 0x400 0x1000 mmcpart 1;u-boot.img.raw raw 0x1400 0x2000 mmcpart 1;u-env.raw raw 0x3400 0x100 mmcpart 1;sysfw.itb.raw raw 0x3600 0x800 mmcpart 1
dfu_alt_info_mmc=boot part 1 1;rootfs part 1 2;tiboot3.bin fat 1 1;tispl.bin fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1;sysfw.itb fat 1 1
dfu_alt_info_ospi=tiboot3.bin raw 0x0 0x080000;tispl.bin raw 0x080000 0x200000;u-boot.img raw 0x280000 0x400000;u-boot-env raw 0x680000 0x020000;sysfw.itb raw 0x6c0000 0x100000;rootfs raw 0x800000 0x3800000
dfu_bufsiz=0x20000
dofastboot=0
dorprocboot=0
emmc_android_boot=echo Trying to boot Android from eMMC ...; run update_to_fit; setenv eval_bootargs setenv bootargs $bootargs; run eval_bootargs; setenv mmcdev 0; setenv bootpart 0:2mmc dev $mmcdev; mmc rescan; part start mmc ${mmcdev} boot boot_start; part size mmc ${mmcdev} boot boot_size; mmc read ${fit_loadaddr} ${boot_start} ${boot_size}; run get_overlaystring; run run_fit
envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootscript; then run bootscript;else if run loadbootenv; then echo Loaded env from ${bootenvfile};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;fi;fi;
eth1addr=70:ff:76:1d:5c:bc
eth2addr=70:ff:76:1d:5c:bd
eth3addr=70:ff:76:1d:5f:34
eth4addr=70:ff:76:1d:5f:35
eth5addr=70:ff:76:1d:5f:36
eth6addr=70:ff:76:1d:5f:37
ethaddr=4c:24:98:fc:09:d6
fastboot.board_rev=E4
fastboot.cpu=AM654
fastboot.secure=GP
fdtaddr=0x82000000
fdtcontroladdr=fdeca178
findfdt=setenv name_fdt k3-am654-base-board.dtb;setenv fdtfile ${name_fdt};setenv overlay_files ${name_overlays}
finduuid=part uuid mmc ${bootpart} uuid
fit_bootfile=fitImage
fit_loadaddr=0x90000000
get_fdt_mmc=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${name_fdt}
get_fdt_ubi=ubifsload ${fdtaddr} ${bootdir}/${name_fdt}
get_fit_mmc=load mmc ${bootpart} ${fit_loadaddr} ${bootdir}/${fit_bootfile}
get_kern_mmc=load mmc ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
get_kern_ubi=ubifsload ${loadaddr} ${bootdir}/${name_kern}
get_overlay_mmc=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $overlay_files;do;load mmc ${bootpart} ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr};done;
get_overlaystring=for overlay in $overlay_files;do;setenv overlaystring ${overlaystring}'#'${overlay};done;
importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${loadaddr} ${filesize}
init_mmc=run args_all args_mmc
init_ubi=run args_all args_ubi; sf probe; ubi part ospi.rootfs; ubifsmount ubi:rootfs;
loadaddr=0x80080000
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
loadbootscript=load mmc ${mmcdev} ${loadaddr} boot.scr
loadfdt=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
loadfit=run args_mmc; run run_fit;
loadimage=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
mmcboot=mmc dev ${mmcdev}; setenv devnum ${mmcdev}; setenv devtype mmc; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadimage; then if test ${boot_fit} -eq 1; then run loadfit; else run mmcloados;fi;fi;fi;
mmcdev=0
mmcloados=run args_mmc; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdtaddr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
mmcrootfstype=ext4 rootwait
mtdids=nor0=47040000.spi.0
mtdparts=mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),128k(ospi.env),128k(ospi.env.backup),1m(ospi.sysfw),-@8m(ospi.rootfs)
name_kern=Image
name_overlays=k3-am654-idk.dtbo
overlayaddr=0x83000000
partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=0,size=-,uuid=${uuid_gpt_rootfs}
partitions_android=uuid_disk=${uuid_gpt_disk};name=bootloader,start=5M,size=8M,uuid=${uuid_gpt_bootloader};name=tiboot3,start=4M,size=1M,uuid=${uuid_gpt_tiboot3};name=boot,start=13M,size=40M,uuid=${uuid_gpt_boot};name=vendor,size=512M,uuid=${uuid_gpt_vendor};name=system,size=2048M,uuid=${uuid_gpt_system};name=userdata,size=-,uuid=${uuid_gpt_userdata}
rd_spec=-
rproc_fw_binaries=0 /lib/firmware/am65x-mcu-r5f0_0-fw 1 /lib/firmware/am65x-mcu-r5f0_1-fw
rproc_load_and_boot_one=if load mmc ${bootpart} $loadaddr ${rproc_fw}; then if rproc load ${rproc_id} ${loadaddr} ${filesize}; then rproc start ${rproc_id};fi;fi
run_fit=bootm ${fit_loadaddr}#${fdtfile}${overlaystring}
run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
serial#=0000000000000129
soc=k3
stdin=serial,usbkbd
update_to_fit=setenv loadaddr ${fit_loadaddr}; setenv bootfile ${fit_bootfile}
vendor=ti
Environment size: 6431/131067 bytes
=>
Thanks.
Eric
Hi Eric,
Looks like you have modified and added prints in only the SDCard(MMC1) uEnv.txt. But looks like eMMC(MMC0) uEnv.txt is picked up with below log
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0(part 0) is current device
SD/MMC found on device 0
** Unable to read file boot.scr **
1490 bytes read in 7 ms (207 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc0 ...
Running uenvcmd ...
1 bytes read in 2 ms (0 Bytes/s)
Already setup.
Initial logs that you shared picked up uEnv.txt from SDCard as you can see the same highlighted logs in the below screenshot to be mmc1
Do you know the difference ? Otherwise you can stop at autoboot and manually set(mmcdev) and check if your script uEnv.txt is loading from mmc1
Hi Dwarakesh R.
Sorry for reply late. I only have EVM board test on Monday.
Let me clear the question first.
1.I set the SW to SD boot.
2.In the uEnv.txt in SD card, I add this.
And in uEnv.txt in emmc, I add this.
You can see different debug message between "SD boot" and "emmc boot".
Then, I boot device and get the log below.
We can know "Trying to boot from MMC" is due to we set the SW to SD boot. This is no question.
But, why is log show "Importing environment from mmc0"?
In my thought, I boot from SD card, and it should load uEnv.txt from SD card, and suppose to see the log
"Eric: SD boot Already setup!!"
Please let me know if my question is wrong.
Thanks.
Eric
Hi Dwarakesh R,
I got two logs as below.
1. SW choose SD boot
2. SW to emmc boot
You can see the boot partition is no question changed accordingly.
However, the environment to load uEnv.txt is always mmc0 in both case.
After I set the command you mentioned, and reboot the EVM board, I always got mmcdev is 0 in both SD and emmc case.
# setenv mmcdev 1
# saveenv
I doubt if there is any hard code to prevent uEnv.txt overwrite it.
Thanks.
Eric
