yocto

以下仅是我的个人随笔和工作记录： Installing the BSP 1. ==============Mount the ISO image : 2. ==============As a non-root user, install the Yocto: /mnt/cdrom/install There is no uninstall script. To uninstall Yocto you need to remove the <yotco_install_path>/QorIQ-SDK-V1.2-<version>- Setup Host Environment 1). cd <yocto_installation_path>/poky for examole: source ./fsl-setup-poky -m p5020ds -j 2 -t 2 source ./fsl-setup-poky -m mpc8572ds -j 2 -t 2 3.===============kernel configuration================: bitbake -c menuconfig virtual/kernel rebuild kernel: when need a new one (e.g.:last time error if no error don

https://www.yoctoproject.org/ OpenEmbedded core components video 常用短语： Yocto Project : A Linux Foundation project that acts as an umbrella for various efforts to improve Embedded Linux. OpenEmbedded : The build system architecture promoted by the Yocto Project. BitBake : A tool that reads metadata and runs tasks. OpenEmbedded-Core : The common base set of metadata that BitBake uses. This metadata is shared between OpenEmbedded and the Yocto Project. Poky : A reference distribution used for test and release purposes by the Yocto Project. Recipe : Meta data defining how bitbake is to configure,

创建bb file： poky/meta/recipes-devtools/nativesdk-custom-ps1-setting/nativesdk-custom-ps1-setting.bb $ vi ../../poky/meta/recipes-devtools/nativesdk-custom-ps1-setting/nativesdk-custom-ps1-setting.bb LICENSE = "CLOSED" inherit nativesdk do_generate(){ echo "export PS1=\"(yocto-sdk) \${PS1}\"" > ${B}/custom-ps1-setting.sh } do_install(){ install -d ${D}/environment-setup.d/ cp ${B}/custom-ps1-setting.sh ${D}/environment-setup.d/ } addtask generate PACKAGES = "${PN}" FILES_${PN} = "/" do_generate() 创建文件：build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-custom-ps1-setting/1.0-r0/custom-ps1

I am using YOCTO project SUMO release to Build Linux kernel for my embedded board. I want to customize the features of my board. They told me to edit the device tree file. My question is what is the path of this DT file ? And when i modify it, I must rebuild all the kernel using Bitbake ? Thanks. Create the following tree in your layer meta-custom: recipes-kernel/ └── linux ├── linux-at91 │ ├── 0001-my-custom-dt.patch └── linux-at91_%.bbappend In linux-at91_%.bbappend , put FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI += "file://0001-my-custom-dt.patch" To generate 0001-my-custom-dt

I am currently working on a board booting in 64 bit mode using aarch64 and I have a u-boot in 32 bit mode, I would use arm-linux-gnueabihf. I looked around but there's no other way than using a secondary toolchain via: open-embedded tutorial to use a secondary toolchain Nevertheless, impossible to make it work. Intel made a layer (meta-tc-icc) but it's old and I didn't manage to make it work neither. Any idea how to configure it ? So there's a few ways around this. The general answer for your problem is that you need to have two machine.conf files for this particular setup, build 32bit U-Boot

I want to give several files Linux capabilities (e.g. CAP_NET_ADMIN). I am using Yocto and my file system should be read-only and must not be changed after flashing the software (this means pkg_postinst with setcap that would usually work is not possible). Is there any other way to give capabilities to files without changing the file structure after booting the target? pkg_postinst scripts already get executed while building the read-only rootfs, so this approach works. You must ensure that the commands that you call in the script are available in the build host, though, otherwise execution of

I am attempting to write a recipe that would simple copy two files (MyfileA , MyfileB) to a specific directory when the overall image is built. This is what my directory structure looks like: MyDir/MyRecipe.bb MyDir/files/MyfileA MyDir/files/MyfileB I would like the two files to be copied to a folder in home (which would not exist initially hence the directories should be created)The folder lets say is called "Testfolder" This is what my bitbake file looks like DESCRIPTION = "Testing Bitbake file" PR = "r0" SRC_URI = "file://MyfileA \ file://MyfileB " do_install() { install -d MyfileA ~