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)
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,
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
