# After meta-mender integration the target (Variscite imx6UL) cannot boot

**URL:** <https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808>\
**Category:** Yocto Project\
**Tags:** yocto, zeus\
**Created:** [June 30, 2021, 2:03am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808 "2021-06-30T02:03:20Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [June 30, 2021, 2:03am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/1 "2021-06-30T02:03:20Z")

</div>

Hi,

I manually integrated meta-mender to our existing Yocto-Zeus system. I was able to successfully built the system with meta-mender integrated. I created a bootable sd by using this command:

sudo dd if=tmp/deploy/images/hero-secc/hero-secc-firmware-release-hero-secc.sdimg of=/dev/sdb conv=fdatasync bs=1M

The sd memory is partitioned like this after running the dd command.

 ![hero-yocto-mender-sd](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/4/4c87eb594da54c6f45edb531342766db315d5b11.jpeg)

So, I plugged in the sd to the target. The pins are correctly set at 00, so I am expecting the target will boot from sd. Unfortunately, even the UBOOT SPL is not running.

Did I mess up something?

Kind regards,  
Marizonne

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [June 30, 2021, 12:57pm UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/2 "2021-06-30T12:57:18Z")

</div>

It’s hard to say. The partition table looks correct but clearly something is wrong since SPL is not loading. You’ll need to compare the UBoot configuration with and without Mender integrated; there must be some missing piece in there. My guess is that it is image sizes or offsets that need adjusting.

Drew

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 5, 2021, 1:12am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/3 "2021-07-05T01:12:51Z")

</div>

Hi Drew,

I now managed to boot the UBoot SPL and UBoot but it cannot load the Kernel:

U-Boot SPL 2018.03-hero-master+g8ff8034d66 (Jul 05 2021 - 00:39:12 +0000)

Part number: VSM-6UL-A06B  
Assembly: AS2006153200  
Date of production: 2020 Jul 02  
SOM configuration: eMMC WiFi (5G)  
Trying to boot from MMC1  
MMC Boot Device: mmc0 (SD)

U-Boot 2018.03-hero-master+g8ff8034d66 (Jul 05 2021 - 00:39:12 +0000)

CPU: Freescale i.MX6ULL rev1.1 900 MHz (running at 396 MHz)  
CPU: Commercial temperature grade (0C to 95C) at 36C  
Reset cause: POR  
Board: Variscite DART-6UL  
I2C: ready  
DRAM: 512 MiB  
MMC: FSL\_SDHC: 0, FSL\_SDHC: 1  
Loading Environment from MMC… OK  
Display: VAR-WVGA-LCD (800x480)  
Video: 800x480x24  
\*\* Unrecognized filesystem type \*\*  
Error: could not access storage.  
In: serial  
Out: serial  
Err: serial  
eMMC: 7.3 GiB  
Net: got MAC0 address from fuse: f8:dc:7a:47:0d:48  
FEC0 [PRIME], usb\_ether  
Error: usb\_ether address not set.

Normal Boot  
Hit any key to stop autoboot: 0  
\*\* File not found /boot/ \*\*  
19604448 bytes read in 17215 ms (1.1 MiB/s)  
Unknown command ‘booti’ - try ‘help’  
=\>

This is my local.conf:  
MENDER\_STORAGE\_TOTAL\_SIZE\_MB = “7516”  
MENDER\_BOOT\_PART\_SIZE\_MB = “16”  
MENDER\_DATA\_PART\_SIZE\_MB = “1024”  
MENDER\_BOOT\_PART = “${MENDER\_STORAGE\_DEVICE\_BASE}1”  
MENDER\_DATA\_PART = “${MENDER\_STORAGE\_DEVICE\_BASE}4”  
MENDER\_ROOTFS\_PART\_A = “${MENDER\_STORAGE\_DEVICE\_BASE}2”  
MENDER\_ROOTFS\_PART\_B = “${MENDER\_STORAGE\_DEVICE\_BASE}3”

MENDER\_IMAGE\_BOOTLOADER\_FILE = “u-boot-spl.img”  
MENDER\_IMAGE\_BOOTLOADER\_BOOTSECTOR\_OFFSET = “2”

MENDER\_DTB\_NAME\_FORCE=“hero-secc-imx6ull-var-dart-6ulcustomboard-emmc-wifi.dtb”  
IMAGE\_BOOT\_FILES\_remove = “${KERNEL\_IMAGETYPE} ${KERNEL\_DEVICETREE}”

