yocto

bitbake: how does the build system choose the recipe provided by more than one layer

由 别来无恙 提交于 2020-07-02 15:53:51
问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe

bitbake: how does the build system choose the recipe provided by more than one layer

由 梦想的初衷 提交于 2020-07-02 15:52:35
问题 The meta layer provide recipe: meta/recipes-graphics/x11-common/xserver-nodm-init.bb The meta-oe layer provide recipe: meta-oe/recipes-graphics/xserver-nodm-init/xserver-nodm-init_2.0.bb My question is: How the build system select the xserver-nodm-init from the multi-layers? Does it select the xserver-nodm-init recipe according to the layers order in conf/bblayers? 回答1: Layer priority ( BBFILE_PRIORITY ) and recipe version number ( PV , often automated from filename) will decide which recipe

PIN muxing in embedded Linux kernel

由 ♀尐吖头ヾ 提交于 2020-06-28 03:57:34
问题 I am using SAMA5D27-SOM1-EK1 Microchip embedded board. I am using Linux kernel 4.14.73 version that I build using Yocto project. That board has a J27 connector that is used as Image Sensor Interface as shown in 4.3.2 Title, page 31 from the board user guide document, besides, Table 4-16. ISC Connector J27 Pin Assignment, page 32 , shows the connector PIN features. This is a link to the board document : SAMA5D27_User_guide My goal is to change some PIN features of this connector, in order to

PIN muxing in embedded Linux kernel

由 最后都变了- 提交于 2020-06-28 03:57:00
问题 I am using SAMA5D27-SOM1-EK1 Microchip embedded board. I am using Linux kernel 4.14.73 version that I build using Yocto project. That board has a J27 connector that is used as Image Sensor Interface as shown in 4.3.2 Title, page 31 from the board user guide document, besides, Table 4-16. ISC Connector J27 Pin Assignment, page 32 , shows the connector PIN features. This is a link to the board document : SAMA5D27_User_guide My goal is to change some PIN features of this connector, in order to

Yocto recipe python whl package

由 筅森魡賤 提交于 2020-06-23 11:54:47
问题 I am writing a custom yocto recipe that should install a python package from a .whl file. I tried it using a recipe that contains: inherit pypi setuptools PYPI_SRC_URI="http://ci.tensorflow.org/view/Nightly/job/nightly-pi-zero/lastSuccessfulBuild/artifact/output-artifacts/tensorflow-1.5.0rc1-cp27-none-any.whl“ But it does not work that way, it states, that a setup.py file is missing and when trying to write a custom do_compile task that runs pip install <PATH-TO-WHL> it says, that pip is an

Yocto recipe python whl package

由 [亡魂溺海] 提交于 2020-06-23 11:54:12
问题 I am writing a custom yocto recipe that should install a python package from a .whl file. I tried it using a recipe that contains: inherit pypi setuptools PYPI_SRC_URI="http://ci.tensorflow.org/view/Nightly/job/nightly-pi-zero/lastSuccessfulBuild/artifact/output-artifacts/tensorflow-1.5.0rc1-cp27-none-any.whl“ But it does not work that way, it states, that a setup.py file is missing and when trying to write a custom do_compile task that runs pip install <PATH-TO-WHL> it says, that pip is an

Yocto: Where is the source for my project?

由 爷，独闯天下 提交于 2020-06-09 18:57:49
问题 I recently discovered Yocto. I'm able to successfully build an image using the command bitbake fsl-image-gui . But now, I would like to browse the code, the project specific code and the Kernel code for the fsl-image-gui but I cannot figure how ? Where is the source code when I build my Yocto project and how could I browse it ? 回答1: There are two halves of the Yocto setup: The sources/ directory, containing the bitbake recipes and supporting configuration, and The build/ directory, where the

【swupdate文档 三】SWUpdate: 嵌入式系统的软件升级

由 瘦欲@ 提交于 2020-05-08 04:53:56
SWUpdate: 嵌入式系统的软件升级 概述 本项目被认为有助于从存储媒体或网络更新嵌入式系统。但是，它应该主要作为一个框架来考虑，在这个框架中可以方便地向应用程序添加更多的协议或安装程序(在SWUpdate中称为处理程序)。 一个用例是从外部本地媒体(如USB-Pen或sd卡)进行更新。在这种情况下，更新是在没有操作员干预的情况下完成的:它被认为是“一键更新”，软件在复位时启动，只需按下一个键(或者以任何目标可以识别的方式)，自动进行所有检查。最后，更新过程只向操作员报告状态(成功或失败)。 输出可以使用帧缓冲设备显示在LCD上，也可以定向到串行通讯端口上(Linux控制台)。 它通常用于单拷贝方案中，在initrd中运行(用Yocto提供的配方生成)。但是，通过使用软件集合( collections )，可以在双拷贝方案中使用它。 如果启动了远程更新，SWUpdate将启动嵌入式web服务器并等待请求。操作者必须上传一个合适的映像，然后SWUpdate会进行检查并安装。所有输出都通过AJAX通知的方式通知操作人员的浏览器。 功能 总体概览 安装在嵌入式介质上(eMMC、SD、Raw NAND、NOR、SPI-NOR flash) 检查镜像是否可用。镜像以指定的格式(cpio)构建，它必须包含一个描述文件，以描述必须更新的软件。 SWUpdate被认为可以更新设备上的UBI卷

整合Xilinx PetaLinux工程编译和Open Source U- Boot/Linux编译

由 痴心易碎 提交于 2020-04-24 18:08:18
整合PetaLinux工程编译和Open Source U- Boot/Linux编译 作者: 付汉杰 1. 测试环境 2. PetaLinux介绍 3. PetaLinux的安装 4. 提高PetaLinux/Yocto的编译速度 4.1. 下载SState cache 4.2. 设置SState cache 4.3. 利用离线下载文件 4.4. 重用下载文件 4.5. 离线编译 5. Open Source Linux和UBoot 5.1. 保留Linux和UBoot源代码 5.2. 取得Linux源代码 5.3. 取得UBoot源代码 5.4. Open Source 编译Linux 5.5. Open Source编译Linux时间 5.6. Open Source编译UBoot 5.7. Open Source编译UBoot时间 6. 总结 1. 测试环境 Ubuntu 16.04 PetaLinux 2019.1 PetaLinux 2019.1 ZCU106 BSP ZCU106 2. PetaLinux介绍 PetaLinux是Xilinx基于Yocto推出的Linux开发工具。Yocto是业界主流的Linux发行版的构建工具，它不仅可以从源代码编译Linux 内核，还可以编译Linux发行版必须的数以千计的的应用程序，功能非常强大。Yocto的出现

override `DEFAULTTUNE` and other machine configuration parameters

由 亡梦爱人 提交于 2020-04-18 05:48:08
问题 I have a board that requires to change the DEFEAULTTUNE . I did this in my conf/local.conf . As this place actually is reserved for build host configuration as far as I understand I think that this is actually not the best suited place. What would be the right place? Changing the machine configuration of the bsp provider does not seem to be the best idea either... Best regards and thanks for any hint 回答1: As I was explained DEFAULTTUNE is an absolute classic to go into the MACHINE
订阅 yocto