AM62L-EVSE-DEV-EVM: SPL Bootloader reset during cold boot

Part Number: AM62L-EVSE-DEV-EVM

Hi Team,

We are evaluating Processor SDK Linux AM62Ax 11.01.07.05 on an AM62Ax EVM and have observed an intermittent boot issue during cold boot / power cycle conditions.

SDK Version: Processor SDK Linux AM62Ax 11.01.07.05

Boot Configuration

  • Board: AM62Ax EVM
  • SDK: 11.01.07.05
  • Boot Media: SD Card (MMC2)
  • Secure Boot Enabled (authentication messages observed)
  • Falcon Mode Enabled

Observed Behavior

During cold boot, the board occasionally exhibits the following behavior:

  1. SPL starts normally and loads the Falcon payload.
  2. ATF (BL31) banner is printed.
  3. The system then appears to stall for approximately 1 second.
  4. A reset occurs without any explicit error message.
  5. The board subsequently boots successfully on the next attempt.

Excerpt from the console log:

Plain Text

  

U-Boot SPL 2025.01...

SYSFW ABI: 4.0

Trying to boot from MMC2

Authentication passed

Loading falcon payload from MMC2

...

Starting ATF on ARM64 core...

 

NOTICE: BL31: v2.13.0(release):

NOTICE: BL31: Built : Jul 1 2025

 

<~1 second gap>

 

U-Boot SPL 2025.01...

SYSFW ABI: 4.0

Trying to boot from MMC2

Authentication passed

 

Loading falcon payload from MMC2

...

Starting ATF on ARM64 core...

 

NOTICE: BL31: v2.13.0(release):

NOTICE: BL31: Built : Jul 1 2025

Additional Observations

  • The issue is sporadic and not reproducible on every power cycle.
  • We have not observed the issue during warm resets, soft resets, or reset-button initiated reboots.
  • The issue appears only after a power cyclereset_bootlog_with_kernel_log_silent.txt 
  • Following the reset, the system boots successfully without any intervention.

Questions

  1. Has TI seen similar behavior on AM62Ax devices running SDK 11.01.07.05?
  2. Is there any known interaction between:
    • Falcon Mode
    • ATF/BL31 initialization
    • DDR initialization during cold boot
    • SD card boot timing that could result in a watchdog-triggered or hardware-induced reset?
  3. Are there any recommended debug mechanisms to identify the reset source (watchdog, PMIC, brownout, device manager reset, etc.)?
  4. Is this behavior more indicative of a hardware issue (power sequencing, PMIC, DDR initialization stability) or a software issue in SPL/ATF/Falcon boot flow?

 

 

Following are the summary of observations so far:
falcon_default_build_log.log 
2. Normally reset is observed when kernel image is loading/verification phase.
3. if we add some delay in early boot cycle then reset shifts even earlier state like, before kernel image loading.
4. If we use smaller kernel image then reset shift farther, during TFA handing over control to kernel.
5.there are 4 led turn on when we give power to board and system start booting and these will be consistent . but in issue case , 3 of these leds goes off momentarily then on and 4th one blinks. 

 

Any guidance on root-cause analysis or known fixes/workarounds would be greatly appreciated.

