Bureaucrats, dave_user, Administrators
8,226
edits
Changes
→git protocol error
{{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.
}}
<section begin=BELK/>
==Building the Yocto BSP== ===Quick reference===
{| class="wikitable" border="1"
|+Repository Information
|-
! stable tag
| belk-4.1.04| belk-4.1.04
|}
|}
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.
{{ImportantMessage|text=This process requires a lot of hardware resources in terms of disk storage, RAM, and processing power. For this reason, it also is recommended to consider the use of a physical machine. For more details on this topic, please refer to [[Advanced_use_of_Yocto_build_system_(BORA_SOM/BELK-L/Development/BXELK)Advanced_use_of_Yocto_build_system|this document]] which talks about the advanced use of the Yocto build system.}}
==== Initialize the build environment ====
BELK/BXELK Yocto BSP uses [https://code.google.com/p/git-repo/ git-repo] tool to fetch all the required git repositories. To install it, please use the following commands:
<pre class="workstation-terminal">
dvdk@dvdk-vm:~/belk$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo -1 > repo
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$ 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 ====
-rw-r--r-- 1 dvdk dvdk 5903 Sep 12 16:05 tmp/deploy/rpm/cortexa9hf_neon/memtester-doc-4.3.0-r0.cortexa9hf_neon.rpm
</pre>
<section end=BTELKBELK/>