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

Board Integrations Yocto Project
,
1

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
hero-yocto-mender-sd942×401 56.6 KB

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

2

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

1 Like
3

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
=>

4

=> 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/ **

5

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

6

=> 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

7

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

8

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

9

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

10

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
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
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.

11

But, after reset, I only got two errors:

[FAILED] Failed to start Terminate Psplash Boot Screen.

[FAILED] Failed to start Variscite Bluetooth setup service.

12

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

13

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

1 Like
14

No worries mate! Thanks for all the support!