Error loading in yocto image to MiMX8QX6AVLFZAC with custom board

[kishorem]

We have built scfw-tcm.bin for our DDR configuration and used that to built an yocto image for Linux version 5.15.71

Commands we used to built yocto image:

MACHINE=imx8qxpc0mek DISTRO=fsl-imx-wayland source ./imx-setup-release.sh -b bld-wayland

bitbake core-image-minimal

Output:

we got the following error and we have also attached the complete log file for the reference.

[ 1.937125] Hardware name: Freescale i.MX8QXP MEK (DT)
[ 1.937129] Call trace:
[ 1.937131] dump_backtrace+0x0/0x19c
[ 1.937145] show_stack+0x18/0x70
[ 1.937155] dump_stack_lvl+0x68/0x84
[ 1.937166] dump_stack+0x18/0x34
[ 1.937175] panic+0x15c/0x31c
[ 1.937184] nmi_panic+0x8c/0x90
[ 1.937196] arm64_serror_panic+0x6c/0x7c
[ 1.937205] do_serror+0x58/0x5c
[ 1.937213] el1h_64_error_handler+0x30/0x50
[ 1.937223] el1h_64_error+0x78/0x7c
[ 1.937232] gckHARDWARE_Flush+0x304/0x4d0
[ 1.937240] gckFUNCTION_Init+0x2c/0x60
[ 1.937248] gckHARDWARE_PostConstruct+0xa0/0x170
[ 1.937257] gckKERNEL_Construct+0x394/0x720
[ 1.937267] gckDEVICE_AddCore+0x4c/0x180
[ 1.937275] gckGALDEVICE_Construct+0x32c/0x8c0
[ 1.937285] gpu_probe+0x550/0x780
[ 1.937292] platform_probe+0x68/0xe0
[ 1.937303] really_probe.part.0+0x9c/0x30c
[ 1.937312] __driver_probe_device+0x98/0x144
[ 1.937320] driver_probe_device+0xc8/0x15c
[ 1.937330] __driver_attach+0x80/0x18c
[ 1.937339] bus_for_each_dev+0x70/0xd0
[ 1.937348] driver_attach+0x24/0x30
[ 1.937359] bus_add_driver+0x108/0x1fc
[ 1.937368] driver_register+0x78/0x130
[ 1.937378] __platform_driver_register+0x28/0x34
[ 1.937389] gpu_init+0x54/0x90
[ 1.937398] do_one_initcall+0x50/0x1b0
[ 1.937405] kernel_init_freeable+0x20c/0x290
[ 1.937421] kernel_init+0x24/0x12c
[ 1.937429] ret_from_fork+0x10/0x20
[ 1.937442] SMP: stopping secondary CPUs
[ 1.940775] Kernel Offset: disabled
[ 1.940777] CPU features: 0x00000001,20000846
[ 1.940783] Memory Limit: none

[Dhruvit]

Hi @kishorem,

I hope you are doing well

The kernel panic can be caused due to several reasons. 

One can check If the emmc size is not too small.

Try to init or interrupt any component which is clock gated or powered off can give kernel panic. etc...

Please check the emmc configuration and clock settings and whether the EMMC connections are proper or not.

Thanks & Regards,

Dhruvit Vasavada