• Product Forums
• Software Forums
• Topics
• Ideas
• Blog
• NXP.COM

Followed the steps as in "i.MX Yocto Project User's Guide" Rev. LF5.15.52_2.1.0 dated 30 September 2022.

Environment: Windows 10, WSL 2, Ubuntu 22.04LTS.

Manifest and configuration details are here:

repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-kirkstone -m imx-5.15.52-2.1.0.xml
DISTRO=fsl-imx-wayland MACHINE=imx6ulevk source imx-setup-release.sh -b build

Error message extract is here:

ERROR: Unable to start bitbake server (None)
ERROR: Server log for this session (/mnt/d/yoctolab/imx-yocto-bsp/build/bitbake-cookerdaemon.log):
10012 13:20:08.583454 --- Starting bitbake server pid 10012 at 2023-01-07 13:20:08.583425 ---
/usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat
Traceback (most recent call last):
File "/mnt/d/yoctolab/imx-yocto-bsp/sources/poky/bitbake/bin/bitbake-server", line 52, in <module>
bb.server.process.execServer(lockfd, readypipeinfd, lockname, sockname, timeout, xmlrpcinterface)
File "/mnt/d/yoctolab/imx-yocto-bsp/sources/poky/bitbake/lib/bb/server/process.py", line 541, in execServer
sock.bind(os.path.basename(sockname))
OSError: [Errno 95] Operation not supported
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name='/mnt/d/yoctolab/imx-yocto-bsp/build/bitbake-cookerdaemon.log' mode='a+' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=3 mode='w' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed <socket.socket fd=6, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0>

File "/mnt/d/yoctolab/imx-yocto-bsp/sources/poky/bitbake/lib/bb/server/process.py", line 541, in execServer
sock.bind(os.path.basename(sockname))
OSError: [Errno 95] Operation not supported
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name='/mnt/d/yoctolab/imx-yocto-bsp/build/bitbake-cookerdaemon.log' mode='a+' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name=3 mode='w' encoding='UTF-8'>
sys:1: ResourceWarning: unclosed <socket.socket fd=6, family=AddressFamily.AF_UNIX, type=SocketKind.SOCK_STREAM, proto=0

Any help?

Sorry to interrupt in middle of conversation. Instead of any reply, I have questions like this is the error below when I used dunfell branch and tried to build the core-image-minimal:
Error is like "ERROR: Task (/home/dexter/yocto_training/source/poky/meta/recipes-devtools/gcc/gcc-cross_12.2.bb:do_compile) failed with exit code '1'"

I am using Ubuntu 22.04 LTS, I was unable to solve this error.

Then again I tried to build same image but this time I used mickledore branch of poky but it throws same error for different package:

ERROR: python3-native-3.11.2-r0 do_compile: oe_runmake failed
ERROR: python3-native-3.11.2-r0 do_compile: ExecutionError('/home/dexter/yocto_training/build/tmp/work/x86_64-linux/python3-native/3.11.2-r0/temp/run.do_compile.1591917', 1, None, None)

I have spent two days searching this. I am getting no results as well as no solution. Can anyone guide me on this? Thanks in advance.

Hi @dexter_flash

I completed the assignment for which I raised this issue and moved on with 20 LTS as I could not resolve the issue completely. Also, I now removed the virtual box and build setup. Given below might help you.

1. "IMXLXYOCTOUG - i.MX Yocto Project User's Guide - Rev. LF6.1.1_1.0.0 — 31 March 2023", states it is compatible with Yocto Release Longdale - 4.1"

"Release LF6.1.1_1.0.0 is released for Yocto Project 4.1 (Langdale)."

2. Given below are Yocto releases:

Mickledore - 4.2 - Support for 7 months (until October 2023)
Langdale - 4.1 - Support until May 2023
Kirkstone - 4.0 - LTS
Dunfell - 3.1 - LTS

I suggest trying Langdale with Ubuntu 22 LTS.

Cheers