MENDER\_FEATURES\_ENABLE\_append = " mender-uboot"  
MENDER\_FEATURES\_ENABLE\_append = " mender-image-sd "  
MENDER\_FEATURES\_DISABLE\_append = " mender-image-uefi "

MACHINE\_EXTRA\_RDEPENDS\_remove = “u-boot-fw-utils”

VARISCITE\_UBOOT\_ENV\_IN\_EMMC = “0”

MENDER\_STORAGE\_DEVICE = “/dev/mmcblk0”  
MENDER\_UBOOT\_STORAGE\_DEVICE = “0”  
UBOOT\_CONFIG = “sd”

MENDER\_BOOT\_PART\_SIZE\_MB\_mender-uboot = “0”  
KERNEL\_IMAGETYPE\_mender-uboot = “Image”

And these are the environment variables:  
=\> printenv  
altbootcmd=run mender\_altbootcmd; run bootcmd  
arch=arm  
baudrate=115200  
board=hero-secc  
board\_name=DART-6UL  
boot\_a\_script=load ${devtype} ${devnum}:${distro\_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}  
boot\_dev=sd  
boot\_efi\_binary=if fdt addr ${fdt\_addr\_r}; then bootefi bootmgr ${fdt\_addr\_r};else bootefi bootmgr ${fdtcontroladdr};fi;load ${devtype} ${devnum}:${distro\_bootpart} ${kernel\_addr\_r} efi/boot/bootarm.efi; if fdt addr ${fdt\_addr\_r}; then bootefi ${kernel\_addr\_r} ${fdt\_addr\_r};else bootefi ${kernel\_addr\_r} ${fdtcontroladdr};fi  
boot\_extlinux=sysboot ${devtype} ${devnum}:${distro\_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf  
boot\_fdt=try  
boot\_net\_usb\_start=usb start  
boot\_prefixes=/ /boot/  
boot\_script\_dhcp=boot.scr.uimg  
boot\_scripts=boot.scr.uimg boot.scr  
boot\_targets=mmc1 mmc0  
bootargs=root=/dev/mmcblk0p2 console=ttymxc0,115200 cma=64MB  
bootcmd=run mender\_setup; setenv bootargs root=${mender\_kernel\_root} ${bootargs}; if test “${fdt\_addr\_r}” != “”; then load ${mender\_uboot\_root} ${fdt\_addr\_r} /boot/${mender\_dtb\_name}; fi; load ${mender\_uboot\_root} ${kernel\_addr\_r} /boot/${mender\_kernel\_name}; ${mender\_boot\_kernel\_type} ${kernel\_addr\_r} - ${fdt\_addr\_r}; run mender\_try\_to\_recover  
bootcmd\_mmc0=setenv devnum 0; run mmc\_boot  
bootcmd\_mmc1=setenv devnum 1; run mmc\_boot  
bootcount=1  
bootdelay=1  
bootenv=uEnv.txt  
bootlimit=1  
cma\_size=cma=64MB  
console=ttymxc0  
cpu=armv7  
distro\_bootcmd=for target in ${boot\_targets}; do run bootcmd\_${target}; done  
efi\_dtb\_prefixes=/ /dtb/ /dtb/current/  
ethact=FEC0  
ethaddr=f8:dc:7a:47:0d:48  
ethprime=FEC0  
fdt\_addr\_r=0x83000000  
fdt\_high=0xffffffff  
fdtfile=hero-secc-imx6ull-var-dart-6ulcustomboard-emmc-sd-card.dtb  
fileaddr=82000000  
filesize=12b23e0  
findfdt=if test $fdtfile = undefined; then if test $board\_name = DART-6UL; then setenv som var-dart; setenv carrier 6ulcustomboard; fi; if test $board\_name = VAR-SOM-6UL; then setenv som var-som; i2c dev 0; if i2c probe 0x20; then setenv carrier symphony-board; else setenv carrier concerto-board; fi; fi; if test $boot\_dev = emmc || test $som\_storage = emmc || test $som\_storage = none; then setenv storage emmc; fi; if test $boot\_dev = nand || test $som\_storage = nand; then setenv storage nand; fi; if test $boot\_dev = sd; then setenv mmc0\_dev sd-card; else if test $wifi = yes; then setenv mmc0\_dev wifi; else setenv mmc0\_dev sd-card; fi; fi; if test -n $soc\_type && test -n $som && test -n $storage && test -n $mmc0\_dev && test -n $carrier; then setenv fdtfile hero-secc-${soc\_type}-${som}-${carrier}-${storage}-${mmc0\_dev}.dtb; fi; setenv som; setenv carrier; setenv storage; setenv mmc0\_dev; if test $fdtfile = undefined; then echo WARNING: Could not determine dtb to use; fi; fi;  
initrd\_high=0xffffffff  
ip\_dyn=yes  
kernel\_addr\_r=0x82000000  
load\_efi\_dtb=load ${devtype} ${devnum}:${distro\_bootpart} ${fdt\_addr\_r} ${prefix}${efi\_fdtfile}  
loadaddr=0x82000000  
mender\_altbootcmd=if test ${mender\_boot\_part} = 2; then setenv mender\_boot\_part 3; setenv mender\_boot\_part\_hex 3; else setenv mender\_boot\_part 2; setenv mender\_boot\_part\_hex 2; fi; setenv upgrade\_available 0; saveenv; run mender\_setup  
mender\_boot\_kernel\_type=booti  
mender\_boot\_part=2  
mender\_boot\_part\_hex=2  
mender\_boot\_part\_name=/dev/mmcblk0p2  
mender\_check\_saveenv\_canary=1  
mender\_kernel\_name=Image  
mender\_kernel\_root=/dev/mmcblk0p2  
mender\_kernel\_root\_name=/dev/mmcblk0p2  
mender\_pre\_setup\_commands= if test “${ramsize\_check}” != “”; then run ramsize\_check; fi; if test “${mmcargs}” != “”; then run mmcargs; fi; if test “${videoargs}” != “”; then run videoargs; fi; if test “${optargs}” != “”; then run optargs; fi; run findfdt; setenv mender\_dtb\_name ${fdt\_file}; setenv kernel\_addr\_r ${loadaddr};  
mender\_saveenv\_canary=1  
mender\_setup=if test “${mender\_saveenv\_canary}” != “1”; then setenv mender\_saveenv\_canary 1; saveenv; fi; if test “${mender\_pre\_setup\_commands}” != “”; then run mender\_pre\_setup\_commands; fi; if test “${mender\_systemd\_machine\_id}” != “”; then setenv bootargs “systemd.machine\_id=${mender\_systemd\_machine\_id} ${bootargs}”; fi; setenv mender\_kernel\_root /dev/mmcblk0p${mender\_boot\_part}; if test ${mender\_boot\_part} = 2; then setenv mender\_boot\_part\_name /dev/mmcblk0p2; else setenv mender\_boot\_part\_name /dev/mmcblk0p3; fi; setenv mender\_kernel\_root\_name ${mender\_boot\_part\_name}; setenv mender\_uboot\_root mmc 0:${mender\_boot\_part\_hex}; setenv mender\_uboot\_root\_name ${mender\_boot\_part\_name}; setenv expand\_bootargs “setenv bootargs \”${bootargs}\""; run expand\_bootargs; setenv expand\_bootargs; if test “${mender\_post\_setup\_commands}” != “”; then run mender\_post\_setup\_commands; fi  
mender\_try\_to\_recover=if test ${upgrade\_available} = 1; then reset; fi  
mender\_uboot\_boot=mmc 0:1  
mender\_uboot\_dev=0  
mender\_uboot\_if=mmc  
mender\_uboot\_root=mmc 0:2  
mender\_uboot\_root\_name=/dev/mmcblk0p2  
mmc\_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan\_dev\_for\_boot\_part; fi  
mmcargs=setenv bootargs console=${console},${baudrate} ${cma\_size}  
netargs=setenv bootargs console=${console},${baudrate} rw ${cma\_size}ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp  
netboot=echo Booting from net …; run netargs; run optargs; if test ${ip\_dyn} = yes; then setenv get\_cmd dhcp; else setenv get\_cmd tftp; fi; ${get\_cmd} ${image}; if test ${boot\_fdt} = yes || test ${boot\_fdt} = try; then run findfdt; echo fdtfile=${fdtfile}; if ${get\_cmd} ${fdt\_addr\_r} ${fdtfile}; then bootz ${loadaddr} - ${fdt\_addr\_r}; else if test ${boot\_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;  
nfsroot=/home/herodev/hero-yocto/rootfs  
optargs=setenv bootargs ${bootargs} ${kernelargs};  
panel=VAR-WVGA-LCD  
ramsize\_check=if test $sdram\_size -lt 256; then setenv cma\_size cma=32MB; setenv fdt\_addr\_r 0x84000000; setenv loadaddr 0x84600000; else setenv cma\_size cma=64MB; fi;  
scan\_dev\_for\_boot=echo Scanning ${devtype} ${devnum}:${distro\_bootpart}…; for prefix in ${boot\_prefixes}; do run scan\_dev\_for\_extlinux; run scan\_dev\_for\_scripts; done;run scan\_dev\_for\_efi;  
scan\_dev\_for\_boot\_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro\_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro\_bootpart} bootfstype; then run scan\_dev\_for\_boot; fi; done  
scan\_dev\_for\_efi=setenv efi\_fdtfile ${fdtfile}; if test -z “${fdtfile}” -a -n “${soc}”; then setenv efi\_fdtfile ${soc}-${board}${boardver}.dtb; fi; for prefix in ${efi\_dtb\_prefixes}; do if test -e ${devtype} ${devnum}:${distro\_bootpart} ${prefix}${efi\_fdtfile}; then run load\_efi\_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro\_bootpart} efi/boot/bootarm.efi; then echo Found EFI removable media binary efi/boot/bootarm.efi; run boot\_efi\_binary; echo EFI LOAD FAILED: continuing…; fi; setenv efi\_fdtfile  
scan\_dev\_for\_extlinux=if test -e ${devtype} ${devnum}:${distro\_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot\_extlinux; echo SCRIPT FAILED: continuing…; fi  
scan\_dev\_for\_scripts=for script in ${boot\_scripts}; do if test -e ${devtype} ${devnum}:${distro\_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot\_a\_script; echo SCRIPT FAILED: continuing…; fi; done  
sdram\_size=512  
serverip=10.1.1.108  
soc=mx6  
soc\_type=imx6ull  
som\_rev=5G  
som\_storage=emmc  
splashdisable=setenv splashfile; setenv splashimage  
splashenable=setenv splashfile /boot/splash.bmp; setenv splashimage 0x83100000  
splashfile=/boot/splash.bmp  
splashimage=0x83100000  
splashsource=sd  
splashsourceauto=yes  
upgrade\_available=0  
usb\_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan\_dev\_for\_boot\_part; fi  
usbnet\_devaddr=f8:dc:7a:00:00:02  
usbnet\_hostaddr=f8:dc:7a:00:00:01  
vendor=lumen  
wifi=yes

Environment size: 7922/131067 bytes  
=\>

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 5, 2021, 1:50am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/4 "2021-07-05T01:50:36Z")

</div>

=\> echo ${fdt\_addr\_r}  
0x83000000

=\> if test “${fdt\_addr\_r}” != “”; then load ${mender\_uboot\_root} ${fdt\_addr\_r} /boot/${mender\_dtb\_name}; fi;  
\*\* File not found /boot/ \*\*

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [July 5, 2021, 3:00am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/5 "2021-07-05T03:00:47Z")

</div>

It looks like some of the environment variables are misdefined. What does the following show from the U-Boot prompt?

> printenv mender\_uboot\_root  
> printenv fdt\_addr\_r  
> printenv mender\_dtb\_name

Drew

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 5, 2021, 3:17am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/6 "2021-07-05T03:17:59Z")

