Raj,


Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it:

dtoverlay=sdio,poll_once=off

I have attached the entire file: config.txt.yocto

However, the Rasbian image does not have any mention of the dtoverlay for the sdio.  Curious. See config.txt attached.


Thanks for the help!

Chuck


On 11/17/20 12:08 AM, Khem Raj wrote:

On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@lists.yoctoproject.org>
wrote:

Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....

I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!

what does /boot/config.txt look like on raspbian and yocto built images

Chuck

Find QSizeF

newSize(qMax(width, 1.0), qMax(height, 1.0));

in src/compositor/extensions/qwaylandxdgshellv5.cpp

and change it to
newSize(qMax((double)width, 1.0), qMax((double)height, 1.0));

and see if it helps.

Hi Guys,

              I am getting qtwayland building issue using dunfell version. can  anybody help me to solve this issue.



Regards,
Sateesh

On 2020-11-18 8:08 a.m., Monsees, Steven C (US) via lists.yoctoproject.org wrote:

I was going through the kernel boot output and saw the following output, can someone tell me why this might be popping up and how I might modify configuration to resolve? :
.
.
LIMWS (BAE LIMWS base distro) 3.0.4 sbcb-default ttyS0
-sh: cannot set terminal process group (1137): Inappropriate ioctl for device
-sh: no job control in this shell

Hi Steve,

Can you describe your build host and environment and what steps you
take to encounter this error? Does it happen with poky/gatesgarth?

What happens if you follow the steps for:

http://docs.yoctoproject.org/brief-yoctoprojectqs/brief-yoctoprojectqs.html

../Randy

.
.
Thanks,
Steve

--
# Randy MacLeod
# Wind River Linux

Hi,

You can use BBMASK variable in your configuration file to prevent bitbake from parsing certain recipes.

For example,
BBMASK = "example.bb"
Here, BitBake ignores the example.bb recipe.

Hope this helps!

On Thu, 19 Nov 2020 at 08:40, NIKHIL PATIL <nikhilvp29@gmail.com> wrote:

Hi ,
If anyone know , please help on these .

It looks like your original email was sent less than an hour ago, give
people some time.

I also recommend looking at the docs yourself.

Thanks,

--
Paul Barker
Konsulko Group

On 11/17/20 9:40 PM, Khem Raj via lists.yoctoproject.org wrote:

Find QSizeF
newSize(qMax(width, 1.0), qMax(height, 1.0));
in src/compositor/extensions/qwaylandxdgshellv5.cpp
and change it to
newSize(qMax((double)width, 1.0), qMax((double)height, 1.0));
and see if it helps.

btw. qtwaywand worked fine with gcc and clang on latest master for rv64
so please describe any local changes you are carrying

On Tue, Nov 17, 2020 at 6:59 PM sateesh m <sateesh0457@gmail.com> wrote:

Hi Guys,

I am getting qtwayland building issue using dunfell version. can anybody help me to solve this issue.



Regards,
Sateesh

Hi,

On Thu, Nov 19, 2020 at 01:13:43PM +0530, NIKHIL PATIL wrote:

Hi ,
I want to add binary in /usr/bin , for these i made own .bb file (
obexpushtest.bb), When i am compiling obexpushtest package separately

You're not compiling a package, you're compiling a recipe named
obexpushtest whose output is packages (one of which is named the same as
the recipe, hence the confusion).

that time it is compiling fine , but when i am adding obexpushtest in
local.conf as a IMAGE_INSTALL , i am getting error.

But here, you're adding a package into an image. Effectively, the first
and second commands you ran don't do the same thing.

## Error :-

/data/nikhil/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-intel/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:01 ago on Thu 19 Nov 2020 05:57:19 AM
UTC.
No match for argument: obexpushtest
Error: Unable to find a match

## obexpushtest.bb file :-

# file recipes-kernel/linux-firmware/linux-firmware_%.bbappend
SUMMARY = "tset_mount example"
SECTION = "test_mount"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"

S = "${WORKDIR}"

