• State TI Thinks Resolved
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1976 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

PROCESSOR-SDK-AM65X: SD card boot fails on IDK

PROCESSOR-SDK-AM65X: SD card boot issue on EVM

Tarun Srivastava
Prodigy 240 points

Part Number: PROCESSOR-SDK-AM65X

Hi, 

I have an AM65x-EVM and I am trying to boot it from SD card (16GB) by programming the pre-built images.

I am using the Software PROCESSOR-SDK-LINUX-AM65X 06_00_00_07.

There's a shell script named create-sdcard.sh under bin/. The execution of this script is successful. (Logs Attached)

Fullscreen create-sdcard.sh-logs.txt Download 
tarun@LAP000280:~/Tarun/PROJECT/TI/AM65x-EVM/Software/linux$ sudo ./bin/create-sdcard.sh 
[sudo] password for tarun: 


################################################################################

This script will create a bootable SD card from custom or pre-built binaries.

The script must be run with root permissions and from the bin directory of
the SDK

Example:
 $ sudo ./create-sdcard.sh

Formatting can be skipped if the SD card is already formatted and
partitioned properly.

################################################################################


Available Drives to write images to: 

#  major   minor    size   name 
1: 179        0   15558144 mmcblk0
 
Enter Device Number or n to exit: 1
 
mmcblk0 was selected

/dev/mmcblk0 is an mmcblkx device
Unmounting the mmcblk0 drives
 unmounted /dev/mmcblk0p1
 unmounted /dev/mmcblk0p2
Current size of mmcblk0p1 71680 bytes
Current size of mmcblk0p2 15469568 bytes

################################################################################

	Select 2 partitions if only need boot and rootfs (most users).
	Select 3 partitions if need SDK & other content on SD card.  This is
        usually used by device manufacturers with access to partition tarballs.

	****WARNING**** continuing will erase all data on mmcblk0

################################################################################

Number of partitions needed [2/3] : 2

 
Now partitioning mmcblk0 with 2 partitions...
 

################################################################################

		Now making 2 partitions

################################################################################

1024+0 records in
1024+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.190086 s, 5.5 MB/s
DISK SIZE - 15931539456 bytes

################################################################################

		Partitioning Boot

################################################################################
mkfs.fat 3.0.28 (2015-05-16)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows

################################################################################

		Partitioning rootfs

################################################################################
mke2fs 1.42.13 (17-May-2015)
/dev/mmcblk0p2 contains a ext3 file system labelled 'rootfs'
	last mounted on / on Fri Oct 11 09:51:18 2019
Proceed anyway? (y,n) y
Discarding device blocks: done                            
Creating filesystem with 3867392 4k blocks and 967232 inodes
Filesystem UUID: f625f7a3-223c-4bf4-a22e-f8d55ad746ba
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done   



################################################################################

   Partitioning is now done
   Continue to install filesystem or select 'n' to safe exit

   **Warning** Continuing will erase files any files in the partitions

################################################################################


Would you like to continue? [y/n] : y

 
 
Mount the partitions 
 
Emptying partitions 
 

Syncing....

################################################################################

	Choose file path to install from

	1 ) Install pre-built images from SDK
	2 ) Enter in custom boot and rootfs file paths

################################################################################

Choose now [1/2] : 1

 
Will now install from SDK pre-built images
now installing:  linux

################################################################################

   Multiple rootfs Tarballs found

################################################################################

	 1:tisdk-rootfs-image-am65xx-evm.tar.xz
	 2:tisdk-docker-rootfs-image-am65xx-evm.tar.xz

Enter Number of rootfs Tarball: 1
 
################################################################################

	Copying files now... will take minutes

################################################################################

Copying boot partition



tispl.bin copied


tiboot3.bin copied


sysfw.itb copied


u-boot.img copied

uEnv.txt copied

Copying rootfs System partition
                                                                                                                                                                                                            

Syncing...
 
Un-mount the partitions 
 
Remove created temp directories 
 
Operation Finished

The Boot Switch configuration is as follows: 

sw3.2 - on

sw3.3 - on

sw2.3 - on

When I plug the SD card to the EVM and boot the platform, it gives the following error:

FDT creation failed! hanging...### ERROR ### Please RESET the board ###

Find the complete bootlogs below,

Fullscreen 8156.bootlogs.txt Download 
OPTIONS: I18n 
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB0, 09:42:07

Press CTRL-A Z for help on special keys


U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:46:46 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.01-rc2
NOTICE:  BL31: Built : 04:28:26, Jul  7 2019
I/TC: 
I/TC: OP-TEE version: 3.2.0-583-g251f7c6-dev #1 Sun Jul  7 04:40:43 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)
detected OLDI-LCD1EVM
Trying to boot from MMC2
cannot find image node 'k3-am654-evm-oldi-lcd1evm.dtbo': -1


U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)

Model: Texas Instruments AM654 Base Board
DRAM:  4 GiB
MMC:   sdhci@4f80000: 0, sdhci@04FA0000: 1
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
detected OLDI-LCD1EVM
Net:   
Warning: cpsw_nuss@046000000 using MAC address from ROM
eth0: cpsw_nuss@046000000, eth1: pruss2_eth
Hit any key to stop autoboot:  0 
Trying to boot Android from eMMC ...
switch to partitions #0, OK
mmc0(part 0) is current device

MMC read: dev # 0, block # 26624, count 81920 ... 81920 blocks read: OK
## Loading kernel from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'kernel@1' kernel subimage
     Description:  LCPD kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x900000c4
     Data Size:    22745096 Bytes = 21.7 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80080000
     Entry Point:  0x80080000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  Android Ramdisk Image
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x915b1180
     Data Size:    1131177 Bytes = 1.1 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
   Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'fdt@1' fdt subimage
     Description:  AM65x Base Board
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x916c54b8
     Data Size:    60796 Bytes = 59.4 KiB
     Architecture: AArch64
     Load Address: 0x83000000
   Verifying Hash Integrity ... OK
   Loading fdt from 0x916c54b8 to 0x83000000
## Loading fdt from FIT Image at 90000000 ...
   Using 'k3-am654-evm-oldi-lcd1evm.dtbo' configuration
   Trying 'fdt@6' fdt subimage
     Description:  AM65x OLDI-LCD Support Overlay
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x916d7910
     Data Size:    2244 Bytes = 2.2 KiB
     Architecture: AArch64
     Load Address: 0x83280000
   Verifying Hash Integrity ... OK
   Loading fdt from 0x916d7910 to 0x83280000
   Booting using the fdt blob at 0x83000000
   Loading Kernel Image ... OK
   Loading Ramdisk to fddb9000, end fdecd2a9 ... OK
   Loading Device Tree to 00000000fdda6000, end 00000000fddb813d ... OK
ft_board_setup: fixing up msmc ram failed -1
ERROR: board-specific fdt fixup failed: FDT_ERR_NOTFOUND
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###
 

