adlink / meta-adlink-nxp Goto Github PK

I have build core-image-mininal succesfully . However it is not possible to save variable from U-BOOT
When i try "saveenv" i have this message :

Environment size: 2331/4092 bytes u-boot=> saveenv Saving Environment to MMC... Writing to MMC(2)... MMC: block number 0x2008 exceeds max(0x2000) failed Failed (1)

How to solve this issue ?

Are there plans to support more recent Yocto versions?

whenever i try to run this command error is occured
repo init -u https://github.com/ADLINK/adlink-manifest -b lec-imx-yocto-hardknott -m adlink-lec-imx8mp-yocto-hardknott_1v5.xml

this error occur ;-
error: Cannot checkout meta-imx: ManifestInvalidRevisionError: revision refs/tags/rel_imx_5.4.70_2.3.0 in meta-imx not found
error: in sync: revision refs/tags/rel_imx_5.4.70_2.3.0 in meta-imx not found

please provide the updated .xml for hardknott

I'm using python 3.10.8 and after setting up the Hardknott branch I'm getting errors building.

$ bitbake core-image-minimal
Traceback (most recent call last):
  File "/home/myuser/adlink-bsp/sources/poky/bitbake/bin/bitbake", line 19, in <module>
    import bb
  File "/home/myuser/adlink-bsp/sources/poky/bitbake/lib/bb/__init__.py", line 128, in <module>
    from bb import fetch2 as fetch
  File "/home/myuser/adlink-bsp/sources/poky/bitbake/lib/bb/fetch2/__init__.py", line 26, in <module>
    import bb.persist_data, bb.utils
  File "/home/myuser/adlink-bsp/sources/poky/bitbake/lib/bb/persist_data.py", line 22, in <module>
    from collections import Mapping
ImportError: cannot import name 'Mapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py)

Updating poky to the latest commit on the hardknott-3.3.6 branch and meta-virtualization to its hardknott branch solved this issue.

When I build the u-boot-imx recipe from the Kirkstone branch I get the following warning:

WARNING: u-boot-imx-2022.04-r0 do_patch: Fuzz detected:

Applying patch 0002-u-boot-modify-Kconfig-Makefile-to-build-lec-imx8mp.patch

When trying to use devtool (devtool modify u-boot-imx) this also fails - is this related to the problematic patches?

Where is adlink-imx-setup-release.sh supposed to come from?

Hi,

I adapted the documentation provided in the repo to build a Kirkstone image for the IMX8MP and I get an error during the build. I kept the source with no modifications in hopes to have a build that passes successfully before starting to tweak around.

The bitbake imx-image-multimedia commands starts building the image, and return after this error:

ERROR: Task (/home/pepinhen/mol-from-adlink-repo/vetscan-mol-instrument/sources/poky/meta/recipes-devtools/libtool/libtool-native_2.4.7.bb:do_install) failed with exit code '1'

Please note that I've attached the log of the failing recipe to the message.

Here are the commands I ran starting from an empty folder:

$ repo init -u https://github.com/ADLINK/adlink-manifest -b lec-imx-yocto-kirkstone -m adlink-lec-imx8mp-yocto-kirkstone_1v0.xml
$ repo sync
$ MACHINE=lec-imx8mp DISTRO=fsl-imx-wayland source adlink-imx-setup-release.sh -b build
$ bitbake imx-image-multimedia

Does anyone reported this error already and have you got anyone knowing how to fix it?

Nico.

log.do_install.571078.txt

Hello,
I tried the Yocto Hardknott BSP on a lec-imx8mp SMARC module from adlink on a LEC-BASE-R1 board.
When an ethernet cable is connected to the board the link is never shown as up, ethtool reports link down.
By reading the Basic Mode Status Register (using phytool) of the PHY, instead is possible to notice that the link status is reported correctly, and on the other side of the cable the PC reports again correctly the negotiation and the link status.

By using the Zeus BSP on the same hardware everything works flawlessly.

Hello,

first of all, thank you for the layers.
I have a couple of questions though.

I am building a custom headless image (no ui, only console) based on kirkstone.
When i bind meta-adlink-nxp, i am forced to use adlink-demo because of LAYERDEPENDS_adlink-nxp = "adlink-demo" which does not look right to me as i don't want to download any additional dependencies.
As far as i understood, the demo-layer brings some default functionality, additional settings, UI and so on.

• Why does the meta-adlink-nxp depend on meta-adlink-demo?
• How can i disable/exclude it in my build?

Are there any plans to support the Kirkstone release?