SRC_URI += "file://obexpushd"

INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
INHIBIT_PACKAGE_STRIP = "1"

You should probably inherit bin_package but override do_install
(otherwise you'll have an issue with the do_install task coming from the
bin_package bbclass trying to pack your whole ${WORKDIR} (S) which
include way too many files you're not interested in).

do_install_append () {

No need for _append since the following is the only thing your recipe
will do, so better just override do_install.

install -d ${D}/${bindir}
install -m 0644 ${WORKDIR}/obexpushd ${D}/${bindir}
cp ${WORKDIR}/obexpushd ${D}/${bindir}
}

# NOTE: Use "=+" instead of "+=". Otherwise, the file is placed into the
linux-firmware package.
PACKAGES =+ "${PN}-example"
FILES_${PN}-example = "/usr/bin/obexpushd"

Here's the issue, you put your file into the obexpushtest-example and
I'm pretty sure that your obexpushtest package is actually empty and by
default empty packages are removed, hence why the image recipe can't
include this package.

IMHO, no need for your PACKAGES and FILES variables as the default will
put your binary in the obexpushtest package, and since your recipe isn't
creating any other package (explicitly), I don't see the use for a new
package.

Quentin

Hi Ross

On Mon, 2020-11-16 at 14:59 +0000, Ross Burton wrote:

From: Ross Burton <ross.burton@arm.com>

For gatesgarth, this is causing:

FileNotFoundError: [Errno 2] No such file or directory:
'/home/pokybuild/yocto-worker/meta-arm/build/repos/meta-kernel'

https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/472

meta-arm gatesgarth needs meta-kernel?

Thanks,

Anuj

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
 config.json | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/config.json b/config.json
index 11a2664..c57260a 100644
--- a/config.json
+++ b/config.json
@@ -275,9 +275,8 @@
             "TEMPLATE" : "ltp-qemu"
         },
         "meta-arm" : {
-            "NEEDREPOS" : ["poky", "meta-arm", "meta-kernel"],
+            "NEEDREPOS" : ["poky", "meta-arm"],
             "ADDLAYER" : [
-                "${BUILDDIR}/../meta-kernel",
                 "${BUILDDIR}/../meta-arm/meta-arm-toolchain",
                 "${BUILDDIR}/../meta-arm/meta-arm",
                 "${BUILDDIR}/../meta-arm/meta-arm-bsp"

this commit 087a099c288c6bedf368c8756d998172b02b50ad
package: get_package_mapping: avoid dependency mapping if renamed package provides original name
is causing this problem:
NOTE: recipe intronix-introndplus-initramfs-1.0-r0: task do_rootfs: Started
ERROR: intronix-introndplus-initramfs-1.0-r0 do_rootfs: Unable to install packages. Command '/home/dev-build2/yocto/poky/build-xco/tmp/work/xco-poky-linux/intronix-introndplus-initramfs/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/dev-build2/yocto/poky/build-xco/tmp/work/xco-poky-linux/intronix-introndplus-initramfs/1.0-r0/opkg.conf -t /home/dev-build2/yocto/poky/build-xco/tmp/work/xco-poky-linux/intronix-introndplus-initramfs/1.0-r0/temp/ipktemp/ -o /home/dev-build2/yocto/poky/build-xco/tmp/work/xco-poky-linux/intronix-introndplus-initramfs/1.0-r0/rootfs  --force_postinstall --prefer-arch-to-version   --add-ignore-recommends busybox-syslog install base-passwd busybox gptfdisk initrdscripts-intronix packagegroup-luks-initramfs packagegroup-tpm2-initramfs run-postinsts' returned 1:
Collected errors:
 * Solver encountered 1 problem(s):
 * Problem 1/1:
 *   - package initrdscripts-intronix-1.0-r0.corei7-64 requires cgos, but none of the providers can be installed
 *
 * Solution 1:
 *   - do not ask to install a package providing initrdscripts-intronix
 * opkg_finalize_intercepts: Failed to open dir /home/dev-build2/yocto/poky/build-xco/tmp/work/xco-poky-linux/intronix-introndplus-initramfs/1.0-r0/temp/ipktemp//opkg-JQVGKK/opkg-intercept-DEACdL: No such file or directory.
 * rm_r: Failed to open dir /home/dev-build2/yocto/poky/build-xco/tmp/work/xco-poky-linux/intronix-introndplus-initramfs/1.0-r0/temp/ipktemp//opkg-JQVGKK/opkg-intercept-DEACdL: No such file or directory.
 * rm_r: Failed to open dir /home/dev-build2/yocto/poky/build-xco/tmp/work/xco-poky-linux/intronix-introndplus-initramfs/1.0-r0/temp/ipktemp//opkg-JQVGKK: No such file or directory.
Disfavor package: busybox-syslog

cgos is that:
https://git.congatec.com/x86/meta-congatec-x86/-/blob/dunfell/recipes-tools/cgos/cgos-mod_1.03.025.bb

Yes. My understanding is that there's separate branches for each
target? This is for master and not gatesgarth.

Ross

Hi all,

I am using Yocto 2.5 and have a working multilib-enabled image based on poky which includes libgdiplus (64-bit). Due to requirements I had to add the 32-bit version, so I added lib32-libgdiplus to my image recipe. This caused the following error output from bitbake:

WARNING: tmlinux-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_gio_module_cache-lib32' failed, details in /home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/temp/log.do_rootfs
ERROR: tmlinux-image-1.0-r0 do_rootfs: The following packages could not be configured offline and rootfs is read-only: ['100-lib32-libglib-2.0-0']
ERROR: tmlinux-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/temp/log.do_rootfs.30106
ERROR: Task (/home/pelle/development/var-fsl-yocto/sources/meta-tagmaster/recipes-core/images/tmlinux-image.bb:do_rootfs) failed with exit code '1'

While searching for the root cause of this, I discovered a change to update_gio_module_cache (https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/scripts/postinst-intercepts/update_gio_module_cache?id=87631af64032b18ea354b27cc586ec13391bd143) that I thought might help. I applied this change (and the changes from https://github.com/openembedded/openembedded-core/commit/d10fd6ae3fe46290c6e3a5250878966d9f12ca3f for the qemuwrapper-cross_1.0.bb recipe) to my local code, and once again tried building the image. The error message from bitbake is the same, but in the do_rootfs log I find this:

/home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/intercept_scripts-bd1c31820bf736a004f4ebe71461d6fa3ae23f7d97783c8f28a606e086741d8a/update_gio_module_cache-lib32: 15: /home/pelle/development/var-fsl-yocto/build_kodkod/tmp/work/imx8qxpb0_var_som-poky-linux/tmlinux-image/1.0-r0/intercept_scripts-bd1c31820bf736a004f4ebe71461d6fa3ae23f7d97783c8f28a606e086741d8a/update_gio_module_cache-lib32: lib32-qemuwrapper: not found

If I search my tmp directory, there is nothing called "lib32-qemuwrapper", but there is "lib32-qemuwrapper-cross".

Does anyone have any ideas or suggestions?

//Pelle

Intel based platform, quick build under "zeus" does not show issue...

I do not see issue under "rocko"...
Currently porting "rocko" to "zeus", Gatesgarth port is next after zeus runs clean...

I am assuming this banner is part of Yocto, are you now attempting to reserve/use a serial device (ttyS0) here ?

Can you possibly point me as to where this is being done ?, and is this a configurable option ?

Thanks,
Steve

Hi,

On Thu, Nov 19, 2020 at 04:45:19PM +0530, NIKHIL PATIL wrote:

Hi ,
Yours correct only , but the thing is we are taking* binary(obexpushd)*
from other source and only need to copy that binary into* /usr/bin* of our
platform(*intel board*).

Hence how we can achieve these using .bb file ? is there any sample
example .

I gave you what you have to do in the previous mail. Remove the last two
lines of your bb file.

If it does not work, give the full error logs and what you're trying to
achieve and what you have.

Quentin