I can see that the SD card is programmed with the pre-built binaries and filesystem properly. Check the screenshot (boot  and rootfs/boot/) below:

Let us know if you have faced this issue and fixed it.

Thanks, 

Tarun

  • 0
    TI__Guru**** 170625 points

    Hi Tarun,

    From the log, seems you have issue with your LCD board detection. Could you please try to remove LCD display board from AM65x EVM base board and try again to boot? Thus we will be sure if the issue is related to LCD board or not.

    Note also that LCD board have several revisions, check below e2e thread for details:

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Hi Pavel,

    I tried to boot the EVM with LCD and the error is still there.

    Find the bootlogs without LCD connected to the platform.

    Fullscreen bootlogs-without-lcd.txt Download 
    OPTIONS: I18n 
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB0, 16:10:05

Press CTRL-A Z for help on special keys


U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:46:46 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.01-rc2
NOTICE:  BL31: Built : 04:28:26, Jul  7 2019
I/TC: 
I/TC: OP-TEE version: 3.2.0-583-g251f7c6-dev #1 Sun Jul  7 04:40:43 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)
Trying to boot from MMC2


U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)

Model: Texas Instruments AM654 Base Board
DRAM:  4 GiB
MMC:   sdhci@4f80000: 0, sdhci@04FA0000: 1
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   
Warning: cpsw_nuss@046000000 using MAC address from ROM
eth0: cpsw_nuss@046000000, eth1: pruss2_eth
Hit any key to stop autoboot:  0 
Trying to boot Android from eMMC ...
switch to partitions #0, OK
mmc0(part 0) is current device

MMC read: dev # 0, block # 26624, count 81920 ... 81920 blocks read: OK
## Loading kernel from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'kernel@1' kernel subimage
     Description:  LCPD kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x900000c4
     Data Size:    22745096 Bytes = 21.7 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80080000
     Entry Point:  0x80080000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  Android Ramdisk Image
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x915b1180
     Data Size:    1131177 Bytes = 1.1 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
   Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'fdt@1' fdt subimage
     Description:  AM65x Base Board
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x916c54b8
     Data Size:    60796 Bytes = 59.4 KiB
     Architecture: AArch64
     Load Address: 0x83000000
   Verifying Hash Integrity ... OK
   Loading fdt from 0x916c54b8 to 0x83000000
   Booting using the fdt blob at 0x83000000
   Loading Kernel Image ... OK
   Loading Ramdisk to fddb9000, end fdecd2a9 ... OK
   Loading Device Tree to 00000000fdda7000, end 00000000fddb8d7b ... OK
ft_board_setup: fixing up msmc ram failed -1
ERROR: board-specific fdt fixup failed: FDT_ERR_NOTFOUND
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###

    Thanks,

    Tarun 

  • 0 in reply to Tarun Srivastava
    Prodigy 240 points

    Hi Pavel,

    I tried to boot the EVM without* LCD and the error is still there.

    Find the bootlogs without LCD connected to the platform.

    Fullscreen 4162.bootlogs-without-lcd.txt Download 
    OPTIONS: I18n 
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB0, 16:10:05

Press CTRL-A Z for help on special keys


U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:46:46 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.01-rc2
NOTICE:  BL31: Built : 04:28:26, Jul  7 2019
I/TC: 
I/TC: OP-TEE version: 3.2.0-583-g251f7c6-dev #1 Sun Jul  7 04:40:43 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)
Trying to boot from MMC2


U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)

Model: Texas Instruments AM654 Base Board
DRAM:  4 GiB
MMC:   sdhci@4f80000: 0, sdhci@04FA0000: 1
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   
Warning: cpsw_nuss@046000000 using MAC address from ROM
eth0: cpsw_nuss@046000000, eth1: pruss2_eth
Hit any key to stop autoboot:  0 
Trying to boot Android from eMMC ...
switch to partitions #0, OK
mmc0(part 0) is current device

MMC read: dev # 0, block # 26624, count 81920 ... 81920 blocks read: OK
## Loading kernel from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'kernel@1' kernel subimage
     Description:  LCPD kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x900000c4
     Data Size:    22745096 Bytes = 21.7 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80080000
     Entry Point:  0x80080000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  Android Ramdisk Image
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x915b1180
     Data Size:    1131177 Bytes = 1.1 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
   Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at 90000000 ...
   Using 'k3-am654-base-board.dtb' configuration
   Trying 'fdt@1' fdt subimage
     Description:  AM65x Base Board
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x916c54b8
     Data Size:    60796 Bytes = 59.4 KiB
     Architecture: AArch64
     Load Address: 0x83000000
   Verifying Hash Integrity ... OK
   Loading fdt from 0x916c54b8 to 0x83000000
   Booting using the fdt blob at 0x83000000
   Loading Kernel Image ... OK
   Loading Ramdisk to fddb9000, end fdecd2a9 ... OK
   Loading Device Tree to 00000000fdda7000, end 00000000fddb8d7b ... OK
ft_board_setup: fixing up msmc ram failed -1
ERROR: board-specific fdt fixup failed: FDT_ERR_NOTFOUND
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###

    Thanks,

    Tarun

  • 0 in reply to Tarun Srivastava
    TI__Guru**** 170625 points

    Tarun,

    From the log, seems that you have issue with boot arguments (u-boot environments variables). I see you are trying to load kernel and filesystem (Android) from eMMC (MMC0), instead of kernel and rootfs (Linux) from SD card (MMC1).

    Hit any key to stop autoboot:  0
    Trying to boot Android from eMMC ...
    switch to partitions #0, OK
    mmc0(part 0) is current device

    I would suggest you to check your uEnv.txt file. You can also interrupt the boot process, enter into the uboot prompt, and execute the commands manually.

    Check also below release note:

    For am57xx devices, the location of the saved U-Boot environment has moved from the external SD card to eMMC. Because of this change, the state of the U-Boot environment can no longer be guaranteed on a newly created SD card. The uEnv.txt file located on the boot partition of the SD card contains the logic to compensate for this change. Upon the initial boot, the environment will be reset to the default, and the empty file ”.psdk_setup” will be created on the boot partition. Subsequent boots will detect this file and bypass resetting the environment.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Hi Pavel, 

    I am not using a custom uEnv.txt.

    When I am running create-sdcard.sh script which will program the prebuilt binaries (including uEnv.txt) to the SD-card, then it should boot successfully.

    According to you, the uEnv.txt should compensate for this change but it's not happening and I am using the uEnv.txt which is provided in prebuilt_images directory. 

    The create-sdcard.sh script is designed in such a way that it takes all the required prebuilt images and program it to the sd card.

    I can see that in the uEnv.txt (provided by TI) resets the u-boot environment variables and then saves the environment. By doing so, the board should have booted successfully, but it's not happening. After resetting the environment, u-boot will initialize the default environment which is defined in u-boot.img (provided by TI).

     


    Kindly, help me to solve this issue with a permanent solution.

    Thanks,

    Tarun

  • 0 in reply to Tarun Srivastava
    TI__Guru**** 170625 points

    Taurun,

    Do you mean that you observe this issue with the default/pre-built uEnv.txt file?

    Refer to below e2e threads regarding uenv.txt usage info:

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Hi Pavel, 

    I can see the links that you have shared has discussions regarding uEnv.txt but I couldn't find the solution.

    Can you tell me, in simple words, the steps to be followed to boot the board using pre-built binaries provided by TI in the above mentioned SDK?

    Assuming that I have an SD card ready by using the script create-sdcard.sh.

    Thanks,

    Tarun

  • 0 in reply to Tarun Srivastava
    TI__Guru**** 170625 points

    Tarun,

    I test on my side, I have TMDX654GPEVM base board, rev E3.

    I created one 32GByte SD card with below script:

    ti-processor-sdk-linux-am65xx-evm-06.00.00.07/bin/create-sdcard.sh

    I select default (pre-built) images.

    Then plug this SD card into EVM J17 SD CARD holder, make boot switches for SD boot (SW3.2 = ON, SW3.3 = ON, SW2.3 = ON, all rest OFF), plug USB cable to UART J42 connector, plug 12V power supply and power on the board. I have below boot log:

    Fullscreen 6366.am65x_gpevm_boot_log.txt Download 
    U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:46:46 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.01-rc2
