Other questions are similar, but do not provide a clear answer to my issue. The hardware and OS installation are new. I am following the setup instructions found at
and I completed the steps through First time configuration. I added the target machine and EULA to local.conf
MACHINE = “verdin-imx8mp”
ACCEPT_FSL_EULA = “1”
using:
bitbake core-image-minimal
is successful.
using:
bitbake tdx-reference-minimal-image
fails with ERROR: Nothing PROVIDES ‘tdx-reference-minimal-image’.
Checked spelling of the target. I have not changed or added any other .bb files.
Yes I am new to Yocto and bitbake, but have worked on other build systems. But the instructions should assume precisely that.
SO please provide suggestions for how to track down the root cause.
THANKS FOR YOUR HELP.
ed
(PS weird there is no tag for bitbake or build and UI does not allow them to be added but does allow bitbak)
Can you please share with us the exact commands you ran on your setup? The repo init and repo sync should be enough to download all sources, along with the sources the tdx-reference-minal-image recipe should be downloaded too.
Can you please create a new folder and try to run these commands again?
You also can check if the recipe is available on the layers folder by running the following command:
$ cd layers/
$ find . -name "*tdx-reference-minimal-image*"
./meta-toradex-demos/recipes-images/images/tdx-reference-minimal-image.bb
Running the find, I get the exact same result as you posted.
Rerunning the repo commands now.
Getting some warnings on the sync:
Fetching: 7% (1/13) bitbake.gitb’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
edprochak@DevX:~$ mkdir testing
edprochak@DevX:~$ cd testing
edprochak@DevX:~/testing$ mkdir oe-core
edprochak@DevX:~/testing$ cd oe-core
edprochak@DevX:~/testing/oe-core$ repo init -u Index of /toradex-manifest.git -b dunfell-5.x.y -m tdxref/default.xml
Downloading Repo source from git-repo - Git at Google
Downloading manifest from Index of /toradex-manifest.git
Your identity is: Ed Prochak edprochak@gmail.com
If you want to change this, please re-run ‘repo init’ with --config-name
repo has been initialized in /home/edprochak/testing/oe-core
edprochak@DevX:~/testing/oe-core$ repo sync
Fetching: 0% (0/13) warming upb’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
Fetching: 7% (1/13) bitbake.gitb’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
Fetching: 38% (5/13) meta-openembedded.gitb’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
Fetching: 69% (9/13) meta-toradex-distro.gitb’curl: (1) Protocol “https” not supported or disabled in libcurl\n’
Fetching: 100% (13/13), done in 3m19.278s
Garbage collecting: 100% (13/13), done in 0.108s
Checking out: 100% (13/13), done in 0.788s
repo sync has finished successfully.
dprochak@DevCellX:~/testing/oe-core$ . export
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.
You had no conf/bblayers.conf file. This configuration file has therefore been
created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.
The Yocto Project has extensive documentation about OE including a reference
manual which can be found at: https://docs.yoctoproject.org
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support
You can also run generated qemu images with a command like ‘runqemu qemux86’.
Other commonly useful commands are:
‘devtool’ and ‘recipetool’ handle common recipe tasks
‘bitbake-layers’ handles common layer tasks
‘oe-pkgdata-util’ handles common target package tasks
Toradex targets are:
tdx-reference-minimal-image
tdx-reference-multimedia-image
other (unsupported) targets may be found in
meta-toradex-demos/recipes-images/images/
A sample conf/local.conf file has been created
Check and edit the file to adapt to your local needs
The following likely need your attention:
DL_DIR
edprochak@DevX:~/testing/oe-core/build$
The DL_DIR message is new (did not get that the first time).
Since the DL_DIR message is new, did you try to execute the bitbake again? Are you facing the same issue?
It’s strange, can you please try to solve the b’curl: (1) Protocol “https” not supported or disabled in libcurl\n’ error by following the instructions on this question? After this, please rerun the repo commands again.
edprochak@DevX:~/testing/oe-core$ curl --version |grep Protocols
Protocols: dict file ftp gopher http imap pop3 rtsp smtp telnet tftp
which curl
/usr/local/bin/curl
When I reran the repo init and repo sync commands, they produced a clean result. I had not tried anything yet to fix the curl https problem, but I did not get the error again.
---
edprochak@DevX:~/testing/oe-core$ repo init -u https://git.toradex.com/toradex-manifest.git -b dunfell-5.x.y -m tdxref/default.xml
Your identity is: Ed Prochak <edprochak@gmail.com>
If you want to change this, please re-run 'repo init' with --config-name
repo has been initialized in /home/edprochak/testing/oe-core
edprochak@DevX:~/testing/oe-core$ repo sync
Fetching: 100% (13/13), done in 5.928s
Garbage collecting: 100% (13/13), done in 0.028s
repo sync has finished successfully.
edprochak@DevX:~/testing/oe-core$
---
(That is concerning that the same commands yield different results. My software is for a medical device and a consistent/repeatable build process is critical for certification!)
Ed, that bit about curl not supporting https is interesting. One would think that the ubuntu 20.04 install would install a libcurl with support for https. Did you build that curl on there or just install via sudo apt-get install curl?
Also, this looks like development environment issue really. You might want to try building inside a docker container:
Is there some other version of yocto on that machine somewhere?
Thanks for your assistance.
I posted my new notes back to the support page.
I have some feedback from my coworker about our particular build that I need to focus on today.
I will try to test this all again on Monday. Have a good weekend.
Ed
I have been following the instruction from Toradex, but they did not specify installing curl. I followed instructions from linux-tutorials/install-curl-ubuntu-16-04/
I realize now that that happened due to outdated instruction that our build environment was still running on ubuntu 16! I think I’ll run the apt-get for the latest curl.
I may have to investigate containers.
There should be only one copy of the yocto project software. This machine is a clean system. When I switched to Ubuntu 20, I did not update. I reinstalled the OS, erasing the old version and any software with it.
I thought I would let you know that I have to focus on our development software. So I will not be able to investigate this issue more at this time. Thanks a lot for your help and support. I will let you know when I get back to this because I think it is an important issue to resolve.
Well, thanks for all the support but this problem turned out to be an ID ten T error, copy/paste produced this command
bitbake tdx-reference-minimal-image<200b><200b><200b><200b><200b><200b><200b>
Found in an editor working on a copy of the command history. The trailing binary characters become part of the name.
