[yocto] Booting live images (core-image-minimal-initramfs) on ARM

he syslinux dependency? I have already booted my kernel via u-boot, so it seems unnecessary. Is there another IMAGE_FSTYPE that is compatible with the "initramfs-live-boot" package? cramfs? If so, do I need to change the "init-live.sh" script in "initramfs-live-boot"

Re: [yocto] Booting live images (core-image-minimal-initramfs) on ARM

ocal.conf file. > > By default, INITRAMFS_FSTYPES set to "cpio-gz" in meta/conf/bitbake.conf file. > > > Thanks and Regards, > Yukatharsani J. > > > > -- > *From:* yocto-boun...@yoctoproject.org > on behalf of Paul Knopf &

[yocto] udev automount.rules not running on boot

I am using the automount.rules in udev-extra-conf. If I boot up with a block device plugged in, nothing is mounted. If I plug in the device AFTER the machine is booted, it shows up (in /run/media/*). How do I get these rules to be applied on boot? -- Thanks, Paul Knopf Software Engineer Med X

Re: [yocto] udev automount.rules not running on boot

This causes the "add' event to be re-triggered, making the USB mount on boot. On Thu, May 5, 2016 at 1:57 PM Paul Knopf wrote: > I am using the automount.rules in udev-extra-conf. > > If I boot up with a block device plugged in, nothing is mounted. If I plug >

[yocto] Using multiple versions of package (PACKAGECONFIG) in the same bitbake

ab? Then, I can include this "base-files-overrite-fstab" in the appropriate image recipe? Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Using multiple versions of package (PACKAGECONFIG) in the same bitbake

Thanks, What I winded up doing is using bbappend to remove fstab from base-files. I then created two separate packages with different fstab files, and added each of them into their own image. On Sun, May 8, 2016 at 1:09 PM Khem Raj wrote: > On May 8, 2016, at 6:50 AM, Paul Knopf wrote: &g

[yocto] Recipe that creates empty /var/log directory is auto-mounted to /var/volatile/log

ar/volatile/log. Where is this happening, and why? - pknopf@ubuntu:~/Git/recipes/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/base-files-fstab-normal/1.0-r0/package$ tree . ├── etc │ └── fstab └── var ├── log -> volatile/log └── volatile └── log -

[yocto] Kernel 3.14.28 (imx duallite) will compile under 1.7, but not under 2.0-2.1

gned int level) ^ make[3]: *** [arch/arm/kernel/return_address.o] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [arch/arm/kernel] Error 2 make[1]: *** [sub-make] Error 2 --- Any idea why update Yocto would cause this build error? -- Thanks, Paul

Re: [yocto] Kernel 3.14.28 (imx duallite) will compile under 1.7, but not under 2.0-2.1

Maybe it has something to do with a different make version in the newer versions of Yocto? Maybe this link is relevant? https://github.com/zanezam/boeffla-kernel-cm-bacon/commit/ef4fea130eeb70eff4f3a549fd3f6e9b11437550 On Tue, May 10, 2016 at 10:22 PM Paul Knopf wrote: > I am trying to upd

[yocto] meta-fsl-bsp-release on krogoth

.cgi/imx/meta-fsl-bsp-release.git/log/?h=jethro_4.1.15-1.0.0_ga> README: Update version to 4.1.15-1.1.1 <http://git.freescale.com/git/cgit.cgi/imx/meta-fsl-bsp-release.git/commit/?h=jethro_4.1.15-1.0.0_ga> Lauren Post 4 weeks master <http://git.freescale.com/git/cgit.cgi/imx/m

[yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)

What configs do I need to include in my machine.conf to support this processor? http://www.nvidia.com/object/jetson-tx1-dev-kit.html "require conf/machine/include/arm/arch-*.inc" ? Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medx

Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)

They are using "require conf/machine/include/tune-cortexa15.inc" for the TK1, but the TX1 uses a Cortex A57, not a A15. There is no "tune-cortexa57". Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Sat, May 14, 2016 at 6:08 PM, Khem Raj wr

Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)

_avr32_AVAILABLE=y CT_ARCH_blackfin_AVAILABLE=y CT_ARCH_m68k_AVAILABLE=y CT_ARCH_mips_AVAILABLE=y CT_ARCH_powerpc_AVAILABLE=y CT_ARCH_s390_AVAILABLE=y CT_ARCH_sh_AVAILABLE=y CT_ARCH_sparc_AVAILABLE=y CT_ARCH_x86_AVAILABLE=y - What files do I need to build with this cross-toolchain, inside

Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)

That layer is for the tk1, not the tx1. I am asking for the proper include files to build for the tx1. Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Sat, May 14, 2016 at 6:27 PM, Khem Raj wrote: > On Sat, May 14, 2016 at 3:23 PM, Paul Knopf wrote: > &g

Re: [yocto] machine arch files for Jetson TX1 (Quad-core ARMCortex-A57 MPCore Processor)

_ARCH_TUNE="cortex-a9". Sorry, I'm that familiar with embedded processors. Any guidance would be greatly appreciated. Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Sat, May 14, 2016 at 6:32 PM, Paul Knopf wrote: > That layer is for the tk1, not th

Re: [yocto] How to install 2 or more initscrips out form one recipe?

Take a look at "initscripts_1.0.bb". A lot of init scripts are created in that single recipe. Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com On Fri, Jul 8, 2016 at 9:57 AM, wrote: > Hej > > I run into a problem when I tried to install 3 in

[yocto] Power button not shutting down the OS

ideas why it isn't currently? Thanks, Paul Knopf Software Engineer Med X Change, Inc pkn...@medxchange.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] Patch for custom imager plugin in wic.

>From 136d6214b6fc2c1118dac5b7f3e029ed006fab8a Mon Sep 17 00:00:00 2001 From: Paul Knopf Date: Mon, 21 May 2018 16:56:51 -0400 Subject: [PATCH] Support for changing the imager used in wic. --- scripts/lib/wic/engine.py | 2 +- scripts/wic | 1 + 2 files changed, 2 insertions(+)

Re: [yocto] Patch for custom imager plugin in wic.

Can this change be merged into master? On Mon, May 21, 2018 at 5:00 PM, Paul Knopf wrote: > From 136d6214b6fc2c1118dac5b7f3e029ed006fab8a Mon Sep 17 00:00:00 2001 > From: Paul Knopf > Date: Mon, 21 May 2018 16:56:51 -0400 > Subject: [PATCH] Support for changing the imager

Re: [yocto] Patch for custom imager plugin in wic.

Can someone instruct me on the proper protocol to request a change? On Wed, May 23, 2018 at 1:37 PM, Paul Knopf wrote: > Can this change be merged into master? > > On Mon, May 21, 2018 at 5:00 PM, Paul Knopf > wrote: > >> From 136d6214b6fc2c1118dac5b7f3e029ed006fab8a Mon

Re: [yocto] Patch for custom imager plugin in wic.

Can anybody see this message? lol On Tue, Jun 5, 2018 at 10:05 AM, Paul Knopf wrote: > Can someone instruct me on the proper protocol to request a change? > > On Wed, May 23, 2018 at 1:37 PM, Paul Knopf > wrote: > >> Can this change be merged into master? >> >>

[yocto] Detecting all AUTOREV usages in a build, for reproducible stable production builds.

I want to store/fix AUTOREV values for production builds. I saw BB_CACHE_POLICY, but the format (sqllite) isn't something that can be checked in. Let's say I have an image: bitbake my-image How do I detect any dependency that is using AUTOREV? I'd like to generate a dynamic.conf file that fixes

Re: [yocto] Detecting all AUTOREV usages in a build, for reproducible stable production builds.

onardo Sandoval < leonardo.sandoval.gonza...@linux.intel.com> wrote: > On Thu, 16 Nov 2017 05:06:30 -0500 > Paul Knopf wrote: > > > I want to store/fix AUTOREV values for production builds. I saw > > BB_CACHE_POLICY, but the format (sqllite) isn't something that can be &g

[yocto] Forcing a single task to re-run each build, by default.

I have a task that I would like to be forced to run for every build. NOTE: I am aware of the deploy.bbclass, but I want to not use sstate. Assume I am not using deploy.bbclass. So, let's say I have this. DEPLOYDIR = "${WORKDIR}

[yocto] When are file checksums gathered from files, for tasks? During recipe parsing?

I have a recipe that depends on a deployed output from an image. -- SRC_URI += "file://${DEPLOY_DIR_IMAGE}/my-image-${MACHINE}.wic.update.tar.gz;subdir=update" do_fetch[depends] += "my-image:do_build" -

Re: [yocto] When are file checksums gathered from files, for tasks? During recipe parsing?

This recipe is not an image recipe. It is a recipe that packages up our image for deployment/updates in the field. Your method assumes I am editing the image recipe. On Wed, Nov 22, 2017 at 4:01 AM, Martin Hundebøll wrote: > Hi Paul, > > On 2017-11-22 09:10, Paul Knopf wrote: >

[yocto] buildhistory.bbclass "version-going-backwards" for AUTOINC

I am getting these errors during builds. clear-app-gitAUTOINC+4d250a7fe4-r0 do_packagedata: QA Issue: Package version for package clear-app-locale-es went backwards which would break pack age feeds from (0:git0+66636e50ea-r0 to 0:git0+4d250a7fe4-r0) [version-going-backwards] I think buildhistory.

[yocto] Preventing a variable from being cached

I have a variable that has a dynamic value that is set from python. --- def get_git_position(d): import bb.process (output, error) = bb.process.run("git rev-parse --abbrev-ref HEAD") result = output.rstrip() (output, error) = bb.process.run("git rev-parse HEAD")

[yocto] Allowing a local command to be executed in a recipe.

I have a local utility that is manually installed on our dev/build machines. How do I configure Yocto to let me use this local command? It is located in /usr/local/bin. Lets say the command is "my-command". -- ___ yocto mailing list yocto@yoctoproject.

Re: [yocto] Allowing a local command to be executed in a recipe.

7 PM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 12/06/2017 07:55 PM, Paul Knopf wrote: > >> I have a local utility that is manually installed on our dev/build >> machines. >> >> How do I configure Yocto to let me use this local command? It

Re: [yocto] Preventing a variable from being cached

I take it that this is not possible? On Mon, Dec 4, 2017 at 5:15 PM, Paul Knopf wrote: > I have a variable that has a dynamic value that is set from python. > > --- > def get_git_position(d): > import bb.process > (output, error) = bb.process.

Re: [yocto] Preventing a variable from being cached

based off of HEAD/branch location. On Thu, Dec 7, 2017 at 11:15 AM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 12/07/2017 05:47 PM, Paul Knopf wrote: > >> I take it that this is not possible? >> > > A recipe will rebuild if you change SRCREV or S

Re: [yocto] Preventing a variable from being cached

mpile don't get run. However, if it does change, do_compile does get called (which is what I want). On Thu, Dec 7, 2017 at 3:22 PM, Paul Knopf wrote: > I have all my meta-layers and build conf files checked into a single > repository (submodules for layers). I want a recipe to look at the

Re: [yocto] Preventing a variable from being cached

ION_VERSION:$BUILD_GIT_INFORMATION_VERSION" >> ${D}${sysconfdir}/app-version } do_deploy() { install ${S}/version.json ${DEPLOYDIR}/version.json } addtask do_deploy after do_install FILES_${PN} = "${sysconfdir}/*" On Thu, Dec 7, 2017 at 3:28 PM, Alexander Kanavin <