Bureaucrats, dave_user, Administrators
8,221
edits
Changes
→git protocol error
{{InfoBoxTop}}
{{Applies To Bora}}
{{Applies To BoraX}}
{{Applies To BoraLite}}
{{Applies To Yocto}}
{{InfoBoxBottom}}
{{ImportantMessage|text=As the structure of the BELK/BXELK is based on several tools, it is strongly recommended the reading of [[Logical_structure_of_Bora_and_BoraX_Embedded_Linux_Kits_(BORA_SOM/BELK-L/General/BXELK)Logical_structure_of_BELK|this document]] first to get an overview.
}}
{{ImportantMessage|text=As the XUELK BELK/BXELK kit is based on Yocto, the implementation of the MVM follows the approach described [[Managed_Virtual_Machine_(MVM)#Yocto-based_Linux_distribution|here]]. As such, the reading of [[Managed_Virtual_Machine_(MVM)#Yocto-based_Linux_distribution|this section]] is highly recommended.
}}
}}
<section begin=BELK/> =Introduction=Building the Yocto BSP== ===Quick reference==={| class="wikitable" border="1"|+Repository Information|-! Repository| BSP Manifest| Yocto BSP Layer|-! URL| git@git.dave.eu:bora/bora-bsp.git| git@git.dave.eu:bora/meta-bora.git|-! stable branch| bora-morty| bora-morty|-! stable tag| belk-4.1.4| belk-4.1.4|} {| class="wikitable" border="1"|+Build targets! Name! Description|-| dave-image-devel| This image include tools for development/debugging|-| dave-image-networking| In addition <code>dave-image-devel</code>, this image provides several networking tools|}
As known, in addition to a bootloader and the o.s. kernel, an embedded Linux system needs a root file system to operate. The root file system must contain everything needed to support the Linux system (applications, settings, data, etc.). The root file system is the file system that is contained on the same partition on which the root directory is located. The Linux kernel, at the end of its startup stage, mounts the root file system on the configured root device and finally launches the <code>/sbin/init</code>, the first user space process and "father" of all the other processes.
For more information on the Linux filesystem, please refer to http://www.thegeekstuff.com/2010/09/linux-file-system-structure/.
BELK/BXELK provides one (or more) pre-built root file system, that can be used during the evaluation/development/deployment cycle. For instance, the root file system included in the <code>bora-image-devel</code> image is suited for the development phase, since it provides a relatively rich set of packages including tools and libraries used to debug the application code. The pre-built root file systems are located here: <code>/home/dvdk/<target_name>/rfs/<kit_name></code>.
Besides the pre-built root file systems, BELK/BXELK also provides a rich repository containing pre-built applications and libraries. These packages can be easily installed on the target by using the <code>smart</code> tool. Please refer to [[Advanced_use_of_Yocto_build_system_(BORA_SOM/BELK-L/Development/BXELK)Advanced_use_of_Yocto_build_system#Using_pre-built_package_archive|this section]] for more details. To generate the supported root file systems, the build of the Yocto BSP has to be run. The output of this process is an image containing the U-Boot binary file, the Linux kernel image, and the selected root file system image. The following sections describe in detail how to execute this operation.
For more general information regarding the Yocto build system, please refer the [[:Category:Yocto|dedicated category page]]. ===How to build the Yocto BSP images including the U-Boot binary file, the Linux kernel image, and the target root file system image===
{{ImportantMessage|text=The following procedure requires the access to the DAVE Embedded Systems' git repositories. The access to such repositories is granted to development kit's owners only. Please refer to [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|this page]] for detailed instructions on how to get it.}}
dvdk@dvdk-vm:~/belk$ chmod a+x repo
dvdk@dvdk-vm:~/belk$ ./repo init -u git@git.dave.eu:bora/bora-bsp.git -b bora-morty
dvdk@dvdk-vm:~/belk$ ./repo sync
dvdk@dvdk-vm:~/belk$ source bora-bsp-init-env.sh
</pre>
===== unauthenticated git protocol error =====
{{ImportantMessage|text=Since March 15th, 2022, GitHub stopped accepting DSA keys. RSA keys uploaded after Nov 2, 2021 will work only with SHA-2 signatures.
The deprecated MACs, ciphers, and unencrypted Git protocol are permanently disabled.<br>For more details on this topic, please refer to [[MISC-TN-015:_Yocto_and_git_protocol_error|this Technical Note]].}}
==== Running the build ====
Please note that even the basic root file system requires a few hours to build on a mid/hi range desktop (4-6 cores, 8-12 GiB RAM) also depending on your Internet connection speed (all sources are fetched from the network). Nearly 20GiB of disk space is required for the build. The process may be slowed down significantly since the performances of a virtual machine are reduced if compared to the physical hardware. Thus, it's recommended to check the hardware capabilities of the host system and, when building with Yocto is required, to consider the following options:
* Migrating the build system to a physical machine
* Assuming that the host system has the required resources, extending the hardware capabilities of the default MVM (e.g. adding more cores and disk space).
Once completed the initialization phase, developers can launch the Yocto image build process with the following commands:
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/belk/build$ bitbake <target-image-name>
</pre>
=== Building additional packages ===
To build additional packages the user must first enter the directory where the <code>bora-bsp-init-env.sh</code> is placed and source it
dvdk@dvdk-vm:~/belk$ source bora-bsp-init-env.sh
dvdk@dvdk-vm:~/belk/build$ bitbake bora-image-devel
</pre>
And then can run any of the [http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#usingpoky-components-bitbake bitbake] command.
</pre>
The resulting packages (the default format is ipk) can be found inside ''build/tmp/deploy/rpm''.