compulab-yokneam / meta-bsp-imx8mm Goto Github PK

BitBake 65.26% Shell 11.41% C++ 0.52% HTML 22.81%

meta-bsp-imx8mm's Introduction

Quick Start Guide

Supported Compulab machines:

Setup Yocto Environment

Install the repo utility:

mkdir ~/bin
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
PATH=${PATH}:~/bin

Set environmet varables:

export LREPO=imx_5.15.32-2.0.0-compulab.xml
export CLB_RELEASE=rel_imx_5.15.32-2.0.0-dev

Define COMPULAB_MACHINE environment variable

Machine	Command Line
mcm-imx8m-mini	`export COMPULAB_MACHINE=mcm-imx8m-mini`
ucm-imx8m-mini	`export COMPULAB_MACHINE=ucm-imx8m-mini`

Prepare NXP BSP

mkdir compulab-freescale-bsp && cd compulab-freescale-bsp
repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-kirkstone -m imx-5.15.32-2.0.0.xml

Download Compulab meta layer

mkdir -p .repo/local_manifests
wget --directory-prefix .repo/local_manifests https://raw.githubusercontent.com/compulab-yokneam/meta-bsp-imx8mm/${CLB_RELEASE}/scripts/${LREPO}

Get entire BSP tree

repo sync

Build

Run Compulab Linux Yocto Project setup

NOTE	Refer to the NXP Readme for details about how to select a correct backend & distro.

MACHINE=${COMPULAB_MACHINE} DISTRO=fsl-imx-xwayland source compulab-setup-env -b build-${COMPULAB_MACHINE}

Build image

bitbake -k imx-image-full

meta-bsp-imx8mm's People

Contributors

Stargazers

Watchers

meta-bsp-imx8mm's Issues

Build failure: wireguard-module

Looking for some guidence if I am doing something wrong or this is an upstream issue.

Using the instructions in https://mediawiki.compulab.com/w/index.php?title=Building_IOT-GATE-iMX8_and_SBC-IOT-iMX8_Yocto_Linux_images, I am able to build the Yocto Zeus images for IOT-GATE-iMX8, but it fails if, I add wireguard-tools wireguard-module to the CORE_IMAGE_EXTRA_INSTALL in conf/local.conf

Here's error -

Summary: 1 task failed:
  /home/dev/sources/meta-openembedded/meta-networking/recipes-kernel/wireguard/wireguard-module_0.0.20190913.bb:do_compile

I guess it is likely, one of the sources for wireguard needs updating.

Firmware-imx-sdma-imx7d should be linux-firmware-imx-sdma-im7d

meta-bsp-imx8mm/conf/layer.conf

Line 18 in 735984d

 CORE_IMAGE_EXTRA_INSTALL += "${@bb.utils.contains('DISTRO_CODENAME', 'dunfell', 'firmware-imx-sdma-imx7d', 'firmware-imx-sdma', d)}" 

In Yocto 3.1.7 builds fail due to firmware-imx-sdma-imx7d in this recipe, instead of linux-firmware-imx-sdma-im7d

do these recipes build 64-bit ARM linux or 32-bit one?

"split_kernel_module_packages" removed from PACKAGESPLITFUNCS.

Hello,
I wonder why you remove "split_kernel_module_packages" from PACKAGESPLITFUNCS.
I there a particular reason ?

meta-bsp-imx8mm/recipes-kernel/linux/linux-compulab_5.15.32.bb

Line 106 in 8da85dd

PACKAGESPLITFUNCS:remove = "split_kernel_module_packages"

This function is mandatory so that KERNEL_MODULE_AUTOLOAD and KERNEL_MODULE_PROBECONF works.
Thanks for your help.

The eMMC module is installed in socket P14

I have eMMC module in socket P14 but it is not possible to see the eMMC device from the Yocto build. I do not have jumper E1 set. To use extra module is it required to set the E1 jumper and boot from the extra module or can it be accessed when booting from internal eMMC?

Link to precompiled images not working

The link at the bottom of the front page (in the README) does not work.

The link is https://drive.google.com/file/d/1PLSpK6_F1oTnSQqcTwHmpUboF7tbKLAv/view?usp=sharing

dunfell release

Hi, do you have a dunfell compatible release of your layer?

Thanks!

Wrong machine override on kirkstone imx-atf

Good day, I was looking at the imx-atf_2.4.bb recipe in branch rel_imx_5.15.32-2.0.0-stable.
The lines 23 to 33 and line 38 present a wrong override sintax for the compatible layer (kirkstone).
I think you should replace the underscore with columns:
PLATFORM_(machine-name) -> PLATFORM:(machine-name)

Can not reproduce kernel build for IOT-GATE-iMX8

We're working on a project using the IOT-GATE-iMX8.
We need the IOT-GATE's CAN interface to support ISO-TP which is not integrated into Linux kernels older than 5.10.
I'm not able to reproduce the kernel build provided on your website using the official documentation.