Thanks.

  • Hi Priyanka,

    but in issue case , 3 of these leds goes off momentarily then on and 4th one blinks. 

    What is the PCB silkprint label of the 4th LED?

  • four LEDs which gets on when power is given to board, silkprint lable written as  LD2 LD3 LD4 LD7. in issue case LD2 LD3 LD7 goes off and ON and LD4(near to the Type C power socket ) blinks once then stable ON followed by other 3 LEDs also gets ON.

  • Hi Priyanka,

    What power supply do you use for the board? Please ensure it can provide at least 3A.

  • We use 100w adapter with type c cable , which gives 3A output

  • Hi Priyanka,

    The issue appears only after a power cyclereset_bootlog_with_kernel_log_silent.txt 

    This log is not accessible. Can you please attach it again?

    Following are the summary of observations so far:
    falcon_default_build_log.log 

    In this log, I don't see reset between ATF and kernel, but when R5 SPL tries to load the ATF+kernel image from MMC2:

    [2026-10-08 18:44:08.618] U-Boot SPL 2025.01-00547-g3bcfad6cee95 (Jul 23 2025 - 16:49:22 +0000)
    [2026-10-08 18:44:08.618] SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
    [2026-10-08 18:44:08.713] SPL initial stack usage: 13568 bytes
    [2026-10-08 18:44:08.713] Trying to boot from MMC2
    [2026-10-08 18:44:08.808] Authentication passed
    [2026-10-08 18:44:08.824] Loading falcon payload from MMC2
    [2026-10-08 18:44:10.767] 
    [2026-10-08 18:44:10.767] U-Boot SPL 2025.01-00547-g3bcfad6cee95 (Jul 23 2025 - 16:49:22 +0000)
    [2026-10-08 18:44:10.767] SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
    [2026-10-08 18:44:10.845] SPL initial stack usage: 13568 bytes
    [2026-10-08 18:44:10.860] Trying to boot from MMC2
    [2026-10-08 18:44:10.953] Authentication passed
    [2026-10-08 18:44:10.953] Loading falcon payload from MMC2
    [2026-10-08 18:44:11.987] Authentication passed
    [2026-10-08 18:44:12.126] Authentication passed
    [2026-10-08 18:44:12.188] Loading Environment from nowhere... OK
    [2026-10-08 18:44:12.188] Authentication passed
    [2026-10-08 18:44:12.203] Authentication passed
    [2026-10-08 18:44:12.215] Starting ATF on ARM64 core...
    [2026-10-08 18:44:12.215] 
    [2026-10-08 18:44:12.215] NOTICE:  BL31: v2.13.0(release):v2.13.0-259-ge0c4d3903b-dirty
    [2026-10-08 18:44:12.215] NOTICE:  BL31: Built : 07:01:36, Jul  1 2025
    [2026-10-08 18:44:12.645] [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]

    Can you please confirm if the reset issue is

    1. before loading/running ATF or

    2. between running ATF and kernel?

    If 1), what is the sdcard you use? brand, capacity, etc? Can you please try a different brand of sdcard to see if the issue still happens?

  • we see following logs before reset occurs . so it looks like during loading issue occurs but cannot confirm

     

    [2026-10-01 16:30:28.910] U-Boot SPL 2025.01-00547-g3bcfad6cee95-dirty (Jul 23 2025 - 16:49:22 +0000)
    [2026-10-01 16:30:28.910] SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
    [2026-10-01 16:30:29.004] SPL initial stack usage: 13568 bytes
    [2026-10-01 16:30:29.004] Trying to boot from MMC2
    [2026-10-01 16:30:29.097] Authentication passed
    [2026-10-01 16:30:29.113] Loading falcon payload from MMC2

     We have tried with the following 

    Sandisk 32 GB sdcard  , HP 64 GB sdcard . Issue is reproducible with both cards

  • Please apply the following U-Boot patch to see if the issue still happens.

    diff --git a/arch/arm/dts/k3-am62a7-sk-u-boot.dtsi b/arch/arm/dts/k3-am62a7-sk-u-boot.dtsi
    index 59e9d231ef25..3c61a123beb5 100644
    --- a/arch/arm/dts/k3-am62a7-sk-u-boot.dtsi
    +++ b/arch/arm/dts/k3-am62a7-sk-u-boot.dtsi
    @@ -113,6 +113,7 @@
     };
     
     &sdhci1 {
    +       sdhci-caps-mask = <0x00000007 0x00000000>;
            bootph-all;
     };

  • Hello   We had tried patch earlier and the issue could still be reproduced.

    We also tried adding some delay which did not seem to help.

    --- a/drivers/mmc/mmc.c
    +++ b/drivers/mmc/mmc.c
    @@ -2761,7 +2761,7 @@ static int mmc_power_cycle(struct mmc *mmc)
             * SD spec recommends at least 1ms of delay. Let's wait for 2ms
             * to be on the safer side.
             */
    -       udelay(2000);
    +       udelay(4000);
          return mmc_power_on(mmc);
    }
  • Hi Priyanka,

    Does the problem happen when using regular boot flow not falcon?

    If so, please provide the procedure about how the falcon boot image is generated.

  • We are not able to reproduce this issue so far  in normal boot flow.

    we have followed the steps as provided in following TI link to enable the falcon for release 11.01.07.05:

     

    echo 'DISTROOVERRIDES:append = ":ti-falcon"' >> conf/local.conf

    https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/11_01_07_05/exports/docs/linux/Foundational_Components/U-Boot/UG-Falcon-Mode.html

  • we see following logs before reset occurs . so it looks like during loading issue occurs but cannot confirm

     

    [2026-10-01 16:30:28.910] U-Boot SPL 2025.01-00547-g3bcfad6cee95-dirty (Jul 23 2025 - 16:49:22 +0000)
    [2026-10-01 16:30:28.910] SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
    [2026-10-01 16:30:29.004] SPL initial stack usage: 13568 bytes
    [2026-10-01 16:30:29.004] Trying to boot from MMC2
    [2026-10-01 16:30:29.097] Authentication passed
    [2026-10-01 16:30:29.113] Loading falcon payload from MMC2

    The reset happens after "Loading falcon payload from MMC2" is printed.

    As you can see in the U-Boot source (linked below), this message is printed from the for-loop in function  k3_falcon_prep() in arch/arm/mach-k3/common.c.

    https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/mach-k3/common.c?h=11.01.07#n538

    Can you please add some printf() in this for-loop to narrow down the exact place where the reset happens? Adding ret error code and loop iteration numbers in those printf() will be helpful too.

    P.S. by reading code in this for-loop, it seems the reset happens when:

            ret = loader->load_image(&kernel_image, &bootdev);

  • 5.there are 4 led turn on when we give power to board and system start booting and these will be consistent . but in issue case , 3 of these leds goes off momentarily then on and 4th one blinks. 

     

    Does this LED behavior happen around the time when the reset happens? If so, do all of the 4 LEDs are ON consistently after the reset and boot continues into Linux?

  • Yes .  this LED behavior happens around the time when the reset occurs . .All of the 4 LEDs are consistently ON  after the reset while the boot continues into Linux.

  • U-Boot SPL 2025.01-00547-g3bcfad6cee95-dirty (Jul 23 2025 - 16:49:22 +0000)
    SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
    SPL initial stack usage: 13568 bytes
    Trying to boot from MMC2
    board_fit_image_post_process: processing image: addr=80000000, size=54436, os=arm-trusted-firmware
    board_fit_image_post_process: matched image for ID 1
    board_fit_image_post_process: processing image: addr=9e800000, size=709668, os=tee
    board_fit_image_post_process: matched image for ID 2
    board_fit_image_post_process: processing image: addr=89000000, size=599356, os=DM
    board_fit_image_post_process: matched image for ID 4
    Authentication passed
    board_fit_image_post_process: processing image: addr=9ca00000, size=32133, os=tifsstub-hs
    board_fit_image_post_process: matched image for ID 5
    board_fit_image_post_process: processing image: addr=9ca00000, size=30387, os=tifsstub-fs
    board_fit_image_post_process: matched image for ID 6
    tifsstub-type: tifsstub-fs
    board_fit_image_post_process: processing image: addr=9ca00000, size=29643, os=tifsstub-gp
    board_fit_image_post_process: matched image for ID 7
    Loading falcon payload from MMC2
    board_fit_image_post_process: processing image: addr=82000000, size=17338009, os=linux
    Authentication passed
    board_fit_image_post_process: processing image: addr=ffffffff, size=63599, os=
    Authentication passed
    
    U-Boot SPL 2025.01-00547-g3bcfad6cee95-dirty (Jul 23 2025 - 16:49:22 +0000)
    SYSFW ABI: 4.0 (firmware rev 0x000b '11.1.5--v11.01.05 (Fancy Rat)')
    SPL initial stack usage: 13568 bytes
    Trying to boot from MMC2
    board_fit_image_post_process: processing image: addr=80000000, size=54436, os=arm-trusted-firmware
    board_fit_image_post_process: matched image for ID 1
    board_fit_image_post_process: processing image: addr=9e800000, size=709668, os=tee
    board_fit_image_post_process: matched image for ID 2
    board_fit_image_post_process: processing image: addr=89000000, size=599356, os=DM
    board_fit_image_post_process: matched image for ID 4
    Authentication passed
    board_fit_image_post_process: processing image: addr=9ca00000, size=32133, os=tifsstub-hs
    board_fit_image_post_process: matched image for ID 5
    board_fit_image_post_process: processing image: addr=9ca00000, size=30387, os=tifsstub-fs
    board_fit_image_post_process: matched image for ID 6
    tifsstub-type: tifsstub-fs
    board_fit_image_post_process: processing image: addr=9ca00000, size=29643, os=tifsstub-gp
    board_fit_image_post_process: matched image for ID 7
    Loading falcon payload from MMC2
    board_fit_image_post_process: processing image: addr=82000000, size=17338009, os=linux
    Authentication passed
    board_fit_image_post_process: processing image: addr=ffffffff, size=63599, os=
    Authentication passed
    Loading Environment from nowhere... OK
    jump_to_image_no_args: Authenticating image: addr=80000000, size=54436, os=arm-trusted-firmware
    Authentication passed
    jump_to_image_no_args: Authenticating image: addr=9e800000, size=709668, os=tee
    Authentication passed
    jump_to_image_no_args: jumping to address 9d167d48
    Starting ATF on ARM64 core...
    
    NOTICE:  BL31: v2.13.0(release):
    NOTICE:  BL31: Built : 07:01:36, Jul  1 2025
    systemd 255.21^ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN -IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -TPM2 -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
    Detected architecture arm64.
    
    Welcome to Arago 2025.01!
    
    Hostname set to <am62axx-evm>.
    /usr/lib/systemd/system/bt-enable.service:9: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether.
    Queued start job for default target Multi-User System.
    [  OK  ] Created slice Slice /system/getty.
    [  OK  ] Created slice Slice /system/modprobe.
    [  OK  ] Created slice Slice /system/serial-getty.
    [  OK  ] Created slice User and Session Slice.
    [  OK  ] Started Dispatch Password Requests to Console Directory Watch.
    [  OK  ] Started Forward Password Requests to Wall Directory Watch.
             Expecting device /dev/ttyS2...
    [  OK  ] Reached target Path Units.
    [  OK  ] Reached target Remote File Systems.
    [  OK  ] Reached target Slice Units.
    [  OK  ] Reached target Swaps.
    [  OK  ] Listening on RPCbind Server Activation Socket.
    [  OK  ] Reached target RPC Port Mapper.
    [  OK  ] Listening on Process Core Dump Socket.
    [  OK  ] Listening on initctl Compatibility Named Pipe.
    [  OK  ] Listening on Journal Audit Socket.
    [  OK  ] Listening on Journal Socket (/dev/log).
    [  OK  ] Listening on Journal Socket.
    [  OK  ] Listening on Network Service Netlink Socket.
    [  OK  ] Listening on udev Control Socket.
    [  OK  ] Listening on udev Kernel Socket.
    [  OK  ] Listening on User Database Manager Socket.
             Mounting POSIX Message Queue File System...
             Mounting Temporary Directory /tmp...
             Starting Create List of Static Device Nodes...
             Starting Load Kernel Module configfs...
             Starting Load Kernel Module drm...
             Starting Load Kernel Module fuse...
             Starting Start psplash boot splash screen...
             Starting RPC Bind...
             Starting File System Check on Root Device...
             Starting Journal Service...
             Starting Load Kernel Modules...
             Starting Generate network units from Kernel command line...
             Starting Coldplug All udev Devices...
    [  OK  ] Mounted POSIX Message Queue File System.
    [  OK  ] Mounted Temporary Directory /tmp.
    [  OK  ] Finished Create List of Static Device Nodes.
    modprobe@configfs.service: Deactivated successfully.
    [  OK  ] Finished Load Kernel Module configfs.
    modprobe@drm.service: Deactivated successfully.
    [  OK  ] Finished Load Kernel Module drm.
    modprobe@fuse.service: Deactivated successfully.
    [  OK  ] Finished Load Kernel Module fuse.
    psplash-start.service: Main process exited, code=exited, status=255/EXCEPTION
    psplash-start.service: Failed with result 'exit-code'.
    [FAILED] Failed to start Start psplash boot splash screen.
    See 'systemctl status psplash-start.service' for details.
    [DEPEND] Dependency failed for Start psplas…temd progress communication helper.
    psplash-systemd.service: Job psplash-systemd.service/start failed with result 'dependency'.
             Mounting FUSE Control File System...
             Mounting Kernel Configuration File System...
             Starting Create Static Device Nodes in /dev gracefully...
    [  OK  ] Started RPC Bind.
    [  OK  ] Finished Load Kernel Modules.
    [  OK  ] Finished Generate network units from Kernel command line.
    [  OK  ] Mounted FUSE Control File System.
             Starting Apply Kernel Variables...
    [  OK  ] Mounted Kernel Configuration File System.
    [  OK  ] Finished File System Check on Root Device.
             Starting Remount Root and Kernel File Systems...
    [  OK  ] Started Journal Service.
    [  OK  ] Finished Create Static Device Nodes in /dev gracefully.
    [  OK  ] Finished Apply Kernel Variables.
    [  OK  ] Finished Remount Root and Kernel File Systems.
             Starting Flush Journal to Persistent Storage...
             Starting Create Static Device Nodes in /dev...
    [  OK  ] Finished Flush Journal to Persistent Storage.
    [  OK  ] Finished Create Static Device Nodes in /dev.
    [  OK  ] Reached target Preparation for Local File Systems.
             Starting Rule-based Manager for Device Events and Files...
             Starting User Database Manager...
    [  OK  ] Started User Database Manager.
    [  OK  ] Started Rule-based Manager for Device Events and Files.
    [  OK  ] Finished Coldplug All udev Devices.
    [  OK  ] Found device /dev/ttyS2.
             Mounting /var/volatile...
    [  OK  ] Mounted /var/volatile.
             Starting Load/Save OS Random Seed...
    [  OK  ] Reached target Local File Systems.
             Starting Create System Files and Directories...
    [  OK  ] Finished Load/Save OS Random Seed.
    [  OK  ] Finished Create System Files and Directories.
             Starting Network Name Resolution...
             Starting Network Time Synchronization...
             Starting Record System Boot/Shutdown in UTMP...
    [  OK  ] Finished Record System Boot/Shutdown in UTMP.
    [  OK  ] Started Network Time Synchronization.
    [  OK  ] Reached target System Time Set.
    [  OK  ] Started Network Name Resolution.
    [  OK  ] Reached target Host and Network Name Lookups.
    [  OK  ] Reached target System Initialization.
    [  OK  ] Started Daily Cleanup of Temporary Directories.
    [  OK  ] Reached target Timer Units.
    [  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
    [  OK  ] Listening on D-Bus System Message Bus Socket.
             Starting Docker Socket for the API...
    [  OK  ] Listening on dropbear.socket.
    [  OK  ] Listening on PC/SC Smart Card Daemon Activation Socket.
             Starting D-Bus System Message Bus...
             Starting Reboot and dump vmcore via kexec...
    [  OK  ] Listening on Docker Socket for the API.
    [  OK  ] Reached target Socket Units.
    [  OK  ] Finished Reboot and dump vmcore via kexec.
    [  OK  ] Started D-Bus System Message Bus.
    [  OK  ] Reached target Basic System.
             Starting Avahi mDNS/DNS-SD Stack...
    [  OK  ] Started A minimalistic network con…h DHCPv4, rdisc and DHCPv6 support.
             Starting Print notice about GPLv3 packages...
             Starting IPv6 Packet Filtering Framework...
             Starting IPv4 Packet Filtering Framework...
    [  OK  ] Started irqbalance daemon.
             Starting Expand the rootfs partiti…to full size of the boot device....
    [  OK  ] Started strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.
             Starting User Login Management...
             Starting Telnet Server...
    [  OK  ] Reached target Hardware activated USB gadget.
    [  OK  ] Finished Telnet Server.
    irqbalanced.service: Referenced but unset environment variable evaluates to an empty string: IRQBALANCE_ARGS
    [  OK  ] Started Avahi mDNS/DNS-SD Stack.
    [  OK  ] Finished IPv4 Packet Filtering Framework.
    [  OK  ] Finished IPv6 Packet Filtering Framework.
    [  OK  ] Reached target Preparation for Network.
             Starting Network Configuration...
    [  OK  ] Finished Expand the rootfs partition to full size of the boot device..
    [  OK  ] Started User Login Management.
    [  OK  ] Created slice Slice /system/tee-supplicant.
    [  OK  ] Started TEE Supplicant on teepriv0.
    [  OK  ] Started Network Configuration.
    tee-supplicant@teepriv0.service: Referenced but unset environment variable evaluates to an empty string: OPTARGS
    [  OK  ] Reached target Network.
    [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
             Starting Enable and configure wl18xx bluetooth stack...
             Starting containerd container runtime...
             Starting LLDP daemon...
    [  OK  ] Started Netperf Benchmark Server.
             Starting Simple Network Management Protocol (SNMP) Daemon....
             Starting Permit User Sessions...
             Starting Virtual Console Setup...
    bt-enable.service: Deactivated successfully.
    [  OK  ] Finished Enable and configure wl18xx bluetooth stack.
    lldpd.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS, LLDPD_OPTIONS
    [  OK  ] Finished Permit User Sessions.
    [  OK  ] Started Getty on tty1.
    [  OK  ] Started Serial Getty on ttyS2.
    [  OK  ] Reached target Login Prompts.
    [  OK  ] Started LLDP daemon.
    [  OK  ] Finished Virtual Console Setup.
    [  OK  ] Started Simple Network Management Protocol (SNMP) Daemon..
    [  OK  ] Created slice Slice /system/systemd-fsck.
             Expecting device /dev/mmcblk0p1...
             Expecting device /dev/mmcblk0p21...
    [  OK  ] Found device /dev/mmcblk0p21.
             Starting File System Check on /dev/mmcblk0p21...
             Expecting device /dev/mmcblk1p1...
    [  OK  ] Found device /dev/mmcblk0p1.
    [  OK  ] Finished File System Check on /dev/mmcblk0p21.
             Mounting /run/media/mnt/vendor/pers-mmcblk0p21...
             Starting File System Check on /dev/mmcblk0p1...
    [  OK  ] Mounted /run/media/mnt/vendor/pers-mmcblk0p21.
    [  OK  ] Found device /dev/mmcblk1p1.
    [  OK  ] Finished File System Check on /dev/mmcblk0p1.
             Mounting /run/media/bootloader-mmcblk0p1...
             Starting File System Check on /dev/mmcblk1p1...
    [  OK  ] Mounted /run/media/bootloader-mmcblk0p1.
    [  OK  ] Finished File System Check on /dev/mmcblk1p1.
             Mounting /run/media/boot-mmcblk1p1...
    [  OK  ] Mounted /run/media/boot-mmcblk1p1.
    [  OK  ] Started containerd container runtime.
    ***************************************************************
    ***************************************************************
    NOTICE: This file system contains the following GPL-3.0 packages:
            bash
            binutils
            cifs-utils
            dosfstools
            gdbserver
            grub-common
            grub-editenv
            grub-efi
            hidapi
            kbd-keymaps-pine
            less
            libbfd
            libdebuginfod1
            libdw1
            libelf1
            libgcc1
            libopcodes
            libreadline8
            libstdc++6
            parted
            tar
    
    If you do not wish to distribute GPL-3.0 components please remove
    the above packages prior to distribution.  This can be done using
    the opkg remove command.  i.e.:
        opkg remove <package>
    Where <package> is the name printed in the list above
    
    NOTE: If the package is a dependency of another package you
          will be notified of the dependent packages.  You should
          use the --force-removal-of-dependent-packages option to
          also remove the dependent packages as well
    ***************************************************************
    ***************************************************************
    gplv3-notice.service: Deactivated successfully.
    [  OK  ] Finished Print notice about GPLv3 packages.
    [  OK  ] Reached target Multi-User System.
    [  OK  ] Started Memory allocation Script.
    [  OK  ] Started Firmware Script.
    [  OK  ] Started GPIO Monitor Script.
    [  OK  ] Started Network setup Script.
             Starting Record Runlevel Change in UTMP...
    devmem.service: Deactivated successfully.
    Startup finished in 1.079s (kernel) + 6.201s (userspace) = 7.281s.
    network-setup.service: Deactivated successfully.
    
    am62axx-evm-tcs
    am62axx-evm login: root (automatic login)
    We will try to add additional debug prints  . Meanwhile I am sharing logs with increased log level

  •   we could also reproduce the issue on EMMC boot mode so it does not seem to be related to sdcard.

  • Hi Priyanka,

    Thanks for the additional information. I am still unable to think what could cause the issue. Let me see if I can reproduce the issue on my SK-AM62A evm. I likely will start the work early next week.