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.

TMDX654GPEVM: I Can't Boot up Yocto Custom Linux

Part Number: TMDX654GPEVM

hello

i have some problem

i built Yocto Custom Linux

so i have this file

bl31.bin
bl31.elf
core-image-sato-am65xx-evm
core-image-sato-am65xx-evm-20191102144423.rootfs.manifest
core-image-sato-am65xx-evm-20191102144423.rootfs.tar.xz
core-image-sato-am65xx-evm-20191102144423.rootfs.wic.xz
core-image-sato-am65xx-evm-20191102144423.testdata.json
core-image-sato-am65xx-evm.manifest
core-image-sato-am65xx-evm.tar.xz
core-image-sato-am65xx-evm.testdata.json
core-image-sato-am65xx-evm.wic
core-image-sato-am65xx-evm.wic.xz
Image
Image--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.bin
Image-am65xx-evm.bin
k3-am654-base-board--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtb
k3-am654-base-board-am65xx-evm.dtb
k3-am654-base-board.dtb
k3-am654-base-board-jailhouse--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-base-board-jailhouse-am65xx-evm.dtbo
k3-am654-base-board-jailhouse.dtbo
k3-am654-evm-csi2-ov490--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-csi2-ov490-am65xx-evm.dtbo
k3-am654-evm-csi2-ov490.dtbo
k3-am654-evm-csi2-ov5640--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-csi2-ov5640-am65xx-evm.dtbo
k3-am654-evm-csi2-ov5640.dtbo
k3-am654-evm-hdmi--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-hdmi-am65xx-evm.dtbo
k3-am654-evm-hdmi.dtbo
k3-am654-evm-oldi-lcd1evm--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-oldi-lcd1evm-am65xx-evm.dtbo
k3-am654-evm-oldi-lcd1evm.dtbo
k3-am654-evm-tc358876--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-tc358876-am65xx-evm.dtbo
k3-am654-evm-tc358876.dtbo
k3-am654-gp--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-gp-am65xx-evm.dtbo
k3-am654-gp.dtbo
k3-am654-idk--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-idk-am65xx-evm.dtbo
k3-am654-idk.dtbo
k3-am654-pcie-usb2--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-pcie-usb2-am65xx-evm.dtbo
k3-am654-pcie-usb2.dtbo
k3-am654-pcie-usb3--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-pcie-usb3-am65xx-evm.dtbo
k3-am654-pcie-usb3.dtbo
modules--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.tgz
modules-am65xx-evm.tgz
testimg.tar
tispl.bin
tispl.bin-am65xx-evm
tispl.bin-am65xx-evm-2019.01+gitAUTOINC+964fa245a2-r28
u-boot-am65xx-evm-2019.01+gitAUTOINC+964fa245a2-r28.img
u-boot-am65xx-evm.img
u-boot.img
vmlinux.gz
vmlinux.gz--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.bin
vmlinux.gz-am65xx-evm.bin
chung@chung:~/yocto/poky/ti-am65/tmp/deploy/images/am65xx-evm$ ls
bl31.bin
bl31.elf
core-image-sato-am65xx-evm
core-image-sato-am65xx-evm-20191102144423.rootfs.manifest
core-image-sato-am65xx-evm-20191102144423.rootfs.tar.xz
core-image-sato-am65xx-evm-20191102144423.rootfs.wic.xz
core-image-sato-am65xx-evm-20191102144423.testdata.json
core-image-sato-am65xx-evm.manifest
core-image-sato-am65xx-evm.tar.xz
core-image-sato-am65xx-evm.testdata.json
core-image-sato-am65xx-evm.wic
core-image-sato-am65xx-evm.wic.xz
Image
Image--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.bin
Image-am65xx-evm.bin
k3-am654-base-board--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtb
k3-am654-base-board-am65xx-evm.dtb
k3-am654-base-board.dtb
k3-am654-base-board-jailhouse--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-base-board-jailhouse-am65xx-evm.dtbo
k3-am654-base-board-jailhouse.dtbo
k3-am654-evm-csi2-ov490--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-csi2-ov490-am65xx-evm.dtbo
k3-am654-evm-csi2-ov490.dtbo
k3-am654-evm-csi2-ov5640--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-csi2-ov5640-am65xx-evm.dtbo
k3-am654-evm-csi2-ov5640.dtbo
k3-am654-evm-hdmi--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-hdmi-am65xx-evm.dtbo
k3-am654-evm-hdmi.dtbo
k3-am654-evm-oldi-lcd1evm--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-oldi-lcd1evm-am65xx-evm.dtbo
k3-am654-evm-oldi-lcd1evm.dtbo
k3-am654-evm-tc358876--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-evm-tc358876-am65xx-evm.dtbo
k3-am654-evm-tc358876.dtbo
k3-am654-gp--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-gp-am65xx-evm.dtbo
k3-am654-gp.dtbo
k3-am654-idk--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-idk-am65xx-evm.dtbo
k3-am654-idk.dtbo
k3-am654-pcie-usb2--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-pcie-usb2-am65xx-evm.dtbo
k3-am654-pcie-usb2.dtbo
k3-am654-pcie-usb3--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.dtbo
k3-am654-pcie-usb3-am65xx-evm.dtbo
k3-am654-pcie-usb3.dtbo
modules--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.tgz
modules-am65xx-evm.tgz
testimg.tar
tispl.bin
tispl.bin-am65xx-evm
tispl.bin-am65xx-evm-2019.01+gitAUTOINC+964fa245a2-r28
u-boot-am65xx-evm-2019.01+gitAUTOINC+964fa245a2-r28.img
u-boot-am65xx-evm.img
u-boot.img
vmlinux.gz
vmlinux.gz--4.19.79+git0+69eee28965-r0a-am65xx-evm-20191102144423.bin
vmlinux.gz-am65xx-evm.bin

