[yocto] source an environment file in bitbake recipe.

[Pandey, Kamal]

Hi,
Is there any way by which I can use the source command inside a bitbake recipe 
for example if I need to source some environment file before compiling.
source   doesn't seem to work 
Will  the command .   work
 
What exactly I need to inherit for source command to work
Thanks
Kamal Pandey

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] assembler error: missing immediate expression at operand 1 -- `dsb`

[Pandey, Kamal]

Hi 
I was trying to compile the rpmsg-lite library provided by NXP for my ZC102 
board. While compiling I was getting the error as follows:

| Scanning dependencies of target rpmsg-lite
| [ 10%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/rpmsg_lite.c.o
| [ 20%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/rpmsg_ns.c.o
| [ 30%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/virtio/virtqueue.c.o
| [ 40%] Building C object 
rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/porting/environment/rpmsg_env_bm.c.o
| {standard input}: Assembler messages:
| {standard input}:199: Error: missing immediate expression at operand 1 -- 
`dsb'
| {standard input}:216: Error: missing immediate expression at operand 1 -- 
`dsb'
| {standard input}:232: Error: missing immediate expression at operand 1 -- 
`dsb'
| rpmsg-lite/CMakeFiles/rpmsg-lite.dir/build.make:158: recipe for target 
'rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/porting/environment/rpmsg_env_bm.c.o'
 failed
| make[2]: *** 
[rpmsg-lite/CMakeFiles/rpmsg-lite.dir/lib/rpmsg_lite/porting/environment/rpmsg_env_bm.c.o]
 Error 1
| CMakeFiles/Makefile2:122: recipe for target 
'rpmsg-lite/CMakeFiles/rpmsg-lite.dir/all' failed
| make[1]: *** [rpmsg-lite/CMakeFiles/rpmsg-lite.dir/all] Error 2
| Makefile:83: recipe for target 'all' failed
| make: *** [all] Error 2
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_compile (log file is located at 
/home/iepl007/yocto_build/build_openamp/tmp/work/pdm3_zynqmp-pdm3-linux/vhip-bsp-r5-0/2018.3+gitAUTOINC+fb88b32f6e-r0/temp/log.do_compile.32551)
ERROR: Task 
(/home/iepl007/yocto_build/poky/../meta-ifm-vhip-openamp-dev/recipes-rpmsg-lite/vhip_bsp_r5_0/vhip-bsp-r5-0.bb:do_compile)
 failed with exit code '1'

While compiling mannualy without using bitbake recipe I am able to compile 
successfully.
Can someone help me resolve the issue, any pointers will be appreciated.
I am using Xilinx sdk 2018.3
Thanks & Regards
Kamal Pandey 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] configuration for a layer apart from local.conf

[Pandey, Kamal]

Hi,
I want to know if there is any other place where we can set configuration for a 
particular layer, apart from local.conf. For example if I want to set 
LICENSE_FLAGS_WHITELIST can I do that in layer.conf, or do I need to do that in 
local.conf only. Similarly for BBMASK too. So basically my question is, for 
setting the configurations of a particular layer, is there any place where I 
can set those variables inside that layer only?
Best Regards
Kamal Pandey

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ntp recipe not able to install few packages in the rootfs

[Pandey, Kamal]

Hi
I was trying to add ntp package to my image, I used the meta-networking layer 
for the recipe and added the ntp package to my custom image.bb recipe.
After compiling I can see multiple packages in package-split directory of the 
working directory of ntp package, but these binaries are missing in the ROOTFS 
directory.
Below is my ntp recipe:


SUMMARY = "Network Time Protocol daemon and utilities"
DESCRIPTION = "The Network Time Protocol (NTP) is used to \
synchronize the time of a computer client or server to \
another server or reference time source, such as a radio \
or satellite receiver or modem."
HOMEPAGE = "http://support.ntp.org;
SECTION = "net"
LICENSE = "NTP"
LIC_FILES_CHKSUM = "file://COPYRIGHT;md5=e877a1d567a6a58996d2b66e3e387003"

DEPENDS = "libevent"

SRC_URI = 
"http://www.eecis.udel.edu/~ntp/ntp_spool/ntp4/ntp-4.2/ntp-${PV}.tar.gz \
   file://ntp-4.2.4_p6-nano.patch \
   file://reproducibility-fixed-path-to-posix-shell.patch \
   file://reproducibility-respect-source-date-epoch.patch \
   file://ntpd \
   file://ntp.conf \
   file://ntpdate \
   file://ntpdate.default \
   file://ntpdate.service \
   file://ntpd.service \
   file://sntp.service \
   file://sntp \
   file://ntpd.list \
"

SRC_URI[md5sum] = "1522d66574bae14abb2622746dad2bdc"
SRC_URI[sha256sum] = 
"709b222b5013d77d26bfff532b5ea470a8039497ef29d09363931c036cb30454"

inherit autotools update-rc.d useradd systemd pkgconfig

# The ac_cv_header_readline_history is to stop ntpdc depending on either
# readline or curses
EXTRA_OECONF += "--with-net-snmp-config=no \
 --without-ntpsnmpd \
 ac_cv_header_readline_history_h=no \
 --with-yielding_select=yes \
 --with-locfile=redhat \
 --without-rpath \
 "
CFLAGS_append = " -DPTYS_ARE_GETPT -DPTYS_ARE_SEARCHED"

USERADD_PACKAGES = "${PN}"
NTP_USER_HOME ?= "/var/lib/ntp"
USERADD_PARAM_${PN} = "--system --home-dir ${NTP_USER_HOME} \
   --no-create-home \
   --shell /bin/false --user-group ntp"

# NB: debug is default-enabled by NTP; keep it default-enabled here.
PACKAGECONFIG ??= "cap debug refclocks openssl \
${@bb.utils.filter('DISTRO_FEATURES', 'ipv6', d)} \
"
PACKAGECONFIG[openssl] = "--with-openssl-libdir=${STAGING_LIBDIR} \
  --with-openssl-incdir=${STAGING_INCDIR} \
  --with-crypto, \
  --without-openssl --without-crypto, \
  openssl"
PACKAGECONFIG[cap] = "--enable-linuxcaps,--disable-linuxcaps,libcap"
PACKAGECONFIG[readline] = "--with-lineeditlibs,--without-lineeditlibs,readline"
PACKAGECONFIG[refclocks] = "--enable-all-clocks,--disable-all-clocks,pps-tools"
PACKAGECONFIG[debug] = "--enable-debugging,--disable-debugging"
PACKAGECONFIG[mdns] = "ac_cv_header_dns_sd_h=yes,ac_cv_header_dns_sd_h=no,mdns"
PACKAGECONFIG[ipv6] = "--enable-ipv6,--disable-ipv6,"

do_install_append() {
install -d ${D}${sysconfdir}/init.d
install -m 644 ${WORKDIR}/ntp.conf ${D}${sysconfdir}
install -m 755 ${WORKDIR}/ntpd ${D}${sysconfdir}/init.d
install -d ${D}${bindir}
install -m 755 ${WORKDIR}/ntpdate ${D}${bindir}/ntpdate-sync

install -m 755 -d ${D}${NTP_USER_HOME}
chown ntp:ntp ${D}${NTP_USER_HOME}

# Fix hardcoded paths in scripts
sed -i 's!/usr/sbin/!${sbindir}/!g' ${D}${sysconfdir}/init.d/ntpd 
${D}${bindir}/ntpdate-sync
sed -i 's!/usr/bin/!${bindir}/!g' ${D}${sysconfdir}/init.d/ntpd 
${D}${bindir}/ntpdate-sync
sed -i 's!/etc/!${sysconfdir}/!g' ${D}${sysconfdir}/init.d/ntpd 
${D}${bindir}/ntpdate-sync
sed -i 's!/var/!${localstatedir}/!g' ${D}${sysconfdir}/init.d/ntpd 
${D}${bindir}/ntpdate-sync
sed -i 
's!^PATH=.*!PATH=${base_sbindir}:${base_bindir}:${sbindir}:${bindir}!' 
${D}${bindir}/ntpdate-sync
sed -i '1s,#!.*perl -w,#! ${bindir}/env perl,' ${D}${sbindir}/ntptrace
sed -i '/use/i use warnings;' ${D}${sbindir}/ntptrace
sed -i '1s,#!.*perl,#! ${bindir}/env perl,' ${D}${sbindir}/ntp-wait
sed -i '/use/i use warnings;' ${D}${sbindir}/ntp-wait
sed -i '1s,#!.*perl -w,#! ${bindir}/env perl,' ${D}${sbindir}/calc_tickadj
sed -i '/use/i use warnings;' ${D}${sbindir}/calc_tickadj

install -d ${D}/${sysconfdir}/default
install -m 644 ${WORKDIR}/ntpdate.default ${D}${sysconfdir}/default/ntpdate
install -m 0644 ${WORKDIR}/sntp ${D}${sysconfdir}/default/

install -d ${D}/${sysconfdir}/network/if-up.d
ln -s ${bindir}/ntpdate-sync ${D}/${sysconfdir}/network/if-up.d

install -d ${D}${systemd_unitdir}/system
install -m 0644 ${WORKDIR}/ntpdate.service ${D}${systemd_unitdir}/system/
install -m 0644 ${WORKDIR}/ntpd.service ${D}${systemd_unitdir}/system/
install -m 0644 ${WORKDIR}/sntp.service ${D}${systemd_unitdir}/system/

install -d ${D}${systemd_unitdir}/ntp-units.d
install 

[yocto] dhcp and avahi package addition to image

[Pandey, Kamal]

Hello,

I was trying to add avahi and dhcp  to my image. While running $bitbake dhcp 
avahi, everything is working fine but when I add these packages to packagegroup 
 or directly to the image recipe using EXTRA_IMAGE_INSTALL or 
IMAGE_INSTALL_append. It starts giving error.
The error  for avahi is shown below:
ERROR: core-image-special-pdm3-1.0-r0 do_rootfs: Could not invoke dnf. Command 
'/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/recipe-sysroot-native/usr/bin/dnf
 -y -c 
/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs/etc/dnf/dnf.conf
 
--setopt=reposdir=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs/etc/yum.repos.d
 
--repofrompath=oe-repo,/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/oe-rootfs-repo
 
--installroot=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/rootfs
 
--setopt=logdir=/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/temp
 --nogpgcheck install packagegroup-pdm3-apps packagegroup-pdm3-qt 
packagegroup-core-tools-debug packagegroup-core-boot packagegroup-core-x11 
packagegroup-pdm3-base packagegroup-core-tools-profile packagegroup-pdm3-fonts 
base-passwd packagegroup-core-ssh-openssh shadow run-postinsts 
kernel-image-fitimage-4.14.79-yocto-standard' returned 1:
Added oe-repo repo from 
/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Tue 09 Apr 2019 01:49:20 PM UTC.
Error:
Problem: conflicting requests
  - nothing provides avahi needed by packagegroup-pdm3-apps-1.0-r1.noarch

ERROR: core-image-special-pdm3-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/home/iepl007/yocto_build/build_dir/tmp/work/pdm3_zynqmp-pdm3-linux/core-image-special-pdm3/1.0-r0/temp/log.do_rootfs.12565
ERROR: Task 
(/home/iepl007/yocto_build/poky/../meta-pdm3-dev/meta-ifm-pdm3/recipes-core/images/core-image-special-pdm3.bb:do_rootfs)
 failed with exit code '1'


And the error for dhcp is shown below:


ERROR: Nothing RPROVIDES 'dhcp' (but 
/home/iepl007/yocto_build/poky/../meta-pdm3-dev/meta-ifm-pdm3/recipes-core/packagegroups/packagegroup-pdm3-app.bb
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dhcp' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dhcp']
NOTE: Runtime target 'packagegroup-pdm3-apps' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-pdm3-apps', 'dhcp']
ERROR: Required build target 'pdm3-special-swuimage' has no buildable providers.
Missing or unbuildable dependency chain was: ['pdm3-special-swuimage', 
'core-image-special-pdm3', 'packagegroup-pdm3-apps', 'dhcp']

Please provide a solution for this I don't want to clean my sstate-cache or the 
tmp directory. I am ready to debug the corrupted sstate if someone is 
experienced with sstate-cache.
Thanks
Kamal Pandey
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] FileExistsError: [Errorno 17] File Exists

[Pandey, Kamal]

Hi I was trying to compile Weston-6.0 using yocto recipe. For this I backported 
some of the packages from master branch of poky to my own layer. During this 
process, there was one package xorgproto which was used in master branch of 
poky but in rocko branch this package is not there. However a similar package 
is there called xproto. Now there is a conflict between these two packages for 
installing the same headers. I appended xorgproto recipe and removed the 
installation of similar header files. But after this I am getting this error. 
However If I continue to compile these errors are ignored.
Is there any way by which I can correct these errors. Why is there no check in 
staging.bbclass if the file exists or not.
The error is shown below:


ERROR: gstreamer1.0-plugins-base-1.12.2-r0 do_prepare_recipe_sysroot: Error 
executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: 
 0001:
*** 0002:extend_recipe_sysroot(d)
 0003:
File: '/home/iepl007/yocto_build/poky/meta/classes/staging.bbclass', lineno: 
565, function: extend_recipe_sysroot
 0561:dest = newmanifest[l]
 0562:if l.endswith("/"):
 0563:staging_copydir(l, targetdir, dest, seendirs)
 0564:continue
*** 0565:staging_copyfile(l, targetdir, dest, postinsts, 
seendirs)
 0566:
 0567:bb.note("Installed into sysroot: %s" % str(msg_adding))
 0568:bb.note("Skipping as already exists in sysroot: %s" % 
str(msg_exists))
 0569:
File: '/home/iepl007/yocto_build/poky/meta/classes/staging.bbclass', lineno: 
151, function: staging_copyfile
 0147:os.symlink(linkto, dest)
 0148:#bb.warn(c)
 0149:else:
 0150:try:
*** 0151:os.link(c, dest)
 0152:except OSError as err:
 0153:if err.errno == errno.EXDEV:
 0154:bb.utils.copyfile(c, dest)
 0155:else:
Exception: FileExistsError: [Errno 17] File exists: 
'/home/iepl007/yocto_build/build_weston/tmp/sysroots-components/aarch64/xorgproto/usr/include/X11/Xwindows.h'
 -> 
'/home/iepl007/yocto_build/build_weston/tmp/work/aarch64-pdm3-linux/gstreamer1.0-plugins-base/1.12.2-r0/recipe-sysroot/usr/include/X11/Xwindows.h'

ERROR: gstreamer1.0-plugins-base-1.12.2-r0 do_prepare_recipe_sysroot: Function 
failed: extend_recipe_sysroot
ERROR: Logfile of failure stored in: 
/home/iepl007/yocto_build/build_weston/tmp/work/aarch64-pdm3-linux/gstreamer1.0-plugins-base/1.12.2-r0/temp/log.do_prepare_recipe_sysroot.27414
ERROR: Task 
(/home/iepl007/yocto_build/poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.12.2.bb:do_prepare_recipe_sysroot)
 failed with exit code '1'

Best Regards
Kamal Pandey

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] using git am to apply git patch in the workdir of any package+

[Pandey, Kamal]

Hello,
I am trying to modify the src code of a package named say x,
For this I type the command $bitbake x -c devshell.
This leads me to the git repo of the x package(if it is a git repo).
Now I do my changes, commit the changes, and create a patch out of it using git 
format-patch.
Now I want this git patch to be applied via git am  whenever I run bitbake x.
In some packages the patch is applied via git am for example linux-yocto-%.bb, 
but in some cases the patch is not being applied via git am for example 
u-boot%.bb
Is there any setting in bitbake to apply git patches via git am so that it is 
easy to modify the older patches via rebase commands, or we have to create new 
patch every time for a small change and the later patches will have dependency 
on older patches.


Best Regards
Kamal Pandey
Junior Software Engineer
[ifm_logo_sqrs]ifm engineering pvt. ltd.
Survey No. 1/10/16, 3rd floor, Above SBI, Bavdhan Branch, N.D.A. Road, Bavdhan, 
Pune, India - 411021 | Web: www.ifm.com | Phone: 
+91-20-22951910 Extn:215 | CIN: U29213PN2010FTC13676

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake openamp-image-minimal fails to create image

[Pandey, Kamal]

Hi wendy,
Thanks for replying. I have already enabled remoteproc, rpmsg and virtio in the 
kernel configuration.
I have also added
CORE_IMAGE_EXTRA_INSTALL += " \
kernel-modules \
"
In my local.conf file.
I generated BOOT.bin file from bootgen.bif file after adding the rpu firmware:
[destination_cpu=r5-0] 
While booting the device I didn't see r5 code being booted.
Now I am trying Building Linux Applications Using OpenAMP RPMsg in Linux 
Userspace
Using meta-openamp layer.
I found that there is a patch "Add Xilinx ZynqMP R5 remoteproc driver.patch"  
to have a53 and r5 communication. Is this patch required for the purpose of  
openamp in userspace?
This patch was missing in meta-xilinx and I brought it to my custom layer, but 
it failed to apply giving the following error:

error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index
| error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index
| error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index
| error: drivers/firmware/xilinx/zynqmp.c: does not exist in index
| error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index
| error: drivers/firmware/xilinx/zynqmp.c: does not exist in index
| error: include/linux/firmware/xlnx-zynqmp.h: does not exist in index
| [ERROR]: Application of 
.kernel-meta//patches//./0276-Add-Xilinx-ZynqMP-R5-remoteproc-driver.patch 
failed.
|  Patch needs to be refreshed. Sample resolution script:
|  .git/rebase-apply/resolve_rejects
| ERROR: Could not apply patches for pdm3-rev-b-zynqmp.
| ERROR: Patch failures can be resolved in the linux source directory 
/media/iepl/iepl1/work/yocto_build/build_openamp/tmp/work-shared/pdm3-rev-b-zynqmp/kernel-source)
| WARNING: 
/media/iepl/iepl1/work/yocto_build/build_openamp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/linux-yocto/4.14.79+gitAUTOINC+f1d93b219b-r0/temp/run.do_patch.17384:1
 exit 1 from 'exit 1'
| ERROR: Function failed: do_patch (log file is located at 
/media/iepl/iepl1/work/yocto_build/build_openamp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/linux-yocto/4.14.79+gitAUTOINC+f1d93b219b-r0/temp/log.do_patch.17384)

Now the Xilinx document UG1186 never mentioned about this patch or driver. Also 
is this patch for the kernelspace implementation or userspace implementation.
And I am using tftp boot. I think that if r5 was able to boot it should show me 
while booting as I am serially connected to the device.
Please provide any pointers on this. Has anyone implemented this using 
meta-openamp layer and no petalinux.
Thanks
From: Jiaying Liang 
Sent: 10 January 2019 11:14
To: Manjukumar Harthikote Matha ; Pandey, Kamal 
; yocto@yoctoproject.org; meta-xil...@yoctoproject.org
Subject: RE: bitbake openamp-image-minimal fails to create image



From: yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org> 
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Manjukumar Harthikote Matha
Sent: Monday, January 07, 2019 10:51 AM
To: Pandey, Kamal mailto:kamal.pan...@ifm.com>>; 
yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>; 
meta-xil...@yoctoproject.org<mailto:meta-xil...@yoctoproject.org>
Subject: Re: [yocto] bitbake openamp-image-minimal fails to create image

+meta-xilinx mailing list

From: Pandey, Kamal [mailto:kamal.pan...@ifm.com]
Sent: Monday, January 07, 2019 8:59 AM
To: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>; Manjukumar 
Harthikote Matha mailto:manju...@xilinx.com>>
Subject: RE: bitbake openamp-image-minimal fails to create image

Hi,
I solved the problem by using meta-openamp(branch should be similar to xilinx 
version) layer in my yocto project and enabled "libmetal" and "open-amp" 
packages in my image recipe. It compiled successfully.  I also add 
rpmsg-echo-test,  rpmsg-mat-mul , and rpmsg-proxy-app packages in the image and 
it successfully compiled. I am building Linux Application that uses RPMsg in 
user space.
Now the executable generated from echo-test or mat-mul are in my host linux 
master (a53-core). I have also created an r5-application using XSDK.
What is the next step to have a communication between a53 and r5. How to use 
the generated elf file for r5 processor.
Also I have enabled remoteproc, rpmsg, virtio  in kernel configuration.
But while using the command " $modprobe zynqmp_r5_remoteproc", I get the 
following error:

"modprobe: module zynqmp_r5_remoteproc not found in modules.dep"
[Wendy] It doesn't look like the zynqmp_r5_remoteproc driver is compiled or 
maybe it is compiled but not add into the system.

Please check the following:

* If your linux kernel has enabled in your kernel .config

* If you have "kernel-modules" added to your image

o   E.g.:

o   CORE_IMAGE_EXTRA_INSTALL += " \

o   kernel-modules \

o   "
Best Regards,
Wendy
How can I boot the r5 processor and where to store the elf file generated.
From: Manjukumar Hart

[yocto] unable to boot r5 core while using meta-openamp layer for r5 and a53 communication

[Pandey, Kamal]

Hello,
I am trying to run echo_test between r5 and a53 cores. I am following Building 
Linux Applications Using OpenAMP RPMsg in Linux
Userspace (UG1186). I built the Linux a53 side image using yocto and did the 
changes in device tree as per mentioned in UG1186 (userspace part page no. 39).
Also, I updated the bootgen.bif file by adding the line :
[destination_cpu=r5-0] 
I created the RPU firmware elf file using Xilinx SDK and it also contains the 
echo_test along with openamp and libmetal. I did not include this elf file in 
my yocto project.
It is just mentioned in the.bif file with proper path.
While booting the machine I did not see any logs for r5 booting as mention in 
ZynqMP Linux Master running on APU with RPMsg in userspace and 2 RPU slaves  of 
the 
link
 as shown :
Starting application...
Try to init remoteproc resource
Init remoteproc resource succeeded
Waiting for events...
Also, while booting the a53 core and running echo_test-openamp, I get the 
following output :
metal: info:  metal_uio_dev_open: No IRQ for device 3ed4.vring.
metal: info:  metal_uio_dev_open: No IRQ for device 3ed4.vring.
metal: info:  metal_uio_dev_open: No IRQ for device 3ed8.shm.
1 - Send data to remote core, retrieve the echo and validate its integrity ..
Remote proc resource initialized.

and then nothing. I had to press Ctrl+C to abort.
Can somebody explain what am I missing and how can I boot r5 core?

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake openamp-image-minimal fails to create image

[Pandey, Kamal]

Hi,
I solved the problem by using meta-openamp(branch should be similar to xilinx 
version) layer in my yocto project and enabled "libmetal" and "open-amp" 
packages in my image recipe. It compiled successfully.  I also add 
rpmsg-echo-test,  rpmsg-mat-mul , and rpmsg-proxy-app packages in the image and 
it successfully compiled. I am building Linux Application that uses RPMsg in 
user space.
Now the executable generated from echo-test or mat-mul are in my host linux 
master (a53-core). I have also created an r5-application using XSDK.
What is the next step to have a communication between a53 and r5. How to use 
the generated elf file for r5 processor.
Also I have enabled remoteproc, rpmsg, virtio  in kernel configuration.
But while using the command " $modprobe zynqmp_r5_remoteproc", I get the 
following error:

"modprobe: module zynqmp_r5_remoteproc not found in modules.dep"

How can I boot the r5 processor and where to store the elf file generated.
From: Manjukumar Harthikote Matha 
Sent: 07 January 2019 13:53
To: Pandey, Kamal ; yocto@yoctoproject.org
Subject: RE: bitbake openamp-image-minimal fails to create image

Hi Kamal,

Seems like the required kernel modules are missing causing the breakage.
Enable them using kernel menuconfig (bitbake virtual/kernel -c menuconfig) and 
then build the image

Thanks,
Manju

From: yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org> 
[mailto:yocto-boun...@yoctoproject.org] On Behalf Of Pandey, Kamal
Sent: Sunday, January 06, 2019 11:14 PM
To: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: [yocto] bitbake openamp-image-minimal fails to create image

Hello,
I used the meta-openamp layer for r5-a53 communication.
but when I simply ran $bitbake openamp-image-minimal, it gave me the following 
error:

ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Could not invoke dnf. Command 
'/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/dnf
 -y -c 
/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf
 
--setopt=reposdir=/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc/yum.repos.d
 
--repofrompath=oe-repo,/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/oe-rootfs-repo
 
--installroot=/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs
 
--setopt=logdir=/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/temp
 --nogpgcheck install kernel-module-virtio-ring kernel-module-virtio-rpmsg-bus 
kernel-module-uio-pdrv-genirq kernel-module-virtio libopen-amp0 
packagegroup-base-extended kernel-image-fitimage-4.14.79-yocto-standard 
run-postinsts libmetal packagegroup-core-boot kernel-module-remoteproc' 
returned 1:
Added oe-repo repo from 
/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Fri 04 Jan 2019 01:58:31 PM UTC.
No package kernel-module-virtio-ring available.
No package   available.
No package kernel-module-virtio available.
No package   available.
Error: Unable to find a match

ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/temp/log.do_rootfs.7153
ERROR: Task 
(/home/iepl/work/yocto_build/poky/../meta-openamp/recipes-openamp/images/openamp-image-minimal.bb:do_rootfs)
 failed with exit code '1'


Can someone provide me a solution to this problem.
Thanks
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] bitbake openamp-image-minimal fails to create image

[Pandey, Kamal]

Hello,
I used the meta-openamp layer for r5-a53 communication.
but when I simply ran $bitbake openamp-image-minimal, it gave me the following 
error:

ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Could not invoke dnf. Command 
'/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/dnf
 -y -c 
/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc/dnf/dnf.conf
 
--setopt=reposdir=/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs/etc/yum.repos.d
 
--repofrompath=oe-repo,/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/oe-rootfs-repo
 
--installroot=/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/rootfs
 
--setopt=logdir=/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/temp
 --nogpgcheck install kernel-module-virtio-ring kernel-module-virtio-rpmsg-bus 
kernel-module-uio-pdrv-genirq kernel-module-virtio libopen-amp0 
packagegroup-base-extended kernel-image-fitimage-4.14.79-yocto-standard 
run-postinsts libmetal packagegroup-core-boot kernel-module-remoteproc' 
returned 1:
Added oe-repo repo from 
/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/oe-rootfs-repo
Last metadata expiration check: 0:00:00 ago on Fri 04 Jan 2019 01:58:31 PM UTC.
No package kernel-module-virtio-ring available.
No package kernel-module-virtio-rpmsg-bus available.
No package kernel-module-virtio available.
No package kernel-module-remoteproc available.
Error: Unable to find a match

ERROR: openamp-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/media/iepl/iepl1/work/yocto_build/build-open-amp/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/openamp-image-minimal/1.0-r0/temp/log.do_rootfs.7153
ERROR: Task 
(/home/iepl/work/yocto_build/poky/../meta-openamp/recipes-openamp/images/openamp-image-minimal.bb:do_rootfs)
 failed with exit code '1'


Can someone provide me a solution to this problem.
Thanks
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Compilation error while backporting xserver-xorg of poky master branch to rocko

[Pandey, Kamal]

Hello,
I am trying to run Weston 5.0 using poky's rocko branch, so I backported a few 
packages from poky master branch to my own custom layer. But in this process 
xserver-xorg is giving me a compilation error. The contents of the log file are 
as follows:

aarch64-pdm3-linux-gcc  
--sysroot=/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot
 -DHAVE_CONFIG_H -I. -I../../../xorg-server-1.20.1/hw/xwayland -I../../include  
  -I../../../xorg-server-1.20.1/glamor -I../../../xorg-server-1.20.1/dri3 
-DHAVE_DIX_CONFIG_H 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/libdrm
 -DHAVE_DIX_CONFIG_H -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
-Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
-Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
-fno-strict-aliasing -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN 
-DHAS_STICKY_DIR_BIT 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/libdrm
 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/pixman-1
 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/freetype2
 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/X11/dri
 -I../../../xorg-server-1.20.1/include -I../../include 
-I../../../xorg-server-1.20.1/Xext -I../../../xorg-server-1.20.1/composite 
-I../../../xorg-server-1.20.1/damageext -I../../../xorg-server-1.20.1/xfixes 
-I../../../xorg-server-1.20.1/Xi -I../../../xorg-server-1.20.1/mi 
-I../../../xorg-server-1.20.1/miext/sync 
-I../../../xorg-server-1.20.1/miext/shadow  
-I../../../xorg-server-1.20.1/miext/damage -I../../../xorg-server-1.20.1/render 
-I../../../xorg-server-1.20.1/randr -I../../../xorg-server-1.20.1/fb 
-I../../../xorg-server-1.20.1/dbe -I../../../xorg-server-1.20.1/present 
-fvisibility=hidden   -O2 -pipe -g -feliminate-unused-debug-types 
-fdebug-prefix-map=/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0=/usr/src/debug/xserver-xorg/2_1.20.1-r0
 
-fdebug-prefix-map=/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot-native=
 
-fdebug-prefix-map=/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot=
  -pthread -c -o Xwayland-tablet-unstable-v2-protocol.o `test -f 
'tablet-unstable-v2-protocol.c' || echo 
'../../../xorg-server-1.20.1/hw/xwayland/'`tablet-unstable-v2-protocol.c
aarch64-pdm3-linux-gcc  
--sysroot=/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot
 -DHAVE_CONFIG_H -I. -I../../../xorg-server-1.20.1/hw/xwayland -I../../include  
  -I../../../xorg-server-1.20.1/glamor -I../../../xorg-server-1.20.1/dri3 
-DHAVE_DIX_CONFIG_H 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/libdrm
 -DHAVE_DIX_CONFIG_H -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
-Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
-Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
-fno-strict-aliasing -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN 
-DHAS_STICKY_DIR_BIT 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/libdrm
 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/pixman-1
 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/freetype2
 
-I/media/iepl/iepl1/work/yocto_build/build-weston/tmp/work/aarch64-pdm3-linux/xserver-xorg/2_1.20.1-r0/recipe-sysroot/usr/include/X11/dri
 

[yocto] upgrading packages in yocto

[Pandey, Kamal]

I want to upgrade some packages of poky/meta/recipes-graphics/ like 
weston_2.0.0.bb to weston_4.0.0.bb. Also I don't want any changes to be made in 
poky/meta layer. What is the best way of doing these kinds of upgradations. I 
think bbappend here will create problems as the SRC_URI and other variables use 
the PV from recipe name to fulfil some operations.
The other thing I can do is create a weston_4.0.0.bb file in my own custom 
layer and work but then I don't know how to disable the older(original) 
weston_2.0.0.bb file.
What will be the best method to upgrade packages. One thing to remind you that 
the SRC_URI is not a repository , it's a tarball repo. So I directly can't 
replace the SRC_URI in .bbappend file.
Any leads regarding this will be appreciated.

-Original Message-
From: yocto-boun...@yoctoproject.org  On Behalf 
Of yocto-requ...@yoctoproject.org
Sent: 30 September 2018 00:30
To: yocto@yoctoproject.org
Subject: yocto Digest, Vol 96, Issue 79

Send yocto mailing list submissions to
yocto@yoctoproject.org

To subscribe or unsubscribe via the World Wide Web, visit

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproject.org_listinfo_yocto=DwICAg=riR7jviByh3sGm7GIiSlHkFN0_aSATB6A8x0nHa2EM0=B4t2KSJ3IM1b9sK9gvCmTFe5JX-rxgD15fYh5lG11MM=Zi9dlMz5JoZfKdwcbr7eV_JK7qB8SJTPYP9LdRWnlG8=RQp-3-7SeXpR_ysQqD1qg5XYb2ycNNJlz5k63RsTovE=
or, via email, send a message with subject or body 'help' to
yocto-requ...@yoctoproject.org

You can reach the person managing the list at
yocto-ow...@yoctoproject.org

When replying, please edit your Subject line so it is more specific than "Re: 
Contents of yocto digest..."

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] error while installing extended sdk

[Pandey, Kamal]

Hi,
I was trying to create an extended SDK for my image. It was successfully 
created, without any errors. But while installing the sdk I got a few warnings 
as shown below:
WARNING: The weston:do_fetch sig is computed to be 
b87adbcf88b1b506b444c099fad499f3, but the sig is locked to 
3bf1dd4b3c15d444a4b15cd0e4c44f59 in SIGGEN_LOCKEDSIGS_t-aarch64
The weston:do_unpack sig is computed to be ddb8cc67d714bc33f8260581fa933ce1, 
but the sig is locked to 2b59dca41c70645ab73c6a6fc6210054 in 
SIGGEN_LOCKEDSIGS_t-aarch64
The weston:do_populate_lic sig is computed to be 
a46b0e6f8735528805144f19ab9c3511, but the sig is locked to 
7e1757176bd889c18cd0e5f423149e8d in SIGGEN_LOCKEDSIGS_t-aarch64
The weston:do_configure sig is computed to be 5bf71ab53d26d6e531350c06f02c2319, 
but the sig is locked to 6c0a7295a257143610ca86020105b80a in 
SIGGEN_LOCKEDSIGS_t-aarch64
The weston:do_compile sig is computed to be ea519407dd4c25cfb7d15b99f0d3afea, 
but the sig is locked to af49c954f1d0e31fddb47ad8a681c70c in 
SIGGEN_LOCKEDSIGS_t-aarch64
The weston:do_package sig is computed to be 8a15931568dcf12530de0601d4a69cba, 
but the sig is locked to bc7f446278eb3efe981ead7857cdc460 in 
SIGGEN_LOCKEDSIGS_t-aarch64
The weston:do_package_write_rpm sig is computed to be 
2fbacf175eaf34adb31e04d9af6692c3, but the sig is locked to 
7cb00a81b8d746a92be64cbbbf8d2c25 in SIGGEN_LOCKEDSIGS_t-aarch64
But the installation was completed without any errors. I checked the 
sysroot/usr/bin directory inside the installed esdk and found Weston bin files 
were not there.
Also while executing devtool command after source the env file I am getting 
this error:
/home/kamal/work/wayland_esdk/sysroots/x86_64-pdm3sdk-linux/usr/bin/python3: 
line 5: 
/home/kamal/work/wayland_esdk/sysroots/x86_64-pdm3sdk-linux/usr/bin/python3.5.real:
 No such file or directory.
Although there is a file in that directory.
One thing to note that I am using python of anaconda not my system one.
Any leads will be appreciated.
Thanks

Best Regards
Kamal Pandey
Junior Software Engineer
[ifm_logo_sqrs]ifm engineering pvt. ltd.
Survey No. 1/10/16, 3rd floor, Above SBI, Bavdhan Branch, N.D.A. Road, Bavdhan, 
Pune, India - 411021 | Web: www.ifm.com | Phone: 
+91-20-22951910 Extn:215 | CIN: U29213PN2010FTC13676

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Error while sdk creation of custom weston-wayland image

[Pandey, Kamal]

Hi,
I am trying to create sdk for core-image-weston image. Although my image is 
compiled and $bitbake core-image-weston -c populate_sdk  executed till 99%. But 
throwing error almost in the end as follows:

Build Configuration:
BB_VERSION   = "1.36.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-pdm3-linux"
MACHINE  = "pdm3-rev-b-zynqmp"
DISTRO   = "pdm3-linux"
DISTRO_VERSION   = "0.2.0.0"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta = "rocko:f7a8c088ae1db6c2ebaa5e0aa4c7c8ed352bb045"
meta-xilinx-bsp  
meta-xilinx-contrib  = "rel-v2018.1:8710079c0720086c081f3340c2c233ab0e874cfe"
meta-xilinx-tools= "rel-v2018.1:93d6b87bdc451ee81d6d716809e0d7e9bc3b7021"
meta-oe  
meta-perl
meta-python  
meta-multimedia  
meta-networking  
meta-filesystems 
meta-webserver   = "rocko:352531015014d1957d6444d114f4451e241c4d23"
meta-ifm-pdm3-bsp
meta-ifm-pdm3= 
"rocko-2.4-xlnx2018.1+wayland:959d08d1b1ad575803c62b0029779798ad6bf8b0"
meta-qt5 = "rocko:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"

Initialising tasks: 100% 
|###|
 Time: 0:00:10
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-weston-pdm3-1.0-r0 do_populate_sdk: Could not invoke dnf. 
Command 
'/home/kamal/work/yocto_build/poky/build_weston/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/core-image-weston-pdm3/1.0-r0/recipe-sysroot-native/usr/bin/dnf
 -y -c 
/home/kamal/work/yocto_build/poky/build_weston/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/core-image-weston-pdm3/1.0-r0/sdk/image/etc/dnf/dnf.conf
 
--setopt=reposdir=/home/kamal/work/yocto_build/poky/build_weston/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/core-image-weston-pdm3/1.0-r0/sdk/image/etc/yum.repos.d
 
--repofrompath=oe-repo,/home/kamal/work/yocto_build/poky/build_weston/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/core-image-weston-pdm3/1.0-r0/oe-sdk-repo
 
--installroot=/home/kamal/work/yocto_build/poky/build_weston/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/core-image-weston-pdm3/1.0-r0/sdk/image
 
--setopt=logdir=/home/kamal/work/yocto_build/poky/build_weston/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/core-image-weston-pdm3/1.0-r0/temp
 --nogpgcheck install nat
 ivesdk-dbus nativesdk-dbus-glib nativesdk-libpam 
nativesdk-packagegroup-qt5-toolchain-host nativesdk-packagegroup-sdk-host 
nativesdk-qtbase-tools packagegroup-cross-canadian-pdm3-rev-b-zynqmp' returned 
1:
Added oe-repo repo from 
/home/kamal/work/yocto_build/poky/build_weston/tmp/work/pdm3_rev_b_zynqmp-pdm3-linux/core-image-weston-pdm3/1.0-r0/oe-sdk-repo
Last metadata expiration check: 0:00:01 ago on Sat 01 Sep 2018 11:08:11 AM UTC.
Dependencies resolved.

 Package Arch Version Repository
   Size

Installing:
 nativesdk-dbus-1x86_64_nativesdk 1.10.20-r0  oe-repo 111 k
 nativesdk-libdbus-glib-1-2  x86_64_nativesdk 0.108-r0oe-repo  56 k
 nativesdk-libpamx86_64_nativesdk 1.3.0-r5oe-repo  34 k
 nativesdk-packagegroup-qt5-toolchain-host
 x86_64_nativesdk 1.0-r0  oe-repo 5.6 k
 nativesdk-packagegroup-sdk-host x86_64_nativesdk 1.0-r12 oe-repo 5.7 k
 nativesdk-qtbase-tools  x86_64_nativesdk 5.9.6+git0+9c50112304-r0
  oe-repo 4.2 M
 packagegroup-cross-canadian-pdm3-rev-b-zynqmp
 x86_64_nativesdk 1.0-r0  oe-repo 5.6 k
Installing dependencies:
 binutils-cross-canadian-aarch64 x86_64_nativesdk 2.29.1-r0   oe-repo 4.8 M
 gcc-cross-canadian-aarch64  x86_64_nativesdk 7.3.0-r0oe-repo  16 M
 gdb-cross-canadian-aarch64  x86_64_nativesdk 8.0-r0  oe-repo 1.9 M
 meta-environment-pdm3-rev-b-zynqmp
 x86_64_nativesdk 1.0-r8  oe-repo  11 k
 nativesdk-autoconf  x86_64_nativesdk 2.69-r11oe-repo 276 k
 nativesdk-automake  x86_64_nativesdk 1.15.1-r0   oe-repo 324 k
 nativesdk-cmake x86_64_nativesdk 3.8.2-r0oe-repo 3.8 M
 nativesdk-dbx86_64_nativesdk 1:5.3.28-r1 oe-repo 454 k
 nativesdk-dnf   x86_64_nativesdk 2.6.3-r0oe-repo 165 k
 nativesdk-dtc   x86_64_nativesdk 1.4.4-r0oe-repo  58 k
 nativesdk-elfutils  x86_64_nativesdk 0.170-r0oe-repo 112 k
 nativesdk-flex  

[yocto] building weston wayland custom image with QT

[Pandey, Kamal]

I was trying to create sdk for Weston wayland image but iam facing these errors 
as shown below:

bitbake -c populate_sdk core-image-weston-pdm3

Build Configuration:
BB_VERSION   = "1.36.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-pdm3-linux"
MACHINE  = "pdm3-rev-b-zynqmp"
DISTRO   = "pdm3-linux"
DISTRO_VERSION   = "0.2.0.0"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta 
meta-poky
meta-selftest
meta-skeleton
meta-yocto-bsp   = "rocko:2731fd35d5570263bc004ab16acf4acb0d94422b"
meta-xilinx-bsp  
meta-xilinx-contrib  = "rel-v2018.1:e7a6531bd8fc9ce5797be082c8478a2701c3766a"
meta-xilinx-tools= "rel-v2018.1:93d6b87bdc451ee81d6d716809e0d7e9bc3b7021"
meta-oe  
meta-perl
meta-python  
meta-multimedia  
meta-networking  
meta-filesystems 
meta-webserver   = "rocko:352531015014d1957d6444d114f4451e241c4d23"
meta-ifm-pdm3-bsp
meta-ifm-pdm3= 
"rocko-2.4-xlnx2018.1+wayland:8008e389aeda83088c57577471bf040221255887"
meta-qt5 = "rocko:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
meta-codesys = "master:08029b5f9add1c414e6341bcea52fe532fb3c6b7"

Initialising tasks: 100% 
|###|
 Time: 0:00:06
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: qtwayland-5.9.6+gitAUTOINC+8c5999644c-r0 do_configure: Error calling 
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/recipe-sysroot-native/usr/bin/qt5/qmake
 -makefile -o Makefile   
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/git/qtwayland.pro
  --   -no-feature-drm-egl-server -no-feature-libhybris-egl-server 
-no-feature-wayland-brcm -feature-wayland-client -feature-wayland-egl 
-feature-wayland-server -feature-xcomposite-egl -feature-xcomposite-glx
ERROR: qtwayland-5.9.6+gitAUTOINC+8c5999644c-r0 do_configure: Function failed: 
do_configure (log file is located at 
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/temp/log.do_configure.3215)
ERROR: Logfile of failure stored in: 
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/temp/log.do_configure.3215
Log data follows:
| DEBUG: Executing shell function qmake5_base_preconfigure
| Previously configured separate build directory detected, cleaning 
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/build
| DEBUG: Shell function qmake5_base_preconfigure finished
| DEBUG: Executing shell function do_configure
| NOTE: qmake prevar substitution: '  '
| NOTE: qmake configure substitution: '  -no-feature-drm-egl-server 
-no-feature-libhybris-egl-server -no-feature-wayland-brcm 
-feature-wayland-client -feature-wayland-egl -feature-wayland-server 
-feature-xcomposite-egl -feature-xcomposite-glx'
| Info: creating stash file 
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/build/.qmake.stash
| Info: creating cache file 
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/build/.qmake.cache
| 
| Running configuration tests...
| Checking for Wayland client library... yes
| Checking for Wayland cursor library... yes
| Checking for wayland-scanner... yes
| Checking for Wayland EGL library... yes
| Checking for XComposite... yes
| Checking for wayland-server... yes
| Done running configuration tests.
| 
| Configure summary:
| 
| Qt Wayland Drivers:
|   EGL  yes
|   Raspberry Pi ... no
|   XComposite EGL . yes
|   XComposite GLX . no
|   DRM EGL  no
|   libhybris EGL .. no
| Qt Wayland Client  yes
| Qt Wayland Compositor  yes
| 
| ERROR: Feature 'xcomposite-glx' was enabled, but the pre-condition 
'features.wayland-client && features.opengl && !features.opengles2 && 
features.xlib && libs.xcomposite && libs.glx' failed.
| 
| ERROR: Feature 'xcomposite-glx' was enabled, but the pre-condition 
'features.wayland-server && features.opengl && !features.opengles2 && 
libs.xcomposite && libs.glx' failed.
| 
| Check config.log for details.
| ERROR: Error calling 
/home/iepl/work/yocto_build/poky/build-weston/tmp/work/aarch64-pdm3-linux/qtwayland/5.9.6+gitAUTOINC+8c5999644c-r0/recipe-sysroot-native/usr/bin/qt5/qmake
 -makefile -o Makefile   

Re: [yocto] chromium is compiling but is not able to add in the image

[Pandey, Kamal]

Thankyou very much for the response.
core-image-minimal-pdm3  is a custom image made from proprietary meta-pdm3 
layer. This layer is used to create images and packages for custom embedded 
device.
I ve enabled x11 in conf/local.conf file.
IMAGE_INSTALL_append = " x11  \
 chromium \  

and yes that device has a mali GPU support.

-Original Message-
From: Stefano Babic  
Sent: 23 August 2018 21:26
To: Pandey, Kamal 
Cc: Ross, Fedor ; Barth, Steffen ; 
Marek Vasut 
Subject: Re: [yocto] chromium is compiling but is not able to add in the image

Hi Kamal,

(out of list):

I just seen your post to Yocto'sML...

On 21/08/2018 15:28, Pandey, Kamal wrote:
> I tried adding chromium package via the meta-browser layer. It is 
> compiling when I run */$ bitbake chromium/*/./ But when I run 
> */$bitbake core-image-minimal-pdm3/*.

..but I can understand that nobody has the small idea what
core-image-minimal-pdm3 is !

> It’s not adding chromium to the image and throwing errors as shown 
> below:
> 
>  
> 
> Loading cache: 100%
> |#
> |#
> |##|
> Time: 0:00:00
> 
> Loaded 3249 entries from dependency cache.
> 
> Parsing recipes: 100%
> |#
> |#
> ||
> Time: 0:00:02
> 
> Parsing of 2368 .bb files complete (2352 cached, 16 parsed). 3260 
> targets, 99 skipped, 10 masked, 0 errors.
> 
> WARNING: No recipes available for:
> 
>  
> /home/iepl/work/yocto_build/meta-xilinx/meta-xilinx-contrib/recipes-ke
> rnel/linux/linux-xlnx_2018.1.bbappend
> 
>  
> /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-extend
> ed/images/swupdate-gui-image.bbappend
> 
>  
> /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-suppor
> t/rescuegui/rescuegui_%.bbappend
> 
>  
> /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-suppor
> t/swupdate/swupdate_%.bbappend
> 
>  
> /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3/recipes-mono/mono/
> mono-native_5.4.1.6.bbappend
> 

Your bblayers.conf is maybe a mess. They are solved in meta-ifm-pdm3 and 
meta-ifm-pdm3-bsp

> NOTE: Resolving any missing task queue dependencies
> 
> ERROR: Nothing RPROVIDES 'chromium' (but 
> /home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-core/i
> mages/core-image-minimal-pdm3.bb
> RDEPENDS on or otherwise requires it)
> 
> NOTE: Runtime target 'chromium' is unbuildable, removing...
> 
> Missing or unbuildable dependency chain was: ['chromium']
> 
> ERROR: Required build target 'core-image-minimal-pdm3' has no 
> buildable providers.
> 
> Missing or unbuildable dependency chain was: 
> ['core-image-minimal-pdm3', 'chromium']
> 
>  
> 
> Summary: There was 1 WARNING message shown.
> 
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> 
> The bblayers.conf file is taken care off.
> 
> I’ve added the line
> 
> */IMAGE_INSTALL_append = “ chromium”/* in the local.conf file along 
> with
>  */LICENSE_FLAG_WHITELIST = /**//**//*
> 
> */" commercial_libav commercial_x264 commercial/**/"/*
> 
> Apart from that Firefox is able to compile and it’s been added to the 
> image. Can somebody tell me what is causing this issue.
> 
>  
> 

Apart of that, are you trying to get in running with something provided by 
Marek for Mali (GPU support) ? I just warn that Chromium without GPU is very 
slow and pratically unusable. Even with GPU support it looks quite slow...

Are you enable x11 ? As far as I know, chromium is running just on top of x11 - 
I added Marek in CC that can sugest something else.

Best regards,
Stefano Babic


--
=
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de 
=

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] chromium is compiling but is not able to add in the image

[Pandey, Kamal]

I tried adding chromium package via the meta-browser layer. It is compiling 
when I run $ bitbake chromium . But when I run $bitbake 
core-image-minimal-pdm3. It’s not adding chromium to the image and throwing 
errors as shown below:

Loading cache: 100% 
||
 Time: 0:00:00
Loaded 3249 entries from dependency cache.
Parsing recipes: 100% 
|##|
 Time: 0:00:02
Parsing of 2368 .bb files complete (2352 cached, 16 parsed). 3260 targets, 99 
skipped, 10 masked, 0 errors.
WARNING: No recipes available for:
  
/home/iepl/work/yocto_build/meta-xilinx/meta-xilinx-contrib/recipes-kernel/linux/linux-xlnx_2018.1.bbappend
  
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-extended/images/swupdate-gui-image.bbappend
  
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/rescuegui/rescuegui_%.bbappend
  
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-support/swupdate/swupdate_%.bbappend
  
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3/recipes-mono/mono/mono-native_5.4.1.6.bbappend
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'chromium' (but 
/home/iepl/work/yocto_build/meta-pdm3/meta-ifm-pdm3-bsp/recipes-core/images/core-image-minimal-pdm3.bb
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'chromium' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['chromium']
ERROR: Required build target 'core-image-minimal-pdm3' has no buildable 
providers.
Missing or unbuildable dependency chain was: ['core-image-minimal-pdm3', 
'chromium']

Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
The bblayers.conf file is taken care off.
I’ve added the line
IMAGE_INSTALL_append = “ chromium” in the local.conf file along with  
LICENSE_FLAG_WHITELIST = 
" commercial_libav commercial_x264 commercial"
Apart from that Firefox is able to compile and it’s been added to the image. 
Can somebody tell me what is causing this issue.

Thanks,
Best Regards
Kamal Pandey
Junior Software Engineer
[ifm_logo_sqrs]ifm engineering pvt. ltd.
Survey No. 1/10/16, 3rd floor, Above SBI, Bavdhan Branch, N.D.A. Road, Bavdhan, 
Pune, India - 411021 | Web: www.ifm.com | Phone: 
+91-20-22951910 Extn:215 | CIN: U29213PN2010FTC13676

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] bitbake firefox using meta-browser layer

[Pandey, Kamal]

I was trying to compile the Firefox browser for a custom embedded device. But 
it is falling giving the following error:

cd 
/home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/firefox-52.9.0esr/firefox-build-dir
| 
/home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/firefox-52.9.0esr/configure
 --target=aarch64-pdm3-linux --host=x86_64-linux 
--with-toolchain-prefix=aarch64-pdm3-linux- --build=x86_64-linux --prefix=/usr
| Reexecuting in the virtualenv
| Adding configure options from 
/home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/mozconfig
|   --enable-application=browser
|   --target=aarch64-pdm3-linux
|   --prefix=/usr
|   --enable-application=browser
|   --enable-official-branding
|   --disable-elf-hack
|   --disable-gold
|   --disable-strip
|   --disable-install-strip
|   --with-system-nss
|   --with-system-nspr
|   --with-system-zlib
|   --with-system-bz2
|   --with-system-libevent
|   --with-system-libvpx
|   --with-system-icu
|   --enable-system-ffi
|   --enable-system-pixman
|   --enable-startup-notification
|   --enable-pulseaudio
|   --disable-tests
|   --disable-necko-wifi
|   --disable-gconf
|   --disable-crashreporter
|   --disable-updater
|   --disable-debug-symbols
| checking for a shell... 
/home/iepl/work/yocto_build/poky/build/tmp/hosttools/sh
| checking for host system type... x86_64-pc-linux-gnu
| checking for target system type... aarch64-pdm3-linux-gnu
| Traceback (most recent call last):
|   File 
"/home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/firefox-52.9.0esr/configure.py",
 line 107, in 
| sys.exit(main(sys.argv))
|   File 
"/home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/firefox-52.9.0esr/configure.py",
 line 26, in main
| sandbox.run(os.path.join(os.path.dirname(__file__), 'moz.configure'))
|   File 
"/home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/firefox-52.9.0esr/python/mozbuild/mozbuild/configure/__init__.py",
 line 359, in run
| raise InvalidOptionError('Unknown option: %s' % without_value)
| mozbuild.configure.options.InvalidOptionError: Unknown option: --build
| *** Fix above errors and then restart with\
|"make -f client.mk build"
| client.mk:375: recipe for target 'configure' failed
| make: *** [configure] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at 
/home/iepl/work/yocto_build/poky/build/tmp/work/aarch64-pdm3-linux/firefox/52.9.0esr-r0/temp/log.do_configure.5847)
ERROR: Task 
(/home/iepl/work/yocto_build/meta-browser/recipes-browser/firefox/firefox_52.9.0esr.bb:do_configure)
 failed with exit code '1'

Can anybody provide me a solution or at least a  hint, so that I can move 
forward.

Best Regards
Kamal Pandey
Junior Software Engineer
[ifm_logo_sqrs]ifm engineering pvt. ltd.
Survey No. 1/10/16, 3rd floor, Above SBI, Bavdhan Branch, N.D.A. Road, Bavdhan, 
Pune, India - 411021 | Web: www.ifm.com | Phone: 
+91-20-22951910 Extn:215 | CIN: U29213PN2010FTC13676

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto