SK-AM62B-P1: Booting SK-AM62B-P1 from eMMC

Hi Mallika,

Please follow the steps mentioned in the AM62 Academy.

https://dev.ti.com/tirex/explore/node?node=A__AdNWBqCVds4ZSqU9osT1tQ__AM62-ACADEMY__uiYMDcq__LATEST

AM62 Academy -> Linux-> Develop Linux on TI EVM -> Flash Linux on eMMC section should provide all the details.

Hope this helps

Best Regards,

Suren

Hi, 

I have tried those steps, I was ended up with these:

root@am62xx-evm:/# dd if=tiboot3.bin of=/dev/mmcblk0boot0 seek=0
dd: failed to open 'tiboot3.bin': No such file or directory


Im using Debian Image which is used for flashing on SD card.

Hi Mallika,

Where on the EVM have you copied the tiboot3.bin and other u-boot images? 

The u-boot images have to be on the EVM first so you can use the dd command.

Best Regards,

Suren

I have mounted them in this path:

root@am62xx-evm:~# ls -l /mnt/sdboot/
total 3294
drwxr-xr-x 2 root root 512 Jan 30 2025 'System Volume Information'
-rwxr-xr-x 1 root root 12285 Dec 6 2024 ti_logo_414x97_32bpp.bmp.gz
-rwxr-xr-x 1 root root 294441 Dec 6 2024 tiboot3-am62x-gp-evm.bin
-rwxr-xr-x 1 root root 297030 Dec 6 2024 tiboot3-am62x-hs-evm.bin
-rwxr-xr-x 1 root root 297030 Dec 6 2024 tiboot3-am62x-hs-fs-evm.bin
-rwxr-xr-x 1 root root 297030 Dec 6 2024 tiboot3.bin
-rwxr-xr-x 1 root root 1159835 Dec 6 2024 tispl.bin
-rwxr-xr-x 1 root root 1011971 Dec 6 2024 u-boot.img



I have done below steps:
root@am62xx-evm:/mnt/sdboot# dd if=tiboot3.bin of=/dev/mmcblk0boot0 seek=0
580+1 records in
580+1 records out
297030 bytes (297 kB, 290 KiB) copied, 0.0229746 s, 12.9 MB/s
root@am62xx-evm:/mnt/sdboot# dd if=tispl.bin of=/dev/mmcblk0boot0 seek=1024
2265+1 records in
2265+1 records out
1159835 bytes (1.2 MB, 1.1 MiB) copied, 0.0703862 s, 16.5 MB/s
root@am62xx-evm:/mnt/sdboot# dd if=u-boot.img of=/dev/mmcblk0boot0 seek=5120
1976+1 records in
1976+1 records out
1011971 bytes (1.0 MB, 988 KiB) copied, 0.0616285 s, 16.4 MB/s

So now you are able to copy them correctly.

Are you able to proceed further?

Best Regards,

Suren

I have used all the commands specified but after using the below commands in u-boot prompt:

=> mmc partconf 0 1 1 1
=> mmc bootbus 0 2 0 0

=> setenv mmcdev 0
=> setenv bootpart 0

Hi Mallika,

Yes "saveenv" @u-boot is disabled by default in the newer SDK as it sometimes causes inconsistencies in the dynamic boot flow.

It is recommended for user to customize "am62x.env" as necessary and rebuild u-boot for user's board design.

For example, "mmcdev/bootpart"

https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env?h=ti-u-boot-2024.04

Best Regards,

Sure

can we use boot script in order to boot automatically as a resolution?

Hi Mallika,

You mean uEnv.txt?

Best Regards,

Suren

Yes, I tried to created the boot.txt file and made the boot.src file and tried to run this automatically.
But I have encountered this:
Wrong image format for "source" command 1 script ready mmc 1 mmc@fa10000.bootdev.part_ /boot/boot.scr ** Booting bootflow 'mmc@fa10000.bootdev.part_1' with script Wrong image format for "source" command Boot failed (err=1)


I tried to create the /boot/boot.txt as shown below:

echo "Starting eMMC Boot..."
setenv fdtfile ti/k3-am625-sk.dtb
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p1 rw rootwait
load mmc 0:1 ${kernel_addr_r} boot/Image
load mmc 0:1 ${fdtaddr} boot/dtb/${fdtfile}
booti ${kernel_addr_r} - ${fdtaddr}



