# How to get information about additional artifact in to the mender blob

**URL:** <https://hub.mender.io/t/how-to-get-information-about-additional-artifact-in-to-the-mender-blob/7978>\
**Category:** General Discussions\
**Tags:** tegra, uefi\
**Created:** [September 1, 2025, 1:57pm UTC](https://hub.mender.io/t/how-to-get-information-about-additional-artifact-in-to-the-mender-blob/7978 "2025-09-01T13:57:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pbergin](https://avatars.discourse-cdn.com/v4/letter/p/c0e974/32.png) [@pbergin](https://hub.mender.io/u/pbergin)\
**Post date:** [September 1, 2025, 1:57pm UTC](https://hub.mender.io/t/how-to-get-information-about-additional-artifact-in-to-the-mender-blob/7978/1 "2025-09-01T13:57:08Z")

</div>

I’m working in Yocto with a Tegra target using meta-tegra, meta-mender and meta-mender-community layers from scarthgap branch. When building the .mender file it will include my rootfs image. In that image there is a UEFI capsule binary included. I would like to have that specified in the metadata of the update image and request some help.

My idea is that during build in Yocto I want to get the version of the bootloader capsule that is placed in the image. For example 36.4.3. Then at install time I want from my scripts to get the version of the bootloader capsule.

Can I have some pointers and ideas how to afford that in Yocto with meta-mender?

Thanks,  
/Peter