Please, try this: https://github.com/ZoranStojsavljevic/bbb-yocto/blob/master/bbb-releases/bbb-dunfell/local.conf This is the systemd addendum in my BBB Dunfell local.conf : ## Add systemd service DIS

#systemd #yocto #linux

what all functionality are you looking for. E.g. there is date utility and hwclock utility which can help you manipulate system time. you could also look into ntpd and/or chrony for Network time setti

#systemd #yocto #linux

Currently not using system as our default init system (investigating why but this might not be an option). Is there any other utility I might use under Yocto to get similar data as that produced by ti

#systemd #yocto #linux

Is there documentation on how to set this up ?

#systemd #yocto #linux

Hi Steve, It comes with systemd. Use it as your init system and then you'll have the command. Quentin

#systemd #yocto #linux

I currently have "ntpq" building and installing correctly... Can someone tell me what it takes to get the "timedatectl" command utility built into Yocto kernel image ? I see it referenced in both : op

#systemd #yocto #linux

I am trying to build an image with the following command line utilities built in: ntpq, timedatectl, and ntpstat. Note : ntp is builtinto my image and working correctly. I performed a simple test usin

#systemd #yocto #linux

closed you can get is qemuarm64, you can also use package management in image and install/update/remove individual packages. something like https://imxdev.gitlab.io/tutorial/How_to_apt-get_to_the_Yoct

#linux #devtool #yocto

Hello! Generally speaking, at the point when we get to working with boards we are needing to interact with the outside world so we have to run on the target hardware. Once U-Boot (or equivalent) is up

#linux #devtool #yocto

Hi, Actually I'm working on the DART-IMX8M board. I can able to build the image in linux machine and run it on the board. But for every build, i have to run the image on board. I have checked on the q

#linux #devtool #yocto

Hi all, I'm using Yocto warrior building a system based on NIVIDA tegra TX2i. My tree is using an external toolchain, gcc linaro 7.2.1 (specified through EXTERNAL_TOOLCHAIN variable in local.conf). I'

#yocto #toolchain #linux

Hi Sheng Leong, Start from a core-image-minimal and add packages manually. Only the packages that are specified to be installed explicitly in your image recipe and the packages specified in RDEPENDS a

#linux #yocto #cups #hplip

Hi, Does anyone here know how to disable specific default recipe (e.g. CUPS and HPLIP) to be included in Yocto image? Thanks Sheng Leong

#linux #yocto #cups #hplip

I think you could start by defining new tune files for this look into meta/conf/machine/include/riscv/arch-riscv.inc and also tune-riscv.inc to understand the underlying mechanism, we currently have l

#devtool #linux #toolchain #yocto

Howdy! Am Di., 28. Juli 2020 um 07:09 Uhr schrieb <andymishra97@...>: Patching the cross toolchain should be the last resort. First, you should create a MACHINE definition that suits your needs

#devtool #linux #toolchain #yocto

Hi, I am trying to build a yocto demo-coreip-cli image for my custom RISC-V SOC which only supports imafd instructions. For the compilation of cross toolchain that is used by Bitbake, I tried changing

#devtool #linux #toolchain #yocto

Hello Martin and Josef, I will try to include the patch in a append-recipe... Thanks a lot for your help, Bernd

#linux #qemu #yocto

What I did was, ran the following command to see what all gets installed.. bitbake <image> -e |grep -v ^# |grep "^DISTRO_FEATURES=\|^IMAGE_FEATURES=" Then used DISTRO_FEATURES_remove in the local.conf

#linux #yocto

What I did was. I ran the following: bitbake <image> -e |grep -v ^# |grep "^DISTRO_FEATURES=\|^IMAGE_FEATURES=" Then used DISTRO_FEATURES_remove in local.conf to remove the unwanted packages. -=Srijan

#linux #yocto

You can backport https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=2cca75155baec8358939e2aae822e256bed4cfe0

#linux #qemu #yocto