Part Number: AM6422
Tool/software:
Hi,
We have a custom board using AM6422.
We can boot Linux using Image.
Now I tried to boot the TI prebuilt image fitImage from SDK.
Here the output:
=> setenv fdtfile ti/k3-am642-sk.dtb
=> run get_fit_config
=> bootm ${loadaddr}#${name_fit_config}
## Loading kernel from FIT Image at 82000000 ...
Using 'conf-ti_k3-am642-sk.dtb' configuration
Verifying Hash Integrity ... OK
Trying 'kernel-1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x820000e0
Data Size: 6603945 Bytes = 6.3 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x81000000
Entry Point: 0x81000000
Hash algo: sha512
Hash value: 4ff47e3d93c4fa16265e50ce234834e5cc09dda56c3468852369cc9d5974f0ec3f8dfae3a878c4386ac211ff83281199bcf9c1f5ba2c505136a708cddfdfb66f
Verifying Hash Integrity ... sha512+ OK
## Loading fdt from FIT Image at 82000000 ...
Using 'conf-ti_k3-am642-sk.dtb' configuration
Verifying Hash Integrity ... OK
Trying 'fdt-ti_k3-am642-sk.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x8265b1f8
Data Size: 61494 Bytes = 60.1 KiB
Architecture: AArch64
Load Address: 0x83000000
Hash algo: sha512
Hash value: 213879ecb927feac06a6786bbd7b09ced931f2094b2df301a099d9d7f232b5dd23d7e6aabf8e9f30def518c15de6542582b4beb28a75fc437d6fa5c703a996a1
Verifying Hash Integrity ... sha512+ OK
Loading fdt from 0x8265b1f8 to 0x83000000
Booting using the fdt blob at 0x83000000
Working FDT set to 83000000
Uncompressing Kernel Image to 81000000
ERROR: reserving fdt memory region failed (addr=9e800000 size=1800000 flags=4)
Loading Device Tree to 0000000087fed000, end 0000000087fff035 ... OK
Working FDT set to 87fed000
Starting kernel ...
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Reserved shared memory is enabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are disabled
I expected here the messages from Kernel.
As we can see Kernel prints no messages.
Any Idea why ?
Best Regards
Walter