</div>

=\> printenv mender\_uboot\_root  
mender\_uboot\_root=mmc 0:2  
=\> printenv fdt\_addr\_r  
fdt\_addr\_r=0x83000000  
=\> printenv mender\_dtb\_name

## Error: “mender\_dtb\_name” not defined

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 5, 2021, 4:09am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/7 "2021-07-05T04:09:17Z")

</div>

I got new error:

=\> printenv mender\_dtb\_name  
mender\_dtb\_name=hero-secc-imx6ull-var-dart-6ulcustomboard-emmc-sd-card.dtb  
=\> run mender\_setup  
=\> setenv bootargs root=${mender\_kernel\_root} ${bootargs}  
=\> if test “${fdt\_addr\_r}” != “”; then load ${mender\_uboot\_root} ${fdt\_addr\_r} /boot/${mender\_dtb\_name}; fi;  
35567 bytes read in 75 ms (462.9 KiB/s)  
=\> load ${mender\_uboot\_root} ${kernel\_addr\_r} /boot/${mender\_kernel\_name};  
19604448 bytes read in 17142 ms (1.1 MiB/s)  
=\> ${mender\_boot\_kernel\_type} ${kernel\_addr\_r} - ${fdt\_addr\_r}  
Unknown command ‘booti’ - try ‘help’