Would you able to give me instructions on how to produce the can-isotp kernel module that can be imported on the provided kernel?
Alternatively how can the boot partition (mmcblk2p1) be modified in order to boot a custom built kernel (which filesystem is it using)?

Here is the link to the can-isotp kernel module: https://github.com/hartkopp/can-isotp

Thanks in advance and kind regards,
Alexander Hölzl

Are there any plans to move to warrior?

We have an existing image working for IMX7 and would like to have it as a base for porting to IMX8. Are there any plans to port to warrior?

Update u-boot defconfig to include "CONFIG_SUPPORT_RAW_INITRD" for iot-gate-imx8

As per issue title, Ubuntu Core does not boot, due to current u-boot binary not supporting raw initrd images.
"CONFIG_SUPPORT_RAW_INITRD=y"

Build crashes on rel_imx_5.4.24_2.1.0-dev with some machines due to Denx's Gitlab redirect

Hi,
I've noticed that due to an error in a recipe which actually has nothing to do with the i.MX8M Mini or this meta layer, the Yocto build on the rel_imx_5.4.24_2.1.0-dev branch fails just after the recipe parsing phase for UCM-IMX8M-MINI. The recipe in question is the one from meta-compulab meta layer and can be found at:
https://github.com/compulab-yokneam/meta-compulab/blob/devel/recipes-bsp/u-boot/u-boot-compulab_2017.07.bb

This layer is pulled by one of Compulab scripts and unfortunately due to a typo or error, bitbake is trying to fetch the refs from Denx's Gitlab for this U-Boot 2017.07. The line in question from the recipe is:
COMPATIBLE_MACHINE_cl-som-imx7 = "cl-som-imx7"
Correct would be:
COMPATIBLE_MACHINE = "cl-som-imx7"

Due to this typo, and the fact that with the new 5.4 branch Compulab added layer masking for anything that has the word boundary in it, the newest U-Boot found after parsing phase (and the first recipe that tries to do do_compile() task) is this one, which is why it is trying to fetch the refs. This typo is effectively sabotaging the COMPATIBLE_MACHINE variable at least after the parsing phase.

Now the interesting thing is that refs can be fetched on some machines, as redirect works proper, but on most machines I've tried, it would crash with a redirect to Sign-in page of Denx's Gitlab, thinking that it actually has to build this old u-boot. Once this stage is passed (either by changing/deleting the recipe or removing the typo), a bit later in the build the proper imx-uboot is taken. However, this is rather difficult to figure out, especially since this U-Boot is not even supposed to be built. In contrast deleting this recipe helps bitbake as the newest one after this is 2016.09 which has the correct COMPATIBLE_MACHINE defined in its recipe, so bitbake doesn't touch it at all.

Fixing the typo resolves the issue. Please fix - I would create a PR myself, but since the change was done on purpose, I'm not sure if it would break something else. The typo was introduced with commit 814b0feb904485f3aa239f55a00e4a8e3189a919, apparently was needed for warrior, but I really doubt that it was meant like this since it's just wrong - it makes no sense to be written like that...

To test if the bitbake touches it during UCM-IMX8M-MINI build, you can break the git link in the recipe - as a result the whole build will fail after parsing.

Cheers!

Kirkstone release

Hi,

Do you already have a plan for the Kirkstone release? We would like to beta test also if possible. Thanks a lot 🍻

Kind regards,
Jeppe

cl-deploy from rel_imx_5.4.24_2.1.0-dev not updating Bootloader(s)

Hi,
I've just successfully built and booted the new rel_2.1.0 from SD Card. However, cl-deploy script does not seem to update bootloaders, so I'm stuck with stock 2018.03 u-boot which seems to hang the new kernel.

Regarding the kernel hang, it sounds similar to one of the other issues here - the last line for me being:
[ 0.817148] mxs-dma 33000000.dma-controller: initialized

The kernel and rootfs are properly updated (mmcblk2p1 and mmcblk2p2), but I noticed that you use JEDEC HW partitions on eMMC (boot0 and boot1 on mmcblk2) which are most likely containing u-boot and u-boot SPL in raw form without the FS. I've searched but I couldn't find a manual on how to manually flash this and with what exact artefact - could you please share a link or explanation on how to flash the bootloaders?
Thanks!

SDP support on IOT-GATE-iMX8 EVK

We're working on IOT-GATE-iMX8 EVK and building the Yocto Linux images based on this guide.

We want to enable SDP to work with UUU Tool but it seems like that the SDP support on SPL is scrapped out on the BSP.

We're getting the following error,

U-Boot SPL 2020.04-iot-gate-imx8-2.3-5.4.24-2.1.0+g4979a99482 (May 28 2021 - 06:32:44 +0000)
power_bd71837_init
DDRINFO(D): Nanya 2048G
DDRINFO: start DRAM init
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
DDRINFO(M): mr5-8 [ 0x5000010 ]
DDRINFO(E): mr5-8 [ 0x5000010 ]
Back to ROM, SDP

We've already raised this on UUU tool repo.

We would like to have a BSP with SDP support.

CC @tkmozhi