@edwardtyrrell @Sanket_Parekh

I think it is better to wait for NXP Official release for Ubuntu 22.04LTS.

"i.MX Yocto Project User's Guide" Rev. LF5.15.52_2.1.0 dated 30 September 2022 is for Ubuntu 20.04LTS.

There were problems in installing following packages in UIbuntu 22.04LTS. I tried installing one by one and these got resolved in different ways.
texinfo pzstd lz4c python

But binutils and the error log is attached here.

I installed Ubuntu 20.04LTS also. Would keep you posted if there is any updates.

Thank you.

Hi @edwardtyrrell

Thank you for the quick response.

I did "repo init".

I tried it again now to verify it. I am getting same error. Is it related to Ubuntu 22.04LTS or python "imp"?

"DeprecationWarning: the imp module is deprecated in favour of importlib"

This looks like Ubuntu 22.04LTS or python related issue?

Hi @edwardtyrrell

Thanks again for quick response.

I did "repo sync" actually. It was typo in my response that I mentioned "init". Sorry about that.

Please see the screen capture / log extract below. I attached entire log in text file here.

thirumaal@DESKTOP-E216GCK:/mnt/d/yoctolab/imx-yocto-bsp$ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-kirkstone -m imx-5.15.52-2.1.0.xml
repo: reusing existing repo client checkout in /mnt/d/yoctolab/imx-yocto-bsp

repo has been initialized in /mnt/d/yoctolab/imx-yocto-bsp
thirumaal@DESKTOP-E216GCK:/mnt/d/yoctolab/imx-yocto-bsp$ repo sync
remote: Enumerating objects: 1054, done.
remote: Counting objects: 100% (390/390), done.
remote: Compressing objects: 100% (66/66), done.
remote: Total 1054 (delta 325), reused 386 (delta 322), pack-reused 664
Fetching: 100% (14/14), done in 4m59.622s
.repo/repo: project not found in manifest.
Updating files: 100% (194/194), done.
Updating files: 100% (509/509), done.
Updating files: 100% (531/531), done.
Updating files: 100% (6010/6010), done.
Updating files: 100% (424/424), done.
Updating files: 100% (5330/5330), done.
Checking out: 100% (13/13), done in 1m26.658s
repo sync has finished successfully.
thirumaal@DESKTOP-E216GCK:/mnt/d/yoctolab/imx-yocto-bsp$ repo sync
Fetching: 100% (13/13), done in 13.603s
Checking out: 100% (13/13), done in 3.511s
repo sync has finished successfully.
thirumaal@DESKTOP-E216GCK:/mnt/d/yoctolab/imx-yocto-bsp$ ls -al
total 0
drwxrwxrwx 1 thirumaal thirumaal 4096 Jan 10 16:42 .
drwxrwxrwx 1 thirumaal thirumaal 4096 Jan 10 14:02 ..
drwxrwxrwx 1 thirumaal thirumaal 4096 Jan 10 16:42 .repo
lrwxrwxrwx 1 thirumaal thirumaal 19 Jan 10 16:42 README -> sources/base/README
lrwxrwxrwx 1 thirumaal thirumaal 23 Jan 10 16:42 README-IMXBSP -> sources/meta-imx/README
lrwxrwxrwx 1 thirumaal thirumaal 43 Jan 10 16:42 imx-setup-release.sh -> sources/meta-imx/tools/imx-setup-release.sh
lrwxrwxrwx 1 thirumaal thirumaal 30 Jan 10 16:42 setup-environment -> sources/base/setup-environment
drwxrwxrwx 1 thirumaal thirumaal 4096 Jan 10 16:43 sources
thirumaal@DESKTOP-E216GCK:/mnt/d/yoctolab/imx-yocto-bsp$ DISTRO=fsl-imx-wayland MACHINE=imx6ulevk source imx-setup-release.sh -b build
...

... License agreement text

...

Your build environment has been configured with:

MACHINE=imx6ulevk
SDKMACHINE=i686
DISTRO=fsl-imx-wayland
EULA=
BSPDIR=
BUILD_DIR=.
meta-freescale directory found
thirumaal@DESKTOP-E216GCK:/mnt/d/yoctolab/imx-yocto-bsp/build$ bitbake core-image-base
ERROR: Unable to start bitbake server (None)
ERROR: Server log for this session (/mnt/d/yoctolab/imx-yocto-bsp/build/bitbake-cookerdaemon.log):
22336 16:46:51.252406 --- Starting bitbake server pid 22336 at 2023-01-10 16:46:51.252379 ---
Traceback (most recent call last):

Hi @arunachalamram ,

It's looking a bit better but I tend to agree with you here regarding your OS or Python version.

I tried it again now to verify it. I am getting same error. Is it related to Ubuntu 22.04LTS or python "imp"?

"DeprecationWarning: the imp module is deprecated in favour of importlib"

This looks like Ubuntu 22.04LTS or python related issue?

I've used Yocto professionally for the last 9 years and I've learnt that there are sometimes problems like yours that happen and often it was down to mismatches in the versions of Python, the OS it was building on, plus Yocto is always moving forward and what it uses to build changes. Various headaches can be caused by using VMs too. The Yocto build system is heavily reliant on Python.

If I have a problem like yours and after messing around with it for sometime, it's not a bad thing to delete it and the repo and start again. Nothing was built anyway so no loss.  Also, going back to my previous comment in the past I've had to try the following things:

1) Roll back the building OS version (your doc says Ubuntu 20.04 and later, you could try 20.04)

2) Try another version of Yocto - in your case that would be Honister or Hardknott. Each time start fresh.

If one or both of these approaches work in building a release, it gives you a starting point and a feel how Yocto works (if this is your first attempt). Then you can go back armed with some knowledge and look deeper into this specific issue. Apart from that there's not a lot else I can suggest remotely.

Cheers.

Hi @edwardtyrrell

It works in a different way.

I tried to build from /mnt/d/... and error given below was thrown initially:

/usr/lib/python3/dist-packages/apport/report.py:13: DeprecationWarning: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12; see the module's documentation for alternative uses
import fnmatch, glob, traceback, errno, sys, atexit, locale, imp, stat

Then I tried poky build from directory created in ubuntu home and then got following error:

$ bitbake core-image-minimal
ERROR: OE-core's config sanity checker detected a potential misconfiguration.
Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
Following is the list of potential problems / advisories:

Your system needs to support the en_US.UTF-8 locale.

Solution for this issue is here:

https://askubuntu.com/questions/162391/how-do-i-fix-my-locale-issue

poky and imx build work from home directory (/mnt/c/...).

But build does not work still from /mnt/d/... : this stands unresolved.

I dont have much space in C drive. Anyway, I could build now.

Btw, thanks for recommending a workstation - I used Xeon for building in the past for building I understand it. I am freelancer. I would go with what I have for the time being.

Hi @arunachalamram ,

Progress! Well done. Always good using a dedicated Linux work station with Embedded Linux much easier to download, debug and build, everything. Keep in mind once you have succeeded with your build you can do a bitbake <image> -c populate_sdk and that will produce an installable SDK for out-of-tree cross compiling complete with everything you need. Compiling using the SDK will ensure that you're building against your actual build's source, kernel, libs etc.

Cheers.

Hi @arunachalamram ,

Looks like you may have missed a step or two.. The document you suggested stated this process:

repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-kirkstone -m imx-5.15.52-2.1.0.xml

repo sync   <= Here. This will sync everything up with the repo ready for a build

DISTRO=fsl-imx-wayland MACHINE=imx6ulevk source imx-setup-release.sh -b build

(Following the last command you should automatically be in the build directory)

Bitbake core-image-base   // build you image..

Once you have done your initial build the next time it's just a matter of:

// In your build's root directory

source setup-environment build   (or similar, there will be some sort of 'setup-environment file in there)

bitbake <image>

Hope this helps.