and created this:

mkimage -A arm64 -O linux -T script -C none -a 0 -e 0 -n "Boot Script" -d /boot/boot.txt /boot/boot.scr



Does this approach works?
If not can you suggest me new approach

Let me check with my expert for a response on the above approach,

In the meantime, have you tried to modify the am62x.env in u-boot and see if it helps?

Best Regards,

Suren

on Boot Prompt i can see this:
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'uEnv.txt'
19849728 bytes read in 250 ms (75.7 MiB/s)
60579 bytes read in 31 ms (1.9 MiB/s)
Working FDT set to 88000000

while using the print env, I can see that the Command is not found at my console

Hi Mallika,

What Suren said early that you need up update the env in U-Boot board/ti/am62x/am62x.env for your eMMC U-Boot build is the correct solution. No matter what scripting you use, without updating am62x.env, U-Boot will always tries to load the script from the SD card because of "mmcdev=1" defined in the SDK prebuilt for SD card boot.

Well, I quickly tested this before I signed off for today with the change sin am62x.env, but the boot from eMMC failed at tiboot3.bin loading tispl.bin. I will continue on this tomorrow.

I'm using this image https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-PvdSyIiioq/10.01.10.04/tisdk-debian-trixie-am62xx-evm-10.01.10.04.wic.xz on my 8GB sd card and this has listed only below files in that:


tiboot3.bin,tispl.bin,u-boot.img,tiboot3-am62-gp,hs,hs-fs bin files.
when i insert the sd card in EVM board in sd boot switch mode,it booted.

I want to use only DDR abd eMMC for my application where the board has to boot from eMMC after making the files transferred to eMMC by creating a sub folder in mmcblk0 and transfer of all kernel files to /boot and using these commands the system is able to boot from eMMC only once.

There is no am62x.env in my file system anywhere.
Thank you and looking forward for your reply.

Guide me if I was wrong in usage of SDK or other way to boot directly to EVM without SD card and directly flashing the boot and image files to eMMC from my Linux PC

Now, the EVM is booting from SD card only when I keep the Boot Switches in eMMC mode. I tried to flash other SDK which is also a Debian and I encountered that SD card  is booting only when I keep the Boot switches in eMMC mode which is 8-15(00000000) (0-7) (11010011)

Mallika Vignesh said:

There is no am62x.env in my file system anywhere.

am62x.env is in the U-Boot source which defines the U-Boot environment variables. The file is not on the SD card Debian.

Mallika Vignesh said:

Now, the EVM is booting from SD card only when I keep the Boot Switches in eMMC mode. I tried to flash other SDK which is also a Debian and I encountered that SD card  is booting only when I keep the Boot switches in eMMC mode which is 8-15(00000000) (0-7) (11010011)

I don't think I can reproduce this problem on my AM62x EVM, I can still change the boot mode switches between eMMC boot or SDCARD boot.

I will be out of office next week but will continue looking into this issue after I am back in office.

Previously when i tried to flash everything in mmcblk0 for eMMc boot, i changed the boot switches for eMMC , from then the system is booting only in  that mode even if the system is booting from SD Card. Is there anyway we can reset this boot switches normal, if the sd card is booting from emmc boot switch mode what if we want the board to get boot from eMMC.

Thank you

Hi Mallika,

I am not sure I fully understand your message, but you would need to adjust the boot mode switches on the EVM for the boot mode you want to use, eMMC or sdcard.

Hi Bin,

I have downloaded the SDK which is ti-processor-sdk-linux-am62xx-evm-10.01.10.04 and installed the SDK and followed by ./setup.sh and changed the below file to boot from mmc0 with following changes:

#include <env/ti/ti_common.env>
#include <env/ti/mmc.env>
#include <env/ti/k3_dfu.env>
#include <env/ti/ospi_nand.env>
#if CONFIG_CMD_REMOTEPROC
#include <env/ti/k3_rproc.env>
#endif

name_kern=Image
console=ttyS2,115200n8
args_all=setenv optargs ${optargs} earlycon=ns16550a,mmio32,0x02800000
${mtdparts}
run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}

boot_targets=mmc1 mmc0 usb pxe dhcp
boot=mmc
mmcdev=0
bootpart=0:2
bootdir=/boot
rd_spec=-