NOTICE:  BL31: Built : 04:28:26, Jul  7 2019
I/TC: 
I/TC: OP-TEE version: 3.2.0-583-g251f7c6-dev #1 Sun Jul  7 04:40:43 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)
Trying to boot from MMC2


U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)

Model: Texas Instruments AM654 Base Board
DRAM:  4 GiB
MMC:   sdhci@4f80000: 0, sdhci@04FA0000: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   
Warning: cpsw_nuss@046000000 using MAC address from ROM
eth0: cpsw_nuss@046000000, eth1: pruss2_eth
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
** Unable to read file boot.scr **
1490 bytes read in 1 ms (1.4 MiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
1 bytes read in 1 ms (1000 Bytes/s)
Already setup.
12632072 bytes read in 1052 ms (11.5 MiB/s)
71809 bytes read in 8 ms (8.6 MiB/s)
## Flattened Device Tree blob at 82000000
   Booting using the fdt blob at 0x82000000
   Loading Device Tree to 00000000fddb9000, end 00000000fdecdfff ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 4.19.38-g4dae378bbe (oe-user@oe-host) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 SMP PREEMPT Sun Jul 7 03:42:51 UTC 2019
[    0.000000] Machine model: Texas Instruments AM654 Base Board
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[    0.000000] bootconsole [ns16550a0] enabled
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009b000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9b000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009b100000, size 15 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@9b100000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009c000000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9c000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009c100000, size 7 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@9c100000, compatible id shared-dma-pool
[    0.000000] cma: Reserved 512 MiB at 0x00000000c0000000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] random: get_random_bytes called from start_kernel+0x94/0x3e4 with crng_init=0
[    0.000000] percpu: Embedded 2 pages/cpu s48536 r8192 d74344 u131072
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: enabling workaround for ARM erratum 845719
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] CPU features: detected: Kernel page table isolation (KPTI)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 64704
[    0.000000] Kernel command line: console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 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) root=PARTUUID=265add23-02 rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes)
[    0.000000] Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes)
[    0.000000] software IO TLB: mapped [mem 0xf9db0000-0xfddb0000] (64MB)
[    0.000000] Memory: 3529856K/4145152K available (8062K kernel code, 752K rwdata, 2880K rodata, 576K init, 614K bss, 91008K reserved, 524288K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] ITS [mem 0x01820000-0x0182ffff]
[    0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
[    0.000000] ITS@0x0000000001820000: allocated 1048576 Devices @8c0800000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GIC: using LPI property table @0x00000008c00c0000
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001880000
[    0.000000] CPU0: using LPI pending table @0x00000008c00d0000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns
[    0.000005] sched_clock: 56 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
[    0.008678] Console: colour dummy device 80x25
[    0.013274] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.023966] pid_max: default: 32768 minimum: 301
[    0.028795] Security Framework initialized
[    0.033052] Mount-cache hash table entries: 8192 (order: 0, 65536 bytes)
[    0.039933] Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes)
[    0.071374] ASID allocator initialised with 32768 entries
[    0.084940] rcu: Hierarchical SRCU implementation.
[    0.098002] Platform MSI: gic-its@18200000 domain created
[    0.103806] PCI/MSI: /interconnect@100000/interrupt-controller@1800000/gic-its@18200000 domain created
[    0.121372] smp: Bringing up secondary CPUs ...
[    0.158506] Detected VIPT I-cache on CPU1
[    0.158543] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000
[    0.158602] CPU1: using LPI pending table @0x00000008c0330000
[    0.158646] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.220188] Detected VIPT I-cache on CPU2
[    0.220231] GICv3: CPU2: found redistributor 100 region 0:0x00000000018c0000
[    0.220293] CPU2: using LPI pending table @0x00000008c03c0000
[    0.220340] CPU2: Booted secondary processor 0x0000000100 [0x410fd034]
[    0.252603] Detected VIPT I-cache on CPU3
[    0.252631] GICv3: CPU3: found redistributor 101 region 0:0x00000000018e0000
[    0.252690] CPU3: using LPI pending table @0x00000008c0450000
[    0.252721] CPU3: Booted secondary processor 0x0000000101 [0x410fd034]
[    0.252864] smp: Brought up 1 node, 4 CPUs
[    0.328501] SMP: Total of 4 processors activated.
[    0.333321] CPU features: detected: GIC system register CPU interface
[    0.339934] CPU features: detected: 32-bit EL0 Support
[    0.367728] CPU: All CPU(s) started at EL2
[    0.371948] alternatives: patching kernel code
[    0.377949] devtmpfs: initialized
[    0.392333] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.402334] futex hash table entries: 1024 (order: 0, 65536 bytes)
[    0.410042] pinctrl core: initialized pinctrl subsystem
[    0.416036] NET: Registered protocol family 16
[    0.421869] vdso: 2 pages (1 code @ (____ptrval____), 1 data @ (____ptrval____))
[    0.429459] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.442845] DMA: preallocated 256 KiB pool for atomic allocations
[    0.451332] davinci_gpio 42110000.wkup_gpio0: IRQ not populated, err = -517
[    0.465096] davinci_gpio 600000.main_gpio0: IRQ not populated, err = -517
[    0.472255] davinci_gpio 601000.main_gpio1: IRQ not populated, err = -517
[    0.489917] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.496798] HugeTLB registered 512 MiB page size, pre-allocated 0 pages
[    0.505547] cryptd: max_cpu_qlen set to 1000
[    0.511651] media: Linux media interface: v0.10
[    0.516328] videodev: Linux video capture interface: v2.00
[    0.521986] pps_core: LinuxPPS API ver. 1 registered
[    0.527069] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.536429] PTP clock support registered
[    0.540481] EDAC MC: Ver: 3.0.0
[    0.544886] Advanced Linux Sound Architecture Driver Initialized.
[    0.552059] clocksource: Switched to clocksource arch_sys_counter
[    0.558508] VFS: Disk quotas dquot_6.6.0
[    0.562622] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)
[    0.576888] NET: Registered protocol family 2
[    0.582053] tcp_listen_portaddr_hash hash table entries: 4096 (order: 0, 65536 bytes)
[    0.590210] TCP established hash table entries: 32768 (order: 2, 262144 bytes)
[    0.597906] TCP bind hash table entries: 32768 (order: 3, 524288 bytes)
[    0.605259] TCP: Hash tables configured (established 32768 bind 32768)
[    0.612128] UDP hash table entries: 2048 (order: 0, 65536 bytes)
[    0.618391] UDP-Lite hash table entries: 2048 (order: 0, 65536 bytes)
[    0.625269] NET: Registered protocol family 1
[    0.630330] RPC: Registered named UNIX socket transport module.
[    0.636409] RPC: Registered udp transport module.
[    0.641228] RPC: Registered tcp transport module.
[    0.646044] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.653778] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    0.667033] Initialise system trusted keyrings
[    0.671798] workingset: timestamp_bits=46 max_order=16 bucket_order=0
[    0.683676] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.690378] NFS: Registering the id_resolver key type
[    0.695585] Key type id_resolver registered
[    0.699872] Key type id_legacy registered
[    0.703987] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.711017] 9p: Installing v9fs 9p2000 file system support
[    0.721528] Key type asymmetric registered
[    0.725744] Asymmetric key parser 'x509' registered
[    0.730802] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.738492] io scheduler noop registered
[    0.742519] io scheduler deadline registered
[    0.747050] io scheduler cfq registered (default)
[    0.751875] io scheduler mq-deadline registered
[    0.756532] io scheduler kyber registered
[    0.762233] pinctrl-single 4301c000.pinmux: 70 pins, size 280
[    0.768776] pinctrl-single 11c000.pinmux: 185 pins, size 740
[    0.774718] pinctrl-single 11c2e8.pinmux: 9 pins, size 36
[    0.781431] pinctrl-single a40000.timesync_router: 512 pins, size 2048
[    0.796292] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled
[    0.818730] brd: module loaded
[    0.829248] loop: module loaded
[    0.834668] libphy: Fixed MDIO Bus: probed
[    0.839437] tun: Universal TUN/TAP device driver, 1.6
[    0.845326] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    0.853350] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    0.859465] sky2: driver version 1.30
[    0.864654] VFIO - User Level meta-driver version: 0.3
[    0.870781] i2c /dev entries driver
[    0.875650] sdhci: Secure Digital Host Controller Interface driver
[    0.881981] sdhci: Copyright(c) Pierre Ossman
[    0.886881] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.893896] ledtrig-cpu: registered to indicate activity on CPUs
[    0.900144] ti-sci interconnect@100000:interconnect@28380000:interconnect@42040000:dmsc: invalid resource
[    0.910943] optee: probing for conduit method from DT.
I/TC: Dynamic shared memory is disabled
[    0.916247] optee: revision 3.4 (251f7c63)
[    0.920179] optee: initialized driver
[    0.929507] NET: Registered protocol family 17
[    0.934151] 9pnet: Installing 9P2000 support
[    0.938583] Key type dns_resolver registered
[    0.943598] registered taskstats version 1
[    0.947800] Loading compiled-in X.509 certificates
[    0.953741] davinci_gpio 42110000.wkup_gpio0: IRQ not populated, err = -517
[    0.961316] davinci_gpio 600000.main_gpio0: IRQ not populated, err = -517
[    0.968514] davinci_gpio 601000.main_gpio1: IRQ not populated, err = -517
[    0.984989] ti-sci interconnect@100000:interconnect@28380000:interconnect@42040000:dmsc: invalid resource
[    0.994988] ti-sci interconnect@100000:interconnect@28380000:interconnect@42040000:dmsc: ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
[    1.028252] random: fast init done
[    1.529690] davinci_gpio 42110000.wkup_gpio0: IRQ not populated, err = -517
[    1.537245] davinci_gpio 600000.main_gpio0: IRQ not populated, err = -517
[    1.544447] davinci_gpio 601000.main_gpio1: IRQ not populated, err = -517
[    1.552905] omap_i2c 42120000.i2c: bus 0 rev0.12 at 400 kHz
[    1.559427] omap_i2c 40b00000.i2c: bus 1 rev0.12 at 100 kHz
[    1.588747] omap_i2c 2000000.i2c: bus 2 rev0.12 at 400 kHz
[    1.595070] omap_i2c 2010000.i2c: bus 3 rev0.12 at 400 kHz
[    1.601431] omap_i2c 2020000.i2c: bus 4 rev0.12 at 400 kHz
[    1.607730] omap_i2c 2030000.i2c: bus 5 rev0.12 at 100 kHz
[    1.617444] k3-ringacc 2b800000.ringacc: Ring Accelerator probed rings:286, gp-rings[96,160] sci-dev-id:195
[    1.627444] k3-ringacc 2b800000.ringacc: dma-ring-reset-quirk: enabled
[    1.634132] k3-ringacc 2b800000.ringacc: RA Proxy rev. 66344100, num_proxies:64
[    1.641987] k3-ringacc 3c000000.ringacc: Ring Accelerator probed rings:818, gp-rings[304,464] sci-dev-id:187
[    1.652064] k3-ringacc 3c000000.ringacc: dma-ring-reset-quirk: enabled
[    1.658751] k3-ringacc 3c000000.ringacc: RA Proxy rev. 66344100, num_proxies:64
[    1.666542] omap8250 40a00000.serial: PM domain ti_sci_pd will not be powered off
[    1.674597] 40a00000.serial: ttyS1 at MMIO 0x40a00000 (irq = 8, base_baud = 6000000) is a 8250
[    1.684296] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 18, base_baud = 3000000) is a 8250
[    1.693071] console [ttyS2] enabled
[    1.693071] console [ttyS2] enabled
[    1.700125] bootconsole [ns16550a0] disabled
[    1.700125] bootconsole [ns16550a0] disabled
[    1.709530] 2810000.serial: ttyS3 at MMIO 0x2810000 (irq = 19, base_baud = 3000000) is a 8250
[    1.718795] 2820000.serial: ttyS4 at MMIO 0x2820000 (irq = 20, base_baud = 3000000) is a 8250
[    1.729834] cadence-qspi 47040000.spi: mt35xu512aba (65536 Kbytes)
[    1.736057] 7 cmdlinepart partitions found on MTD device 47040000.spi.0
[    1.742673] Creating 7 MTD partitions on "47040000.spi.0":
[    1.748166] 0x000000000000-0x000000080000 : "ospi.tiboot3"
[    1.754498] 0x000000080000-0x000000280000 : "ospi.tispl"
[    1.760492] 0x000000280000-0x000000680000 : "ospi.u-boot"
[    1.766589] 0x000000680000-0x0000006a0000 : "ospi.env"
[    1.772387] 0x0000006a0000-0x0000006c0000 : "ospi.env.backup"
[    1.778785] 0x0000006c0000-0x0000007c0000 : "ospi.sysfw"
[    1.784735] 0x000000800000-0x000004000000 : "ospi.rootfs"
[    1.900301] cadence-qspi 47040000.spi: Cadence QSPI NOR probe failed -517
[    1.915078] am65-cpsw-nuss 46000000.ethernet: rx-flow-id-base is not set -22
[    1.922253] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA07100, cpsw version 0x6BA80100 Ports: 2
[    1.933847] UDMA has not been proped
[    1.937442] am65-cpsw-nuss 46000000.ethernet: Failed to request tx dma channel -517
[    1.947565] am65-cpts 310d0000.cpts: CPTS ver 0x4e8a2109, freq:200000000, add_val:4 pps:0
[    1.956339] thermal thermal_zone1: failed to read out thermal zone (-22)
[    1.963062] thermal thermal_zone2: failed to read out thermal zone (-22)
[    1.970484] OF: /interconnect@100000/interconnect@28380000/rti@40610000: arguments longer than property
[    1.979891] keystone-wdt 40610000.rti: heartbeat 60 sec
[    1.986106] mmc0: Unknown controller version (4). You may experience problems.
[    2.024442] mmc0: SDHCI controller on 4f80000.sdhci [4f80000.sdhci] using ADMA 64-bit
[    2.033113] mmc1: Unknown controller version (4). You may experience problems.
[    2.071489] mmc1: SDHCI controller on 4fa0000.sdhci [4fa0000.sdhci] using ADMA 64-bit
[    2.087120] mmc0: new HS200 MMC card at address 0001
[    2.093318] mmcblk0: mmc0:0001 R1J56L 14.7 GiB 
[    2.099994] mmcblk0boot0: mmc0:0001 R1J56L partition 1 8.00 MiB
[    2.110064] mmcblk0boot1: mmc0:0001 R1J56L partition 2 8.00 MiB
[    2.116188] mmcblk0rpmb: mmc0:0001 R1J56L partition 3 4.00 MiB, chardev (243:0)
[    2.133670] omap-mailbox 31f80000.mailbox: omap mailbox rev 0x66fc5900
[    2.140664] omap-mailbox 31f81000.mailbox: omap mailbox rev 0x66fc5900
[    2.148292] ti-udma 285c0000.udmap: Channels: 96 (tchan: 48, echan: 0, rchan: 48, rflow: 96)
[    2.163184] ti-udma 31150000.udmap: Channels: 267 (tchan: 120, echan: 32, rchan: 150, rflow: 300)
[    2.174317] mmc1: new high speed SDHC card at address 1388
[    2.181084] mmcblk1: mmc1:1388 USD00 29.5 GiB 
[    2.199558]  mmcblk1: p1 p2
[    2.203814] cadence-qspi 47040000.spi: mt35xu512aba (65536 Kbytes)
[    2.210031] 7 cmdlinepart partitions found on MTD device 47040000.spi.0
[    2.216644] Creating 7 MTD partitions on "47040000.spi.0":
[    2.222141] 0x000000000000-0x000000080000 : "ospi.tiboot3"
[    2.228438] 0x000000080000-0x000000280000 : "ospi.tispl"
[    2.234446] 0x000000280000-0x000000680000 : "ospi.u-boot"
[    2.240489] 0x000000680000-0x0000006a0000 : "ospi.env"
[    2.246268] 0x0000006a0000-0x0000006c0000 : "ospi.env.backup"
[    2.252640] 0x0000006c0000-0x0000007c0000 : "ospi.sysfw"
[    2.258568] 0x000000800000-0x000004000000 : "ospi.rootfs"
[    2.271724] m25p80 spi7.0: n25q128a13 (16384 Kbytes)
[    2.277981] am65-cpsw-nuss 46000000.ethernet: rx-flow-id-base is not set -22
[    2.285154] am65-cpsw-nuss 46000000.ethernet: initializing am65 cpsw nuss version 0x6BA07100, cpsw version 0x6BA80100 Ports: 2
[    2.305423] am65-cpsw-nuss 46000000.ethernet: set new flow-id-base 48
[    2.318926] pps pps0: new PPS source ptp1
[    2.323179] am65-cpsw-nuss 46000000.ethernet: CPTS ver 0x4e8a2109, freq:200000000, add_val:4 pps:1
[    2.332159] am65-cpsw-nuss 46000000.ethernet: initialized cpsw ale version 0.4
[    2.339380] am65-cpsw-nuss 46000000.ethernet: ALE Table size 64
[    2.384080] am65-cpsw-nuss 46000000.ethernet: davinci mdio revision 9.7, bus freq 1000000
[    2.392258] libphy: 46000000.ethernet: probed
[    2.400123] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    2.407094] hctosys: unable to open rtc device (rtc0)
[    2.508693] ALSA device list:
[    2.511662]   No soundcards found.
[    3.416435] EXT4-fs (mmcblk1p2): recovery complete
[    3.422137] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[    3.430283] VFS: Mounted root (ext4 filesystem) on device 179:98.
[    3.444442] devtmpfs: mounted
[    3.447670] Freeing unused kernel memory: 576K
[    3.452167] Run /sbin/init as init process
[    3.997270] systemd[1]: System time before build time, advancing clock.
[    4.153036] NET: Registered protocol family 10
[    4.158600] Segment Routing with IPv6
[    4.241193] systemd[1]: systemd 239 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN -PCRE2 default-hierarchy=hybrid)
[    4.262922] systemd[1]: Detected architecture arm64.

Welcome to Arago 2019.05!

[    4.304988] systemd[1]: Set hostname to <am65xx-evm>.
[    4.556974] systemd[1]: File /lib/systemd/system/systemd-journald.service:36 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[    4.574066] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[    4.954492] random: systemd: uninitialized urandom read (16 bytes read)
[    4.964269] systemd[1]: Created slice system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[    4.980340] random: systemd: uninitialized urandom read (16 bytes read)
[    4.987008] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    5.004171] random: systemd: uninitialized urandom read (16 bytes read)
[    5.011150] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    5.028365] systemd[1]: Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[    5.048582] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Process Core Dump Socket.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Reached target Swap.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Listening on Journal Socket.
         Mounting POSIX Message Queue File System...
         Starting udev Coldplug all Devices...
         Mounting Kernel Debug File System...
         Mounting Temporary Directory (/tmp)...
         Starting Remount Root and Kernel File Systems...
[    5.346403] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
         Starting Load Kernel Modules...
         Mounting Huge Pages File System...[    5.394381] cryptodev: loading out-of-tree module taints kernel.

[    5.409196] cryptodev: driver 1.9 loaded.
         Starting Create list of required st…ce nodes for the current kernel...
[  OK  ] Reached target Slices.
         Starting Journal Service...
[  OK  ] Reached target Paths.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Started Journal Service.
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Started Create list of required sta…vice nodes for the current kernel.
         Mounting Kernel Configuration File System...
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Apply Kernel Variables.
[    5.768742] systemd-journald[170]: Received request to flush runtime journal from PID 1
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Containers.
         Mounting /var/volatile...
         Mounting /media/ram...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /var/volatile.
[  OK  ] Mounted /media/ram.
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Load/Save Random Seed...
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started udev Coldplug all Devices.
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started udev Kernel Device Manager.
         Starting Network Service...
[  OK  ] Started Network Service.
         Starting Network Name Resolution...
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on dropbear.socket.
[  OK  ] Listening on RPCbind Server Activation Socket.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Print notice about GPLv3 packages...
[  OK  ] Started strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.
[  OK  ] Started Job spooling tools.
         Starting rng-tools.service...
[  OK  ] Started irqbalance daemon.
[    6.609904] omap_rng 4e10000.trng: Random Number Generator ver. 230b34c
         Starting TI IPC Daemon...
[  OK  ] Started Periodic Command Scheduler.
         Starting RPC Bind Service...
[  OK  ] Started D-Bus System Message Bus.
         Starting Login Service...
         Starting Reboot and dump vmcore via kexec...
[  OK  ] Started Daily rotation of log files.
[  OK  ] Reached target Timers.
[  OK  ] Started Network Name Resolution.
[    6.794272] [drm] Initialized pvr 1.17.4948957 20110701 for 7000000.gpu on minor 0
[  OK  ] Found device /dev/ttyS2.
[  OK  ] Started TI IPC Daemon.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Reached target Network.
         Starting Lightning Fast Webserver With Light System Requirements...
         Starting Simple Network Management Protocol (SNMP) Daemon....
