This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM62A1-Q1: AM62A: Boot time optimization

Part Number: AM62A1-Q1
Other Parts Discussed in Thread: SK-AM62A-LP

Hi Team, 

I am trying to optimize the boot time of AM62A. SDK: 11.01.07

I am observing this task is taking almost a sec (may not be related to this task though). 

[1.295520 1.087431] Authentication passed

Can you please help me optimizing the boot time here ? I have already enabled falcon mode.  

Also, If there are patches available to optimize the boot time, please feel free to share. 

[0.000001 0.000001] 
[0.000358 0.000357] U-Boot SPL 2025.01-00547-g3bcfad6cee95-dirty (Jul 23 2025 - 16:49:22 +0000)
[0.001177 0.001177] SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
[0.095756 0.094579] SPL initial stack usage: 13568 bytes
[0.096511 0.000755] Trying to boot from MMC2
[0.207696 0.111185] Authentication passed
[0.208089 0.000393] Loading falcon payload from MMC2
[1.295520 1.087431] Authentication passed
[1.407734 0.112214] Authentication passed
[1.487617 0.079883] Loading Environment from nowhere... OK
[1.488277 0.000660] Authentication passed
[1.503472 0.015195] Authentication passed
[1.519476 0.016004] Starting ATF on ARM64 core...

Thanks,

Avijit

  • Hi, today is a holiday in the US, please expect delayed response.

  • Correction,

    I am using part# SK-AM62A-LP 

  • Hi Avjit,

    I am observing this task is taking almost a sec (may not be related to this task though). 

    [1.295520 1.087431] Authentication passed

    The authentication overhead would be the HS devices verifying the images using Secure firmware, TIFS.
    If it's an HS device and secure boot is needed, these can't be turned off.  Refer: https://docs.u-boot.org/en/stable/board/ti/k3.html

    You can reduce kernel boot time and user space boot time further using the methods mentioned in the following guide.

    Please refer the Boot time Optimizations guide: https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/latest/exports/docs/linux/How_to_Guides/Target/How_to_boot_quickly.html

    Regards,
    Vinu

  • Thank you for your response. 

    I am able to follow the link you have provided and achieve significant boot time improvement. 

    I see there are still 2 big scope of improvement..

    1. I am observing this authentication process is taking significant amount of time. 

    2. PBL is taking ~2.15 secs to load the u-boot. I am measuring the time from power button press to first u-boot log shows up on the minicom terminal. 

    Is there anything I can do to optimize these 2 steps in the boot flow ? 

    I am able to boot the device from uboot to shell prompt to terminal prompt access in 1.93s.

    [0.000383 0.000382] U-Boot SPL 2025.01-00547-g3bcfad6cee95-dirty (Jul 23 2025 - 16:49:22 +0000)  <= power button press this takes 2.15s 
    [0.001729 0.001729] SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
    [0.079507 0.077778] SPL initial stack usage: 13568 bytes
    [0.080575 0.001068] Trying to boot from MMC1
    [0.159463 0.078888] Authentication passed                                                                                            <= Trying to optimize boot time here
    [0.160229 0.000766] Loading falcon payload from MMC1
    [0.575443 0.415214] Authentication passed
    [0.655445 0.080002] Authentication passed
    [0.847457 0.192012] Loading Environment from nowhere... OK
    [0.848592 0.001135] init_env from device 9 not supported!
    [0.863434 0.014842] Authentication passed
    [0.864019 0.000585] Authentication passed
    [0.879413 0.015394] Starting ATF on ARM64 core...
    [0.880209 0.000796]
    [0.880247 0.000038] NOTICE: BL31: v2.13.0(release):v2.13.0-259-ge0c4d3903b-dirty
    [0.881587 0.001341] NOTICE: BL31: Built : 07:01:36, Jul 1 2025
    [1.823436 0.941849] init started: BusyBox v1.36.1 ()
    [1.824489 0.001052] starting pid 84, tty '': '/bin/mount -t proc proc /proc'
    [1.826082 0.001593] starting pid 85, tty '': '/bin/mount -t sysfs sysfs /sys'
    [1.839827 0.013745] starting pid 86, tty '': '/bin/mount -t devtmpfs devtmpfs /dev >/dev/null 2>&1'
    [1.842201 0.002374] starting pid 87, tty '': '/bin/mount -o remount,rw /'
    [1.871425 0.029224] starting pid 90, tty '': '/bin/mkdir -p /dev/pts'
    [1.873276 0.001851] starting pid 91, tty '': '/bin/mount -a'
    [1.874477 0.001200] starting pid 92, tty '': '/sbin/swapon -a'
    [1.887311 0.012835] starting pid 99, tty '/dev/ttyS2': '/usr/sbin/ttyrun ttyS2 /sbin/getty 115200 ttyS2'
    [1.999403 0.112092]
    [1.999511 0.000108]
    [1.999563 0.000051] am62axx-evm login: grabserial stopped due to time expiration

  • Hi Avjith,

    Glad to know that you could reduce the boot time significantly.

    From power-on to first SPL log include hardware initialization, ROM execution and loading the initial boot image.
    During this the TIFS and DM firmwares should be loaded to R5 core, before A53 cores can be start.

    You can try the following to decrease the overall boot time.

    1. Reduce the size of tiboot3.bin by removing unused configs.

    2. You can also try to reduce the DM firmware size by removing unused resources, logs etc.

    3. Reduce the linux image size, similarly.

    As mentioned, the early boot delay is due to primary hardware/ROM initialization and security firmware overhead. 
    Some gains can be made by optimizing the image sizes, but the security authentication is a hardware enforced process on HS devices that has a fixed baseline cost.

    Regards,
    Vinu