splashfile=ti_logo_414x97_32bpp.bmp.gz
splashimage=0x80200000
splashpos=m,m
splashsource=mmc
rproc_fw_binaries= 0 /lib/firmware/am62-mcu-m4f0_0-fw

#if CONFIG_BOOTMETH_ANDROID
#include <env/ti/android.env>
force_avb=0
adtb_idx=0
get_adtb_idx=
if test ${board_name} = am62x_lp_skevm; then
setenv adtb_idx 1;
else
setenv adtb_idx 0;
fi;
bootcmd=run get_adtb_idx; bootflow scan -lb
#endif



Once after chnaging the mmcdev to 0 , I have run the below commands which are specified below for generating the bootloader files:


https://dev.ti.com/tirex/explore/content/am62x_academy_10_00_00_01/am62x_academy_10_00_00_01/source/linux/ch-develop/dev-build-uboot.html

I have set the Toolchain Path and everything fine:
Compile the R5 Image is succesful but when trying to compile for ARM64 Image Im facing below error:

CC lib/strto.o
CC lib/abuf.o
CC lib/date.o
CC lib/rtc-lib.o
CC lib/elf.o
AR lib/built-in.o
LD u-boot
/home/optilink/ti-processor-sdk-linux-am62xx-evm-10.01.10.04/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/aarch64-oe-linux/aarch64-oe-linux-ld.bfd: cannot find -lgcc: No such file or directory
make[1]: *** [/home/optilink/ti-processor-sdk-linux-am62xx-evm-10.01.10.04/board-support/ti-u-boot-2024.04+git/Makefile:1766: u-boot] Error 1
make[1]: Leaving directory '/home/optilink/ti-processor-sdk-linux-am62xx-evm-10.01.10.04/board-support/u-boot-build/a53'
make: *** [Makefile:177: sub-make] Error 2

How to proceed further and Is the modification for making the default boot option for eMMC boot is right?

Bin is OoO this week. Please expect delayed response till next week.

Can someone assist with this?

Hi Mallika,

Before I was OoO last week, I tried to modify am62x.env to directly boot from MMC0 and the boot runs into issues. I will be looking into it and get back to you.

Hi Bin,

I can see now the system is able to boot from eMMC but once I give a command of reboot its getting failed with below prompt on console:

root@am62xx-evm:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mtdblock0 31:0 0 512K 0 disk
mtdblock1 31:1 0 2M 0 disk
mtdblock2 31:2 0 4M 0 disk
mtdblock3 31:3 0 256K 0 disk
mtdblock4 31:4 0 256K 0 disk
mtdblock5 31:5 0 55.8M 0 disk
mtdblock6 31:6 0 256K 0 disk
mmcblk0 179:0 0 14.8G 0 disk
`-mmcblk0p1 179:1 0 14.8G 0 part /
mmcblk0boot0 179:32 0 31.5M 1 disk
mmcblk0boot1 179:64 0 31.5M 1 disk
root@am62xx-evm:~# reboot
root@am62xx-evm:~# Stopping Session c6 of User root...
[ OK ] Removed slice Slice /system/modprobe.
[ OK ] Removed slice Slice /system/systemd-coredump.
[ OK ] Stopped target Graphical Interface.
[ OK ] Stopped target Multi-User System.
[ OK ] Stopped target Login Prompts.
[ OK ] Stopped target Host and Network Name Lookups.
[ OK ] Stopped target RPC Port Mapper.
[ OK ] Stopped target Sound Card.
[ OK ] Stopped target Timer Units.
[ OK ] Stopped Daily rotation of log files.
[ OK ] Stopped Daily Cleanup of Temporary Directories.
[ OK ] Stopped target System Time Set.
[ OK ] Stopped target Hardware activated USB gadget.
[ OK ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Stopping Job spooling tools...
Stopping Avahi mDNS/DNS-SD Stack...
Stopping containerd container runtime...
Stopping Periodic Command Scheduler...
Stopping Getty on tty1...
Stopping irqbalance daemon...
Stopping Reboot and dump vmcore via kexec...
Stopping LLDP daemon...
Stopping Netperf Benchmark Server...
Stopping Telephony service...
Stopping PulseAudio Sound System...
[ OK ] Stopped Expand the rootfs partition to full size of the boot device..
Stopping Serial Getty on ttyS2...
Stopping Seva Launcher Service...
Stopping Simple Network Management Protocol (SNMP) Daemon....
Stopping strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf...
Stopping Load/Save OS Random Seed...
Stopping TEE Supplicant on teepriv0...
Stopping Telnet Server...
[ OK ] Stopped Job spooling tools.
[ OK ] Stopped Avahi mDNS/DNS-SD Stack.
[ OK ] Stopped Periodic Command Scheduler.
[ OK ] Stopped irqbalance daemon.
[ OK ] Stopped Telephony service.
[ OK ] Stopped PulseAudio Sound System.
[ OK ] Stopped Seva Launcher Service.
[ OK ] Stopped strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.
[ OK ] Stopped LLDP daemon.
[ OK ] Stopped Netperf Benchmark Server.
[ OK ] Stopped Simple Network Management Protocol (SNMP) Daemon..
[ OK ] Stopped containerd container runtime.
[ OK ] Stopped Getty on tty1.
[ OK ] Stopped Serial Getty on ttyS2.
[ OK ] Stopped TEE Supplicant on teepriv0.
[ OK ] Stopped Reboot and dump vmcore via kexec.
[ OK ] Stopped Load/Save OS Random Seed.
[ OK ] Stopped Telnet Server.
[ OK ] Stopped Session c6 of User root.
[ OK ] Removed slice Slice /system/getty.
[ OK ] Removed slice Slice /system/serial-getty.
[ OK ] Removed slice Slice /system/tee-supplicant.
Stopping Save/Restore Sound Card State...
Stopping User Login Management...
Stopping Permit User Sessions...
Stopping User Manager for UID 0...
[ OK ] Stopped User Manager for UID 0.
[ OK ] Stopped Save/Restore Sound Card State.
[ OK ] Stopped Permit User Sessions.
[ OK ] Stopped target Network.
[ OK ] Stopped target Remote File Systems.
Stopping Network Configuration...
Stopping User Runtime Directory /run/user/0...
[ OK ] Stopped User Login Management.
[ OK ] Unmounted /run/user/0.
[ OK ] Stopped Network Configuration.
[ OK ] Stopped User Runtime Directory /run/user/0.
[50600.807552] kauditd_printk_skb: 8 callbacks suppressed
[50600.807574] audit: type=1334 audit(50622.760:39): prog-id=14 op=UNLOAD
[50600.819404] audit: type=1334 audit(50622.760:40): prog-id=17 op=UNLOAD
[ OK ] Removed slice User Slice of UID 0.
[ OK ] Stopped target Preparation for Network.
[ OK ] Stopped IPv6 Packet Filtering Framework.
[ OK ] Stopped IPv4 Packet Filtering Framework.
[ OK ] Stopped target Basic System.
[ OK ] Stopped target Path Units.
[ OK ] Stopped Dispatch Password Requests to Console Directory Watch.
[ OK ] Stopped Forward Password Requests to Wall Directory Watch.
[ OK ] Stopped target Slice Units.
[ OK ] Removed slice User and Session Slice.
[ OK ] Stopped target Socket Units.
[ OK ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Closed Docker Socket for the API.
[ OK ] Closed dropbear.socket.
[ OK ] Closed PC/SC Smart Card Daemon Activation Socket.
[ OK ] Closed Network Service Netlink Socket.
Stopping D-Bus System Message Bus...
[ OK ] Stopped Generate network units from Kernel command line.
[ OK ] Stopped D-Bus System Message Bus.
[50601.148738] audit: type=1334 audit(50623.100:41): prog-id=13 op=UNLOAD
[ OK ] Closed D-Bus System Message Bus Socket.
[ OK ] Stopped target System Initialization.
Stopping Network Name Resolution...
Stopping Network Time Synchronization...
Stopping Record System Boot/Shutdown in UTMP...
[ OK ] Stopped Network Name Resolution.
[ OK ] Stopped Network Time Synchronization.
[50601.313615] audit: type=1334 audit(50623.264:42): prog-id=9 op=UNLOAD
[50601.320296] audit: type=1334 audit(50623.264:43): prog-id=8 op=UNLOAD
[ OK ] Stopped Apply Kernel Variables.
[ OK ] Closed Process Core Dump Socket.
[ OK ] Stopped Load Kernel Modules.
[ OK ] Stopped Record System Boot/Shutdown in UTMP.
[ OK ] Stopped Create System Files and Directories.
[ OK ] Stopped target Local File Systems.
Unmounting Temporary Directory /tmp...
Unmounting /var/volatile...
[ OK ] Unmounted Temporary Directory /tmp.
[ OK ] Unmounted /var/volatile.
[ OK ] Stopped target Preparation for Local File Systems.
[ OK ] Stopped target Swaps.
[ OK ] Reached target Unmount All Filesystems.
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Stopped Create Static Device Nodes in /dev.
[ OK ] Stopped Create Static Device Nodes in /dev gracefully.
[ OK ] Reached target System Shutdown.
[ OK ] Reached target Late Shutdown Services.
[ OK ] Finished System Reboot.
[ OK ] Reached target System Reboot.
[50601.745509] audit: type=1334 audit(50623.696:44): prog-id=5 op=UNLOAD
[50601.752049] audit: type=1334 audit(50623.696:45): prog-id=4 op=UNLOAD
[50601.758544] audit: type=1334 audit(50623.696:46): prog-id=3 op=UNLOAD
[50601.765012] audit: type=1334 audit(50623.700:47): prog-id=16 op=UNLOAD
[50601.771551] audit: type=1334 audit(50623.700:48): prog-id=15 op=UNLOAD
[50601.779360] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[50601.786348] watchdog: watchdog0: watchdog did not stop!
[50601.812971] systemd-shutdown[1]: Using hardware watchdog 'K3 RTI Watchdog', version 0, device /dev/watchdog0
[50601.822868] systemd-shutdown[1]: Modifying watchdog hardware timeout is not supported, reusing the programmed timeout.
[50601.833587] systemd-shutdown[1]: Watchdog running with a hardware timeout of 1min.
[50601.858775] systemd-shutdown[1]: Syncing filesystems and block devices.
[50601.883003] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[50601.910375] systemd-journald[125]: Received SIGTERM from PID 1 (systemd-shutdow).
[50601.923360] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[50601.946978] systemd-shutdown[1]: Unmounting file systems.
[50601.955775] (sd-remount)[1710]: Remounting '/' read-only with options ''.
[50602.031370] EXT4-fs (mmcblk0p1): re-mounted ef7d57e6-588a-4385-9429-4fd97d50aa22 ro. Quota mode: none.
[50602.058656] systemd-shutdown[1]: All filesystems unmounted.
[50602.064403] systemd-shutdown[1]: Deactivating swaps.
[50602.069769] systemd-shutdown[1]: All swaps deactivated.
[50602.075020] systemd-shutdown[1]: Detaching loop devices.
[50602.085997] systemd-shutdown[1]: All loop devices detached.
[50602.091715] systemd-shutdown[1]: Stopping MD devices.
[50602.097177] systemd-shutdown[1]: All MD devices stopped.
[50602.102693] systemd-shutdown[1]: Detaching DM devices.
[50602.108332] systemd-shutdown[1]: All DM devices detached.
[50602.113748] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
[50602.123405] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[50602.130292] systemd-shutdown[1]: Failed to disable hardware watchdog, ignoring: Device or resource busy
[50602.139683] watchdog: watchdog0: nowayout prevents watchdog being stopped!
[50602.146546] watchdog: watchdog0: watchdog did not stop!
[50602.157922] systemd-shutdown[1]: Syncing filesystems and block devices.
[50602.164826] systemd-shutdown[1]: Rebooting.
[50602.197659] reboot: Restarting system

Hi Mallika,

Mallika Vignesh said:

I can see now the system is able to boot from eMMC

Do you mean you can now directly boot into Linux without typing the following two commands in U-Boot prompt?

=> setenv mmcdev 0
=> setenv bootpart 0

If so, what change have you made to eliminate this manual step?

I gave below commands on U-Boot prompt:
=> mmc partconf 0 1 1 1
=> mmc bootbus 0 2 0 0

Made the boot switch operation to eMMC and removed the SD card.
The system has booted from eMMC and verified this with command of (lsblk).

I tried to reboot the system from command line but its not happening and freezes  with above prompts enclosed.