[    6.952902] k3_r5_rproc interconnect@100000:interconnect@28380000:r5fss@41000000: creating child devices for R5F cores
         Starting Permit User Sessions...
[    6.971341] platform 41000000.r5f: assigned reserved memory node r5f-dma-memory@9c000000
[    6.980652] remoteproc remoteproc0: 41000000.r5f is available
[    7.580192] remoteproc remoteproc0: powering up 41000000.r5f
[    7.585906] remoteproc remoteproc0: Booting fw image am65x-mcu-r5f0_0-fw, size 4050720
[    7.595031] platform 41000000.r5f: booting R5F core using boot addr = 0x0
[    7.613897] remoteproc remoteproc0: registered virtio0 (type 7)
[    7.619934] remoteproc remoteproc0: remote processor 41000000.r5f is now up
[    7.623504] random: crng init done
[    7.632599] random: 7 urandom warning(s) missed due to ratelimiting
[    7.707067] TI DP83867 k3-cpsw-mdio:00: attached PHY driver [TI DP83867] (mii_bus:phy_addr=k3-cpsw-mdio:00, irq=POLL)
[    7.719295] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    7.748242] davinci_mdio b232400.mdio: davinci mdio revision 1.7, bus freq 1000000
[    7.761769] libphy: b232400.mdio: probed
[    7.809225] davinci_mdio b232400.mdio: phy[0]: device b232400.mdio:00, driver TI DP83867
[    7.817646] davinci_mdio b232400.mdio: phy[3]: device b232400.mdio:03, driver TI DP83867
[    7.878149] remoteproc remoteproc1: b034000.pru is available
[    7.891269] pru-rproc b034000.pru: PRU rproc node pru@b034000 probed successfully
[    7.907764] remoteproc remoteproc2: b004000.rtu is available
[    7.915335] pru-rproc b004000.rtu: PRU rproc node rtu@b004000 probed successfully
[    7.941797] remoteproc remoteproc3: b038000.pru is available
[    7.972549] pru-rproc b038000.pru: PRU rproc node pru@b038000 probed successfully
[    7.991886] remoteproc remoteproc4: b006000.rtu is available
[  OK  ] Started rng-tools.service.
[  OK  ] Started RPC Bind Service.
[  OK  ] Started Reboot and dump vmcore via kexec.
[  OK  ] Started Lightning Fast Webserver With Light System Requirements.
[  OK  ] Started Permit User Sessions.
[    8.139623] pru-rproc b006000.rtu: PRU rproc node rtu@b006000 probed successfully
[    8.179518] remoteproc remoteproc5: b134000.pru is available
[    8.219686] pru-rproc b134000.pru: PRU rproc node pru@b134000 probed successfully
[    8.242795] remoteproc remoteproc6: b104000.rtu is available
[    8.261451] pru-rproc b104000.rtu: PRU rproc node rtu@b104000 probed successfully
[    8.276027] NET: Registered protocol family 15
[    8.293426] remoteproc remoteproc7: b138000.pru is available
[    8.335958] pru-rproc b138000.pru: PRU rproc node pru@b138000 probed successfully
[    8.366066] remoteproc remoteproc8: b106000.rtu is available
[    8.416526] pru-rproc b106000.rtu: PRU rproc node rtu@b106000 probed successfully
[    8.450562] remoteproc remoteproc9: b234000.pru is available
[    8.477189] pru-rproc b234000.pru: PRU rproc node pru@b234000 probed successfully
[    8.489170] remoteproc remoteproc10: b204000.rtu is available
[    8.496242] pru-rproc b204000.rtu: PRU rproc node rtu@b204000 probed successfully
[    8.522579] remoteproc remoteproc11: b238000.pru is available
[    8.553223] pru-rproc b238000.pru: PRU rproc node pru@b238000 probed successfully
[    8.565202] remoteproc remoteproc12: b206000.rtu is available
[    8.574233] pru-rproc b206000.rtu: PRU rproc node rtu@b206000 probed successfully
[    8.607440] Initializing XFRM netlink socket
[    8.719075] icssg-prueth pruss2_eth: TI PRU ethernet initialized: dual EMAC mode, dual_icssg 0
[    8.737479] am65-cpsw-nuss 46000000.ethernet eth0: Link is Down
[    8.895419] dwc3 4030000.usb: Failed to get clk 'ref': -2
[    8.917957] OF: graph: no port node found in /interconnect@100000/phy@4110000
[    8.927245] virtio_rpmsg_bus virtio0: rpmsg host is online
[    8.932946] virtio_rpmsg_bus virtio0: creating channel rpmsg-proto addr 0x3d
[    9.127451] NET: Registered protocol family 45
[    9.165442] icssg-prueth pruss2_eth eth1: flow id base = 150
[    9.175781] icssg-prueth pruss2_eth eth1: mgm flow id base = 154
[    9.185257] remoteproc remoteproc9: powering up b234000.pru
[    9.224209] remoteproc remoteproc9: Booting fw image ti-pruss/am65x-pru0-prueth-fw.elf, size 14868
[    9.233291] remoteproc remoteproc9: remote processor b234000.pru is now up
[    9.240241] remoteproc remoteproc10: powering up b204000.rtu
[    9.243694] usbcore: registered new interface driver usbfs
[    9.252606] usbcore: registered new interface driver hub
[    9.258225] usbcore: registered new device driver usb
[    9.265869] remoteproc remoteproc10: Booting fw image ti-pruss/am65x-rtu0-prueth-fw.elf, size 15488
[    9.275073] remoteproc remoteproc10: remote processor b204000.rtu is now up
[    9.283304] net eth1: started
[    9.286544] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[    9.318562] icssg-prueth pruss2_eth eth2: flow id base = 157
[    9.327578] icssg-prueth pruss2_eth eth2: mgm flow id base = 161
[    9.336649] remoteproc remoteproc11: powering up b238000.pru
[  OK  ] Started Login Service.
[    9.349473] remoteproc remoteproc11: Booting fw image ti-pruss/am65x-pru1-prueth-fw.elf, size 14868
[    9.361756] remoteproc remoteproc11: remote processor b238000.pru is now up
[    9.368965] remoteproc remoteproc12: powering up b206000.rtu
[  OK  ] Started Serial Getty on ttyS2.
[    9.378122] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    9.380883] remoteproc remoteproc12: Booting fw image ti-pruss/am65x-rtu1-prueth-fw.elf, size 15488
[    9.386335] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 1
[    9.396069] remoteproc remoteproc12: remote processor b206000.rtu is now up
[    9.410895] xhci-hcd xhci-hcd.2.auto: hcc params 0x0298fe6d hci version 0x110 quirks 0x0000000000010010
[    9.411646] net eth2: started
[    9.420409] xhci-hcd xhci-hcd.2.auto: irq 302, io mem 0x04030000
[    9.423808] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
[    9.429747] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    9.443577] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.443593] usb usb1: Product: xHCI Host Controller
[    9.455713] usb usb1: Manufacturer: Linux 4.19.38-g4dae378bbe xhci-hcd
[    9.462264] usb usb1: SerialNumber: xhci-hcd.2.auto
[  OK  [    9.467949] hub 1-0:1.0: USB hub found
] Started Getty on tty1.
[    9.473001] hub 1-0:1.0: 1 port detected
[  OK  ] Reached target Login Prompts.
[    9.479561] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller
[    9.489146] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2
[    9.489172] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.0  SuperSpeed
[    9.489283] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    9.489423] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    9.489430] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.489436] usb usb2: Product: xHCI Host Controller
         [    9.489441] usb usb2: Manufacturer: Linux 4.19.38-g4dae378bbe xhci-hcd
