https://wiki.koansoftware.com/api.php?action=feedcontributions&feedformat=atom&user=Koan KoanSoftware Wiki - User contributions [en] 2026-05-02T13:44:46Z User contributions MediaWiki 1.39.15 https://wiki.koansoftware.com/index.php?title=BitBake%27s_passthrough_environment_variables&diff=415 BitBake's passthrough environment variables 2025-12-01T15:21:38Z <p>Koan: Created page with &quot;== BitBake&#039;s passthrough environment variables == When you need to manage custom variables in a script having an impact with Bitbake, it is possible to add custom environment variables to BitBake&#039;s passthrough mechanism. #!/bin/bash # # A script to demonstrate adding custom environment variables to BitBake&#039;s passthrough mechanism. # export CUSTOM=&quot;CustomValue&quot; export MYVAR=$CUSTOM-$USER BB_ENV_PASSTHROUGH_ADDITIONS=&quot;$BB_ENV_PASSTHROUGH_...&quot;</p> <hr /> <div>== BitBake's passthrough environment variables ==<br /> <br /> When you need to manage custom variables in a script having an impact with Bitbake,<br /> it is possible to add custom environment variables to BitBake's passthrough mechanism.<br /> <br /> #!/bin/bash<br /> #<br /> # A script to demonstrate adding custom environment variables to BitBake's passthrough mechanism.<br /> #<br /> <br /> export CUSTOM=&quot;CustomValue&quot;<br /> export MYVAR=$CUSTOM-$USER<br /> BB_ENV_PASSTHROUGH_ADDITIONS=&quot;$BB_ENV_PASSTHROUGH_ADDITIONS MYVAR&quot;<br /> bitbake -e os-release | grep ^MYVAR=<br /> <br /> Execution example<br /> <br /> $ ../bitbake-test-passthrough.sh<br /> MYVAR=&quot;custom_value-tux&quot;</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=414 Main Page 2025-12-01T15:19:08Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> * [[Optimal swap size for building with Yocto Project]]<br /> * [[Linux Network Managers and Configuration Files]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> * [[Yocto Project override operators]]<br /> * [[How to generate an initrd image with Yocto]]<br /> * [[How to verify the metalayers SHA when using Yocto]]<br /> * [[BitBake's passthrough environment variables]]<br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_verify_the_metalayers_SHA_when_using_Yocto&diff=413 How to verify the metalayers SHA when using Yocto 2025-11-19T11:12:42Z <p>Koan: </p> <hr /> <div>== How to verify the metalayers SHA when using Yocto ==<br /> <br /> When working with '''Yocto Project''', maintaining a reliable and reproducible build environment is essential. <br /> <br /> One of the simplest yet most important steps in ensuring this integrity is verifying the '''SHA''' of the '''metalayers''' you are using during the build.<br /> <br /> Whether you're synchronizing your project with upstream layers, checking for unexpected changes, or documenting the exact state of your build environment, validating the commit hashes helps guarantee consistency and traceability. <br /> <br /> Below you can find a command that can help you to point out the layers list and the respective SHA verification without starting a '''bitbake''' build.<br /> <br /> The goal of this command is to avoid to touch an existing build.<br /> <br /> bitbake --dry-run os-release<br /> <br /> Build Configuration:<br /> BB_VERSION = &quot;2.8.1&quot;<br /> BUILD_SYS = &quot;x86_64-linux&quot;<br /> NATIVELSBSTRING = &quot;universal&quot;<br /> TARGET_SYS = &quot;arm-poky-linux-gnueabi&quot;<br /> MACHINE = &quot;beaglebone&quot;<br /> DISTRO = &quot;poky&quot;<br /> DISTRO_VERSION = &quot;5.0.14&quot;<br /> TUNE_FEATURES = &quot;arm armv7a vfp thumb neon callconvention-hard&quot;<br /> TARGET_FPU = &quot;hard&quot;<br /> meta <br /> meta-poky <br /> meta-yocto-bsp = &quot;scarthgap:7e8674996b0164b07e56bc066d0fba790e627061&quot;<br /> meta-oe = &quot;scarthgap:f1f248262d662315159ee96c604f97415d1dbe6a&quot;<br /> meta-arm-toolchain <br /> meta-arm = &quot;scarthgap:a81c19915b5b9e71ed394032e9a50fd06919e1cd&quot;<br /> meta-ti-bsp <br /> meta-beagle = &quot;scarthgap:f483464c72055cdcb81853e06afc89719e73073f&quot;</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_verify_the_metalayers_SHA_when_using_Yocto&diff=412 How to verify the metalayers SHA when using Yocto 2025-11-19T11:11:15Z <p>Koan: Created page with &quot;== How to verify the metalayers SHA when using Yocto == When working with &#039;&#039;&#039;Yocto Project&#039;&#039;&#039;, maintaining a reliable and reproducible build environment is essential. One of the simplest yet most important steps in ensuring this integrity is verifying the &#039;&#039;&#039;SHA&#039;&#039;&#039; of the &#039;&#039;&#039;metalayers&#039;&#039;&#039; you are using during the build. Whether you&#039;re synchronizing your project with upstream layers, checking for unexpected changes, or documenting the exact state of your build environ...&quot;</p> <hr /> <div>== How to verify the metalayers SHA when using Yocto ==<br /> <br /> When working with '''Yocto Project''', maintaining a reliable and reproducible build environment is essential. <br /> <br /> One of the simplest yet most important steps in ensuring this integrity is verifying the '''SHA''' of the '''metalayers''' you are using during the build.<br /> <br /> Whether you're synchronizing your project with upstream layers, checking for unexpected changes, or documenting the exact state of your build environment, validating the commit hashes helps guarantee consistency and traceability. <br /> <br /> Below you can find a command that can help you to point out the layers list and the respective SHA verification without starting a '''bitbake''' build.<br /> <br /> The goal of this command is to avoid to touch an existing build.<br /> <br /> bitbake --dry-run os-release</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=411 Main Page 2025-11-19T11:04:23Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> * [[Optimal swap size for building with Yocto Project]]<br /> * [[Linux Network Managers and Configuration Files]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> * [[Yocto Project override operators]]<br /> * [[How to generate an initrd image with Yocto]]<br /> * [[How to verify the metalayers SHA when using Yocto]]<br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Linux_Network_Managers_and_Configuration_Files&diff=400 Linux Network Managers and Configuration Files 2025-06-21T13:33:30Z <p>Koan: </p> <hr /> <div>= Linux Network Managers and Configuration Files =<br /> <br /> Linux supports various network management systems, each designed for different use cases such as desktop environments, servers, or embedded systems. Below is a summary of the most commonly used network managers along with their associated configuration files.<br /> <br /> == 1. NetworkManager ==<br /> <br /> '''NetworkManager''' is a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available. It is widely used in desktop Linux distributions such as Ubuntu, Fedora, and others.<br /> <br /> * '''Service''': NetworkManager<br /> * '''CLI Tools''': nmcli, nmtui<br /> * '''Main Configuration Files''':<br /> ** /etc/NetworkManager/NetworkManager.conf – Main configuration file.<br /> ** /etc/NetworkManager/system-connections/ – Directory containing individual connection profiles.<br /> ** /var/lib/NetworkManager/ – Runtime data.<br /> <br /> === Example Connection File ===<br /> <br /> '''/etc/NetworkManager/system-connections/wired-connection.nmconnection'''<br /> <br /> [connection]<br /> id=wired-connection<br /> type=ethernet<br /> interface-name=enp0s3<br /> <br /> [ipv4]<br /> method=auto<br /> <br /> == 2. systemd-networkd ==<br /> <br /> '''systemd-networkd''' is a system service that manages networks. It detects and configures network devices as they appear and can also create virtual network devices.<br /> <br /> * '''Service''': systemd-networkd<br /> * '''CLI Tools''': networkctl, systemctl<br /> * '''Main Configuration Files''':<br /> ** /etc/systemd/network/*.network – Match and configure physical interfaces.<br /> ** /etc/systemd/network/*.netdev – Configuration for virtual devices.<br /> <br /> === Example Network File ===<br /> '''/etc/systemd/network/20-wired.network'''<br /> <br /> [Match]<br /> Name=enp0s3<br /> <br /> [Network]<br /> DHCP=yes<br /> <br /> <br /> == 3. ifupdown (traditional Debian tool) ==<br /> <br /> '''ifupdown''' is the classic network configuration tool used in older Debian and Ubuntu systems. It is gradually being replaced by newer systems like NetworkManager or systemd-networkd.<br /> <br /> * '''Service''': No dedicated service (scripts run via ifup/ifdown)<br /> * '''CLI Tools''': ifup, ifdown<br /> * '''Main Configuration File''':<br /> ** /etc/network/interfaces<br /> <br /> === Example Interfaces File ===<br /> '''/etc/network/interfaces'''<br /> <br /> auto lo<br /> iface lo inet loopback<br /> <br /> auto enp0s3<br /> iface enp0s3 inet dhcp<br /> <br /> <br /> == 4. netplan ==<br /> <br /> '''Netplan''' is a utility for configuring networking on modern Ubuntu systems (17.10 and later). It abstracts configuration and delegates to either NetworkManager or systemd-networkd.<br /> <br /> * '''Service''': Depends on backend (NetworkManager or systemd-networkd)<br /> * '''CLI Tools''': netplan apply, netplan try<br /> * '''Main Configuration Files''':<br /> ** /etc/netplan/*.yaml<br /> <br /> === Example Netplan YAML File ===<br /> '''/etc/netplan/01-netcfg.yaml'''<br /> <br /> network:<br /> version: 2<br /> ethernets:<br /> enp0s3:<br /> dhcp4: true<br /> <br /> <br /> == 5. Wicd ==<br /> <br /> '''Wicd''' is a network connection manager that aims to provide a simple interface to connect to networks. It is now '''mostly obsolete''' but may still be found on lightweight systems.<br /> <br /> * '''Service''': wicd<br /> * '''CLI Tools''': wicd-curses, wicd-cli<br /> * '''Main Coniguration Files''':<br /> ** /etc/wicd/ – Configuration directory<br /> ** /etc/wicd/wireless-settings.conf – Wireless-specific configuration<br /> ** /etc/wicd/wired-settings.conf – Wired-specific configuration<br /> <br /> <br /> == 6. ConnMan (Connection Manager) ==<br /> <br /> '''ConnMan''' is a daemon for managing internet connections within embedded devices. It is lightweight and often used in systems with limited resources.<br /> <br /> * '''Service''': connmand<br /> * '''CLI Tools''': connmanctl<br /> * '''Main Configuration Files''':<br /> ** /etc/connman/main.conf – General configuration<br /> ** /var/lib/connman/ – Profiles and saved settings<br /> <br /> === Example ConnMan Configuration ===<br /> '''/etc/connman/main.conf'''<br /> <br /> [General]<br /> PreferredTechnologies=ethernet,wifi<br /> SingleConnectedTechnology=true<br /> <br /> <br /> = Summary Table =<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Network Manager !! Main Config File(s) !! CLI Tools !! Typical Use<br /> |-<br /> | NetworkManager || /etc/NetworkManager/ || nmcli, nmtui || Desktop<br /> |-<br /> | systemd-networkd || /etc/systemd/network/ || networkctl || Server, Embedded<br /> |-<br /> | ifupdown || /etc/network/interfaces || ifup, ifdown || Legacy Debian/Ubuntu<br /> |-<br /> | netplan || /etc/netplan/*.yaml || netplan || Ubuntu (modern)<br /> |-<br /> | Wicd || /etc/wicd/ || wicd-curses, wicd-cli || Lightweight Desktop<br /> |-<br /> | ConnMan || /etc/connman/ || connmanctl || Embedded Systems<br /> |}<br /> <br /> <br /> -------------<br /> <br /> <br /> &lt;pre&gt;<br /> +--------------------+<br /> | User Interface |<br /> |--------------------|<br /> | nmcli / nmtui &lt;-- NetworkManager<br /> | networkctl &lt;-- systemd-networkd<br /> | netplan apply &lt;-- Netplan<br /> +--------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Configuration Files |<br /> |-----------------------------|<br /> | /etc/netplan/*.yaml &lt;-- Netplan<br /> | /etc/NetworkManager/*.conf &lt;-- NetworkManager<br /> | /etc/systemd/network/*.network &lt;-- systemd-networkd<br /> | /etc/network/interfaces &lt;-- ifupdown<br /> +-----------------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Network Managers (Daemons) |<br /> |-----------------------------|<br /> | NetworkManager.service<br /> | systemd-networkd.service<br /> | ifupdown (manual)<br /> | connman.service<br /> +-----------------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Kernel/Drivers |<br /> |-----------------------------|<br /> | Interface mgmt, DHCP, etc. |<br /> +-----------------------------+<br /> &lt;/pre&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=399 Main Page 2025-06-21T13:26:13Z <p>Koan: </p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> * [[Optimal swap size for building with Yocto Project]]<br /> * [[Linux Network Managers and Configuration Files]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> * [[Yocto Project override operators]]<br /> * [[How to generate an initrd image with Yocto]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Linux_Network_Managers_and_Configuration_Files&diff=398 Linux Network Managers and Configuration Files 2025-06-20T06:28:34Z <p>Koan: </p> <hr /> <div>= Linux Network Managers and Configuration Files =<br /> <br /> Linux supports various network management systems, each designed for different use cases such as desktop environments, servers, or embedded systems. Below is a summary of the most commonly used network managers along with their associated configuration files.<br /> <br /> == 1. NetworkManager ==<br /> <br /> NetworkManager is a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available. It is widely used in desktop Linux distributions such as Ubuntu, Fedora, and others.<br /> <br /> * '''Service''': `NetworkManager`<br /> * '''CLI Tools''': `nmcli`, `nmtui`<br /> * '''Main Configuration Files''':<br /> ** `/etc/NetworkManager/NetworkManager.conf` – Main configuration file.<br /> ** `/etc/NetworkManager/system-connections/` – Directory containing individual connection profiles.<br /> ** `/var/lib/NetworkManager/` – Runtime data.<br /> <br /> === Example Connection File ===<br /> `/etc/NetworkManager/system-connections/wired-connection.nmconnection`<br /> <br /> [connection]<br /> id=wired-connection<br /> type=ethernet<br /> interface-name=enp0s3<br /> <br /> [ipv4]<br /> method=auto<br /> <br /> == 2. systemd-networkd ==<br /> <br /> `systemd-networkd` is a system service that manages networks. It detects and configures network devices as they appear and can also create virtual network devices.<br /> <br /> * '''Service''': `systemd-networkd`<br /> * '''CLI Tools''': `networkctl`, `systemctl`<br /> * '''Main Configuration Files''':<br /> ** `/etc/systemd/network/*.network` – Match and configure physical interfaces.<br /> ** `/etc/systemd/network/*.netdev` – Configuration for virtual devices.<br /> <br /> === Example Network File ===<br /> `/etc/systemd/network/20-wired.network`<br /> &lt;syntaxhighlight lang=&quot;ini&quot;&gt;<br /> [Match]<br /> Name=enp0s3<br /> <br /> [Network]<br /> DHCP=yes<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == 3. ifupdown (traditional Debian tool) ==<br /> <br /> `ifupdown` is the classic network configuration tool used in older Debian and Ubuntu systems. It is gradually being replaced by newer systems like NetworkManager or `systemd-networkd`.<br /> <br /> * '''Service''': No dedicated service (scripts run via `ifup`/`ifdown`)<br /> * '''CLI Tools''': `ifup`, `ifdown`<br /> * '''Main Configuration File''':<br /> ** `/etc/network/interfaces`<br /> <br /> === Example Interfaces File ===<br /> `/etc/network/interfaces`<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> auto lo<br /> iface lo inet loopback<br /> <br /> auto enp0s3<br /> iface enp0s3 inet dhcp<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == 4. netplan ==<br /> <br /> Netplan is a utility for configuring networking on modern Ubuntu systems (17.10 and later). It abstracts configuration and delegates to either NetworkManager or `systemd-networkd`.<br /> <br /> * '''Service''': Depends on backend (NetworkManager or systemd-networkd)<br /> * '''CLI Tools''': `netplan apply`, `netplan try`<br /> * '''Main Configuration Files''':<br /> ** `/etc/netplan/*.yaml`<br /> <br /> === Example Netplan YAML File ===<br /> `/etc/netplan/01-netcfg.yaml`<br /> &lt;syntaxhighlight lang=&quot;yaml&quot;&gt;<br /> network:<br /> version: 2<br /> ethernets:<br /> enp0s3:<br /> dhcp4: true<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == 5. Wicd ==<br /> <br /> Wicd is a network connection manager that aims to provide a simple interface to connect to networks. It is now mostly obsolete but may still be found on lightweight systems.<br /> <br /> * '''Service''': `wicd`<br /> * '''CLI Tools''': `wicd-curses`, `wicd-cli`<br /> * '''Main Configuration Files''':<br /> ** `/etc/wicd/` – Configuration directory<br /> ** `/etc/wicd/wireless-settings.conf` – Wireless-specific configuration<br /> ** `/etc/wicd/wired-settings.conf` – Wired-specific configuration<br /> <br /> == 6. ConnMan (Connection Manager) ==<br /> <br /> ConnMan is a daemon for managing internet connections within embedded devices. It is lightweight and often used in systems with limited resources.<br /> <br /> * '''Service''': `connmand`<br /> * '''CLI Tools''': `connmanctl`<br /> * '''Main Configuration Files''':<br /> ** `/etc/connman/main.conf` – General configuration<br /> ** `/var/lib/connman/` – Profiles and saved settings<br /> <br /> === Example ConnMan Configuration ===<br /> `/etc/connman/main.conf`<br /> &lt;syntaxhighlight lang=&quot;ini&quot;&gt;<br /> [General]<br /> PreferredTechnologies=ethernet,wifi<br /> SingleConnectedTechnology=true<br /> &lt;/syntaxhighlight&gt;<br /> <br /> = Summary Table =<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Network Manager !! Main Config File(s) !! CLI Tools !! Typical Use<br /> |-<br /> | NetworkManager || /etc/NetworkManager/ || nmcli, nmtui || Desktop<br /> |-<br /> | systemd-networkd || /etc/systemd/network/ || networkctl || Server, Embedded<br /> |-<br /> | ifupdown || /etc/network/interfaces || ifup, ifdown || Legacy Debian/Ubuntu<br /> |-<br /> | netplan || /etc/netplan/*.yaml || netplan || Ubuntu (modern)<br /> |-<br /> | Wicd || /etc/wicd/ || wicd-curses, wicd-cli || Lightweight Desktop<br /> |-<br /> | ConnMan || /etc/connman/ || connmanctl || Embedded Systems<br /> |}<br /> <br /> <br /> -------------<br /> <br /> <br /> &lt;pre&gt;<br /> +--------------------+<br /> | User Interface |<br /> |--------------------|<br /> | nmcli / nmtui &lt;-- NetworkManager<br /> | networkctl &lt;-- systemd-networkd<br /> | netplan apply &lt;-- Netplan<br /> +--------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Configuration Files |<br /> |-----------------------------|<br /> | /etc/netplan/*.yaml &lt;-- Netplan<br /> | /etc/NetworkManager/*.conf &lt;-- NetworkManager<br /> | /etc/systemd/network/*.network &lt;-- systemd-networkd<br /> | /etc/network/interfaces &lt;-- ifupdown<br /> +-----------------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Network Managers (Daemons) |<br /> |-----------------------------|<br /> | NetworkManager.service<br /> | systemd-networkd.service<br /> | ifupdown (manual)<br /> | connman.service<br /> +-----------------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Kernel/Drivers |<br /> |-----------------------------|<br /> | Interface mgmt, DHCP, etc. |<br /> +-----------------------------+<br /> &lt;/pre&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Linux_Network_Managers_and_Configuration_Files&diff=397 Linux Network Managers and Configuration Files 2025-06-20T06:26:27Z <p>Koan: Created page with &quot;= Linux Network Managers and Configuration Files = Linux supports various network management systems, each designed for different use cases such as desktop environments, serv...&quot;</p> <hr /> <div>= Linux Network Managers and Configuration Files =<br /> <br /> Linux supports various network management systems, each designed for different use cases such as desktop environments, servers, or embedded systems. Below is a summary of the most commonly used network managers along with their associated configuration files.<br /> <br /> == 1. NetworkManager ==<br /> <br /> NetworkManager is a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available. It is widely used in desktop Linux distributions such as Ubuntu, Fedora, and others.<br /> <br /> * '''Service''': `NetworkManager`<br /> * '''CLI Tools''': `nmcli`, `nmtui`<br /> * '''Main Configuration Files''':<br /> ** `/etc/NetworkManager/NetworkManager.conf` – Main configuration file.<br /> ** `/etc/NetworkManager/system-connections/` – Directory containing individual connection profiles.<br /> ** `/var/lib/NetworkManager/` – Runtime data.<br /> <br /> === Example Connection File ===<br /> `/etc/NetworkManager/system-connections/wired-connection.nmconnection`<br /> &lt;syntaxhighlight lang=&quot;ini&quot;&gt;<br /> [connection]<br /> id=wired-connection<br /> type=ethernet<br /> interface-name=enp0s3<br /> <br /> [ipv4]<br /> method=auto<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == 2. systemd-networkd ==<br /> <br /> `systemd-networkd` is a system service that manages networks. It detects and configures network devices as they appear and can also create virtual network devices.<br /> <br /> * '''Service''': `systemd-networkd`<br /> * '''CLI Tools''': `networkctl`, `systemctl`<br /> * '''Main Configuration Files''':<br /> ** `/etc/systemd/network/*.network` – Match and configure physical interfaces.<br /> ** `/etc/systemd/network/*.netdev` – Configuration for virtual devices.<br /> <br /> === Example Network File ===<br /> `/etc/systemd/network/20-wired.network`<br /> &lt;syntaxhighlight lang=&quot;ini&quot;&gt;<br /> [Match]<br /> Name=enp0s3<br /> <br /> [Network]<br /> DHCP=yes<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == 3. ifupdown (traditional Debian tool) ==<br /> <br /> `ifupdown` is the classic network configuration tool used in older Debian and Ubuntu systems. It is gradually being replaced by newer systems like NetworkManager or `systemd-networkd`.<br /> <br /> * '''Service''': No dedicated service (scripts run via `ifup`/`ifdown`)<br /> * '''CLI Tools''': `ifup`, `ifdown`<br /> * '''Main Configuration File''':<br /> ** `/etc/network/interfaces`<br /> <br /> === Example Interfaces File ===<br /> `/etc/network/interfaces`<br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> auto lo<br /> iface lo inet loopback<br /> <br /> auto enp0s3<br /> iface enp0s3 inet dhcp<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == 4. netplan ==<br /> <br /> Netplan is a utility for configuring networking on modern Ubuntu systems (17.10 and later). It abstracts configuration and delegates to either NetworkManager or `systemd-networkd`.<br /> <br /> * '''Service''': Depends on backend (NetworkManager or systemd-networkd)<br /> * '''CLI Tools''': `netplan apply`, `netplan try`<br /> * '''Main Configuration Files''':<br /> ** `/etc/netplan/*.yaml`<br /> <br /> === Example Netplan YAML File ===<br /> `/etc/netplan/01-netcfg.yaml`<br /> &lt;syntaxhighlight lang=&quot;yaml&quot;&gt;<br /> network:<br /> version: 2<br /> ethernets:<br /> enp0s3:<br /> dhcp4: true<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == 5. Wicd ==<br /> <br /> Wicd is a network connection manager that aims to provide a simple interface to connect to networks. It is now mostly obsolete but may still be found on lightweight systems.<br /> <br /> * '''Service''': `wicd`<br /> * '''CLI Tools''': `wicd-curses`, `wicd-cli`<br /> * '''Main Configuration Files''':<br /> ** `/etc/wicd/` – Configuration directory<br /> ** `/etc/wicd/wireless-settings.conf` – Wireless-specific configuration<br /> ** `/etc/wicd/wired-settings.conf` – Wired-specific configuration<br /> <br /> == 6. ConnMan (Connection Manager) ==<br /> <br /> ConnMan is a daemon for managing internet connections within embedded devices. It is lightweight and often used in systems with limited resources.<br /> <br /> * '''Service''': `connmand`<br /> * '''CLI Tools''': `connmanctl`<br /> * '''Main Configuration Files''':<br /> ** `/etc/connman/main.conf` – General configuration<br /> ** `/var/lib/connman/` – Profiles and saved settings<br /> <br /> === Example ConnMan Configuration ===<br /> `/etc/connman/main.conf`<br /> &lt;syntaxhighlight lang=&quot;ini&quot;&gt;<br /> [General]<br /> PreferredTechnologies=ethernet,wifi<br /> SingleConnectedTechnology=true<br /> &lt;/syntaxhighlight&gt;<br /> <br /> = Summary Table =<br /> <br /> {| class=&quot;wikitable&quot;<br /> ! Network Manager !! Main Config File(s) !! CLI Tools !! Typical Use<br /> |-<br /> | NetworkManager || /etc/NetworkManager/ || nmcli, nmtui || Desktop<br /> |-<br /> | systemd-networkd || /etc/systemd/network/ || networkctl || Server, Embedded<br /> |-<br /> | ifupdown || /etc/network/interfaces || ifup, ifdown || Legacy Debian/Ubuntu<br /> |-<br /> | netplan || /etc/netplan/*.yaml || netplan || Ubuntu (modern)<br /> |-<br /> | Wicd || /etc/wicd/ || wicd-curses, wicd-cli || Lightweight Desktop<br /> |-<br /> | ConnMan || /etc/connman/ || connmanctl || Embedded Systems<br /> |}<br /> <br /> <br /> -------------<br /> <br /> <br /> &lt;pre&gt;<br /> +--------------------+<br /> | User Interface |<br /> |--------------------|<br /> | nmcli / nmtui &lt;-- NetworkManager<br /> | networkctl &lt;-- systemd-networkd<br /> | netplan apply &lt;-- Netplan<br /> +--------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Configuration Files |<br /> |-----------------------------|<br /> | /etc/netplan/*.yaml &lt;-- Netplan<br /> | /etc/NetworkManager/*.conf &lt;-- NetworkManager<br /> | /etc/systemd/network/*.network &lt;-- systemd-networkd<br /> | /etc/network/interfaces &lt;-- ifupdown<br /> +-----------------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Network Managers (Daemons) |<br /> |-----------------------------|<br /> | NetworkManager.service<br /> | systemd-networkd.service<br /> | ifupdown (manual)<br /> | connman.service<br /> +-----------------------------+<br /> <br /> ↓<br /> <br /> +-----------------------------+<br /> | Kernel/Drivers |<br /> |-----------------------------|<br /> | Interface mgmt, DHCP, etc. |<br /> +-----------------------------+<br /> &lt;/pre&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=396 Main Page 2025-06-20T06:23:40Z <p>Koan: /* Problem solving - Howto */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> * [[Optimal swap size for building with Yocto Project]]<br /> * [[Linux Network Managers and Configuration Files]]<br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> * [[Yocto Project override operators]]<br /> * [[How to generate an initrd image with Yocto]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_generate_an_initrd_image_with_Yocto&diff=395 How to generate an initrd image with Yocto 2025-05-05T15:20:16Z <p>Koan: Created page with &quot;== How to generate an initramf image with Yocto == To build an &#039;&#039;&#039;initramfs&#039;&#039;&#039;, you only need to specify the &#039;&#039;&#039;initramfs&#039;&#039;&#039; image name (e.g., INITRAMFS_IMAGE) and its type...&quot;</p> <hr /> <div>== How to generate an initramf image with Yocto ==<br /> <br /> <br /> To build an '''initramfs''', you only need to specify the '''initramfs''' image name (e.g., INITRAMFS_IMAGE) and its type (e.g., INITRAMFS_FSTYPES). <br /> <br /> INITRAMFS_IMAGE = &quot;core-image-tiny-initramfs&quot;<br /> INITRAMFS_FSTYPES = &quot;cpio.gz&quot;<br /> <br /> Moreover, the kernel requires these features to load and uncompress the initramfs: <br /> <br /> CONFIG_BLK_DEV_INITRD=y<br /> CONFIG_INITRAMFS_SOURCE=&quot;&quot;<br /> CONFIG_RD_GZIP=y<br /> CONFIG_DECOMPRESS_GZIP=y<br /> <br /> In addition if you want the initramfs to be packaged into the kernel binary instead of being a separate binary (or a different image node of a kernel fitimage) use this setting:<br /> <br /> INITRAMFS_IMAGE_BUNDLE = &quot;1&quot;</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=394 Main Page 2025-05-05T15:16:31Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> * [[Optimal swap size for building with Yocto Project]]<br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> * [[Yocto Project override operators]]<br /> * [[How to generate an initrd image with Yocto]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Yocto_Project_override_operators&diff=393 Yocto Project override operators 2025-03-28T16:23:26Z <p>Koan: Created page with &quot;== Yocto Project override operators == Override operators in Yocto Project VARIABLENAME:prepend = &quot; value&quot; VARIABLENAME:append = &quot; value&quot; VARIABLENAME:remove = &quot; value&quot;...&quot;</p> <hr /> <div>== Yocto Project override operators ==<br /> <br /> <br /> Override operators in Yocto Project<br /> <br /> VARIABLENAME:prepend = &quot; value&quot;<br /> VARIABLENAME:append = &quot; value&quot;<br /> VARIABLENAME:remove = &quot; value&quot;<br /> <br /> Although not recommended, worst case, you can also use the “forcevariable” override, which is the strongest override possible. Here is an example:<br /> <br /> VARIABLENAME:forcevariable = &quot; value&quot;</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=392 Main Page 2025-03-28T16:19:45Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> * [[Optimal swap size for building with Yocto Project]]<br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> * [[Yocto Project override operators]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Optimal_swap_size_for_building_with_Yocto_Project&diff=391 Optimal swap size for building with Yocto Project 2025-03-25T17:26:08Z <p>Koan: Created page with &quot;== Optimal swap size for building with Yocto Project == BitBake, the build engine used in the Yocto Project, is notorious for its appetite for system memory, especially when...&quot;</p> <hr /> <div>== Optimal swap size for building with Yocto Project ==<br /> <br /> BitBake, the build engine used in the Yocto Project, is notorious for its appetite for system memory, especially when compiling large and complex software images. When your computer's RAM gets filled to capacity during a BitBake process, it can lead to frustrating build failures, system crashes, or agonizingly slow build times. This is where swap space comes in.<br /> <br /> Think of swap space as a reserve of extra memory on your hard drive. When your system's RAM is fully occupied, the operating system cleverly moves less frequently used data from RAM to this swap space. This frees up crucial RAM for BitBake to continue its work, preventing those dreaded out-of-memory errors that halt progress.<br /> <br /> While using swap space introduces a performance penalty, as hard drives are significantly slower than RAM, it provides a crucial safety net. It allows builds that would otherwise crash to complete successfully. Essentially, it trades a bit of speed for increased stability and reliability. This improvement is a practical way to address memory limitations and ensure that BitBake can handle even the most demanding build tasks, ultimately making the development process smoother and more predictable.<br /> <br /> <br /> == What is swap and why resize it ==<br /> <br /> <br /> '''Recommended swap sizes'''<br /> <br /> * System RAM : 8GB to 64GB <br /> * Swap size : At least 4GB<br /> * Swap suggested : 1.5x RAM<br /> <br /> <br /> '''Prerequisites'''<br /> <br /> Before modifying your swap configuration, ensure you have:<br /> <br /> * Root or sudo privileges: All commands in this guide require elevated permissions<br /> * Sufficient free disk space: Verify available space with df -h<br /> * Backup of critical data: System-level changes always carry some risk<br /> * Understanding of current swap usage: Check with these commands:<br /> <br /> # Show current swap files/partitions and their sizes<br /> sudo swapon --show<br /> <br /> # View memory and swap usage<br /> free -h<br /> <br /> # Check if swap is being actively used<br /> vmstat 1 5<br /> <br /> <br /> == Step-by-Step process to resize swap ==<br /> <br /> <br /> '''Turn off all running swap processes'''<br /> <br /> sudo swapoff -a<br /> <br /> This command disables all swap spaces defined in /etc/fstab and currently active. It may take some time to complete as the system moves data from swap back to RAM.<br /> <br /> <br /> '''Resize the swap file'''<br /> <br /> For this example, we'll create a 16GB swap file (adjust the size to your needs):<br /> <br /> # Remove the old swap file if it exists<br /> sudo rm /swapfile<br /> <br /> # Create a new swap file with desired size (4G in this example)<br /> sudo fallocate -l 16GB /swapfile<br /> <br /> ### Alternative method if fallocate fails:<br /> ### sudo dd if=/dev/zero of=/swapfile bs=1G count=16<br /> <br /> <br /> '''Set proper permissions and ownership'''<br /> <br /> Swap files should be readable and writable only by root for security:<br /> <br /> # Set correct permissions (only root can read/write)<br /> sudo chmod 600 /swapfile<br /> <br /> # Verify permissions<br /> ls -lh /swapfile<br /> <br /> <br /> '''Set up the swap area'''<br /> <br /> # Format the file as swap<br /> sudo mkswap /swapfile<br /> <br /> You should see output confirming the swap file creation.<br /> <br /> <br /> '''Activate the swap file'''<br /> <br /> # Enable the swap file<br /> sudo swapon /swapfile<br /> <br /> '''Verify the swap is active'''<br /> <br /> sudo swapon --show<br /> free -h</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=390 Main Page 2025-03-25T17:16:38Z <p>Koan: /* Problem solving - Howto */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> * [[Optimal swap size for building with Yocto Project]]<br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_configure_network_using_systemd-networkd_in_Yocto&diff=389 How to configure network using systemd-networkd in Yocto 2025-03-16T15:53:13Z <p>Koan: </p> <hr /> <div>== How to configure network using systemd-networkd in Yocto ==<br /> <br /> When using '''Yocto Project''' it sometimes may be necessary to setup a '''static IP address''' via a custom recipe.<br /> <br /> When the network manager is '''systemd-networkd''' the file usually responsible for that is '''/lib/systemd/network/80-wired.network'''<br /> <br /> Simply change it from the original<br /> <br /> # cat /lib/systemd/network/80-wired.network<br /> <br /> [Match]<br /> Type=ether<br /> Name=!veth*<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> DHCP=yes<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac<br /> <br /> To the following<br /> <br /> # cat /lib/systemd/network/80-wired.network<br /> <br /> [Match]<br /> Type=ether<br /> Name=eth0<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> Address=192.168.0.184/24<br /> Gateway=192.168.0.1<br /> DNS=1.1.1.1<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac<br /> <br /> Below is an example of a possible solution<br /> <br /> Create a '''.bbappend''' recipe to manage that and replace the existing '''wired.network''' file with your custom one<br /> <br /> meta-custom/<br /> └─ recipes-core/<br /> └── systemd-conf<br /> ├── systemd-conf<br /> │   └── wired.network<br /> └── systemd-conf_%.bbappend<br /> <br /> <br /> The recipe systemd-conf_%.bbappend<br /> <br /> # recipes-core/systemd-conf/systemd-conf_%.bbappend <br /> <br /> FILESEXTRAPATHS:prepend := &quot;${THISDIR}/${PN}:&quot;<br /> <br /> <br /> The network file<br /> <br /> # wired.network <br /> <br /> [Match]<br /> Type=ether<br /> Name=eth0<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> Address=192.168.0.184/24<br /> Gateway=192.168.0.1<br /> DNS=1.1.1.1<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_configure_network_using_systemd-networkd_in_Yocto&diff=388 How to configure network using systemd-networkd in Yocto 2025-03-15T14:00:05Z <p>Koan: </p> <hr /> <div>== How to configure network using systemd-networkd in Yocto ==<br /> <br /> When using '''Yocto Project''' it sometimes may be necessary to setup a '''static IP address''' via a custom recipe.<br /> <br /> When the network manager is '''systemd-networkd''' the file usually responsible for that is '''/lib/systemd/network/80-wired.network'''<br /> <br /> Simply change it from the original<br /> <br /> # cat /lib/systemd/network/80-wired.network<br /> <br /> [Match]<br /> Type=ether<br /> Name=!veth*<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> DHCP=yes<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac<br /> <br /> To the following<br /> <br /> # cat /lib/systemd/network/80-wired.network<br /> <br /> [Match]<br /> Type=ether<br /> Name=!veth*<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> Address=192.168.0.184/24<br /> Gateway=192.168.0.1<br /> DNS=1.1.1.1<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac<br /> <br /> Below is an example of a possible solution<br /> <br /> Create a '''.bbappend''' recipe to manage that and replace the existing '''wired.network''' file with your custom one<br /> <br /> meta-custom/<br /> └─ recipes-core/<br /> └── systemd-conf<br /> ├── systemd-conf<br /> │   └── wired.network<br /> └── systemd-conf_%.bbappend<br /> <br /> <br /> The recipe systemd-conf_%.bbappend<br /> <br /> # recipes-core/systemd-conf/systemd-conf_%.bbappend <br /> <br /> FILESEXTRAPATHS:prepend := &quot;${THISDIR}/${PN}:&quot;<br /> <br /> <br /> The network file<br /> <br /> # wired.network <br /> <br /> [Match]<br /> Type=ether<br /> Name=!veth*<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> Address=192.168.0.184/24<br /> Gateway=192.168.0.1<br /> DNS=1.1.1.1<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_configure_network_using_systemd-networkd_in_Yocto&diff=387 How to configure network using systemd-networkd in Yocto 2025-03-15T13:49:40Z <p>Koan: Created page with &quot;== How to configure network using systemd-networkd in Yocto == When using &#039;&#039;&#039;Yocto Project&#039;&#039;&#039; it sometimes may be necessary to setup a &#039;&#039;&#039;static IP address&#039;&#039;&#039; via a custom re...&quot;</p> <hr /> <div>== How to configure network using systemd-networkd in Yocto ==<br /> <br /> When using '''Yocto Project''' it sometimes may be necessary to setup a '''static IP address''' via a custom recipe.<br /> <br /> When the network manager is '''systemd-networkd''' the file usually responsible for that is '''/lib/systemd/network/80-wired.network'''<br /> <br /> Simply change it from the original<br /> <br /> # cat /lib/systemd/network/80-wired.network<br /> <br /> [Match]<br /> Type=ether<br /> Name=!veth*<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> DHCP=yes<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac<br /> <br /> To the following<br /> <br /> # cat /lib/systemd/network/80-wired.network<br /> <br /> [Match]<br /> Type=ether<br /> Name=!veth*<br /> KernelCommandLine=!nfsroot<br /> KernelCommandLine=!ip<br /> <br /> [Network]<br /> Address=192.168.0.184/24<br /> Gateway=192.168.0.1<br /> DNS=1.1.1.1<br /> <br /> [DHCP]<br /> UseMTU=yes<br /> RouteMetric=10<br /> ClientIdentifier=mac<br /> <br /> Below is an example of a recipe to manage that</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=386 Main Page 2025-03-15T13:45:55Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> * [[How to configure network using systemd-networkd in Yocto]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Replacement_for_command_ldd_on_Linux&diff=385 Replacement for command ldd on Linux 2025-02-28T10:32:25Z <p>Koan: </p> <hr /> <div>== Replacement for command ldd on Linux ==<br /> <br /> Are you looking to install the '''ldd''' command on your Linux system but it isn't available?<br /> <br /> This is typical when you are using Yocto Project on the target board.<br /> <br /> '''Alternative Method to Check Library Dependencies in Linux<br /> '''<br /> While the '''ldd''' command is a powerful tool for examining library dependencies, there are alternative methods that can provide similar information. <br /> One such method is using the objdump command.<br /> <br /> # LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-armhf.so.3 /usr/bin/gpg<br /> <br /> linux-vdso.so.1 (0xbef3e000)<br /> libz.so.1 =&gt; /lib/libz.so.1 (0xb6f70000)<br /> libbz2.so.1 =&gt; /usr/lib/libbz2.so.1 (0xb6f50000)<br /> libgcrypt.so.20 =&gt; /usr/lib/libgcrypt.so.20 (0xb6ea0000)<br /> libreadline.so.8 =&gt; /usr/lib/libreadline.so.8 (0xb6e50000)<br /> libassuan.so.0 =&gt; /usr/lib/libassuan.so.0 (0xb6e30000)<br /> libnpth.so.0 =&gt; /usr/lib/libnpth.so.0 (0xb6e10000)<br /> libgpg-error.so.0 =&gt; /usr/lib/libgpg-error.so.0 (0xb6de0000)<br /> libc.so.6 =&gt; /lib/libc.so.6 (0xb6cc0000)<br /> libcap.so.2 =&gt; /lib/libcap.so.2 (0xb6ca0000)<br /> libtinfo.so.5 =&gt; /lib/libtinfo.so.5 (0xb6c70000)<br /> /lib/ld-linux-armhf.so.3 (0xb6f98000)<br /> <br /> or<br /> <br /> root@intel-corei7-64:~# LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-x86-64.so.2 /usr/bin/aplay<br /> <br /> linux-vdso.so.1 (0x00007ffc005c6000)<br /> libasound.so.2 =&gt; /usr/lib/libasound.so.2 (0x00007f0a498fe000)<br /> libc.so.6 =&gt; /lib/libc.so.6 (0x00007f0a496fe000)<br /> libm.so.6 =&gt; /lib/libm.so.6 (0x00007f0a49620000)<br /> libpthread.so.0 =&gt; /lib/libpthread.so.0 (0x00007f0a4961b000)<br /> librt.so.1 =&gt; /lib/librt.so.1 (0x00007f0a49616000)<br /> /lib/ld-linux-x86-64.so.2 (0x00007f0a49a23000)<br /> <br /> or using the cross compiler '''objdump''' command<br /> <br /> root@intel-corei7-64:~# aarch64-poky-linux-objdump -x nInvaders | grep NEEDED<br /> <br /> NEEDED libncurses.so.5<br /> NEEDED libtinfo.so.5<br /> NEEDED libc.so.6<br /> NEEDED ld-linux-aarch64.so.1</div> Koan https://wiki.koansoftware.com/index.php?title=Replacement_for_command_ldd_on_Linux&diff=384 Replacement for command ldd on Linux 2025-02-28T10:32:14Z <p>Koan: </p> <hr /> <div>== Replacement for command ldd on Linux ==<br /> <br /> Are you looking to install the '''ldd''' command on your Linux system but it isn't available?<br /> <br /> This is typical when you are using Yocto Project on the target board.<br /> <br /> '''Alternative Method to Check Library Dependencies in Linux<br /> '''<br /> While the '''ldd''' command is a powerful tool for examining library dependencies, there are alternative methods that can provide similar information. <br /> One such method is using the objdump command.<br /> <br /> # LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-armhf.so.3 /usr/bin/gpg<br /> <br /> linux-vdso.so.1 (0xbef3e000)<br /> libz.so.1 =&gt; /lib/libz.so.1 (0xb6f70000)<br /> libbz2.so.1 =&gt; /usr/lib/libbz2.so.1 (0xb6f50000)<br /> libgcrypt.so.20 =&gt; /usr/lib/libgcrypt.so.20 (0xb6ea0000)<br /> libreadline.so.8 =&gt; /usr/lib/libreadline.so.8 (0xb6e50000)<br /> libassuan.so.0 =&gt; /usr/lib/libassuan.so.0 (0xb6e30000)<br /> libnpth.so.0 =&gt; /usr/lib/libnpth.so.0 (0xb6e10000)<br /> libgpg-error.so.0 =&gt; /usr/lib/libgpg-error.so.0 (0xb6de0000)<br /> libc.so.6 =&gt; /lib/libc.so.6 (0xb6cc0000)<br /> libcap.so.2 =&gt; /lib/libcap.so.2 (0xb6ca0000)<br /> libtinfo.so.5 =&gt; /lib/libtinfo.so.5 (0xb6c70000)<br /> /lib/ld-linux-armhf.so.3 (0xb6f98000)<br /> <br /> or<br /> <br /> root@intel-corei7-64:~# LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-x86-64.so.2 /usr/bin/aplay<br /> <br /> linux-vdso.so.1 (0x00007ffc005c6000)<br /> libasound.so.2 =&gt; /usr/lib/libasound.so.2 (0x00007f0a498fe000)<br /> libc.so.6 =&gt; /lib/libc.so.6 (0x00007f0a496fe000)<br /> libm.so.6 =&gt; /lib/libm.so.6 (0x00007f0a49620000)<br /> libpthread.so.0 =&gt; /lib/libpthread.so.0 (0x00007f0a4961b000)<br /> librt.so.1 =&gt; /lib/librt.so.1 (0x00007f0a49616000)<br /> /lib/ld-linux-x86-64.so.2 (0x00007f0a49a23000)<br /> <br /> or using the cross compiler '''objdump''' command<br /> <br /> root@intel-corei7-64:~# aarch64-poky-linux-objdump -x nInvaders | grep NEEDED<br /> <br /> NEEDED libncurses.so.5<br /> NEEDED libtinfo.so.5<br /> NEEDED libc.so.6<br /> NEEDED ld-linux-aarch64.so.1</div> Koan https://wiki.koansoftware.com/index.php?title=Best_hardware_to_build_Yocto_Project&diff=383 Best hardware to build Yocto Project 2025-02-27T14:17:18Z <p>Koan: Created page with &quot;Best hardware to build Yocto Project * CPU Ryzen 9950X with * 64 GB DDR5 RAM and * 2 TB Samsung 990PRO PCI-e 4.0 disk * Ubuntu 24.04 (native or Dockerfile) The overhead of...&quot;</p> <hr /> <div>Best hardware to build Yocto Project<br /> <br /> * CPU Ryzen 9950X with<br /> * 64 GB DDR5 RAM and <br /> * 2 TB Samsung 990PRO PCI-e 4.0 disk <br /> * Ubuntu 24.04 (native or Dockerfile)<br /> <br /> The overhead of doing the build in a Docker vs. native is only 1% and while the average build time with native Ubuntu 24.04 was 18 minutes 52 seconds it is only 19 minutes and 5 seconds (delta of 13 seconds) with the Docker container.<br /> <br /> NOTE: These details are dated FEB.2025 and may need an update later</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=382 Main Page 2025-02-27T14:12:53Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Best hardware to build Yocto Project]] <br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_run_CVE_checks_using_the_Yocto_Project&diff=381 How to run CVE checks using the Yocto Project 2024-12-11T17:25:14Z <p>Koan: </p> <hr /> <div>== How to run CVE checks using the Yocto Project ==<br /> <br /> Enable CVE check<br /> <br /> The Yocto Project provides a '''cve-check''' class which can be enabled to perform scans on packages for public CVE’s. <br /> <br /> It is possible to enable this feature to run a scan of packages but also on images.<br /> <br /> To enable the CVE check you can add the following to e.g local.conf:<br /> <br /> INHERIT += &quot;cve-check&quot;<br /> <br /> Then run<br /> <br /> bitbake core-image-minimal<br /> <br /> Or <br /> <br /> bitbake --runall cve_check core-image-minimal<br /> <br /> <br /> You will get to the output a list of unpatched CVE’s where found and several log files<br /> <br /> * '''Complete CVE report''' summary created at: .../'''build/tmp/log/cve/cve-summary'''<br /> <br /> * '''Complete CVE JSON report''' summary created at: .../'''build/tmp/log/cve/cve-summary.json'''<br /> <br /> <br /> It is also possible to check the CVE status of individual packages as follows:<br /> <br /> bitbake -c cve_check flex libarchive</div> Koan https://wiki.koansoftware.com/index.php?title=Add_build_information_into_a_Yocto_image&diff=380 Add build information into a Yocto image 2024-12-10T17:22:11Z <p>Koan: </p> <hr /> <div>== Creating Add build information into a Yocto image ==<br /> <br /> Importing variables into the device with '''buildinfo'''<br /> <br /> There is a little known image feature in Yocto called buildinfo that will help us get the required information. <br /> <br /> Buildinfo is available in Yocto 1.8 and later versions. This image feature will write a set of OpenEmbedded variables to a file /etc/build in the image, which in turn gets '''written to the target device'''.<br /> <br /> To enable buildinfo, open conf/local.conf and append <br /> <br /> INHERIT += &quot;image-buildinfo&quot;<br /> IMAGE_BUILDINFO_VARS:append = &quot; DATETIME DISTRO_NAME IMAGE_BASENAME MACHINE TUNE_PKGARCH&quot; <br /> IMAGE_BUILDINFO_VARS:append = &quot; MACHINE_FEATURES DISTRO_FEATURES COMMON_FEATURES IMAGE_FEATURES&quot;<br /> IMAGE_BUILDINFO_VARS:append = &quot; TUNE_FEATURES TARGET_FPU&quot;<br /> <br /> Then build the desired image, e.g. with bitbake -k core-image-minimal.<br /> And run the image, e.g. with runqemu qemuarm nographic, and look at the file generated in /etc/build.<br /> <br /> A sample resulting file '''/etc/build''' or '''/etc/buildinfo''' (depending on the Yocto vesion) is shown below.<br /> <br /> -----------------------<br /> Build Configuration: |<br /> -----------------------<br /> DISTRO = poky<br /> DISTRO_VERSION = 4.0.19<br /> DATETIME = 20240626102217<br /> DISTRO_NAME = Poky (Yocto Project Reference Distro)<br /> IMAGE_BASENAME = core-image-minimal<br /> MACHINE = qemuarm<br /> TUNE_PKGARCH = cortexa15t2hf-neon<br /> MACHINE_FEATURES = alsa bluetooth usbgadget screen vfat rtc qemu-usermode<br /> DISTRO_FEATURES = acl alsa argp bluetooth debuginfod ext2 ipv4 ipv6 largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 vfat seccomp largefile opengl ptest multiarch wayland vulkan pulseaudio sysvinit gobject-introspection-data ldconfig<br /> COMMON_FEATURES = <br /> IMAGE_FEATURES = debug-tweaks package-management ssh-server-openssh<br /> TUNE_FEATURES = arm vfp cortexa15 neon thumb callconvention-hard<br /> TARGET_FPU = hard<br /> -----------------------<br /> Layer Revisions: |<br /> -----------------------<br /> meta = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df <br /> meta-poky = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df <br /> meta-yocto-bsp = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df <br /> meta-oe = kirkstone:0560b848996a0feb410a8cd8ca07c60fe2f3b5bc <br /> <br /> <br /> ----------<br /> <br /> '''Buildhistory'''<br /> <br /> To enable buildhistory, open conf/local.conf and append<br /> <br /> INHERIT += &quot;buildhistory&quot;<br /> BUILDHISTORY_COMMIT = &quot;1&quot;<br /> <br /> The same details are registered on the HOST for every build when you enable '''buildhistory'''<br /> <br /> commit 3c194a01ee722b94f474c7911ccb926ee2858639 (HEAD -&gt; master)<br /> Author: buildhistory &lt;buildhistory@poky&gt;<br /> Date: Wed Jun 26 10:22:52 2024 +0000<br /> <br /> Build 20240626102217 of poky 4.0.19 for machine qemuarm on koanserver<br /> <br /> cmd: bitbake core-image-minimal<br /> <br /> result: succeeded<br /> <br /> metadata revisions:<br /> meta = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df<br /> meta-poky = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df<br /> meta-yocto-bsp = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df<br /> meta-oe = kirkstone:0560b848996a0feb410a8cd8ca07c60fe2f3b5bc</div> Koan https://wiki.koansoftware.com/index.php?title=Add_build_information_into_a_Yocto_image&diff=379 Add build information into a Yocto image 2024-12-10T17:22:01Z <p>Koan: </p> <hr /> <div>== Creating Add build information into a Yocto image ==<br /> <br /> Importing variables into the device with '''buildinfo'''<br /> <br /> There is a little known image feature in Yocto called buildinfo that will help us get the required information. <br /> <br /> Buildinfo is available in Yocto 1.8 and later versions. This image feature will write a set of OpenEmbedded variables to a file /etc/build in the image, which in turn gets '''written to the target device'''.<br /> <br /> To enable buildinfo, open conf/local.conf and append <br /> <br /> INHERIT += &quot;image-buildinfo&quot;<br /> IMAGE_BUILDINFO_VARS:append = &quot; DATETIME DISTRO_NAME IMAGE_BASENAME MACHINE TUNE_PKGARCH&quot; <br /> IMAGE_BUILDINFO_VARS:append = &quot; MACHINE_FEATURES DISTRO_FEATURES COMMON_FEATURES IMAGE_FEATURES&quot;<br /> IMAGE_BUILDINFO_VARS:append = &quot; TUNE_FEATURES TARGET_FPU&quot;<br /> <br /> Then build the desired image, e.g. with bitbake -k core-image-minimal.<br /> And run the image, e.g. with runqemu qemuarm nographic, and look at the file generated in /etc/build.<br /> <br /> A sample resulting file '''/etc/build''' or '''/etc/build''' (depending on the Yocto vesion) is shown below.<br /> <br /> -----------------------<br /> Build Configuration: |<br /> -----------------------<br /> DISTRO = poky<br /> DISTRO_VERSION = 4.0.19<br /> DATETIME = 20240626102217<br /> DISTRO_NAME = Poky (Yocto Project Reference Distro)<br /> IMAGE_BASENAME = core-image-minimal<br /> MACHINE = qemuarm<br /> TUNE_PKGARCH = cortexa15t2hf-neon<br /> MACHINE_FEATURES = alsa bluetooth usbgadget screen vfat rtc qemu-usermode<br /> DISTRO_FEATURES = acl alsa argp bluetooth debuginfod ext2 ipv4 ipv6 largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 vfat seccomp largefile opengl ptest multiarch wayland vulkan pulseaudio sysvinit gobject-introspection-data ldconfig<br /> COMMON_FEATURES = <br /> IMAGE_FEATURES = debug-tweaks package-management ssh-server-openssh<br /> TUNE_FEATURES = arm vfp cortexa15 neon thumb callconvention-hard<br /> TARGET_FPU = hard<br /> -----------------------<br /> Layer Revisions: |<br /> -----------------------<br /> meta = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df <br /> meta-poky = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df <br /> meta-yocto-bsp = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df <br /> meta-oe = kirkstone:0560b848996a0feb410a8cd8ca07c60fe2f3b5bc <br /> <br /> <br /> ----------<br /> <br /> '''Buildhistory'''<br /> <br /> To enable buildhistory, open conf/local.conf and append<br /> <br /> INHERIT += &quot;buildhistory&quot;<br /> BUILDHISTORY_COMMIT = &quot;1&quot;<br /> <br /> The same details are registered on the HOST for every build when you enable '''buildhistory'''<br /> <br /> commit 3c194a01ee722b94f474c7911ccb926ee2858639 (HEAD -&gt; master)<br /> Author: buildhistory &lt;buildhistory@poky&gt;<br /> Date: Wed Jun 26 10:22:52 2024 +0000<br /> <br /> Build 20240626102217 of poky 4.0.19 for machine qemuarm on koanserver<br /> <br /> cmd: bitbake core-image-minimal<br /> <br /> result: succeeded<br /> <br /> metadata revisions:<br /> meta = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df<br /> meta-poky = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df<br /> meta-yocto-bsp = kirkstone:e139e9d0ce343ba77a09601a976c92acd562c9df<br /> meta-oe = kirkstone:0560b848996a0feb410a8cd8ca07c60fe2f3b5bc</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_add_binary_files_via_a_custom_recipe&diff=378 How to add binary files via a custom recipe 2024-12-04T08:32:45Z <p>Koan: Created page with &quot;== How to add binary files via a custom recipe == When using Yocto Project it sometimes may be necessary to insert binary files via a custom recipe. Below is an example of a...&quot;</p> <hr /> <div>== How to add binary files via a custom recipe ==<br /> <br /> When using Yocto Project it sometimes may be necessary to insert binary files via a custom recipe.<br /> <br /> Below is an example of a recipe to manage that<br /> <br /> #<br /> # binary_0.1.bb<br /> #<br /> <br /> DESCRIPTION = &quot;Install custom files to /root directory&quot;<br /> LICENSE = &quot;CLOSED&quot;<br /> LIC_FILES_CHKSUM = &quot;&quot;<br /> <br /> SRC_URI = &quot;file://my-binary \<br /> file://my-config-file&quot;<br /> <br /> do_install() {<br /> # Create the /root directory in the target filesystem<br /> install -d ${D}${sysconfdir}/root<br /> <br /> # Install your binary and config file<br /> install -m 0755 ${WORKDIR}/my-binary ${D}/root/my-binary<br /> install -m 0644 ${WORKDIR}/my-config-file ${D}/root/my-config-file<br /> }<br /> <br /> FILES:${PN} = &quot;/root&quot;</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=377 Main Page 2024-12-04T08:25:49Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> * [[How to add binary files via a custom recipe]]<br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Yocto_Project_my_own_quick_start&diff=376 Yocto Project my own quick start 2024-10-17T14:42:16Z <p>Koan: /* Edit the configuration files */</p> <hr /> <div>This page is an excerpt from [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start Copyright © 2010-2020 Linux Foundation]<br /> <br /> <br /> == The required packages ==<br /> <br /> Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu.<br /> <br /> If you have different distributions, please refer to the [https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html Yocto Project Documentation]<br /> <br /> You must install essential host packages on your build host. <br /> The following command installs the host packages based on an Ubuntu distribution:<br /> <br /> $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath \<br /> socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping \<br /> python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1<br /> <br /> $ sudo locale-gen en_US.UTF-8<br /> <br /> == Development Code - branch 5.0 'scarthgap' LTS ==<br /> <br /> Yocto Project code can be found in the Yocto Project Source Repositories.<br /> To check out current development code using git:<br /> <br /> $ cd $HOME/yocto<br /> $ git clone git://git.yoctoproject.org/poky -b scarthgap<br /> <br /> poky/<br /> ├── bitbake<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── MAINTAINERS.md<br /> ├── MEMORIAM<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware.md -&gt; meta-yocto-bsp/README.hardware.md<br /> ├── README.md -&gt; README.poky.md<br /> ├── README.OE-Core.md<br /> ├── README.poky.md -&gt; meta-poky/README.poky.md<br /> ├── README.qemu.md<br /> ├── scripts<br /> └── SECURITY.md<br /> <br /> In addition you can install an optional but frequently essential metalayer<br /> <br /> $ cd $HOME/yocto/poky<br /> $ git clone git://git.openembedded.org/meta-openembedded -b scarthgap<br /> <br /> == Initializing the Build Environment ==<br /> <br /> From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:<br /> <br /> $ cd $HOME/yocto/poky<br /> $ source oe-init-build-env<br /> <br /> At this point, the '''build''' directory has been created for you and it is now your current working directory. <br /> This is the default tree you should have to build.<br /> <br /> poky/<br /> ├── bitbake<br /> ├── build &lt;----- run bitbake inside here<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> == Edit the configuration files ==<br /> <br /> Add meta-openembedded/meta-oe to the bblayers.conf<br /> <br /> bitbake-layers add-layer ../meta-openembedded/meta-oe<br /> <br /> <br /> Remember also to edit the file $HOME/yocto/poky/build/conf/local.conf<br /> and check the following variables:<br /> <br /> MACHINE ?= &quot;qemuarm&quot;<br /> DISTRO ?= &quot;poky&quot;<br /> PACKAGE_CLASSES ?= &quot;package_ipk&quot;<br /> INHERIT += &quot;rm_work&quot;<br /> <br /> == Building the Image ==<br /> <br /> At this point, you need to select an image to build. <br /> If this is your first build using the Yocto Project, you should try the smallest and simplest image:<br /> <br /> $ bitbake core-image-minimal <br /> <br /> Now you just wait for the build to finish.<br /> <br /> == Starting the QEMU Emulator ==<br /> <br /> Before you start the QEMU emulator, be sure you have already to set up the emulation environment. <br /> <br /> The following command setup the emulation environment and launch QEMU.<br /> <br /> $ runqemu qemuarm<br /> <br /> Or if you prefer, open a new shell terminal, setup the environment again and run<br /> <br /> $ runqemu qemuarm nographic<br /> <br /> == Building cross-compiler ==<br /> <br /> If you want you can create a re-distribuible cross-compiler targeted at your MACHINE.<br /> <br /> $ bitbake meta-toolchain</div> Koan https://wiki.koansoftware.com/index.php?title=Directories_and_installation_variables&diff=375 Directories and installation variables 2024-10-14T07:15:09Z <p>Koan: </p> <hr /> <div>== Yocto Project Openembedded directories installation variables ==<br /> <br /> The following table provides a list of the variables that are used to control the directories into which files are installed.<br /> <br /> These variables can be used directly by the recipe to refer to paths that will be used after the package is installed.<br /> <br /> Variable name Definition Typical value<br /> --------------------- ------------------------ --------------------<br /> prefix /usr /usr<br /> base_prefix (empty) (empty)<br /> exec_prefix ${base_prefix} (empty)<br /> base_bindir ${base_prefix}/bin /bin<br /> base_sbindir ${base_prefix}/sbin /sbin<br /> base_libdir ${base_prefix}/lib /lib<br /> datadir ${prefix}/share /usr/share<br /> sysconfdir /etc /etc<br /> localstatedir /var /var<br /> infodir ${datadir}/info /usr/share/info<br /> mandir ${datadir}/man /usr/share/man<br /> docdir ${datadir}/doc /usr/share/doc<br /> servicedir /srv /srv<br /> bindir ${exec_prefix}/bin /usr/bin<br /> sbindir ${exec_prefix}/sbin /usr/sbin<br /> libexecdir ${exec_prefix}/libexec /usr/libexec<br /> libdir ${exec_prefix}/lib /usr/lib<br /> includedir ${exec_prefix}/include /usr/include<br /> palmtopdir ${libdir}/opie /usr/lib/opie<br /> palmqtdir ${palmtopdir} /usr/lib/opie<br /> systemd_unitdir ${systemd_unitdir} /usr/lib/systemd<br /> systemd_system_unitdir ${systemd_system_unitdir} /usr/lib/systemd/system<br /> systemd_user_unitdir ${systemd_user_unitdir} /usr/lib/systemd/user<br /> <br /> When specifying paths as part of the FILES variable, it is good practice to use appropriate path variables. <br /> <br /> For example, use ${sysconfdir} rather than /etc, or ${bindir} rather than /usr/bin. <br /> <br /> You can find a list of these variables at the top of the meta/conf/bitbake.conf file in the Source Directory. <br /> <br /> You will also find the default values of the various FILES:* variables in this file.<br /> https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/conf/bitbake.conf</div> Koan https://wiki.koansoftware.com/index.php?title=Yocto_Project_my_own_quick_start&diff=374 Yocto Project my own quick start 2024-10-05T15:10:47Z <p>Koan: /* Development Code - branch 5.0 &#039;scarthgap&#039; LTS */</p> <hr /> <div>This page is an excerpt from [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start Copyright © 2010-2020 Linux Foundation]<br /> <br /> <br /> == The required packages ==<br /> <br /> Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu.<br /> <br /> If you have different distributions, please refer to the [https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html Yocto Project Documentation]<br /> <br /> You must install essential host packages on your build host. <br /> The following command installs the host packages based on an Ubuntu distribution:<br /> <br /> $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath \<br /> socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping \<br /> python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1<br /> <br /> $ sudo locale-gen en_US.UTF-8<br /> <br /> == Development Code - branch 5.0 'scarthgap' LTS ==<br /> <br /> Yocto Project code can be found in the Yocto Project Source Repositories.<br /> To check out current development code using git:<br /> <br /> $ cd $HOME/yocto<br /> $ git clone git://git.yoctoproject.org/poky -b scarthgap<br /> <br /> poky/<br /> ├── bitbake<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── MAINTAINERS.md<br /> ├── MEMORIAM<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware.md -&gt; meta-yocto-bsp/README.hardware.md<br /> ├── README.md -&gt; README.poky.md<br /> ├── README.OE-Core.md<br /> ├── README.poky.md -&gt; meta-poky/README.poky.md<br /> ├── README.qemu.md<br /> ├── scripts<br /> └── SECURITY.md<br /> <br /> In addition you can install an optional but frequently essential metalayer<br /> <br /> $ cd $HOME/yocto/poky<br /> $ git clone git://git.openembedded.org/meta-openembedded -b scarthgap<br /> <br /> == Initializing the Build Environment ==<br /> <br /> From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:<br /> <br /> $ cd $HOME/yocto/poky<br /> $ source oe-init-build-env<br /> <br /> At this point, the '''build''' directory has been created for you and it is now your current working directory. <br /> This is the default tree you should have to build.<br /> <br /> poky/<br /> ├── bitbake<br /> ├── build &lt;----- run bitbake inside here<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> == Edit the configuration files ==<br /> <br /> Edit $HOME/yocto/poky/build/conf/bblayers.conf<br /> <br /> <br /> # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf<br /> # changes incompatibly<br /> POKY_BBLAYERS_CONF_VERSION = &quot;2&quot;<br /> <br /> BBPATH = &quot;${TOPDIR}&quot;<br /> BBFILES ?= &quot;&quot;<br /> <br /> BBLAYERS ?= &quot; \<br /> /home/koan/yocto/poky/meta \<br /> /home/koan/yocto/poky/meta-poky \<br /> /home/koan/yocto/poky/meta-yocto-bsp \<br /> /home/koan/yocto/poky/meta-openembedded/meta-oe \<br /> &quot;<br /> <br /> Remember also to edit the file $HOME/yocto/poky/build/conf/local.conf<br /> and check the following variables:<br /> <br /> MACHINE ?= &quot;qemuarm&quot;<br /> DISTRO ?= &quot;poky&quot;<br /> PACKAGE_CLASSES ?= &quot;package_ipk&quot;<br /> INHERIT += &quot;rm_work&quot;<br /> <br /> == Building the Image ==<br /> <br /> At this point, you need to select an image to build. <br /> If this is your first build using the Yocto Project, you should try the smallest and simplest image:<br /> <br /> $ bitbake core-image-minimal <br /> <br /> Now you just wait for the build to finish.<br /> <br /> == Starting the QEMU Emulator ==<br /> <br /> Before you start the QEMU emulator, be sure you have already to set up the emulation environment. <br /> <br /> The following command setup the emulation environment and launch QEMU.<br /> <br /> $ runqemu qemuarm<br /> <br /> Or if you prefer, open a new shell terminal, setup the environment again and run<br /> <br /> $ runqemu qemuarm nographic<br /> <br /> == Building cross-compiler ==<br /> <br /> If you want you can create a re-distribuible cross-compiler targeted at your MACHINE.<br /> <br /> $ bitbake meta-toolchain</div> Koan https://wiki.koansoftware.com/index.php?title=Yocto_Project_my_own_quick_start&diff=373 Yocto Project my own quick start 2024-10-05T15:07:56Z <p>Koan: /* The required packages */</p> <hr /> <div>This page is an excerpt from [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start Copyright © 2010-2020 Linux Foundation]<br /> <br /> <br /> == The required packages ==<br /> <br /> Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu.<br /> <br /> If you have different distributions, please refer to the [https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html Yocto Project Documentation]<br /> <br /> You must install essential host packages on your build host. <br /> The following command installs the host packages based on an Ubuntu distribution:<br /> <br /> $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath \<br /> socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping \<br /> python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1<br /> <br /> $ sudo locale-gen en_US.UTF-8<br /> <br /> == Development Code - branch 5.0 'scarthgap' LTS ==<br /> <br /> Yocto Project code can be found in the Yocto Project Source Repositories.<br /> To check out current development code using git:<br /> <br /> $ cd $HOME/yocto<br /> $ git clone git://git.yoctoproject.org/poky -b scarthgap<br /> <br /> poky/<br /> ├── bitbake<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> In addition you can install an optional but frequently essential metalayer<br /> <br /> $ cd $HOME/yocto/poky<br /> $ git clone git://git.openembedded.org/meta-openembedded -b scarthgap<br /> <br /> == Initializing the Build Environment ==<br /> <br /> From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:<br /> <br /> $ cd $HOME/yocto/poky<br /> $ source oe-init-build-env<br /> <br /> At this point, the '''build''' directory has been created for you and it is now your current working directory. <br /> This is the default tree you should have to build.<br /> <br /> poky/<br /> ├── bitbake<br /> ├── build &lt;----- run bitbake inside here<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> == Edit the configuration files ==<br /> <br /> Edit $HOME/yocto/poky/build/conf/bblayers.conf<br /> <br /> <br /> # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf<br /> # changes incompatibly<br /> POKY_BBLAYERS_CONF_VERSION = &quot;2&quot;<br /> <br /> BBPATH = &quot;${TOPDIR}&quot;<br /> BBFILES ?= &quot;&quot;<br /> <br /> BBLAYERS ?= &quot; \<br /> /home/koan/yocto/poky/meta \<br /> /home/koan/yocto/poky/meta-poky \<br /> /home/koan/yocto/poky/meta-yocto-bsp \<br /> /home/koan/yocto/poky/meta-openembedded/meta-oe \<br /> &quot;<br /> <br /> Remember also to edit the file $HOME/yocto/poky/build/conf/local.conf<br /> and check the following variables:<br /> <br /> MACHINE ?= &quot;qemuarm&quot;<br /> DISTRO ?= &quot;poky&quot;<br /> PACKAGE_CLASSES ?= &quot;package_ipk&quot;<br /> INHERIT += &quot;rm_work&quot;<br /> <br /> == Building the Image ==<br /> <br /> At this point, you need to select an image to build. <br /> If this is your first build using the Yocto Project, you should try the smallest and simplest image:<br /> <br /> $ bitbake core-image-minimal <br /> <br /> Now you just wait for the build to finish.<br /> <br /> == Starting the QEMU Emulator ==<br /> <br /> Before you start the QEMU emulator, be sure you have already to set up the emulation environment. <br /> <br /> The following command setup the emulation environment and launch QEMU.<br /> <br /> $ runqemu qemuarm<br /> <br /> Or if you prefer, open a new shell terminal, setup the environment again and run<br /> <br /> $ runqemu qemuarm nographic<br /> <br /> == Building cross-compiler ==<br /> <br /> If you want you can create a re-distribuible cross-compiler targeted at your MACHINE.<br /> <br /> $ bitbake meta-toolchain</div> Koan https://wiki.koansoftware.com/index.php?title=Yocto_Project_my_own_quick_start&diff=372 Yocto Project my own quick start 2024-10-05T15:07:22Z <p>Koan: branch 5.0 scarthgap</p> <hr /> <div>This page is an excerpt from [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start Copyright © 2010-2020 Linux Foundation]<br /> <br /> <br /> == The required packages ==<br /> <br /> Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu.<br /> <br /> If you have different distributions, please refer to the [https://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start]<br /> <br /> You must install essential host packages on your build host. <br /> The following command installs the host packages based on an Ubuntu distribution:<br /> <br /> $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath \<br /> socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping \<br /> python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1<br /> <br /> $ sudo locale-gen en_US.UTF-8<br /> <br /> == Development Code - branch 5.0 'scarthgap' LTS ==<br /> <br /> Yocto Project code can be found in the Yocto Project Source Repositories.<br /> To check out current development code using git:<br /> <br /> $ cd $HOME/yocto<br /> $ git clone git://git.yoctoproject.org/poky -b scarthgap<br /> <br /> poky/<br /> ├── bitbake<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> In addition you can install an optional but frequently essential metalayer<br /> <br /> $ cd $HOME/yocto/poky<br /> $ git clone git://git.openembedded.org/meta-openembedded -b scarthgap<br /> <br /> == Initializing the Build Environment ==<br /> <br /> From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:<br /> <br /> $ cd $HOME/yocto/poky<br /> $ source oe-init-build-env<br /> <br /> At this point, the '''build''' directory has been created for you and it is now your current working directory. <br /> This is the default tree you should have to build.<br /> <br /> poky/<br /> ├── bitbake<br /> ├── build &lt;----- run bitbake inside here<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> == Edit the configuration files ==<br /> <br /> Edit $HOME/yocto/poky/build/conf/bblayers.conf<br /> <br /> <br /> # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf<br /> # changes incompatibly<br /> POKY_BBLAYERS_CONF_VERSION = &quot;2&quot;<br /> <br /> BBPATH = &quot;${TOPDIR}&quot;<br /> BBFILES ?= &quot;&quot;<br /> <br /> BBLAYERS ?= &quot; \<br /> /home/koan/yocto/poky/meta \<br /> /home/koan/yocto/poky/meta-poky \<br /> /home/koan/yocto/poky/meta-yocto-bsp \<br /> /home/koan/yocto/poky/meta-openembedded/meta-oe \<br /> &quot;<br /> <br /> Remember also to edit the file $HOME/yocto/poky/build/conf/local.conf<br /> and check the following variables:<br /> <br /> MACHINE ?= &quot;qemuarm&quot;<br /> DISTRO ?= &quot;poky&quot;<br /> PACKAGE_CLASSES ?= &quot;package_ipk&quot;<br /> INHERIT += &quot;rm_work&quot;<br /> <br /> == Building the Image ==<br /> <br /> At this point, you need to select an image to build. <br /> If this is your first build using the Yocto Project, you should try the smallest and simplest image:<br /> <br /> $ bitbake core-image-minimal <br /> <br /> Now you just wait for the build to finish.<br /> <br /> == Starting the QEMU Emulator ==<br /> <br /> Before you start the QEMU emulator, be sure you have already to set up the emulation environment. <br /> <br /> The following command setup the emulation environment and launch QEMU.<br /> <br /> $ runqemu qemuarm<br /> <br /> Or if you prefer, open a new shell terminal, setup the environment again and run<br /> <br /> $ runqemu qemuarm nographic<br /> <br /> == Building cross-compiler ==<br /> <br /> If you want you can create a re-distribuible cross-compiler targeted at your MACHINE.<br /> <br /> $ bitbake meta-toolchain</div> Koan https://wiki.koansoftware.com/index.php?title=Yocto_Project_my_own_quick_start&diff=371 Yocto Project my own quick start 2024-10-05T15:05:23Z <p>Koan: /* The required packages */</p> <hr /> <div>This page is an excerpt from [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start Copyright © 2010-2020 Linux Foundation]<br /> <br /> <br /> == The required packages ==<br /> <br /> Packages and package installation vary depending on your development system. In general, you need to have root access and then install the required packages. The next few sections show you how to get set up with the right packages for Ubuntu.<br /> <br /> If you have different distributions, please refer to the [https://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html Yocto Project Quick Start]<br /> <br /> You must install essential host packages on your build host. <br /> The following command installs the host packages based on an Ubuntu distribution:<br /> <br /> $ sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath \<br /> socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping \<br /> python3-git python3-jinja2 python3-subunit zstd liblz4-tool file locales libacl1<br /> <br /> $ sudo locale-gen en_US.UTF-8<br /> <br /> == Development Code - branch 3.1 'dunfell' LTS ==<br /> <br /> Yocto Project code can be found in the Yocto Project Source Repositories.<br /> To check out current development code using git:<br /> <br /> $ cd $HOME/yocto<br /> $ git clone git://git.yoctoproject.org/poky -b dunfell<br /> <br /> <br /> $ cd $HOME/yocto/poky<br /> $ git clone git://git.openembedded.org/meta-openembedded -b dunfell<br /> <br /> poky/<br /> ├── bitbake<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> == Initializing the Build Environment ==<br /> <br /> From the parent directory your Source Directory, initialize your environment and provide a meaningful Build Directory name:<br /> <br /> $ cd $HOME/yocto/poky<br /> $ source oe-init-build-env<br /> <br /> At this point, the '''build''' directory has been created for you and it is now your current working directory. <br /> This is the default tree you should have to build.<br /> <br /> poky/<br /> ├── bitbake<br /> ├── build &lt;----- run bitbake inside here<br /> ├── contrib<br /> ├── documentation<br /> ├── LICENSE<br /> ├── LICENSE.GPL-2.0-only<br /> ├── LICENSE.MIT<br /> ├── meta<br /> ├── meta-poky<br /> ├── meta-selftest<br /> ├── meta-skeleton<br /> ├── meta-yocto-bsp<br /> ├── oe-init-build-env<br /> ├── README.hardware -&gt; meta-yocto-bsp/README.hardware<br /> ├── README.OE-Core<br /> ├── README.poky -&gt; meta-poky/README.poky<br /> ├── README.qemu<br /> └── scripts<br /> <br /> == Edit the configuration files ==<br /> <br /> Edit $HOME/yocto/poky/build/conf/bblayers.conf<br /> <br /> <br /> # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf<br /> # changes incompatibly<br /> POKY_BBLAYERS_CONF_VERSION = &quot;2&quot;<br /> <br /> BBPATH = &quot;${TOPDIR}&quot;<br /> BBFILES ?= &quot;&quot;<br /> <br /> BBLAYERS ?= &quot; \<br /> /home/koan/yocto/poky/meta \<br /> /home/koan/yocto/poky/meta-poky \<br /> /home/koan/yocto/poky/meta-yocto-bsp \<br /> /home/koan/yocto/poky/meta-openembedded/meta-oe \<br /> &quot;<br /> <br /> Remember also to edit the file $HOME/yocto/poky/build/conf/local.conf<br /> and check the following variables:<br /> <br /> MACHINE ?= &quot;qemuarm&quot;<br /> DISTRO ?= &quot;poky&quot;<br /> PACKAGE_CLASSES ?= &quot;package_ipk&quot;<br /> INHERIT += &quot;rm_work&quot;<br /> <br /> == Building the Image ==<br /> <br /> At this point, you need to select an image to build. <br /> If this is your first build using the Yocto Project, you should try the smallest and simplest image:<br /> <br /> $ bitbake core-image-minimal <br /> <br /> Now you just wait for the build to finish.<br /> <br /> == Starting the QEMU Emulator ==<br /> <br /> Before you start the QEMU emulator, be sure you have already to set up the emulation environment. <br /> <br /> The following command setup the emulation environment and launch QEMU.<br /> <br /> $ runqemu qemuarm<br /> <br /> Or if you prefer, open a new shell terminal, setup the environment again and run<br /> <br /> $ runqemu qemuarm nographic<br /> <br /> == Building cross-compiler ==<br /> <br /> If you want you can create a re-distribuible cross-compiler targeted at your MACHINE.<br /> <br /> $ bitbake meta-toolchain</div> Koan https://wiki.koansoftware.com/index.php?title=Add_a_systemd_service_file_into_a_Yocto_image&diff=370 Add a systemd service file into a Yocto image 2024-09-26T21:50:48Z <p>Koan: /* Add a systemd service file into a Yocto image */</p> <hr /> <div>== Add a systemd service file into a Yocto image ==<br /> <br /> During [https://koansoftware.com/training KOAN training] we use a [https://github.com/koansoftware/meta-training meta-training] layer to create an '''example.bb''' recipe building a '''helloworld''' executable.<br /> <br /> In this article we want to create a recipe to add a systemd service file that starts such '''helloworld''' executable.<br /> <br /> Read more details in [https://koansoftware.com/guide-to-use-systemd-with-yocto-project/ this post] published into [https://koansoftware.com/ KOAN website].<br /> <br /> == Enable systemd in the final image ==<br /> <br /> If '''systemd''' is not enabled by default in your Yocto Project final image you are very likely still using SystemV.<br /> Add the following lines to the '''local.conf''' to enable '''systemd''' as default init manager.<br /> <br /> DISTRO_FEATURES:append = &quot; systemd&quot;<br /> DISTRO_FEATURES_BACKFILL_CONSIDERED += &quot;sysvinit&quot;<br /> VIRTUAL-RUNTIME_init_manager = &quot;systemd&quot;<br /> VIRTUAL-RUNTIME_initscripts = &quot;systemd-compat-units&quot;<br /> <br /> == Create a recipe to add a systemd service file ==<br /> <br /> For the '''helloworld''' application, we don’t necessarily need a service file as this application does not provide services to other parts of this system. However, for example purposes, we will create an autostart script to run hello at boot time. The output from this invocation will be available in the systemd logs using the '''journalctl''' command. This service file can also be manually invoked at runtime.<br /> <br /> First, we will create the service file itself which is read and processed by systemd:<br /> <br /> mkdir -p meta-training/recipes-example/systemd/files/<br /> <br /> Edit a new configuration file <br /> gedit meta-training/recipes-example/systemd/files/hello.service<br /> <br /> containing the following code<br /> <br /> [Unit]<br /> Description=GNU Hello World startup script for KOAN training course<br /> <br /> [Service]<br /> ExecStart=/usr/bin/hello<br /> <br /> [Install]<br /> WantedBy=multi-user.target<br /> <br /> Now let’s add the recipe settings to integrate this into the systemd configuration for our build:<br /> <br /> <br /> Edit a new configuration file <br /> gedit meta-training/recipes-example/systemd/hellosystemd_1.00.bb<br /> <br /> containing the following code<br /> <br /> LICENSE = &quot;CLOSED&quot;<br /> <br /> inherit systemd<br /> <br /> SYSTEMD_AUTO_ENABLE = &quot;enable&quot;<br /> SYSTEMD_SERVICE:${PN} = &quot;hello.service&quot;<br /> <br /> SRC_URI:append = &quot; file://hello.service &quot;<br /> FILES:${PN} += &quot;${systemd_unitdir}/system/hello.service&quot;<br /> <br /> do_install:append() {<br /> install -d ${D}/${systemd_unitdir}/system<br /> install -m 0644 ${WORKDIR}/hello.service ${D}/${systemd_unitdir}/system<br /> }<br /> <br /> Add the recipe to the image editing local.conf<br /> <br /> IMAGE_INSTALL:append = &quot; hellosystemd&quot;<br /> <br /> Now rebuild your image<br /> <br /> bitbake core-image-minimal<br /> <br /> Boot and verify that the service started and the output is visible in the systemd logs.<br /> <br /> &lt;br /&gt;<br /> --------<br /> &lt;br /&gt;<br /> <br /> = UPDATE - Selecting an Initialization Manager =<br /> <br /> Instead of the previous settings you can use the following '''INIT_MANAGER''' variable to select your favorite '''init''' mechanism.<br /> <br /> By default, the Yocto Project uses '''SysVinit''' as the initialization manager. There is also support for '''systemd''', which is a full replacement for init with parallel starting of services, reduced shell overhead, increased security and resource limits for services, and other features that are used by many distributions.<br /> <br /> In comparison to '''SysVinit''', '''systemd''' treats components as units. Using units is a broader concept as compared to using a service. A unit includes several different types of entities. Service is one of the types of entities. The '''runlevel''' concept in '''SysVinit''' corresponds to the concept of a target in '''systemd''', where target is also a type of supported unit.<br /> <br /> In systems with '''SysVinit''' services load sequentially (i.e. one by one) during init and parallelization is not supported. With '''systemd''', services start in parallel. This method can have an impact on the startup performance of a given service, though '''systemd''' will also provide more services by default, therefore increasing the total system boot time. '''systemd''' also substantially increases system size because of its multiple components and the extra dependencies it pulls.<br /> <br /> == Using SysVinit with udev ==<br /> <br /> '''SysVinit''' with the udev device manager corresponds to the default setting in Poky. This corresponds to setting:<br /> <br /> INIT_MANAGER = &quot;sysvinit&quot;<br /> <br /> == Using systemd ==<br /> <br /> The last option is to use '''systemd''' together with the udev device manager. This is the most powerful and versatile solution, especially for more complex systems:<br /> <br /> INIT_MANAGER = &quot;systemd&quot;<br /> <br /> == Controlling systemd from the target command line ==<br /> <br /> Here is a quick reference for controling '''systemd''' from the command line on the target. Instead of opening and sometimes modifying files, most interaction happens through the '''systemctl''' and '''journalctl''' commands:<br /> <br /> systemctl status: show the status of all services<br /> systemctl status &lt;service&gt;: show the status of one service<br /> systemctl [start|stop] &lt;service&gt;: start or stop a service<br /> systemctl [enable|disable] &lt;service&gt;: enable or disable a service at boot time<br /> systemctl list-units: list all available units<br /> journalctl -a: show all logs for all services<br /> journalctl -f: show only the last log entries, and keep printing updates as they arrive<br /> journalctl -u: show only logs from a particular service<br /> <br /> == References ==<br /> <br /> https://docs.yoctoproject.org/dev/ref-manual/variables.html#term-INIT_MANAGER<br /> <br /> https://docs.yoctoproject.org/dev/dev-manual/init-manager.html#init-manager</div> Koan https://wiki.koansoftware.com/index.php?title=Manage_the_GPIO_lines_in_C_with_libgpiod&diff=369 Manage the GPIO lines in C with libgpiod 2024-09-12T09:07:49Z <p>Koan: Created page with &quot;== Manage the GPIO lines in C with libgpiod == Since linux 4.8 the GPIO sysfs interface is deprecated. User space should use the character device instead. &#039;&#039;&#039;libgpiod&#039;&#039;&#039; en...&quot;</p> <hr /> <div>== Manage the GPIO lines in C with libgpiod ==<br /> <br /> Since linux 4.8 the GPIO sysfs interface is deprecated. User space should use the character device instead. <br /> <br /> '''libgpiod''' encapsulates the ioctl calls and data structures behind a straightforward API.<br /> <br /> <br /> == Manage the GPIO using the C language ==<br /> <br /> <br /> - [https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/tree/README libgpiod documentation]<br /> <br /> - [https://github.com/starnight/libgpiod-example libgpiod-example git repo]<br /> <br /> <br /> <br /> == Example ==<br /> <br /> <br /> #include &lt;gpiod.h&gt;<br /> #include &lt;stdio.h&gt;<br /> #include &lt;unistd.h&gt;<br /> <br /> #ifndef CONSUMER<br /> #define CONSUMER &quot;Consumer&quot;<br /> #endif<br /> <br /> int main(int argc, char **argv)<br /> {<br /> char *chipname = &quot;gpiochip0&quot;;<br /> unsigned int line_num = 23; // GPIO Pin #23<br /> unsigned int val;<br /> struct gpiod_chip *chip;<br /> struct gpiod_line *line;<br /> int i, ret;<br /> <br /> chip = gpiod_chip_open_by_name(chipname);<br /> if (!chip) {<br /> perror(&quot;Open chip failed\n&quot;);<br /> goto end;<br /> }<br /> <br /> line = gpiod_chip_get_line(chip, line_num);<br /> if (!line) {<br /> perror(&quot;Get line failed\n&quot;);<br /> goto close_chip;<br /> }<br /> <br /> ret = gpiod_line_request_output(line, CONSUMER, 0);<br /> if (ret &lt; 0) {<br /> perror(&quot;Request line as output failed\n&quot;);<br /> goto release_line;<br /> }<br /> <br /> /* Blink 20 times */<br /> val = 0;<br /> for (i = 20; i &gt; 0; i--) {<br /> ret = gpiod_line_set_value(line, val);<br /> if (ret &lt; 0) {<br /> perror(&quot;Set line output failed\n&quot;);<br /> goto release_line;<br /> }<br /> printf(&quot;Output %u on line #%u\n&quot;, val, line_num);<br /> sleep(1);<br /> val = !val;<br /> }<br /> <br /> release_line:<br /> gpiod_line_release(line);<br /> close_chip:<br /> gpiod_chip_close(chip);<br /> end:<br /> return 0;<br /> }</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=368 Main Page 2024-09-12T08:59:21Z <p>Koan: </p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> <br /> == C/C++ userspace ==<br /> * [[Manage the GPIO lines in C with libgpiod]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=367 Main Page 2024-08-26T07:31:35Z <p>Koan: </p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;</div> Koan https://wiki.koansoftware.com/index.php?title=File:Koan-header.jpg&diff=366 File:Koan-header.jpg 2024-08-26T07:12:58Z <p>Koan: KOAN embedded software engineering</p> <hr /> <div>KOAN embedded software engineering</div> Koan https://wiki.koansoftware.com/index.php?title=File:Koan-header.png&diff=365 File:Koan-header.png 2024-08-26T07:10:49Z <p>Koan: KOAN embedded software engineering</p> <hr /> <div>KOAN embedded software engineering</div> Koan https://wiki.koansoftware.com/index.php?title=MediaWiki:Sidebar&diff=364 MediaWiki:Sidebar 2024-08-26T06:56:47Z <p>Koan: Added link to KOAN website</p> <hr /> <div>* navigation<br /> ** https://www.koansoftware.com|KOAN website<br /> ** mainpage|mainpage-description<br /> ** portal-url|portal<br /> ** currentevents-url|currentevents<br /> ** recentchanges-url|recentchanges<br /> ** randompage-url|randompage<br /> ** helppage|help<br /> * SEARCH<br /> * TOOLBOX<br /> * LANGUAGES</div> Koan https://wiki.koansoftware.com/index.php?title=How_to_run_CVE_checks_using_the_Yocto_Project&diff=363 How to run CVE checks using the Yocto Project 2024-07-18T15:11:00Z <p>Koan: Created page with &quot;== How to run CVE checks using the Yocto Project == Enable CVE check The Yocto Project provides a &#039;&#039;&#039;cve-check&#039;&#039;&#039; class which can be enabled to perform scans on packages for...&quot;</p> <hr /> <div>== How to run CVE checks using the Yocto Project ==<br /> <br /> Enable CVE check<br /> <br /> The Yocto Project provides a '''cve-check''' class which can be enabled to perform scans on packages for public CVE’s. <br /> <br /> It is possible to enable this feature to run a scan of packages but also on images.<br /> <br /> To enable the CVE check you can add the following to e.g local.conf:<br /> <br /> INHERIT += &quot;cve-check&quot;<br /> <br /> Then run<br /> <br /> bitbake --runall cve_check core-image-minimal<br /> <br /> <br /> You will get to the output a list of unpatched CVE’s where found and several log files<br /> <br /> * '''Complete CVE report''' summary created at: .../'''build/tmp/log/cve/cve-summary'''<br /> <br /> * '''Complete CVE JSON report''' summary created at: .../'''build/tmp/log/cve/cve-summary.json'''</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=362 Main Page 2024-07-18T15:05:51Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> * [[How to run CVE checks using the Yocto Project]]<br /> <br /> <br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]</div> Koan https://wiki.koansoftware.com/index.php?title=Replacement_for_command_ldd_on_Linux&diff=361 Replacement for command ldd on Linux 2024-07-12T15:34:48Z <p>Koan: Created page with &quot;== Replacement for command ldd on Linux == Are you looking to install the &#039;&#039;&#039;ldd&#039;&#039;&#039; command on your Linux system but it isn&#039;t available? This is typical when you are using Y...&quot;</p> <hr /> <div>== Replacement for command ldd on Linux ==<br /> <br /> Are you looking to install the '''ldd''' command on your Linux system but it isn't available?<br /> <br /> This is typical when you are using Yocto Project on the target board.<br /> <br /> '''Alternative Method to Check Library Dependencies in Linux<br /> '''<br /> While the '''ldd''' command is a powerful tool for examining library dependencies, there are alternative methods that can provide similar information. <br /> One such method is using the objdump command.<br /> <br /> # LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-armhf.so.3 /usr/bin/gpg<br /> <br /> linux-vdso.so.1 (0xbef3e000)<br /> libz.so.1 =&gt; /lib/libz.so.1 (0xb6f70000)<br /> libbz2.so.1 =&gt; /usr/lib/libbz2.so.1 (0xb6f50000)<br /> libgcrypt.so.20 =&gt; /usr/lib/libgcrypt.so.20 (0xb6ea0000)<br /> libreadline.so.8 =&gt; /usr/lib/libreadline.so.8 (0xb6e50000)<br /> libassuan.so.0 =&gt; /usr/lib/libassuan.so.0 (0xb6e30000)<br /> libnpth.so.0 =&gt; /usr/lib/libnpth.so.0 (0xb6e10000)<br /> libgpg-error.so.0 =&gt; /usr/lib/libgpg-error.so.0 (0xb6de0000)<br /> libc.so.6 =&gt; /lib/libc.so.6 (0xb6cc0000)<br /> libcap.so.2 =&gt; /lib/libcap.so.2 (0xb6ca0000)<br /> libtinfo.so.5 =&gt; /lib/libtinfo.so.5 (0xb6c70000)<br /> /lib/ld-linux-armhf.so.3 (0xb6f98000)<br /> <br /> or<br /> <br /> root@intel-corei7-64:~# LD_TRACE_LOADED_OBJECTS=1 /lib/ld-linux-x86-64.so.2 /usr/bin/aplay<br /> <br /> linux-vdso.so.1 (0x00007ffc005c6000)<br /> libasound.so.2 =&gt; /usr/lib/libasound.so.2 (0x00007f0a498fe000)<br /> libc.so.6 =&gt; /lib/libc.so.6 (0x00007f0a496fe000)<br /> libm.so.6 =&gt; /lib/libm.so.6 (0x00007f0a49620000)<br /> libpthread.so.0 =&gt; /lib/libpthread.so.0 (0x00007f0a4961b000)<br /> librt.so.1 =&gt; /lib/librt.so.1 (0x00007f0a49616000)<br /> /lib/ld-linux-x86-64.so.2 (0x00007f0a49a23000)</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=360 Main Page 2024-07-12T15:28:09Z <p>Koan: /* Problem solving - Howto */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> * [[Replacement for command ldd on Linux]]<br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]</div> Koan https://wiki.koansoftware.com/index.php?title=Set_Proprietary_license_for_a_recipe&diff=359 Set Proprietary license for a recipe 2024-07-11T12:49:31Z <p>Koan: Created page with &quot;== Yocto Project - Set Proprietary license for a recipe == &#039;&#039;&#039;CLOSED&#039;&#039;&#039; is not &#039;&#039;&#039;commercial&#039;&#039;&#039;/&#039;&#039;&#039;proprietary&#039;&#039;&#039;! A common misconception is that setting &#039;&#039;&#039;LICENSE = &quot;CLOSE...&quot;</p> <hr /> <div>== Yocto Project - Set Proprietary license for a recipe ==<br /> <br /> '''CLOSED''' is not '''commercial'''/'''proprietary'''!<br /> <br /> A common misconception is that setting '''LICENSE = &quot;CLOSED&quot;''' means the recipe in question is closed source, respectively '''proprietary'''. <br /> <br /> This is not the actual case: the license value '''CLOSED''' has the meaning “do not care about the license of this recipe”. <br /> <br /> This effectively disables all license tracking for this recipe and should be avoided.<br /> <br /> The correct way to set a '''proprietary''', nonstandard license is<br /> <br /> LICENSE = &quot;Proprietary&quot;<br /> <br /> This often correlates with being commercial, which is expressed by the flag<br /> <br /> LICENSE_FLAGS = &quot;commercial&quot;<br /> <br /> The commercial flag is automatically expanded with the recipe name, and can then be matched, therefore allowed for the build, as outlined in the first paragraph.<br /> <br /> ---<br /> <br /> [https://hub.mender.io/t/understanding-licenses-in-a-yocto-project-build/4848 Credits]</div> Koan https://wiki.koansoftware.com/index.php?title=Main_Page&diff=358 Main Page 2024-07-11T12:46:40Z <p>Koan: /* Yocto Project */</p> <hr /> <div>Welcome on [https://koansoftware.com Koan Software] official wiki<br /> <br /> == DISCLAIMER ==<br /> <br /> '''KoanSoftware(R) and KaeilOS(R) are registered trademarks of KOAN sas - Bergamo, ITALY <br /> <br /> All contents of this website are released under the [http://creativecommons.org/licenses/by-sa/3.0/deed.en_US Creative Commons Attribution-ShareAlike 3.0 Unported License]'''&lt;br&gt;<br /> &lt;br&gt;<br /> <br /> == KOAN Embedded Software Engineering == <br /> <br /> [https://koansoftware.com KOAN] is an Italian software house, specialized in embedded and real time Linux software solutions on RISC platforms of the ARM family (Raspberry, Atmel, Freescale, NXP). Founded on 1996 from diversified experiences, is a supplier of embedded software systems for industrial automation, telecommunications, automotive, mechatronics and aerospace.<br /> <br /> == What is this wiki? == <br /> This is a collection of useful notes about Yocto Project and OpenEmbedded, GNU/Linux distributions aimed for embedded devices developed.<br /> <br /> <br /> == Problem solving - Howto ==<br /> * [[FAQ]]<br /> * [[Setup NFS root filesystem]]<br /> * [[Setup an external toolchain with Yocto]]<br /> * [[Fixing Perl Locale Errors in a Clean Ubuntu Install]]<br /> * [[Using VMware Player to run Linux training]]<br /> * [[Issues running python on Linux]]<br /> * [[Error Initialize GIT git init --initial-branch=main]]<br /> * [[repo issue &quot;def print(self, *args, **kwargs):&quot;]]<br /> <br /> <br /> == Openembedded Core ==<br /> * [[Submit patches to Openembedded]] <br /> * [http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]<br /> * [[OE-Core Standalone Setup]]<br /> <br /> <br /> == Openembedded Debugging ==<br /> * [[Openembedded debugging]]<br /> * [[Packages information list]]<br /> <br /> <br /> == Yocto Project ==<br /> * [[Yocto Project my own quick start]] <br /> * [[Yocto versus Poky versus Angstrom]]<br /> * [http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html Yocto Project reference Manual]<br /> * [http://git.yoctoproject.org/ Yocto source Repositories]<br /> * [http://layers.openembedded.org OpenEmbedded layers index]<br /> * [https://wiki.yoctoproject.org/wiki/Releases Yocto version releases]<br /> * [http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core Migrating metadata to OE-Core]<br /> * [[OE/Yocto prebuilt toolchains]]<br /> * [[Howto build a kernel module out of the kernel tree]]<br /> * [[Howto speed up Yocto build]]<br /> * [[bitbake options]]<br /> * [[Directories and installation variables]]<br /> * [[How to add libstdc++ to a Yocto (Poky) image]]<br /> * [[How to run a script at boot automatically]]<br /> * [[How to run a systemd script at boot automatically]]<br /> * [[Create patches using quilt]]<br /> * [[Building Software from an External Source]]<br /> * [[opkg command options]]<br /> * [[Managing RDEPENDS into a recipe]]<br /> * [[Extract the list of packages into a Yocto image]]<br /> * [[Toaster setup and usage]]<br /> * [[Python assignment operators]]<br /> * [[Skip connectivity checks]]<br /> * [[Set default root password]]<br /> * [[Yocto package management]]<br /> * [[Yocto build on a cluster with IceCC]]<br /> * [[Add native gcc to the target image]]<br /> * [[List IPK package depencencies]]<br /> * [[Yocto Project what I wish I'd known]]<br /> * [[Using devtool to modify recipes in Yocto]]<br /> * [[How to include uEnv.txt in Yocto image]]<br /> * [[Add build information into a Yocto image]]<br /> * [[Add a systemd service file into a Yocto image]]<br /> * [[Yocto Project licenses for LIC_FILES_CHKSUM]]<br /> * [[Set Proprietary license for a recipe]]<br /> * [[Yocto sstate usage summary to the build]]<br /> * [[Upgrade to Yocto honister 3.4]]<br /> * [[Override syntax change from Yocto honister 3.4]]<br /> * [[Modify the linux kernel with configuration fragments in Yocto]]<br /> * [[Add a debug banner in a Yocto recipe]]<br /> * [[How to trace a variable setting with bitbake-getvar]]<br /> * [[How to detect the Yocto version using bitbake]]<br /> * [[Support other languages and keyboards than English in Yocto]]<br /> * [[List the files shipped by your recipe]]<br /> <br /> Many other details are available in the [https://wiki.yoctoproject.org/wiki/Technical_FAQ Yocto Project wiki]<br /> <br /> == Linux kernel ==<br /> * [[Kernel message logging with printk]]<br /> <br /> <br /> == Microsoft .NET and Mono ==<br /> * [[Embedded Linux .NET applications with Yocto]]<br /> <br /> <br /> == Qt ==<br /> * [[Install Qt 5 on Ubuntu]]<br /> <br /> <br /> == Hardware and SBC ==<br /> * [[iMX6 definitive GPIO guide]]<br /> <br /> <br /> == Documents ==<br /> * [[ARM cores list]]<br /> * [[systemd vs sysvinit]]<br /> * [http://linux.koolsolutions.com/2011/02/26/howto-create-and-submit-your-first-linux-kernel-patch/ How to create and submit Linux kernel patch using GIT]<br /> * [[Development with VMware]]<br /> * [[How to Shrink a VirtualBox Virtual Machine]]<br /> <br /> <br /> == About us ==<br /> * [https://koansoftware.com/company/ Who we are]</div> Koan https://wiki.koansoftware.com/index.php?title=Submit_patches_to_Openembedded&diff=357 Submit patches to Openembedded 2024-06-27T09:06:09Z <p>Koan: /* Submit patches to Openembedded (core) */</p> <hr /> <div>== Submit patches to Openembedded (core) == <br /> Contributions to the Yocto Project and OpenEmbedded are very welcome.<br /> You can read the official [[https://docs.yoctoproject.org/dev/contributor-guide/submit-changes.html Yocto contributor-guide]]<br /> <br /> === Set up git ===<br /> <br /> In this case I have a subscribed the openembedded-devel mailing list with a gmail.com account and I sign my patch with another account.<br /> Properly configure git (using tekkub@gmail.com as an example user)<br /> <br /> On Debian / Ubuntu (Note: Fedora uses `yum` OpenSuse uses zypper or yast)<br /> <br /> sudo aptitude install git-core git-email<br /> <br /> These are important to the commit meta-data<br /> <br /> git config --global user.name &quot;Myself Me&quot;<br /> git config --global user.email &quot;myname@mydomain.com&quot;<br /> <br /> Any Google Apps account<br /> <br /> git config --global sendemail.smtpserver smtp.gmail.com<br /> git config --global sendemail.smtpserverport 587<br /> git config --global sendemail.smtpencryption tls<br /> git config --global sendemail.smtpuser tekkupl@gmail.com<br /> <br /> === Committing your patch ===<br /> <br /> Commit with a concise and descriptive message - one that explains your changes in a way others get a short overview without looking at the code. <br /> <br /> Move to oe-core directory or whereever you keep your clone of the repo<br /> cd oe-core<br /> <br /> Add the modified file<br /> git add path/recipename<br /> <br /> Add a comment including my signature &quot;Signed-off-by: Your Name &lt;name@domain.com&gt;&quot;<br /> <br /> git commit -s<br /> recipename: brief description<br /> * Longer description<br /> * if<br /> * required<br /> <br /> <br /> In case you are sending patches for meta-openembedded or any layer other than openembedded-core, please add the appropriate prefix so that it is clear which layer the patch is intended to be applied to:<br /> <br /> git format-patch --subject-prefix=&quot;meta-oe][PATCH&quot; ...<br /> <br /> <br /> Please substitute &quot;PATCH&quot; with &quot;PATCH v2&quot; if you are submitting a revised version after addressing feedback (or v3, v4 etc.) <br /> <br /> For multiple commits you can substitute -1 above with -N (where N is the number of commits) <br /> <br /> <br /> ==== Sending using git-send-email ====<br /> <br /> To send just the top commit on your current branch (substitute mailing list address as appropriate):<br /> <br /> git send-email --to=openembedded-core@lists.openembedded.org patchfilename<br /> <br /> == Community review ==<br /> <br /> Your patch will be sent to the mailing list and should be immediately visible on http://patches.openembedded.org/<br /> .</div> Koan https://wiki.koansoftware.com/index.php?title=Submit_patches_to_Openembedded&diff=356 Submit patches to Openembedded 2024-06-27T08:33:34Z <p>Koan: /* Committing your patch */</p> <hr /> <div>== Submit patches to Openembedded (core) == <br /> Submitting patches to oe-core is slightly different than what was used with oe-classic.<br /> You can read the official [[http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded Openembedded howto]]<br /> <br /> === Set up git ===<br /> <br /> In this case I have a subscribed the openembedded-devel mailing list with a gmail.com account and I sign my patch with another account.<br /> Properly configure git (using tekkub@gmail.com as an example user)<br /> <br /> On Debian / Ubuntu (Note: Fedora uses `yum` OpenSuse uses zypper or yast)<br /> <br /> sudo aptitude install git-core git-email<br /> <br /> These are important to the commit meta-data<br /> <br /> git config --global user.name &quot;Myself Me&quot;<br /> git config --global user.email &quot;myname@mydomain.com&quot;<br /> <br /> Any Google Apps account<br /> <br /> git config --global sendemail.smtpserver smtp.gmail.com<br /> git config --global sendemail.smtpserverport 587<br /> git config --global sendemail.smtpencryption tls<br /> git config --global sendemail.smtpuser tekkupl@gmail.com<br /> <br /> === Committing your patch ===<br /> <br /> Commit with a concise and descriptive message - one that explains your changes in a way others get a short overview without looking at the code. <br /> <br /> Move to oe-core directory or whereever you keep your clone of the repo<br /> cd oe-core<br /> <br /> Add the modified file<br /> git add path/recipename<br /> <br /> Add a comment including my signature &quot;Signed-off-by: Your Name &lt;name@domain.com&gt;&quot;<br /> <br /> git commit -s<br /> recipename: brief description<br /> * Longer description<br /> * if<br /> * required<br /> <br /> <br /> In case you are sending patches for meta-openembedded or any layer other than openembedded-core, please add the appropriate prefix so that it is clear which layer the patch is intended to be applied to:<br /> <br /> git format-patch --subject-prefix=&quot;meta-oe][PATCH&quot; ...<br /> <br /> <br /> Please substitute &quot;PATCH&quot; with &quot;PATCH v2&quot; if you are submitting a revised version after addressing feedback (or v3, v4 etc.) <br /> <br /> For multiple commits you can substitute -1 above with -N (where N is the number of commits) <br /> <br /> <br /> ==== Sending using git-send-email ====<br /> <br /> To send just the top commit on your current branch (substitute mailing list address as appropriate):<br /> <br /> git send-email --to=openembedded-core@lists.openembedded.org patchfilename<br /> <br /> == Community review ==<br /> <br /> Your patch will be sent to the mailing list and should be immediately visible on http://patches.openembedded.org/<br /> .</div> Koan