so i used ti-sdk/bin/create-sdcard.sh from Ti SDK

but i can't boot up

i did this routin

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

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:   8       16  976762584 sdb
2:   8       32  244198584 sdc
3:   8       48    7761920 sdd
 
Enter Device Number or n to exit: 3
 
sdd was selected

/dev/sdd is an sdx device
Current size of sdd1 71680 bytes
Current size of sdd2 7672832 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 sdd

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

Number of partitions needed [2/3] : 2

 
Now partitioning sdd 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.266519 s, 3.9 MB/s
DISK SIZE - 7948206080 bytes

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

		Partitioning Boot

################################################################################
mkfs.fat 4.1 (2017-01-24)
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
mkfs.vfat: unable to open /dev/sdd1: No such file or directory

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

		Partitioning rootfs

################################################################################
mke2fs 1.44.1 (24-Mar-2018)
The file /dev/sdd2 does not exist and no size was specified.


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

   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] : 2

 

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

  For U-boot and MLO

  If files are located in Tarball write complete path including the file name.
      e.x. $:  /home/user/MyCustomTars/boot.tar.xz

  If files are located in a directory write the directory path
      e.x. $: /ti-sdk/board-support/prebuilt-images/

  NOTE: Not all platforms will have an MLO file and this file can
        be ignored for platforms that do not support an MLO.

  Update: The proper location for the kernel image and device tree
          files have moved from the boot partition to the root filesystem.

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

Enter path for Boot Partition : /home/chung/yocto/BootImg/bootloader/

Directory exists

This directory contains:
u-boot.img

u-boot.img is copy from yocto build folder, original name is "u-boot-am65xx-evm-2019.01+gitAUTOINC+964fa245a2-r28.img" Is this correct? [y/n] : y ################################################################################ For Kernel Image and Device Trees files What would you like to do? 1) Reuse kernel image and device tree files found in the selected rootfs. 2) Provide a directory that contains the kernel image and device tree files to be used. ################################################################################ Choose option 1 or 2 : 1 Reusing kernel and dt files from the rootfs's boot directory ################################################################################ For Rootfs partition If files are located in Tarball write complete path including the file name. e.x. $: /home/user/MyCustomTars/rootfs.tar.xz If files are located in a directory write the directory path e.x. $: /ti-sdk/targetNFS/ ################################################################################ Enter path for Rootfs Partition : /home/chung/yocto/BootImg/core-image-sato-am65xx-evm-20191102144423.rootfs.tar.xz File exists ################################################################################ Copying files now... will take minutes ################################################################################ Copying boot partition Boot image not found u-boot.img copied Copying rootfs System partition Syncing... Un-mount the partitions Remove created temp directories Operation Finished

and insert my board, didn't boot up

what is my mistake? 

thanks to read and sorry about my language skill