[    9.489447] usb usb2: SerialNumber: xhci-hcd.2.auto
[    9.491909] hub 2-0:1.0: USB hub found
Starting Synchronize System and HW clocks...[    9.550365] hub 2-0:1.0: 1 port detected

[  OK  ] Started NFS status monitor for NFSv2/3 locking..
         Starting rc.pvr.service...
[FAILED] Failed to start Synchronize System and HW clocks.
See 'systemctl status sync-clocks.service' for details.
[    9.794676] PVR_K: UM DDK-(4948957) and KM DDK-(4948957) match. [ OK ]
[  OK  ] Started rc.pvr.service.
         Starting weston.service...
[  OK  ] Started weston.service.
         Starting Matrix GUI...
         Starting telnetd.service...
[  OK  ] Started Matrix GUI.
[  OK  ] Started telnetd.service.
         Starting thttpd.service...
[  OK  ] Created slice system-systemd\x2dfsck.slice.
[  OK  ] Started thttpd.service.
         Starting thermal-zone-init.service...
[  OK  ] Started thermal-zone-init.service.
[  OK  ] Started Simple Network Management Protocol (SNMP) Daemon..
[  OK  ] Found device /dev/mmcblk1p1.
         Starting File System Check on /dev/mmcblk1p1...
[  OK  ] Started File System Check on /dev/mmcblk1p1.
         Mounting /run/media/mmcblk1p1...
[  OK  ] Mounted /run/media/mmcblk1p1.

 _____                    _____           _         _   
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_ 
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|  
              |___|                    |___|            

Arago Project http://arago-project.org am65xx-evm ttyS2

Arago 2019.05 am65xx-evm ttyS2

am65xx-evm login: ***************************************************************
***************************************************************
NOTICE: This file system contains the following GPLv3 packages:
	autoconf
	bash
	bc
	binutils
	cifs-utils
	cpio
	cpp-symlinks
	cpp
	dosfstools
	elfutils
	g++-symlinks
	g++
	gawk
	gcc-symlinks
	gcc
	gdb
	gdbserver
	gettext
	glmark2
	gstreamer1.0-libav
	gzip
	hidapi
	libbfd
	libdw1
	libelf1
	libgdbm-compat4
	libgdbm6
	libgettextlib
	libgettextsrc
	libgmp10
	libidn2-0
	libmpc3
	libmpfr6
	libreadline7
	libunistring2
	m4
	make
	nettle
	parted
	pdm-anomaly-detection
	which

If you do not wish to distribute GPLv3 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
***************************************************************
***************************************************************

 _____                    _____           _         _   
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_ 
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|  
              |___|                    |___|            

Arago Project http://arago-project.org am65xx-evm ttyS2

Arago 2019.05 am65xx-evm ttyS2

am65xx-evm login: root
root@am65xx-evm:~#

    When I stop the boot process in u-boot prompt, I can print the boot environments, I have below values:

    Fullscreen am65x_gpevm_uboot_envionments.txt Download 
    U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:46:46 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.01-rc2
NOTICE:  BL31: Built : 04:28:26, Jul  7 2019
I/TC: 
I/TC: OP-TEE version: 3.2.0-583-g251f7c6-dev #1 Sun Jul  7 04:40:43 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)
Trying to boot from MMC2


U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)

Model: Texas Instruments AM654 Base Board
DRAM:  4 GiB
MMC:   sdhci@4f80000: 0, sdhci@04FA0000: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   
Warning: cpsw_nuss@046000000 using MAC address from ROM
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} ${optargs} rootfstype=ubifs root=ubi0:rootfs rw ubi.mtd=ospi.rootfs
baudrate=115200
board=am65x
board_name=am65x
board_rev=E3
board_serial=0021
board_software_revision=01
boot=mmc
boot_fit=0
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 1; run envboot; run init_${boot}; 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
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; mmc 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:4c:fe
eth2addr=70:ff:76:1d:4c:ff
ethaddr=f4:84:4c:eb:b5:1c
fastboot.board_rev=E3
fastboot.cpu=AM654
fastboot.secure=GP
fdtaddr=0x82000000
fdtcontroladdr=fdecfb98
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=1
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
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=-
run_fit=bootm ${fit_loadaddr}#${fdtfile}${overlaystring}
run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
serial#=0000000000000021
soc=k3
stdin=serial,usbkbd
update_to_fit=setenv loadaddr ${fit_loadaddr}; setenv bootfile ${fit_bootfile}
vendor=ti