=\> printenv mender\_boot\_kernel\_type  
mender\_boot\_kernel\_type=booti

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 5, 2021, 4:29am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/8 "2021-07-05T04:29:01Z")

</div>

I fixed the error by setting mender\_boot\_kernel\_type to bootz.  
After that, it just hang after running mender\_try\_to\_recover.

=\> run mender\_setup  
=\> setenv bootargs root=${mender\_kernel\_root} ${bootargs}  
=\> printenv bootargs  
bootargs=root=/dev/mmcblk0p2 console=ttymxc0,115200 cma=64MB  
=\> if test “${fdt\_addr\_r}” != “”; then load ${mender\_uboot\_root} ${fdt\_addr\_r} /boot/${mender\_dtb\_name}; fi;  
35567 bytes read in 75 ms (462.9 KiB/s)  
=\> load ${mender\_uboot\_root} ${kernel\_addr\_r} /boot/${mender\_kernel\_name}  
19604448 bytes read in 17143 ms (1.1 MiB/s)  
=\> ${mender\_boot\_kernel\_type} ${kernel\_addr\_r} - ${fdt\_addr\_r}  
=\> printenv mender\_boot\_kernel\_type  
mender\_boot\_kernel\_type=bootz  
=\> printenv kernel\_addr\_r  
kernel\_addr\_r=0x82000000  
=\> printenv fdt\_addr\_r  
fdt\_addr\_r=0x83000000  
=\> run mender\_try\_to\_recover

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [July 5, 2021, 11:29am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/9 "2021-07-05T11:29:08Z")

