# Mender bootstrap and unknown artifact
**URL:** https://hub.mender.io/t/mender-bootstrap-and-unknown-artifact/6822
**Category:** General Discussions
**Tags:** yocto, langdale
**Created:** [May 15, 2024, 6:48pm UTC](https://hub.mender.io/t/mender-bootstrap-and-unknown-artifact/6822 "2024-05-15T18:48:44Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@krzysztofch](https://hub.mender.io/u/krzysztofch)
#### Post date: [May 15, 2024, 6:48pm UTC](https://hub.mender.io/t/mender-bootstrap-and-unknown-artifact/6822/1 "2024-05-15T18:48:44Z")
Hi,
I have encountered problem with mender bootstrap artifact after porting mender to Yocto Langdale from master-next branch on my custom Zynq board. I found similar topics on this forum but none was helpful in this case.
I successfully created image and have running mender services, but in the webapp panel, after accepting my board the initial Yocto image has always artifact\_name unknown. I am able to update the whole rootfs partition with a new image or single file and then the version is displayed correctly.
Moreover I noticed that the bootstrap.mender file is present in /data/mender and is consumed the first time I boot my board. But after that the board has still unknown version. I checked the device type during bootstrap generation and it looks good.
Do you have any idea how may I debug this issue deeper, to check why my initial artifact name is not set correctly? My mender version is 3.5.1.
Best regards,
Krzysztof
---
### Author:  [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)
#### Post date: [May 16, 2024, 11:55am UTC](https://hub.mender.io/t/mender-bootstrap-and-unknown-artifact/6822/2 "2024-05-16T11:55:57Z")
Hi @krzysztofch,
Just as a starting point, does your `langdale` incarnation of `meta-mender` reflect the latest state of `master` respectively `kirkstone`, or is it something possibly outdated?
Plus, can you eventually share your `local.conf` respectively build specifics?
Greets,
Josef
---
### Author:  [@krzysztofch](https://hub.mender.io/u/krzysztofch)
#### Post date: [May 18, 2024, 6:10pm UTC](https://hub.mender.io/t/mender-bootstrap-and-unknown-artifact/6822/3 "2024-05-18T18:10:46Z")
Hi @TheYoctoJester,
I use the latest master-next commit 5fb0af6b89eba96fb5bedaa2d26168233d050d67, however indeed it was committed 9 months ago. The master branch does not support the langdale release, or at least it is not listed in the layer.conf. Could you advise which branch should I use for Yocto langdale version?
This is my mender-related conf part in petalinuxbsp.conf which is included in local.conf file
```auto
#User Configuration
IMAGE_INSTALL:append = "linux-firmware-rtl8192cu"
#OE_TERMINAL = "tmux"
IMAGE_BOOT_FILES:zynq = "BOOT.BIN boot.scr uImage uboot.env"
EXTRA_IMAGEDEPENDS:append:zynq = " xilinx-bootbin "
BIF_PARTITION_IMAGE[bitstream] ?= "${DEPLOY_DIR_IMAGE}/download-${MACHINE}.bit"
BIF_PARTITION_DEPENDS[bitstream] ?= "virtual/bitstream"
ARTIFACTIMG_FSTYPE = "ext4"
MENDER_SERVER_URL = "https://eu.hosted.mender.io"
MENDER_TENANT_TOKEN = "ncYviHyFPvN-ob9d8MssaIBkYx5GrbriOE1kmz988GU"
MENDER_DEVICE_TYPES_COMPATIBLE = "zynq-generic-7z007s"
MENDER_ARTIFACT_NAME = "release-1"
INHERIT += " mender-full mender-artifactimg "
MENDER_STORAGE_TOTAL_SIZE_MB = "1024"
MENDER_FEATURES_ENABLE:append = " mender-uboot mender-systemd mender-image mender-image-sd "
MENDER_FEATURES_DISABLE:append = " mender-grub mender-image-uefi"
MENDER_CONNECT_USER = "root"
MENDER_INVENTORY_POLL_INTERVAL_SECONDS = "120"
MENDER_RETRY_POLL_INTERVAL_SECONDS = "30"
MENDER_UPDATE_POLL_INTERVAL_SECONDS = "60"
MENDER_UBOOT_ENV_LINUX_PATH = "/uboot/uboot.env"
MENDER_UBOOT_ENV_REDUND_LINUX_PATH = "/uboot/uboot-redund.env"
BOOTBIN_BASE_NAME = "BOOT"
```
Best regards,
Krzysztof
---
### Author:  [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)
#### Post date: [May 19, 2024, 8:46pm UTC](https://hub.mender.io/t/mender-bootstrap-and-unknown-artifact/6822/4 "2024-05-19T20:46:00Z")
Hi @krzysztofch,
Ah I see. Unfortunately there is no branch I can really recommend for `langdale`, as we do not officially support it - and it is end of life anyways. The Petalinux release cycle has always been problematic, and the only real advice I can give is to move towards `meta-xilinx` for a full production quality setup. Those should be available for `scarthgap` soon, and we also already have preliminary support which should be finalised soon.
Greets,
Josef