Environment size: 5622/131067 bytes
=>

    Please check what u-boot environments you have on your side.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Hi Pavel, 

    Thanks for sharing the logs. 

    Can you please share the following:

    1) uEnv.txt that you are using

    2) md5sum of the u-boot.img in prebuilt-images directory

    Thanks,

    Tarun

  • 0 in reply to Tarun Srivastava
    TI__Guru**** 170625 points

    Tarun,

    Tarun Srivastava said:
    1) uEnv.txt that you are using

    I am using the default pre-built uEnv.txt available at:

    ti-processor-sdk-linux-am65xx-evm-06.00.00.07/board-support/prebuilt-images/uEnv.txt

    I am attaching uEnv.txt for your reference:

    Fullscreen 2311.uEnv.txt Download 
    # This uEnv.txt file can contain additional environment settings that you
# want to set in U-Boot at boot time.  This can be simple variables such
# as the serverip or custom variables.  The format of this file is:
#    variable=value
# NOTE: This file will be evaluated after the bootcmd is run and the
#       bootcmd must be set to load this file if it exists (this is the
#       default on all newer U-Boot images.  This also means that some
#       variables such as bootdelay cannot be changed by this file since
#       it is not evaluated until the bootcmd is run.

# The environment is saved to eMMC, but we wish that a newly created SD card
# will boot without any manual configuration. To do this we will reset the
# environment upon the first boot, and then create a file in the boot partition
# of the SD card to mark when the first-time setup has been done.

psdk_setup_file=.psdk_setup
check_psdk_setup=load mmc 1:1 ${loadaddr} ${psdk_setup_file}

# Unfortunately, the following will be erased before it can be invoked
# (See below in "uenvcmd")
#mark_psdk_setup=mw .b ${loadaddr} 0 1; fatwrite mmc 1:1 ${loadaddr} ${psdk_setup_file} 1

# Reset to the default environment
do_psdk_setup=env default -f -a; saveenv

# If not previously configured, then configure the environment and indicate this by writing a file
uenvcmd=if run check_psdk_setup; then echo "Already setup."; else run do_psdk_setup; mw.b ${loadaddr} 0 1; fatwrite mmc 1:1 ${loadaddr} .psdk_setup 1; reset; fi

    Tarun Srivastava said:
    2) md5sum of the u-boot.img in prebuilt-images directory

    I am providing the md5 sum from my prebuilt-images directory

    pbotev@lin-0306:~/workdir/AM65x/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/board-support/prebuilt-images$ md5sum u-boot-am65xx-evm.img
    aa54731301d9fff1ed37ab718d2f7f27  u-boot-am65xx-evm.img


    pbotev@lin-0306:~/workdir/AM65x/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/board-support/prebuilt-images$ md5sum uEnv.txt
    bb0428a3ff35399bfa99ad9a82e1b3bf  uEnv.txt


    Also from my SD card boot partition:

    pbotev@lin-0306:~$ md5sum /media/pbotev/boot3/u-boot.img
    aa54731301d9fff1ed37ab718d2f7f27  /media/pbotev/boot3/u-boot.img


    pbotev@lin-0306:~$ md5sum /media/pbotev/boot3/uEnv.txt
    bb0428a3ff35399bfa99ad9a82e1b3bf  /media/pbotev/boot3/uEnv.txt

     

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Hi Pavel, 

    Thanks for sharing the md5sum if the requested files.

    I have verified it with the files that I'm using and both of them are the same as yours.

    Let's try to find out whether I'm using the correct method to program sdcard or not. 

    I'm following the below steps for a fresh SD card. Let me know if you have performed anything extra apart from the below steps:

    1) Insert the SD Card to the Host PC(Linux, in my case)

    2) Executing the script as follows:

    $ sudo ./bin/create-sdcard.sh

    3) Take out the sdcard after the successful execution of the above script.

    4) Insert it to the AM65x-EVM's J17 connector

    5) Verify the boot switch configuration: SW2.3 - ON, SW3.2 - ON and SW3.3 - ON (Rest in OFF)

    6) Provide 12V to J2

    7) Power on the board using SW1

    Is there anything else you're performing to create the sd card with prebuilt images? Any prior environment setup or any script execution?

    Thanks,

    Tarun

  • 0 in reply to Tarun Srivastava
    TI__Guru**** 170625 points

    Tarun,

    Tarun Srivastava said:
    I'm following the below steps for a fresh SD card.

    Yes, these are my steps.

    Tarun Srivastava said:
    Is there anything else you're performing to create the sd card with prebuilt images? Any prior environment setup or any script execution?

    No

    I would suggest you to:

     - try with another SD card

    - try to setup your uboot environments manually

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Hi Pavel, 

    I'm able to boot the board if I'm changing the bootcmd environment variable to "if test ${boot_fit} -eq 1; then run update_to_fit; fi; run findfdt; run envboot; run init_${boot}; run get_kern_${boot}; run get_fdt_${boot}; run get_overlay_${boot}; run run_kern"


    But, the by-default boot environment variable definitions which are embedded in boot.img should have necessary environment.

    I request you to perform following on your platform:

    - Boot the board

    - Stop the boot in u-boot CLI

    - Pass the command "env default -f -a"

    - Pass the command "saveenv"

    - Turn off the platform

    - Turn on the platform and see if you face the same error that I'm facing.

    If this also doesn't clear things then we have to think in some other direction.

    Thanks,

    Tarun

     

  • 0 in reply to Tarun Srivastava
    TI__Guru**** 170625 points

    Taurun,

    Tarun Srivastava said:

    I request you to perform following on your platform:

    - Boot the board

    - Stop the boot in u-boot CLI

    - Pass the command "env default -f -a"

    - Pass the command "saveenv"

    - Turn off the platform

    - Turn on the platform and see if you face the same error that I'm facing.

    I tried this on my side:

    Hit any key to stop autoboot:  0
    => env default -f -a
    ## Resetting to default environment
    => saveenv
    Saving Environment to MMC... Writing to redundant MMC(0)... OK
    =>

    But I am not able to reproduce your error. I am still able to boot Linux from SD card successful.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Prodigy 240 points

    Pavel, 

    Thanks for confirming it again.

    Now, can we try to figure out what is going wrong in my case?

    We both are using the same pre-built images, the same script to program these images to sd card but we observe the different responses.

    As far as I know, env default -f -a  resets the u-boot environment and uses the one which is embedded in u-boot.img.

    In your platform same environments are able to load kernel but not in my platform.

    Is there is any possibility that the eMMC content is responsible for this behavior?

    I can compare all the environment variables with yours. 

    Can you do printenv and share all the environment variables? 

    Also, if you have any other suggestion then we can try that.

    Thanks,

    Tarun