By default, Torizon OS comes with NetworkManager and ModemManager. Also, it doesn’t have Connman:
torizon@apalis-imx8-06980209:~$ sudo tdx-info
Software summary
------------------------------------------------------------
Bootloader: U-Boot
Kernel version: 5.15.129-6.5.0+git.6f8fd49366db #1-TorizonCore SMP PREEMPT Fri Dec 22 11:15:52 UTC 2023
Kernel command line: pci=nomsi root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/d84a97a24c27b978c409f4a362d0c0c28589d246081ac1a02c48b317582ca645/0
Distro name: NAME="TorizonCore"
Distro version: VERSION_ID=6.5.0-build.8
Distro variant: VARIANT="Docker"
Hostname: apalis-imx8-06980209
------------------------------------------------------------
Hardware info
------------------------------------------------------------
HW model: Toradex Apalis iMX8QM V1.1 on Apalis Evaluation Board
Toradex version: 0037 V1.1C
Serial number: 06980209
Processor arch: aarch64
------------------------------------------------------------
torizon@apalis-imx8-06980209:~$ nmcli --version
nmcli tool, version 1.36.2
torizon@apalis-imx8-06980209:~$ mmcli --version
mmcli 1.18.8
Copyright (2011 - 2021) Aleksander Morgado
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
torizon@apalis-imx8-06980209:~$ connmanctl --version
-sh: connmanctl: command not found
So seems like you are “redoing” work with your set of IMAGE_INSTALL.
Also, about IMAGE_INSTALL on local.conf, please check Bitbake documentation. You should use CORE_IMAGE_EXTRA_INSTALL instead:
Having said that, the issue you are facing seems related to building RAC (Remote Access Client).
Could you please share the TOML configuration you are getting? According to your error log, it should be at /home/cristiang/YoctoLinux_latest/build-test/tmp/work/cortexa72-cortexa53-tdx-linux/rac/0.0+gitAUTOINC+719afe6b829316c096b3-r0/cargo_home/config.
Could you please also try building without the “rework” you are doing related to NetworkManager, ModemManager and Connman?
Now this is a pull of 6.5.0 from the repo that only has layers in local.conf that I’ve been appending for a couple of years and have worked fine.
V6.5.0 built fine for me a month or so back but now gets an error for what looks like something related to Rust and Cargo? I haven’t made any changes to networking like described in this post.
Also, this error looks strange -
Caused by:
could not parse input as TOML
Caused by:
TOML parse error at line 41, column 1
|
41 | olpc-cjson = { path = “/mnt/usb/Yocto_BSP_6.5.0_Verdin-patch/build/tmp/work/cortexa53-tdx-linux/rac/0.0+gitAUTOINC+719afe6b829316c096b3-r0/tough/olpc-cjson” }
| ^
duplicate key olpc-cjson in table patch.https://github.com/toradex/tough
I was using this: repo init -u git://git.toradex.com/toradex-manifest.git -b refs/tags/6.5.0 -m tdxref/default.xml since our project requires to have the revision constant. Will this bug fix be backported? Or must we use kirkstone-6.x.y?
It’s a bit troubling to me that an upstream change can break a stable release like this.
We’re migrating our custom project from an ancient Yocto version so I’m still learning about the new build process
In general guidelines, as you are using a quarterly release, during your development it is expected that you keep updating your OpenEmbedded layers at least with upcoming Quarterly releases. As you can see, there is no support for previous Quarterly/Monthly/Nightly releases.
Thanks for the reply, to continue building the reference image I created a custom manifest repository to pull in that compilation fix. Hopefully it builds now
As said previously, please check the Embedded Linux Support Strategy from our documentation.
If you are using BSP 6, which is active, it is expected that you keep updating your layers together with atl least our Quarterly releases.
As BSP/Torizon layers version 6.6.0 were released, previous versions of BSP 6 are not maintained anymore. So there should be no expectation to fix unmaintained versions.
Good question
The way our RAC recipe was written made it sensitive to some upstream changes (e.g. RAC’s dependencies). With this issue that happened and was fixed already, we are improving the recipe to avoid such issues in the future.
Hey, just pulled the kirkstone-6.x.y branch this morning and got the same error. Should I be specifying a different manifest in the ‘repo init’ command?
@buchmeister, strange are you sure you are on the latest commit for meta-toradex-torizon with the fix I mentioned previously?
I don’t think you need to update the entire manifest/other layers. Just updating meta-toradex-torizon should suffice as seen by other users on these forums who have successfully tested this fix.
Another idea, is perhaps you may need to also clean your build for the fix to take full effect.
