Kernel panic - not syncing: No working init found

Verdin iMX8MP Q 4GB IT V1.1A / Dahlia carrier board Rev. 1.1 / Linux Tdx Version 6.0/kirkstone

We are building a YOCTO image with customized device tree and additional recipes. The build generates a packed file called ‘Verdin-iMX8MP_ctc-tdx-image-Tezi_6.4.0-devel-20231124090122+build.0.tar’ that I am trying to flash using a USB stick.
I unpack the file and copy all 10 extracted files to a subdir on the USB stick. I put the Verdin in recovery mode and load EasyInstaller 5.7.3 into RAM using the Toradex supplied EZI.
Our Linux image shows up in EasyInstaller and can be installed without error message. Finally I select reboot.
In the bootloader console I can see the bootloader is running however it cannot start our Linux image.

The error message from bootloader reads: ---[ end **Kernel panic - not syncing: No working init found.** Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. ]---.

Attached files:
image.json (1.9 KB) from YOCTO build
Bootloader_Console.txt (25.4 KB)
Bootloader_Environment.txt (4.5 KB)
Bootloader_mmcInfo.txt (866 Bytes)

Hi @zorro ,

Given that this error occurred when trying to boot your custom image, the first thing I would suspect is that your customization might be cause of it.

What recipes did you add to the image? Specifically anything that changes the kernel or how it initializes, like a bbappend file?

Can you share your recipes/layers so that we can try to reproduce the error? You can attach the files in a new reply or you can also send them via email at if you don’t want to share it here.

Best regards,
Lucas Akira

it’s not simple to reproduce. We use Azure DevOps and Docker to run the YOCTO build.
We also do modify the device tree.
We are investigating, I’ll share news as soon as possible. In the end, also we need 9 user partitions to be created.

Hi @zorro ,

OK, no problem. Let us know if you have any updates to share.

Best regards,
Lucas Akira