</div>

It should actually be booting at the `${mender_boot_kernel_type} ${kernel_addr_r} - ${fdt_addr_r}` step. You should not get to the `mender_try_to_recover` step. Very strange.

Can you run the steps again but echo the `${mender_boot_kernel_type} ${kernel_addr_r} - ${fdt_addr_r}` command before invoking it?  
Drew

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 5, 2021, 12:01pm UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/10 "2021-07-05T12:01:35Z")

</div>

I was able to fix this by changing mender\_boot\_kernel\_type to zImage. I can now boot the kernel but I got new error:

**[FAILED] Failed to start Remount Root and Kernel File Systems.**  
See ‘systemctl status systemd-remount-fs.service’ for details.

root@hero-secc:~# systemctl status systemd-remount-fs.service  
[[0;1;32m\*[[0m systemd-remount-fs.service - Remount Root and Kernel File Systems

Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; enabled-runti  
me; vendor preset: disabled)  
Active: [[0;1;32mactive (exited)[[0m since Tue 2021-06-15 07:37:42 UTC; 6min  
ago  
Docs: man:systemd-remount-fs.service(8)  
[APIFileSystems](https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems)  
Process: 288 ExecStart=/lib/systemd/systemd-remount-fs (code=exited, status=0/  
SUCCESS)  
Main PID: 288 (code=exited, status=0/SUCCESS)

Jun 15 07:37:40 hero-secc systemd[1]: Starting Remount Root and Kernel File Syst  
ems…  
Jun 15 07:37:42 hero-secc systemd[1]: Started Remount Root and Kernel File Syste  
ms.

**[FAILED] Failed to start Network Time Synchronization.**  
See ‘systemctl status systemd-timesyncd.service’ for details.

root@hero-secc:~#  
[[0;1;31m\*[[0m systemd-timesyncd.service - Network Time Synchronization  
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendo  
r preset: enabled)  
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2021-06-15 07:37:49  
UTC; 8min ago  
Docs: man:systemd-timesyncd.service(8)  
Process: 604 ExecStart=/lib/systemd/systemd-timesyncd [[0;1;31m(code=exited, s  
tatus=238/STATE\_DIRECTORY)[[0m  
Main PID: 604 (code=exited, status=238/STATE\_DIRECTORY)

Jun 15 07:37:49 hero-secc systemd[1]: systemd-timesyncd.service: Service has no  
hold-off time (RestartSec=0), scheduling restart.  
Jun 15 07:37:49 hero-secc systemd[1]: systemd-timesyncd.service: Scheduled resta  
rt job, restart counter is at 5.  
Jun 15 07:37:49 hero-secc systemd[1]: Stopped Network Time Synchronization.  
Jun 15 07:37:49 hero-secc systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185msys  
temd-timesyncd.service: Start request repeated too quickly.[[0m  
Jun 15 07:37:49 hero-secc systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185msys  
temd-timesyncd.service: Failed with result ‘exit-code’.[[0m  
Jun 15 07:37:49 hero-secc systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start  
Network Time Synchronization.[[0m

**[FAILED] Failed to start Login Service.**  
See ‘systemctl status systemd-logind.service’ for details.

root@hero-secc:~#  
[[0;1;31m\*[[0m systemd-logind.service - Login Service  
Loaded: loaded (/lib/systemd/system/systemd-logind.service; static; vendor pr  
eset: disabled)  
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2021-06-15 07:37:59  
UTC; 9min ago  
Docs: man:systemd-logind.service(8)  
man:logind.conf(5)  
[logind](https://www.freedesktop.org/wiki/Software/systemd/logind)  
[multiseat](https://www.freedesktop.org/wiki/Software/systemd/multiseat)  
Process: 713 ExecStartPre=/sbin/modprobe -abq drm [[0;1;31m(code=exited, statu  
s=238/STATE\_DIRECTORY)[[0m  
Process: 714 ExecStart=/lib/systemd/systemd-logind [[0;1;31m(code=exited, stat  
us=238/STATE\_DIRECTORY)[[0m  
Main PID: 714 (code=exited, status=238/STATE\_DIRECTORY)

Jun 15 07:37:59 hero-secc systemd[1]: systemd-logind.service: Service has no hol  
d-off time (RestartSec=0), scheduling restart.  
Jun 15 07:37:59 hero-secc systemd[1]: systemd-logind.service: Scheduled restart  
job, restart counter is at 5.  
Jun 15 07:37:59 hero-secc systemd[1]: Stopped Login Service.  
Jun 15 07:37:59 hero-secc systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185msys  
temd-logind.service: Start request repeated too quickly.[[0m  
Jun 15 07:37:59 hero-secc systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185msys

**[FAILED] Failed to start PulseAudio system server.**  
See ‘systemctl status pulseaudio.service’ for details.

root@hero-secc:~#  
[[0;1;31m\*[[0m pulseaudio.service - PulseAudio system server  
Loaded: loaded (/etc/systemd/system/pulseaudio.service; enabled; vendor prese  
t: disabled)  
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2021-06-15 07:37:56  
UTC; 10min ago  
Process: 620 ExecStart=/usr/bin/pulseaudio --system --disallow-exit --disable-  
shm --exit-idle-time=-1 --daemonize [[0;1;31m(code=exited, status=1/FAILURE)[[0m

Jun 15 07:37:52 hero-secc systemd[1]: Starting PulseAudio system server…  
Jun 15 07:37:56 hero-secc pulseaudio[620]: W: [pulseaudio] main.c: Running in sy  
stem mode, but --disallow-module-loading not set.  
Jun 15 07:37:56 hero-secc pulseaudio[673]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to  
create ‘/var/lib/pulse’: Read-only file system[[0m  
Jun 15 07:37:56 hero-secc pulseaudio[620]: E: [pulseaudio] main.c: Daemon startu  
p failed.  
Jun 15 07:37:56 hero-secc systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mpulseaudio.serv  
ice: Control process exited, code=exited, status=1/FAILURE[[0m  
Jun 15 07:37:56 hero-secc systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185mpul  
seaudio.service: Failed with result ‘exit-code’.[[0m  
Jun 15 07:37:56 hero-secc systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start  
PulseAudio system server.[[0m

**[FAILED] Failed to start Terminate Psplash Boot Screen.**  
See ‘systemctl status psplash-quit.service’ for details.

root@hero-secc:~#  
[[0;1;31m\*[[0m psplash-quit.service - Terminate Psplash Boot Screen  
Loaded: loaded (/lib/systemd/system/psplash-quit.service; enabled; vendor pre  
set: enabled)  
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2021-06-15 07:37:57  
UTC; 11min ago  
Process: 682 ExecStart=/usr/bin/psplash-write QUIT [[0;1;31m(code=exited, stat  
us=255/EXCEPTION)[[0m  
Main PID: 682 (code=exited, status=255/EXCEPTION)

Jun 15 07:37:57 hero-secc systemd[1]: Starting Terminate Psplash Boot Screen…  
Jun 15 07:37:57 hero-secc systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mpsplash-quit.se  
rvice: Main process exited, code=exited, status=255/EXCEPTION[[0m  
Jun 15 07:37:57 hero-secc systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185mpsp  
lash-quit.service: Failed with result ‘exit-code’.[[0m  
Jun 15 07:37:57 hero-secc systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start  
Terminate Psplash Boot Screen.[[0m

**[FAILED] Failed to start Variscite Bluetooth setup service.**  
See ‘systemctl status variscite-bt.service’ for details.

root@hero-secc:~#  
[[0;1;31m\*[[0m variscite-bt.service - Variscite Bluetooth setup service  
Loaded: loaded (/lib/systemd/system/variscite-bt.service; enabled; vendor pre  
set: disabled)  
Active: [[0;1;31mfailed[[0m (Result: exit-code) since Tue 2021-06-15 07:38:00  
UTC; 12min ago  
Process: 658 ExecStart=/etc/bluetooth/variscite-bt start (code=exited, status=  
0/SUCCESS)  
Process: 730 ExecStop=/etc/bluetooth/variscite-bt stop [[0;1;31m(code=exited,  
status=1/FAILURE)[[0m

Jun 15 07:37:53 hero-secc systemd[1]: Starting Variscite Bluetooth setup service  
…  
Jun 15 07:37:59 hero-secc variscite-bt[658]: No BT found  
Jun 15 07:38:00 hero-secc variscite-bt[730]: Can’t get device info: No such devi  
ce  
Jun 15 07:38:00 hero-secc systemd[1]: [[0;1;39m[[0;1;31m[[0;1;39mvariscite-bt.se  
rvice: Control process exited, code=exited, status=1/FAILURE[[0m  
Jun 15 07:38:00 hero-secc systemd[1]: [[0;1;38;5;185m[[0;1;39m[[0;1;38;5;185mvar  
iscite-bt.service: Failed with result ‘exit-code’.[[0m  
Jun 15 07:38:00 hero-secc systemd[1]: [[0;1;31m[[0;1;39m[[0;1;31mFailed to start  
Variscite Bluetooth setup service.[[0m

**[FAILED] Failed to start Mender-configure device configuration.**  
See ‘systemctl status mender-configure-…ply-device-config.service’ for details.

root@hero-secc:~#  
Invalid unit name “mender-configure-…ply-device-config.service” was escaped as  
“mender-configure-\xe2\x80\xa6ply-device-config.service” (maybe you should use  
systemd-escape?)  
Unit mender-configure-\xe2\x80\xa6ply-device-config.service could not be found.

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 5, 2021, 12:11pm UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/11 "2021-07-05T12:11:47Z")

</div>

But, after reset, I only got two errors:

[FAILED] Failed to start Terminate Psplash Boot Screen.

[FAILED] Failed to start Variscite Bluetooth setup service.

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [July 5, 2021, 3:32pm UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/12 "2021-07-05T15:32:46Z")

</div>

I’m not sure what to suggest for this issue. It seems like something is definitely not happy but since I no longer have access to the hardware or to your custom manual integration, I don’t know what else could be wrong.

Sorry,  
Drew

---

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [July 5, 2021, 3:55pm UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/13 "2021-07-05T15:55:34Z")

</div>

At least you are on to user-space errors now, try going thru each problem one by one using journalctl to inspect the full log for each service that errored

---

<div class="post-metadata">

**Author:** ![marizonne.villafranc](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@marizonne.villafranc](https://hub.mender.io/u/marizonne.villafranc)\
**Post date:** [July 6, 2021, 12:08am UTC](https://hub.mender.io/t/after-meta-mender-integration-the-target-variscite-imx6ul-cannot-boot/3808/14 "2021-07-06T00:08:47Z")

</div>

No worries mate! Thanks for all the support!