Hi! I have got some problems with the integration of mender to an existing Yocto image
Board description
I use a Reterminal, a board powered by Raspberry Pi Compute Module 4 (CM4) with 4GB RAM & 32GB eMMC
URL: Getting Started with reTerminal - Seeed Wiki
My version of Yocto Project is dunfell and I also use the following layers:
layer path priority
==========================================================================
meta /home/usr/Yocto_from_scratch/layers/poky/meta 5
meta-poky /home/usr/Yocto_from_scratch/layers/poky/meta-poky 5
meta-yocto-bsp /home/usr/Yocto_from_scratch/layers/poky/meta-yocto-bsp 5
meta-mender-core /home/usr/Yocto_from_scratch/layers/meta-mender/meta-mender-core 6
meta-raspberrypi /home/usr/Yocto_from_scratch/layers/meta-raspberrypi 9
meta-mender-raspberrypi /home/usr/Yocto_from_scratch/layers/meta-mender/meta-mender-raspberrypi 10
meta-qt5 /home/jprobst/Yocto_from_scratch/layers/meta-qt5 7
meta-oe /home/jprobst/Yocto_from_scratch/layers/meta-openembedded/meta-oe 6
meta-python /home/jprobst/Yocto_from_scratch/layers/meta-openembedded/meta-python 7
meta-mender-demo /home/jprobst/Yocto_from_scratch/layers/meta-mender/meta-mender-demo 10
meta-seeed-cm4 /home/jprobst/Yocto_from_scratch/layers/meta-seeed-cm4 6
Test results
The building of my image is a success but I have a warning while building :
Build Configuration:
BB_VERSION = "1.46.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "seeed-reterminal-mender"
DISTRO = "poky"
DISTRO_VERSION = "3.1.17"
TUNE_FEATURES = "aarch64 cortexa72 crc crypto"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "dunfell:1e298a42223dd2628288b372caf66c52506a8081"
meta-mender-core = "dunfell:1ff13795e760e3ba336e9304326069ba6edf7a90"
meta-raspberrypi = "dunfell:934064a01903b2ba9a82be93b3f0efdb4543a0e8"
meta-mender-raspberrypi = "dunfell:1ff13795e760e3ba336e9304326069ba6edf7a90"
meta-qt5 = "dunfell:5ef3a0ffd3324937252790266e2b2e64d33ef34f"
meta-oe
meta-python = "dunfell:deee226017877d51188e0a46f9e6b93c10ffbb34"
meta-mender-demo = "dunfell:1ff13795e760e3ba336e9304326069ba6edf7a90"
meta-seeed-cm4 = "dunfell:4c2793f00d4f97f1e2aefc7516c71e465b51671f"
Initialising tasks: 100% |####################################################################################################################################################################################################################################| Time: 0:00:06Sstate summary: Wanted 44 Found 0 Missed 44 Current 2147 (0% match, 97% complete)
NOTE: Executing Tasks
WARNING: u-boot-1_2020.01-r0 do_provide_mender_defines: Found more than one dtb specified in KERNEL_DEVICETREE
( broadcom/bcm2711-rpi-4-b.dtb broadcom/bcm2711-rpi-400.dtb broadcom/bcm2711-rpi-cm4.dtb overlays/at86rf233.dtbo overlays/dwc2.dtbo overlays/gpio-key.dtbo overlays/hifiberry-amp.dtbo overlays/hifiberry-dac.dtbo overlays/hifiberry-dacplus.dtbo overlays/hifiberry-digi.dtbo overlays/i2c-rtc.dtbo overlays/iqaudio-dac.dtbo overlays/iqaudio-dacplus.dtbo overlays/miniuart-bt.dtbo overlays/mcp2515-can0.dtbo overlays/mcp2515-can1.dtbo overlays/pitft22.dtbo overlays/pitft28-resistive.dtbo overlays/pitft28-capacitive.dtbo overlays/pitft35-resistive.dtbo overlays/pps-gpio.dtbo overlays/rpi-ft5406.dtbo overlays/rpi-poe.dtbo overlays/vc4-kms-v3d.dtbo overlays/vc4-fkms-v3d.dtbo overlays/w1-gpio-pullup.dtbo overlays/w1-gpio.dtbo overlays/gpio-ir.dtbo overlays/gpio-ir-tx.dtbo overlays/disable-bt.dtbo overlays/reTerminal.dtbo overlays/i2c3.dtbo ).
Only one should be specified. Choosing the last one: broadcom/bcm2711-rpi-cm4.dtb.
Set KERNEL_DEVICETREE to the desired dtb file to silence this warning.
and when I flash the image on the Reterminal, I only see a black screen. I tried to debug what is happening at boot time using UART serial connextion but I only got the following messages:
11:12:54.160 -> U-Boot 2020.01 (Jan 06 2020 - 20:56:31 +0000)
11:12:54.160 ->
11:12:54.160 -> DRAM: 3.9 GiB
11:12:54.342 -> RPI: Board rev 0x14 outside known range
11:12:54.342 -> RPI Unknown model (0xc03140)
11:12:54.389 -> MMC: mmcnr@7e300000: 1, mmc@7e340000: 0
11:12:54.389 -> Loading Environment from MMC... OK
11:12:54.479 -> In: serial
11:12:54.479 -> Out: serial
11:12:54.479 -> Err: serial
11:12:54.479 -> Net: No ethernet found.
11:12:54.479 -> starting USB...
11:12:54.479 -> Bus usb@7e980000: scanning bus usb@7e980000 for devices... 2 USB Device(s) found
11:12:57.075 -> scanning usb for storage devices... 0 Storage Device(s) found
11:12:57.075 -> Hit any key to stop autoboot: 2 1 0
11:12:59.128 -> switch to partitions #0, OK
11:12:59.173 -> mmc0(part 0) is current device
11:12:59.173 -> Scanning mmc 0:1...
11:12:59.173 -> Found U-Boot script /boot.scr
11:12:59.219 -> 299 bytes read in 8 ms (36.1 KiB/s)
11:12:59.219 -> ## Executing script at 02400000
11:12:59.265 -> switch to partitions #0, OK
11:12:59.265 -> mmc0(part 0) is current device
11:13:00.770 -> 23136768 bytes read in 1477 ms (14.9 MiB/s)
11:13:00.907 -> ## Flattened Device Tree blob at 2eff2200
11:13:00.952 -> Booting using the fdt blob at 0x2eff2200
11:13:00.952 -> Using Device Tree in place at 000000002eff2200, end 000000002f002f39
11:13:00.952 ->
11:13:00.952 -> Starting kernel ...
After this it seems that either the board is stuck in the “starting kernel” mode or that it does not send any messages after starting the kernel.
If anyone would have an idea of why this is happening I would be really grateful.
I am new to the use of mender and yocto so maybe I missed some key point