Date   

Re: Enaable to add binary in /usr/bin using .bb file

NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
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




Re: Enaable to add binary in /usr/bin using .bb file

NIKHIL PATIL
 

Hi , 
  for these issue we got solution ,
   obexpushd binary interpreter is on /lib64  folder ,   but in our custom image /lib64 support is not there .
   so we are trying to add lib64 support for our custom image .

   For sato image by default it is taking lib64 support , so it work there.
   

On Thu, Nov 19, 2020 at 6:30 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> wrote:
Hi ,
   Thank You very much , we are able to copy obexpushd to /usr/bin using .bb file.  

  I have one more dout ;
1)  We created our own custom image (bitbake core-image-xxxx) , after flashing image to board . when we run obexpushd binary  it shows as follows :-
    
root@intel-corei7-64:~#
root@intel-corei7-64:~# obexpushd
-sh: /usr/bin/obexpushd: No such file or directory
root@intel-corei7-64:~# cd /usr/bin          
root@intel-corei7-64:/usr/bin# ls | grep obexpush
obexpushd
root@intel-corei7-64:/usr/bin#

Even though binary is there it shows no such file or directory.

2) But when we are flashing a sato image (bitbake core-image-sato-sdk ) , that time obexpushd binary is working fine .
    
    Why it is happening like these ?
    Is there any permission related issue with custom image and sato image ?
 

On Thu, Nov 19, 2020 at 4:48 PM Quentin Schulz <quentin.schulz@...> wrote:
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




qtwayland compile issue 5.15 #dunfell

sateesh m
 

Hi Guys,

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



Regards,
Sateesh


Re: [yocto-autobuilder2 PATCH] config.json: drop redundant meta-kernel mentions

Anuj Mittal
 

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"



Re: qtwayland compile issue 5.15 #dunfell

Khem Raj
 

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.

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


Re: Enaable to add binary in /usr/bin using .bb file

Quentin Schulz
 

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


Re: Raspberry PI enabling MMC1

chuck kamas
 

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




qtwayland compile issue 5.15 #dunfell

sateesh m
 

Hi Guys,

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



Regards,
Sateesh


Re: Raspberry PI enabling MMC1

chuck kamas
 

Making some progress here!


I added a compiled version of the attached device tree and now the mmc1 shows up in my yocto image! Yes! Now I need to find out the secret magic in that tree that I need to add...


Chuck


On 11/18/20 7:59 PM, chuck kamas via lists.yoctoproject.org wrote:

Raj,


I found out how to debug the boot process of the PI from:

https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md

by turning on the boot code debug.

sed -i -e "s/BOOT_UART=0/BOOT_UART=1/" bootcode.bin


I found out that the sdio overlay does not exist!

MESS:00:00:07.868162:0: dtdebug: Failed to open overlay file 'overlays/sdio.dtbo'
MESS:00:00:07.874093:0: Failed to load overlay 'sdio'
MESS:00:00:07.878881:0: brfs: File read: /mfs/sd/overlays/sdio.dtbo
MESS:00:00:07.891322:0: brfs: File read: /mfs/sd/cmdline.txt


So what am I missing on how to turn on the sdio on GPIO22-27? Is it not an overlay and instead a driver/other code/linux config that needs to be set?


Chuck


On 11/17/20 4:29 PM, chuck kamas via lists.yoctoproject.org wrote:
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@...>
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










      




Re: Raspberry PI enabling MMC1

chuck kamas
 

Raj,


I found out how to debug the boot process of the PI from:

https://github.com/raspberrypi/documentation/blob/master/hardware/raspberrypi/bootmodes/README.md

by turning on the boot code debug.

sed -i -e "s/BOOT_UART=0/BOOT_UART=1/" bootcode.bin


I found out that the sdio overlay does not exist!

MESS:00:00:07.868162:0: dtdebug: Failed to open overlay file 'overlays/sdio.dtbo'
MESS:00:00:07.874093:0: Failed to load overlay 'sdio'
MESS:00:00:07.878881:0: brfs: File read: /mfs/sd/overlays/sdio.dtbo
MESS:00:00:07.891322:0: brfs: File read: /mfs/sd/cmdline.txt


So what am I missing on how to turn on the sdio on GPIO22-27? Is it not an overlay and instead a driver/other code/linux config that needs to be set?


Chuck


On 11/17/20 4:29 PM, chuck kamas via lists.yoctoproject.org wrote:
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@...>
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












Re: qtwayland compile issue 5.15 #dunfell

Khem Raj
 

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


Re: [yocto-autobuilder2 PATCH] config.json: drop redundant meta-kernel mentions

Anuj Mittal
 

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"



#yocto #yocto

Monsees, Steven C (US)
 

 

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

.

.

 

Thanks,

Steve


Re: Enaable to add binary in /usr/bin using .bb file

NIKHIL PATIL
 

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 .

On Thu, Nov 19, 2020 at 2:46 PM Quentin Schulz <quentin.schulz@...> wrote:
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


Enaable to add binary in /usr/bin using .bb file

NIKHIL PATIL
 

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 that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## 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"

do_install_append () {
        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"






Re: [PATCH yocto-autobuilder-helper] auh-config: add non-default distro features

Alexander Kanavin
 

ping :)

Alex


On Tue, 10 Nov 2020 at 09:56, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@...> wrote:
This adds systemd and pam related recipes to upstream checks and devtool-driven updates.

Signed-off-by: Alexander Kanavin <alex.kanavin@...>
---
 scripts/auh-config/local.conf.append | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/auh-config/local.conf.append b/scripts/auh-config/local.conf.append
index 9628737..b18590f 100644
--- a/scripts/auh-config/local.conf.append
+++ b/scripts/auh-config/local.conf.append
@@ -1,3 +1,4 @@

 INHERIT += "buildhistory"
 LICENSE_FLAGS_WHITELIST = "commercial"
+DISTRO_FEATURES_append = ' systemd pam'
--
2.29.1





OpenEmbedded Happy Hour November 25 9pm/2100 UTC

Denys Dmytriyenko
 

Hi,

Just a reminder about our upcoming OpenEmbedded Happy Hour on November 25 for
Oceania/Asia timezones @ 2100/9pm UTC (4pm EDT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+November+25&iso=20201125T21

--
Denys


Re: Raspberry PI enabling MMC1

chuck kamas
 

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




Re: Enaable to add binary in /usr/bin using .bb file

NIKHIL PATIL
 

Hi ,
    If anyone know , please help on these .

On Thu, Nov 19, 2020 at 1:14 PM NIKHIL PATIL via lists.yoctoproject.org <nikhilvp29=gmail.com@...> 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 that time it is compiling fine  , but when i am adding obexpushtest in local.conf as a IMAGE_INSTALL , i am getting error.

## 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"

do_install_append () {
        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"









Re: qtwayland compile issue 5.15 #dunfell

Khem Raj
 

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.

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

2041 - 2060 of 53484