Re: [yocto] Building Out-of-Tree Modules on the BBB Target

> That's correct. That command only adds the kernel source and > build infrastructure to the SDK, not to your target image. *You'd still* *> need to arrange to have the kernel-devsrc package installed on the* *> target image if you want it on the board's rootfs.* How you arrange > to have the packa

Re: [yocto] Custom eSDK build fails

I see that my custom layers are not being copied in /sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/layers. Though the conf files at /sdk-ext/image/opt/${DISTRO}/${POKY_VERSION}/conf. How can I include my layers also in this? Warm Regards, Priyanshu Sharma On Thu, May 2, 2019 at 3:12 PM Priyanshu S

[yocto] wic cp doesn't work with ext4 partition

Hi, I'm trying to update some artifact after image is build using wic tool. I've tried wic rm image.wic:2/boot/uImage and this works fine (verified with wic ls). While when I want to copy something to ext4 partition (I've tried to copy to vfat boot partition and it works fine) like: wic cp uImage_

Re: [yocto] wic cp doesn't work with ext4 partition

On Wed, May 15, 2019 at 1:47 PM Belisko Marek wrote: > Hi, > > I'm trying to update some artifact after image is build using wic tool. > I've tried wic rm image.wic:2/boot/uImage and this works fine (verified > with wic ls). While when I want to copy something to ext4 partition (I've > tried to c

[yocto] Unable to install additional tools in SDK

Hi all, I need to include in my native sdk the ODB compiler in order to produce some sources. Since it is a nativesdk- only package, I wrote the following nativesdk-odb-compiler_2.5.0.bb ---

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

On Wed, May 15, 2019 at 3:44 AM Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > That's correct. That command only adds the kernel source and > > build infrastructure to the SDK, not to your target image. *You'd still* > *> need to arrange to have the kernel-devsrc package installed

Re: [yocto] problem adding a user

Hi Greg, Well, I suppose I wrote the book you are referring to... Using useradd -p PASSWORD USER takes the password hash for PASSWORD hence the use of openssl in: useadd -p `openssl passwd PASSWORD` USER openssl password creates the password hash using the original crypt hash algorithm if

Re: [yocto] problem adding a user

Hi Rudolf, Thanks for the reply, and the information on how openssl works. I'm trying to create a user with the same group name so the code that I'm using reduces to: EXTRA_USERS_PARAMS = "\ useradd -p `openssl passwd test` sakura; \ usermod -a -G sudo ${SAKURA_USER}; \ " I also,

Re: [yocto] problem adding a user

Hi Greg, > I've also tried both the back-quote and the single-quote, no difference. Help me to understand this. the back-quotes are the right ones. If you use the single ones your password in the /etc/shadow ends up being 'openssl passwd test' (without the quotes), unless the build fails be

Re: [yocto] problem adding a user

Hi Rudolf, 1st, yes I inherit extrausers. Attached are the passwd & shadow files. It shouldn't make any difference, but I'm building this for an RPi3 using the Qt Boot2Qt version of the Yocto environment, distro 2.5.3. Greg From: Rudolf J Streif Sent: Wednes

Re: [yocto] problem adding a user

The ! for the password in /etc/shadow indicates that the account is disabled: sakura:!:18031:0:9:7::: Either there is something wrong with the password generation or it gets disabled by something else. Maybe it's worth trying with a plain image without Boot2Qt or anything else. :rjs

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

> The core-image-kernel-dev image is how I do all my on target > testing when I introduce a new reference kernel for a release. Maybe you are correct. Maybe I should use/add in my local.conf the following: KERNEL_DEV_TOOLS ?= "packagegroup-core-tools-profile packagegroup-core-buildessential kerne

Re: [yocto] problem adding a user

Ok, I had been using the useradd class in a couple of other recipes to allow me to copy files to the sakura user directory and another location, but owned by sakura. That seems to have been what was causing the problem. I had been using the extrausers class in my top level image recipe. So now

Re: [yocto] problem adding a user

Instead of useradd -p `openssl passwd test` sakura which attempts to add the user and set the password which fails if the user already exists, use usermod -p `openssl passwd test` sakura which sets the user's password. :rjs On 5/15/19 1:18 PM, Greg Wilson-Lindberg wrote: Ok, I had

Re: [yocto] problem adding a user

Thank you very much, that got me back on the right path. Maybe I'll see you at the Yocto day at the Embedded Linux Conference. Regards, Greg Wilson-Lindberg Principal Firmware Engineer | Sakura Finetek USA, Inc. 1750 W 214th Street | Torrance, CA 90501 | U.S.A. T: +1 310 783 5075 F: +1 310

Re: [yocto] Building Out-of-Tree Modules on the BBB Target

On Wed, May 15, 2019 at 4:09 PM Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > The core-image-kernel-dev image is how I do all my on target > > testing when I introduce a new reference kernel for a release. > > Maybe you are correct. Maybe I should use/add in my local.conf the > f

[yocto] [meta-raspberrypi] Screen(s) remain black on Raspberry Pi 3 B+

Hi! I'm facing some trouble with the X-Server on the Raspberry Pi 3 B+. No matter if I use a screen on the HDMI port or running the 7" touch screen, they remain black. After testing with sumo - where at least a splash screen was shown - I moved on to thud, as recommended by Andrei Gherzan to sort

Re: [yocto] problem adding a user

Glad to hear that it works now. I am planning on attending the YP DevDay. :rjs On Wed, May 15, 2019, 13:53 Greg Wilson-Lindberg wrote: > Thank you very much, that got me back on the right path. > > Maybe I'll see you at the Yocto day at the Embedded Linux Conference. > > Regards, > > [image: ci

[yocto] Upgrading to Sumo triggered issue with python3 autopackaging - "ERROR: Nothing RPROVIDES 'python3-signal'"

Hello, I upgraded to Sumo(2.5) and now bitbake is complaining that nothing rprovides python3-signal. ERROR: Nothing RPROVIDES 'python3-signal' (but /home/worker/building/sources/meta-bluetooth/recipes-bluetooth/bluetooth-app/bluetooth-app.bb RDEPENDS on or otherwise requires it) After some searc

Re: [yocto] Upgrading to Sumo triggered issue with python3 autopackaging - "ERROR: Nothing RPROVIDES 'python3-signal'"

Hi, Upon further inspection, I found a previous commit that appears to have a bit more information: python: Restructure python packaging and replace it with autopackaging (http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=8d94b9db221d1def42f091b991903faa2d1651ce) The following text appears h

[yocto] [meta-security][PATCH] checksec: update to 1.11.1

* checksec.sh: Updated to 1.11.1 * checksec.sh: resolved issues with readelf * checksec.sh: Added docker images for testing * checksec.sh: Added armhf and aarch64 libc locations * checksec.sh: Replace FS_COUNT with fgrep * checksec.sh: Fixed symbols count in csv * checksec.sh: Fixed RW-RPATH and RW