Error for mcm-imx8m-mini machine

Hello, i got error for mcm-imx8m-mini-machine

WARNING: No bb files in default matched BBFILE_PATTERN_compulab-net '^/home/metehan/compulab-freescale-bsp/sources/meta-compulab-bsp/meta-net/'

ERROR: Nothing PROVIDES 'virtual/kernel'

ERROR: Nothing PROVIDES 'virtual/bootloader' (but /home/metehan/compulab-freescale-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt6-layer/recipes-fsl/images/imx-image-full.bb DEPENDS on or otherwise requires it)

ERROR: Nothing RPROVIDES 'kernel-modules' (but /home/metehan/compulab-freescale-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt6-layer/recipes-fsl/images/imx-image-full.bb, /home/metehan/compulab-freesca

ERROR: Nothing RPROVIDES 'kernel' (but /home/metehan/compulab-freescale-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt6-layer/recipes-fsl/images/imx-image-full.bb RDEPENDS on or otherwise requires it)

ERROR: Nothing RPROVIDES 'packagegroup-base-nfs' (but /home/metehan/compulab-freescale-bsp/sources/poky/meta/recipes-core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'packagegroup-base-nfs'

these are some errors(really much errors i have).
How can i fix those errors?
Thanks.

bitbake error

Hi, i get a error at bitbake step,
"ERROR: The following required tools (as specified by HOSTTOOLS) appear to be unavailable in PATH, please install them in order to proceed: git-lfs bison tree git-lfs".
could you help me,
thanks

imx_5.15.32-2.0.0-compulab: Build warnings

Hi,

While I was compiling the new version of OS (imx_5.15.32-2.0.0-compulab) I got the following WARNING in Yocto console:

WARNING: No bb files in default matched BBFILE_PATTERN_compulab-net '^/home/builder/compulab-freescale-bsp/sources/meta-compulab-bsp/meta-net/' NOTE: Resolving any missing task queue dependencies NOTE: Multiple providers are available for runtime mfgtool-image-image (linux-fslc-lts-mfgtool, linux-fslc-mfgtool, linux-imx-mfgtool) Consider defining a PREFERRED_RPROVIDER entry to match mfgtool-image-image NOTE: Multiple providers are available for runtime mfgtool-image (linux-fslc-lts-mfgtool, linux-fslc-mfgtool, linux-imx-mfgtool) Consider defining a PREFERRED_RPROVIDER entry to match mfgtool-image NOTE: Multiple providers are available for runtime mfgtool-base (linux-fslc-lts-mfgtool, linux-fslc-mfgtool, linux-imx-mfgtool) Consider defining a PREFERRED_RPROVIDER entry to match mfgtool-base

Thanos

0042-can-mcp25xxfd-update-driver can failed to build with rel_imx_5.4.24_2.1.0

The tag iot-gate-imx8_r2.2 introduce some new kernel patches, especially 0042-can-mcp25xxfd-update-driver.patch which seems not buildable with recommanded NXP release kernel (rel_imx_5.4.24_2.1.0) if CONFIG_DEBUG_FS is disabled (which is the case in most production definitions).

In file included from drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.h:11,
                 from drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.c:52:
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can_debugfs.h:34:41: warning: « struct mcp25xxfd_can_priv » est déclaré à l'intérieur d'une liste de paramètres et ne sera pas visible en dehors de cette définition ou déclaration
 void mcp25xxfd_can_debugfs_setup(struct mcp25xxfd_can_priv *cpriv)
                                         ^~~~~~~~~~~~~~~~~~
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can_debugfs.h:39:42: warning: « struct mcp25xxfd_can_priv » est déclaré à l'intérieur d'une liste de paramètres et ne sera pas visible en dehors de cette définition ou déclaration
 void mcp25xxfd_can_debugfs_remove(struct mcp25xxfd_can_priv *cpriv)
                                          ^~~~~~~~~~~~~~~~~~
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.c: Dans la fonction « mcp25xxfd_can_open »:
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.c:486:17: error: « struct mcp25xxfd_can_priv » n'a pas de membre nommé « stats »; vouliez-vous employer « status » ?
  memset(&cpriv->stats, 0, sizeof(cpriv->stats));
                 ^~~~~
                 status
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.c:486:41: error: « struct mcp25xxfd_can_priv » n'a pas de membre nommé « stats »; vouliez-vous employer « status » ?
  memset(&cpriv->stats, 0, sizeof(cpriv->stats));
                                         ^~~~~
                                         status
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.c: Dans la fonction « mcp25xxfd_can_setup »:
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.c:670:30: error: passage de l'argument 1 de « mcp25xxfd_can_debugfs_setup » depuis un type pointeur incompatible [-Werror=incompatible-pointer-types]
  mcp25xxfd_can_debugfs_setup(cpriv);
                              ^~~~~
In file included from drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.h:11,
                 from drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.c:52:
drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can_debugfs.h:34:61: note: « struct mcp25xxfd_can_priv * » attendu mais l'argument est de type « struct mcp25xxfd_can_priv * »
 void mcp25xxfd_can_debugfs_setup(struct mcp25xxfd_can_priv *cpriv)
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
cc1 : certains avertissements sont traités comme des erreurs
scripts/Makefile.build:265 : la recette pour la cible « drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.o » a échouée
make[6]: *** [drivers/net/can/spi/mcp25xxfd/mcp25xxfd_can.o] Erreur 1
scripts/Makefile.build:500 : la recette pour la cible « drivers/net/can/spi/mcp25xxfd » a échouée
make[5]: *** [drivers/net/can/spi/mcp25xxfd] Erreur 2
scripts/Makefile.build:500 : la recette pour la cible « drivers/net/can/spi » a échouée
make[4]: *** [drivers/net/can/spi] Erreur 2
scripts/Makefile.build:500 : la recette pour la cible « drivers/net/can » a échouée
make[3]: *** [drivers/net/can] Erreur 2
scripts/Makefile.build:500 : la recette pour la cible « drivers/net » a échouée
make[2]: *** [drivers/net] Erreur 2

Disabling 0042-can-mcp25xxfd-update-drive.patch patch, while keeping the other new patches works.

It seems the code strongly rely on the stats structure on mcp25xxfd_can_priv structure which is not enabled if CONFIG_DEBUG_FS is disable

Setup script does not run unless you choose default options

When I run:
MACHINE=ucm-imx8m-mini DISTRO=fsl-imx-xwayland source sources/meta-bsp-imx8mm/tools/setup-imx8mm-env -b build-xwayland

And then reach the user config step, if you choose any non-default values such as 'no' for chrome the script produces an error and exits:

chrome configuration [ yes ] (Ctrl^C -- exit) : 3
cat: /tmp/userKT2: No such file or directory

It works fine if you say yes, this is on a vanilla Ubuntu 16.04.4 with the required Yocto packages installed.

mcm-imx8m-mini alsa error

Hello, i faced the error for mcm-imx8m-mini. How can I solve it ?

[ 254.273138] fsl-sai 30020000.sai: failed to derive required Tx rate: 1411200
[ 254.280258] fsl-sai 30020000.sai: ASoC: error at snd_soc_dai_hw_params on 30020000.sai: -22
[ 254.288972] 30020000.sai-wm8731-hifi: ASoC: soc_pcm_hw_params() failed (-22)
ALSA lib ../../../alsa-lib-1.2.6.1/src/pcm/pcm_direct.c:1305:(snd1_pcm_direct_initialize_slave) unable to install hw params
ALSA lib ../../../alsa-lib-1.2.6.1/src/pcm/pcm_dmix.c:1013:(snd_pcm_dmix_open) unable to initialize slave
aplay: main:831: audio open error: Invalid argument

Readme guide for rel3.2.1 and rel3.2 does not work, when run from the scratch

I have performed the steps to build the yocto project for rel3.2.1 but I get the error when running repo sync:

repo sync
remote: Enumerating objects: 1372, done.
remote: Counting objects: 100% (708/708), done.
remote: Compressing objects: 100% (199/199), done.
remote: Total 1372 (delta 561), reused 640 (delta 506), pack-reused 664
Fetching: 25% (4/16) 0:07 | 2 jobs | 0:04 meta-bsp-imx8mm @ sources/meta-bsp-imx8mm
fatal: couldn't find remote ref refs/heads/iot-gate-imx8_r3.2.1

I have eddited the xml file with the revisions where I have replaced the tag with the corresponding hash and it works:
diff -Nur .repo/local_manifests/imx_5.15.32-2.0.0-compulab.xml /home/jyu/imx_5.15.32-2.0.0-compulab.xml
--- .repo/local_manifests/imx_5.15.32-2.0.0-compulab.xml 2023-06-20 14:31:10.932643495 +0200
+++ /home/jyu/imx_5.15.32-2.0.0-compulab.xml 2023-06-20 14:20:01.154525878 +0200
@@ -5,7 +5,7 @@

   <project name="meta-compulab" remote="compulab" revision="6316d8ca737f7460ea24d83f3aeec9f8d00b6e8a" path="sources/meta-compulab"/>
   <project name="meta-compulab-bsp" remote="compulab" revision="7f5882eb9bd139e4dde204ffa6b0aa96577b36d0" path="sources/meta-compulab-bsp"/>
-  <project name="meta-bsp-imx8mm" remote="compulab" revision="iot-gate-imx8_r3.2.1" path="sources/meta-bsp-imx8mm" >
+  <project name="meta-bsp-imx8mm" remote="compulab" revision="6a9d624d4fdd1b7031d6e69cbb2eadef74f0cb3c" path="sources/meta-bsp-imx8mm" >
     <linkfile src="tools/compulab-setup-env" dest="compulab-setup-env" />
   </project>

I think initially tags are not available for the repo sync command if git repository was not checked out before.

iot-gate-imx8 - Device tree issues on boot

Hello,
when booting I get the following log.
Note that several components fail to look up, especially

2023-09-11T11:31:54.515746+00:00 meshgw-bbgpp kernel: [    0.831143] imx8m_pm_domain power-domains:hsiomix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515749+00:00 meshgw-bbgpp kernel: [    0.831154] imx8m_pm_domain power-domains:hsiomix-pd: Looking up power-supply property in node /power-domains/hsiomix-pd failed
2023-09-11T11:31:54.515752+00:00 meshgw-bbgpp kernel: [    0.831255] imx8m_pm_domain power-domains:pcie-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515758+00:00 meshgw-bbgpp kernel: [    0.831264] imx8m_pm_domain power-domains:pcie-pd: Looking up power-supply property in node /power-domains/pcie-pd failed
2023-09-11T11:31:54.515762+00:00 meshgw-bbgpp kernel: [    0.831366] imx8m_pm_domain power-domains:usbotg1-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515764+00:00 meshgw-bbgpp kernel: [    0.831375] imx8m_pm_domain power-domains:usbotg1-pd: Looking up power-supply property in node /power-domains/usbotg1-pd failed
2023-09-11T11:31:54.515767+00:00 meshgw-bbgpp kernel: [    0.831473] imx8m_pm_domain power-domains:usbotg2-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515769+00:00 meshgw-bbgpp kernel: [    0.831484] imx8m_pm_domain power-domains:usbotg2-pd: Looking up power-supply property in node /power-domains/usbotg2-pd failed
2023-09-11T11:31:54.515772+00:00 meshgw-bbgpp kernel: [    0.831580] imx8m_pm_domain power-domains:gpumix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515779+00:00 meshgw-bbgpp kernel: [    0.831589] imx8m_pm_domain power-domains:gpumix-pd: Looking up power-supply property in node /power-domains/gpumix-pd failed
2023-09-11T11:31:54.515782+00:00 meshgw-bbgpp kernel: [    0.831713] imx8m_pm_domain power-domains:vpumix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515784+00:00 meshgw-bbgpp kernel: [    0.831722] imx8m_pm_domain power-domains:vpumix-pd: Looking up power-supply property in node /power-domains/vpumix-pd failed
2023-09-11T11:31:54.515787+00:00 meshgw-bbgpp kernel: [    0.831816] imx8m_pm_domain power-domains:vpug1-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515789+00:00 meshgw-bbgpp kernel: [    0.831825] imx8m_pm_domain power-domains:vpug1-pd: Looking up power-supply property in node /power-domains/vpug1-pd failed
2023-09-11T11:31:54.515792+00:00 meshgw-bbgpp kernel: [    0.831925] imx8m_pm_domain power-domains:vpug2-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515799+00:00 meshgw-bbgpp kernel: [    0.831938] imx8m_pm_domain power-domains:vpug2-pd: Looking up power-supply property in node /power-domains/vpug2-pd failed
2023-09-11T11:31:54.515802+00:00 meshgw-bbgpp kernel: [    0.832035] imx8m_pm_domain power-domains:vpuh1-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515805+00:00 meshgw-bbgpp kernel: [    0.832044] imx8m_pm_domain power-domains:vpuh1-pd: Looking up power-supply property in node /power-domains/vpuh1-pd failed
2023-09-11T11:31:54.515808+00:00 meshgw-bbgpp kernel: [    0.832148] imx8m_pm_domain power-domains:dispmix-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.515811+00:00 meshgw-bbgpp kernel: [    0.832157] imx8m_pm_domain power-domains:dispmix-pd: Looking up power-supply property in node /power-domains/dispmix-pd failed
2023-09-11T11:31:54.515814+00:00 meshgw-bbgpp kernel: [    0.832278] imx8m_pm_domain power-domains:mipi-pd: Looking up power-supply from device tree
2023-09-11T11:31:54.516418+00:00 meshgw-bbgpp kernel: [    0.832289] imx8m_pm_domain power-domains:mipi-pd: Looking up power-supply property in node /power-domains/mipi-pd failed

2023-09-11T11:31:54.517050+00:00 meshgw-bbgpp kernel: [    1.180205] sdhci-pltfm: SDHCI platform and OF driver helper
2023-09-11T11:31:54.517052+00:00 meshgw-bbgpp kernel: [    1.187161] sdhci-esdhc-imx 30b60000.mmc: Looking up vmmc-supply from device tree
2023-09-11T11:31:54.517054+00:00 meshgw-bbgpp kernel: [    1.187177] sdhci-esdhc-imx 30b60000.mmc: Looking up vmmc-supply property in node /soc@0/bus@30800000/mmc@30b60000 failed
2023-09-11T11:31:54.517057+00:00 meshgw-bbgpp kernel: [    1.187214] sdhci-esdhc-imx 30b60000.mmc: Looking up vqmmc-supply from device tree
2023-09-11T11:31:54.517060+00:00 meshgw-bbgpp kernel: [    1.187222] sdhci-esdhc-imx 30b60000.mmc: Looking up vqmmc-supply property in node /soc@0/bus@30800000/mmc@30b60000 failed

2023-09-11T11:31:54.517867+00:00 meshgw-bbgpp kernel: [    1.605299] rohm-bd718x7 1-004b: Looking up buck6-supply property in node /soc@0/bus@30800000/i2c@30a30000/bd71837@4b failed
2023-09-11T11:31:54.517876+00:00 meshgw-bbgpp kernel: [    1.605351] LDO5: supplied by regulator-dummy
2023-09-11T11:31:54.517879+00:00 meshgw-bbgpp kernel: [    1.610503] LDO6: will resolve supply early: buck7
2023-09-11T11:31:54.517874+00:00 meshgw-bbgpp systemd[1]: Finished Bind mount volatile /srv.
2023-09-11T11:31:54.517882+00:00 meshgw-bbgpp kernel: [    1.610510] rohm-bd718x7 1-004b: Looking up buck7-supply from device tree
2023-09-11T11:31:54.517884+00:00 meshgw-bbgpp kernel: [    1.610542] rohm-bd718x7 1-004b: Looking up buck7-supply property in node /soc@0/bus@30800000/i2c@30a30000/bd71837@4b failed
2023-09-11T11:31:54.517887+00:00 meshgw-bbgpp kernel: [    1.610587] LDO6: supplied by regulator-dummy
2023-09-11T11:31:54.517889+00:00 meshgw-bbgpp kernel: [    1.614960] regulator-dummy: could not add device link regulator.26: -ENOENT
2023-09-11T11:31:54.517891+00:00 meshgw-bbgpp kernel: [    1.615538] LDO6: 900 <--> 1800 mV at 1200 mV, enabled
2023-09-11T11:31:54.517888+00:00 meshgw-bbgpp systemd[1]: Starting Load/Save Random Seed...
2023-09-11T11:31:54.517904+00:00 meshgw-bbgpp kernel: [    1.616071] LDO7: 1800 <--> 3300 mV at 1800 mV, disabled
2023-09-11T11:31:54.517900+00:00 meshgw-bbgpp systemd[1]: Finished Load/Save Random Seed.
2023-09-11T11:31:54.517907+00:00 meshgw-bbgpp kernel: [    1.616857] at24 1-0050: Looking up vcc-supply from device tree
2023-09-11T11:31:54.517909+00:00 meshgw-bbgpp kernel: [    1.616867] at24 1-0050: Looking up vcc-supply property in node /soc@0/bus@30800000/i2c@30a30000/eeprom@50 failed
2023-09-11T11:31:54.517912+00:00 meshgw-bbgpp kernel: [    1.616914] at24 1-0050: supply vcc not found, using dummy regulator
2023-09-11T11:31:54.517914+00:00 meshgw-bbgpp kernel: [    1.624178] at24 1-0050: 1024 byte 24c08 EEPROM, writable, 16 bytes/write
2023-09-11T11:31:54.517917+00:00 meshgw-bbgpp kernel: [    1.631052] i2c i2c-1: IMX I2C adapter registered
2023-09-11T11:31:54.517913+00:00 meshgw-bbgpp systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
2023-09-11T11:31:54.517926+00:00 meshgw-bbgpp kernel: [    1.637432] imx6q-pcie 33800000.pcie: Looking up epdev_on-supply from device tree
2023-09-11T11:31:54.517930+00:00 meshgw-bbgpp kernel: [    1.637455] imx6q-pcie 33800000.pcie: Looking up epdev_on-supply property in node /soc@0/pcie@33800000 failed
2023-09-11T11:31:54.517933+00:00 meshgw-bbgpp kernel: [    1.637543] imx6q-pcie 33800000.pcie: supply epdev_on not found, using dummy regulator
2023-09-11T11:31:54.517927+00:00 meshgw-bbgpp systemd-udevd[289]: Using default interface naming scheme 'v250'.
2023-09-11T11:31:54.517936+00:00 meshgw-bbgpp kernel: [    1.637590] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 38, base_baud = 5000000) is a IMX
2023-09-11T11:31:54.517938+00:00 meshgw-bbgpp kernel: [    1.645824] imx6q-pcie 33800000.pcie: Looking up vpcie-supply from device tree
2023-09-11T11:31:54.517940+00:00 meshgw-bbgpp kernel: [    1.654275] imx6q-pcie 33800000.pcie: Looking up vpcie-supply property in node /soc@0/pcie@33800000 failed
2023-09-11T11:31:54.517941+00:00 meshgw-bbgpp systemd-udevd[285]: Using default interface naming scheme 'v250'.
2023-09-11T11:31:54.517950+00:00 meshgw-bbgpp kernel: [    1.654319] imx6q-pcie 33800000.pcie: Looking up vph-supply from device tree
2023-09-11T11:31:54.517953+00:00 meshgw-bbgpp kernel: [    1.654327] imx6q-pcie 33800000.pcie: Looking up vph-supply property in node /soc@0/pcie@33800000 failed
2023-09-11T11:31:54.517956+00:00 meshgw-bbgpp kernel: [    1.654373] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!.
2023-09-11T11:31:54.517959+00:00 meshgw-bbgpp kernel: [    1.656614] fec 30be0000.ethernet: Looking up phy-supply from device tree
2023-09-11T11:31:54.517962+00:00 meshgw-bbgpp kernel: [    1.659993] fec 30be0000.ethernet: Looking up phy-supply property in node /soc@0/bus@30800000/ethernet@30be0000 failed

I see that they are mostly initialized later successfully. For example, vmmc-supply fails at 1.1s but succeeds at 1.8s.
I don't have these issues on zeus, this is kirkstone.

Full log:
syslog-kirkstone-boot-errors.log

Device tree:
sb-iotgimx8-kirkstone.dts.txt

Missing bt-start recipe.

I am working on rel_imx_5.4.24_2.1.0-dev branch.

$ time bitbake -k fsl-image-qt5-validation-imx
Parsing recipes: 100% |################################################################| Time: 0:00:22
Parsing of 3215 .bb files complete (0 cached, 3215 parsed). 4673 targets, 247 skipped, 2 masked, 0 err
ors.
ERROR: No recipes available for:
  /home/marcin/compulab/sources/meta-bsp-imx8mm/recipes-bsp/bt-start/bt-start_%.bbappend

Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Build continues after disabling the bbappend file.

uboot 2021.04 hangs on IOT-GATE-IMX8

Hello, i did a yocto build with dunfell and meta-bsp-imx8mm at tag revision "iot-gate-imx8_r3.0". I flashed it on a iot-gate-imx8 devkit but the resulting u-boot (imx-boot) hangs during initialization.
In order to let it work I had to revert the patch "0103-Revert-legacy-changes.patch" and then everything started correctly.
Is this expected? Am I missing something?
Thanks
Carmelo

Kernel hangs after sdma firmware load

Hi,

Im noticing this behaviour while trying your BSP

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.4.24-iot-gate-imx8-2.2+gbabac008e5cf (oe-user@oe-host) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Thu Oct 1 17:15:08 UTC 2020
[    0.000000] Machine model: CompuLab SB-IOTGIMX8 board + CAN bus extension
[    0.000000] earlycon: ec_imx6q0 at MMIO 0x0000000030880000 (options '115200')
[    0.000000] printk: bootconsole [ec_imx6q0] enabled
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] OF: reserved mem: node linux,cma compatible matching fail
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbfbcfa40-0xbfbd0fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA32    [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 24 pages/cpu s58840 r8192 d31272 u98304
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc2,115200 earlycon=ec_imx6q,0x30880000,115200 root=/dev/sda2 rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 2032760K/2097152K available (14524K kernel code, 1180K rwdata, 4488K rodata, 2560K init, 999K bss, 64392K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from start_kernel+0x2b8/0x44c with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns
[    0.008416] Console: colour dummy device 80x25
[    0.012569] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.022845] pid_max: default: 32768 minimum: 301
[    0.027541] LSM: Security Framework initializing
[    0.032164] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.039562] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.071500] ASID allocator initialised with 32768 entries
[    0.079493] rcu: Hierarchical SRCU implementation.
[    0.088170] EFI services will not be available.
[    0.095518] smp: Bringing up secondary CPUs ...
[    0.127647] Detected VIPT I-cache on CPU1
[    0.127671] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.127703] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.159674] Detected VIPT I-cache on CPU2
[    0.159691] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.159710] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.191720] Detected VIPT I-cache on CPU3
[    0.191735] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.191752] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.191803] smp: Brought up 1 node, 4 CPUs
[    0.245555] SMP: Total of 4 processors activated.
[    0.250277] CPU features: detected: 32-bit EL0 Support
[    0.255448] CPU features: detected: CRC32 instructions
[    0.266876] CPU: All CPU(s) started at EL2
[    0.268129] alternatives: patching kernel code
[    0.273950] devtmpfs: initialized
[    0.281276] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.288216] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.295404] pinctrl core: initialized pinctrl subsystem
[    0.300947] DMI not present or invalid.
[    0.304430] NET: Registered protocol family 16
[    0.309026] DMA: preallocated 256 KiB pool for atomic allocations
[    0.314821] audit: initializing netlink subsys (disabled)
[    0.320360] audit: type=2000 audit(0.272:1): state=initialized audit_enabled=0 res=1
[    0.328045] cpuidle: using governor menu
[    0.332372] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.339450] Serial: AMBA PL011 UART driver
[    0.342955] imx mu driver is registered.
[    0.346845] imx rpmsg driver is registered.
[    0.354960] imx8mm-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.377823] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.381707] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.388437] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.395173] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.403417] cryptd: max_cpu_qlen set to 1000
[    0.411202] ACPI: Interpreter disabled.
[    0.413487] iommu: Default domain type: Translated 
[    0.417208] vgaarb: loaded
[    0.420054] SCSI subsystem initialized
[    0.423842] usbcore: registered new interface driver usbfs
[    0.429353] usbcore: registered new interface driver hub
[    0.434486] usbcore: registered new device driver usb
[    0.440579] mc: Linux media interface: v0.10
[    0.443808] videodev: Linux video capture interface: v2.00
[    0.449314] pps_core: LinuxPPS API ver. 1 registered
[    0.454274] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[    0.463469] PTP clock support registered
[    0.467530] EDAC MC: Ver: 3.0.0
[    0.471244] No BMan portals available!
[    0.474510] QMan: Allocated lookup table at (____ptrval____), entry count 65537
[    0.481893] No QMan portals available!
[    0.485755] No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree
[    0.491744] FPGA manager framework
[    0.495235] Bluetooth: Core ver 2.22
[    0.498485] NET: Registered protocol family 31
[    0.502924] Bluetooth: HCI device and connection manager initialized
[    0.509316] Bluetooth: HCI socket layer initialized
[    0.514213] Bluetooth: L2CAP socket layer initialized
[    0.519295] Bluetooth: SCO socket layer initialized
[    0.524795] clocksource: Switched to clocksource arch_sys_counter
[    0.530479] VFS: Disk quotas dquot_6.6.0
[    0.534298] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.541316] pnp: PnP ACPI: disabled
[    0.549707] thermal_sys: Registered thermal governor 'step_wise'
[    0.549986] NET: Registered protocol family 2
[    0.557828] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    0.566150] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.574179] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.581646] TCP: Hash tables configured (established 16384 bind 16384)
[    0.588058] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.594763] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.602035] NET: Registered protocol family 1
[    0.606630] RPC: Registered named UNIX socket transport module.
[    0.612230] RPC: Registered udp transport module.
[    0.616947] RPC: Registered tcp transport module.
[    0.621672] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.628152] PCI: CLS 0 bytes, default 64
[    0.632715] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    0.640198] kvm [1]: IPA Size Limit: 40bits
[    0.644516] kvm [1]: GICv3: no GICV resource entry
[    0.648891] kvm [1]: disabling GICv2 emulation
[    0.653359] kvm [1]: GIC system register CPU interface enabled
[    0.659265] kvm [1]: vgic interrupt IRQ1
[    0.663240] kvm [1]: Hyp mode initialized successfully
[    0.673534] Initialise system trusted keyrings
[    0.675245] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    0.686725] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.690281] NFS: Registering the id_resolver key type
[    0.694825] Key type id_resolver registered
[    0.698999] Key type id_legacy registered
[    0.703029] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.709775] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.716234] 9p: Installing v9fs 9p2000 file system support
[    0.734780] Key type asymmetric registered
[    0.736022] Asymmetric key parser 'x509' registered
[    0.740956] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.748367] io scheduler mq-deadline registered
[    0.752914] io scheduler kyber registered
[    0.760241] EINJ: ACPI disabled.
[    0.766928] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.773196] mxs-dma 33000000.dma-controller: initialized
[    0.774586] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin

I tried to apply custom patches. It did not work.

Regards,
Etienne

U-boot build with https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8-r3.2.1/Documentation/imx_boot_image_build.md

I have tried to build bootloader as described in r3.2 referred from compulab wiki page but it failed due to patches incompatibility:

git -C imx-atf am ${LAYER_DIR}/recipes-bsp/imx-atf/compulab/imx8mm/*.patch
}
Applying: imx8mm: Assign RDC_PDAP_UART4 to D0
Applying: iot-gate-imx8: RDC: Remove UART2 D0 restrictions
Applying: imx8mm: Set BL2_BASE to the upper egde of the 1G
Applying: imx8mm: RDC: Remove UART1 D0 restrictions
Applying: imx8mm: Set IMX_BOOT_UART_BASE for CompuLab boards
error: patch failed: plat/imx/imx8m/imx8mm/platform.mk:62
error: plat/imx/imx8m/imx8mm/platform.mk: patch does not apply
Patch failed at 0005 imx8mm: Set IMX_BOOT_UART_BASE for CompuLab boards
hint: Use 'git am --show-current-patch=diff' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Bootloader update procedure for r3.2 referred from Compulab wiki page misses the boot0 (or simmilar) string in Flashing section

dd if=${RESULTS}/flash.bin of=/dev/ bs=1K seek=33 status=progress

README.md is wrong on rel_imx_5.4.24_2.1.0-dev branch

The readme.md suggests that both mcm-imx8m-mini and ucm-imx8m-mini dev kits are supported. However paragraph 1.2 Download CompuLab meta layer suggests to clone meta-bsp-imx8mm on a tag rather than this branch:
/git clone -b rel_imx_5.4.24_2.1.0-1.0 https://github.com/compulab-yokneam/meta-bsp-imx8mm.git sources/meta-bsp-imx8mm/
Yocto build fails for ucm-imx8m-mini fails since tag rel_imx_5.4.24_2.1.0-1.0 clearly does not support ucm-imx8m-mini as written in its README.md. Cloning with rel_imx_5.4.24_2.1.0-dev works.
Please fix.