Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer? 
Hello! Thank you for providing detailed information about your setup and the steps you’ve taken. Let’s review the issue and see how you can ensure your kernel + initramfs binary is deployed within your Toradex Easy Installer (Tezi) image.
Problem Summary
Your Image.gz-initramfs-verdin-imx8mp.bin is being built correctly and shows up as ~30MB in deploy/images, but the kernel file in the Tezi install folder is just 8.1MB (the size of the plain Image.gz), implying the bundled version is not being picked up for the installer output.
Points to Check
1. IMAGE_BOOT_FILES Syntax
Your IMAGE_BOOT_FILES entry looks correct, specifically the part:
Image.gz-initramfs-verdin-imx8mp.bin;Image.gz
This syntax should copy Image.gz-initramfs-verdin-imx8mp.bin as Image.gz into your deploy directory.
Suggestion:
Make sure in deploy/images/verdin-imx8mp you only have:
Image.gzImage.gz-initramfs-verdin-imx8mp.bin
and not both a plain Image.gz and the initramfs bundle with similar timestamps. Double-check that the filename mapping is not getting overwritten in a later build step.
2. Clean Build Output
Sometimes old artifacts can result in the wrong files being installed. Try:
bitbake -c cleanall linux-toradex
bitbake <your-image>
Then inspect deploy/images/verdin-imx8mp for the correct filenames and sizes before and after running the Tezi preparation step.
3. Tezi Output Mapping
The files included in the Tezi output depend on the bitbake recipe for your image. When you set TEZI_USE_BOOTFILES = "false", all required boot files (including kernel, DTBs, overlays, etc.) should be gathered by the image recipe into the Tezi folder.
Important:
The file that lands in the root of the Tezi install folder as Image.gz will be whatever is picked as the first mapping to that name in IMAGE_BOOT_FILES. If there is also just an Image.gz file (unbundled), and the mapping causes it to be used instead (due to build or copy order), you may end up with the wrong one.
4. Confirm File Used in Tezi Folder
Directly after bitbake completes, check the content in:
<your build>/deploy/images/verdin-imx8mp/teziimage
(if teziimage output dir exists) or in the tezi output of your custom image. Confirm that the Image.gz file there is your intended kernel+initramfs bundle (approx 30MB).
Troubleshooting steps:
- Rebuild with a clean state as described.
- Search for all
Image.gz* in your deploy and Tezi output folders:find ./deploy/images/verdin-imx8mp/ -name "Image.gz*"
- Use
ls -lh to check sizes and make sure the mapping is as you expect.
- Double-check
IMAGE_BOOT_FILES isn’t overridden elsewhere (e.g., in a machine or distro .conf).
- If you still get a mismatch, you can temporarily move/rename the plain
Image.gz after build before packaging, ensuring only the bundled file remains to be mapped as Image.gz.
Additional References
While exact instructions for initramfs bundling with Tezi images are not explicitly documented, you can find more on the Verdin and Tezi install process at:
You can also browse Toradex’s GitHub or Community for similar user experiences.
Summary
- Ensure only your bundled kernel is mapped to
Image.gz in the Tezi output.
- Remove or rename any plain
Image.gz if it accidentally overrides the intended file.
- Rebuild from clean if needed to clear any artifacts.
- Confirm output content and sizes before flashing.
Let me know if these steps clarify the origin of the smaller kernel in your Tezi image or if you need further help!
Best regards,
Toradex AI Assistant.
