[yocto] Raspberry pi with Yocto os sd card is not working with Raspbian os sd card

[AKASH BHARDWAJ]

Few months ago,I built an custom image for Raspberrypi using Yocto
Project,flashed it in a sd card and was able to boot
raspberrypi.Presently,I am trying to use  a different sd card with raspbian
os in same Raspberrypi.But it is not able to boot Raspberrypi.How can I
rectify this problem?This is my code which I used few years back to
generate yocto image.










PACKAGE_CLASSES ?= "package_rpm package_deb"
>
>
> EXTRA_IMAGE_FEATURES ?= "debug-tweaks dbg-pkgs dev-pkgs tools-sdk
> tools-debug eclipse-debug "
>
>
> USER_CLASSES ?= "buildstats image-mklibs image-prelink"
>
>
>
>
> BB_DISKMON_DIRS ??= "\
> STOPTASKS,${TMPDIR},1G,100K \
> STOPTASKS,${DL_DIR},1G,100K \
> STOPTASKS,${SSTATE_DIR},1G,100K \
> STOPTASKS,/tmp,100M,100K \
> ABORT,${TMPDIR},100M,1K \
> ABORT,${DL_DIR},100M,1K \
> ABORT,${SSTATE_DIR},100M,1K \
> ABORT,/tmp,10M,1K"
>
>
>
>
>
> CONF_VERSION = "1"
> MACHINE = "raspberrypi3"
> PREFERRED_VERSION_linux-raspberrypi = "4.%"
> DISTRO_FEATURES_remove = "x11 wayland"
> DISTRO_FEATURES_append = " systemd"
> VIRTUAL-RUNTIME_init_manager = "systemd"
> IMAGE_INSTALL_append = " git apt dpkg opkg rpm sudo wiringpi wiringpi-dev
> connman connman-client tzdata i2c-tools i2c-tools-dev glibc-utils rpm
> dhcp-server bluez5 python-smbus bridge-utils hostapd apache2 openvpn
> iptables nano"
> IMAGE_INSTALL += "wiringpi"
> ENABLE_UART="1"
> ENABLE_SPI_BUS= "1"
> ENABLE_I2C = "1"
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Using multilib to build 32-bit glibc on 64-bit target platform

[Nicholas Tsirakis]

Hello,

I'm having trouble understanding the proper usage of multilib within the
Yocto project. I've read through Yocto's documentation, but I think I am
missing something crucial. Here are the steps I've taken:

1. Added the following to my local.conf:
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

2. Attempted to build lib32-glibc with bitbake. Received the following
errors for lib32-glib-initial (shortened for brevity):

| :10:36: error: 'REG_RBP' undeclared (first use in this function)
| :9:26: note: in expansion of macro 'ucontext'
| :10:20: note: in expansion of macro 'mcontext'
| :11:61: note: in expansion of macro 'mreg'
| :10:36: note: each undeclared identifier is reported only once for
each function it appears in
| :9:26: note: in expansion of macro 'ucontext'
| :10:20: note: in expansion of macro 'mcontext'
| :11:61: note: in expansion of macro 'mreg'
| :10:36: error: 'REG_RSP' undeclared (first use in this function)
| :9:26: note: in expansion of macro 'ucontext'
| :10:20: note: in expansion of macro 'mcontext'
| :12:61: note: in expansion of macro 'mreg'
...
| :5:73: error: 'La_x86_64_xmm' undeclared (first use in this
function)
...
| :10:87: error: invalid use of undefined type 'struct
La_x86_64_regs'
...

3. At this point it appeared to me like it was attempting to build a 64-bit
version of glibc in a 32-bit environment, so I tried building the
lib32-linux-libc-headers by adding the following to its recipe:

do_install_prepend() {
if [ "${MLPREFIX}" == "lib32-" ]; then
ARCH="x86"
fi
}

This was more a shot in the dark than anything else and still yielded the
same result. Can someone clear up the proper usage of multilib and tell me
if I'm doing something wrong? Please note that my project currently uses
OE's pyro branches.

Thank you for your time.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

[Jolley, Stephen K]

All,



The triage team meets weekly and does its best to handle the bugs reported into 
the Bugzilla. The number of people attending that meeting has fallen, as have 
the number of people available to help fix bugs. One of the things we hear 
users report is they don't know how to help. We (the triage team) are therefore 
going to start reporting out the currently 296 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out 
with these.



Bugs are split into two types, "true bugs" where things don't work as they 
should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", 
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and 
then "2.8".



Please review this link and if a bug is something you would be able to help 
with either take ownership of the bug, or send me 
(stephen.k.jol...@intel.com) an e-mail with 
the bug number you would like and I will assign it to you (please make sure you 
have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

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

Re: [yocto] [PATCH] ref-manual: add EXCLUDE_PACKAGES_FROM_SHLIBS description

[Tim Orling]

Variable documentation is pulled in from:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/documentation.conf

Notably, EXCLUDE_PACKAGES_FROM_SHLIBS is not defined there, which is why it
is not in the generated docs.
On Mon, Dec 10, 2018 at 4:53 AM Oleksii Konoplitskyi 
wrote:

> Some packages containing shared libraries might be registered as shlib
> providers when they shouldn't (for example, the lib is for their private
> use
> and must not generate any dependency).
>
> EXCLUDE_FROM_SHLIBS is targeted at that, but it could be set for entire
> recipe
> only.
>
> Variable EXCLUDE_PACKAGES_FROM_SHLIBS allows to set list of packages
> that are
> not candidates for shlib providers.
>
> Signed-off-by: Oleksii Konoplitskyi 
> 
> ---
>   documentation/ref-manual/ref-variables.xml | 28
> 
>   1 file changed, 28 insertions(+)
>
> diff --git a/documentation/ref-manual/ref-variables.xml
> b/documentation/ref-manual/ref-variables.xml
> index 595f2db..98d3f86 100644
> --- a/documentation/ref-manual/ref-variables.xml
> +++ b/documentation/ref-manual/ref-variables.xml
> @@ -4289,6 +4289,34 @@
>   
>   
>
> +
> id='var-EXCLUDE_PACKAGES_FROM_SHLIBS'>EXCLUDE_PACKAGES_FROM_SHLIBS
> +
> +EXCLUDE_PACKAGES_FROM_SHLIBS[doc] = "Causes the
> OpenEmbedded build system's shared libraries resolver to exclude
> packages when scanning for shared libraries."
> +
> +
> +
> +
> +Triggers the OpenEmbedded build system's shared
> libraries
> +resolver to exclude packages when scanning for
> +shared libraries.
> +The
> EXCLUDE_PACKAGES_FROM_SHLIBS variable is
> +similar to the
> +
> linkend='var-EXCLUDE_FROM_SHLIBS'>EXCLUDE_FROM_SHLIBS
> +variable, which excludes all the packages provided
> by recipe
> +and not excludes particular package.
> +
> +
> +
> +Use the
> + EXCLUDE_PACKAGES_FROM_SHLIBS variable as a list
> of packages that
> +are not candidates for shared libraries providers:
> +
> + EXCLUDE_PACKAGES_FROM_SHLIBS += "glibc-ptest glibc-dev"
> +
> +
> +
> +
> +
>id='var-EXCLUDE_FROM_WORLD'>EXCLUDE_FROM_WORLD
>   
>   EXCLUDE_FROM_WORLD[doc] = "Directs BitBake to exclude
> a recipe from world builds (i.e. bitbake world)."
>
>
> --
> 2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] FILESYSTEM_PERMS_TABLE / fs-perms.txt

[Mark Hatle]

On 12/10/18 4:14 AM, madoga wrote:
>> On 12/5/18 11:12 AM, madoga wrote:
>>
>>> Hello List,
>>> I am trying to configure my entire filesystem by using 
>>> FILESYSTEM_PERMS_TABLES
>>> variable pointing to my custom fs-perms.txt, but it does not work. While I
>>> debugged package.bbclass looking for any error or failure, I found something
>>> strange with os.chmod & os.lchown methods (at function fix_perms):
>>> # Fix the permission, owner and group of path
>>> def fix_perms(path, mode, uid, gid, dir):
>>> if mode and not os.path.islink(path):
>>> #bb.note("Fixup Perms: chmod 0%o %s" % (mode, dir))
>>> os.chmod(path, mode)
>>> # -1 is a special value that means don't change the uid/gid
>>> # if they are BOTH -1, don't bother to lchown
>>> if not (uid == -1 and gid == -1):
>>> #bb.note("Fixup Perms: lchown %d:%d %s" % (uid, gid, dir))
>>> os.lchown(path, uid, gid)
>>> I have hardcoded mode variable to “0333”, just for testing: os.chmod(path,
>>> 0o333)and I have seen that permissions were been configured into a “0711”. 
>>> Also
>>> I am going to ask about os.lchown, due to my filesystem is still been owned 
>>> by
>>> my user and my group.
>>> Does anyone have an idea about what is going on? Has somebody have the same
>>> problem?
>>
>> The commands run under the pseudo environment. Pseudo captures these commands
>> and stores them in a database it can 'replay' at any time.
>>
>> It only make them in the actual filesystem if permitted by the host.
>>
>> You must look at the filesystem results in the live system (running pseudo) 
>> or
>> in the results of the build -- otherwise what you are looking at is not 
>> valid.
>>
>> (BTW this is the reason that the commended code was left in that function. In
>> case something is wrong, just remove the comments and you'll get notes on 
>> what
>> it is doing to help debug. This shouldn't be necessary unless you are
>> developing the function itself.. but that is why they are there.)
>>
> 
> Thank you for your reply Mark!

pseudo replaces fakeroot.  Fakeroot can't capture some of the items that are
needed [and a few other reasons).

> Does the pseudo environment allow to set the entire rootfs by using fakeroot? 
> Perhaps this is not the right way to make it, I am not pretty sure about 
> that. I would like to obtain my rfs with a concrete permissions when bitbake 
> finishes, folders, executables... Is there another/better way to accomplish?

psuedo is just a LD_PRELOAD library that is connected to a database that
captures permissions changes to files..

> About debbuging bb.notes, I have already removed the comments and everything 
> seems working OK.

This tells me that it's likely working properly and you are not in the pseudo
environment.  You need to be in that loaded environment with the correct
database attached to look at the set permissions.  Any task in the system
prefixed by 'fakeroot' will do this for you.

--Mark

> Best Regards,
> Mario
> 
>> --Mark
>>
>>> Thank you
>>> Best Regards,
>>> Mario
> 
> 

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

Re: [yocto] nativesdk-packagegroup-sdk-host not found. Why?

[Mauro Ziliani]

Solved.

Th nativesdk-package-sdk-host was not found because in conf/local.conf I 
set DPKG_ARCH="armhf".


Erasing this setup all works.


Mauro


Il 10/12/18 08:13, Mauro Ziliani ha scritto:

Hi all.

I try to rebuild meta-toolchain-qt5 and meta-toolchain, but bitbake 
tells me the it can found nativesdk-packagegroup-sdk-host and on 
populate_sdk task.


Why?


Which configuration variables drive the production of the recipe 
nativesdk-packagegroup-sdk-host.bb?



Thanks all


Mauro


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

[yocto] Yocto Development with Windows

[Shantanoo Desai]

Hello All,

 

I was looking to get some information about using Windows for Yocto. I have
seen some mention of Docker to use Yocto however I am completely unaware if
there are already manuals or so available for the same.

 

Particularly, I was looking for Embedded Applications that are developed in
Windows and if they can be ported to Target boards.

 

Any help would be appreciated

 

Regards,

 

Shan

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

[yocto] [PATCH] ref-manual: add EXCLUDE_PACKAGES_FROM_SHLIBS description

[Oleksii Konoplitskyi]

Some packages containing shared libraries might be registered as shlib
providers when they shouldn't (for example, the lib is for their private use
and must not generate any dependency).

EXCLUDE_FROM_SHLIBS is targeted at that, but it could be set for entire
recipe
only.

Variable EXCLUDE_PACKAGES_FROM_SHLIBS allows to set list of packages
that are
not candidates for shlib providers.

Signed-off-by:OleksiiKonoplitskyi
---
  documentation/ref-manual/ref-variables.xml | 28

  1 file changed, 28 insertions(+)

diff --git a/documentation/ref-manual/ref-variables.xml
b/documentation/ref-manual/ref-variables.xml
index 595f2db..98d3f86 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -4289,6 +4289,34 @@



+ EXCLUDE_PACKAGES_FROM_SHLIBS
+ 
+ EXCLUDE_PACKAGES_FROM_SHLIBS[doc] = "Causes the
OpenEmbedded build system's shared libraries resolver to exclude
packages when scanning for shared libraries."
+ 
+ 
+ 
+
+ Triggers the OpenEmbedded build system's shared
libraries
+ resolver to exclude packages when scanning for
+ shared libraries.
+ The
EXCLUDE_PACKAGES_FROM_SHLIBS variable is
+ similar to the
+ EXCLUDE_FROM_SHLIBS
+ variable, which excludes all the packages provided
by recipe
+ and not excludes particular package.
+ 
+
+ 
+ Use the
+ EXCLUDE_PACKAGES_FROM_SHLIBS variable as a list
of packages that
+ are not candidates for shared libraries providers:
+ 
+ EXCLUDE_PACKAGES_FROM_SHLIBS += "glibc-ptest glibc-dev"
+ 
+ 
+ 
+ 
+
EXCLUDE_FROM_WORLD

EXCLUDE_FROM_WORLD[doc] = "Directs BitBake to exclude
a recipe from world builds (i.e. bitbake world)."
--
2.7.4

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

Re: [yocto] [PATCH] meta-yocto-bsp: beaglebone-yocto.conf: support 8250 serial driver

[richard . purdie]

On Mon, 2018-12-10 at 12:01 +0100, Heiko Schocher wrote:
> Hello all,
> 
> Am 13.11.2018 um 08:06 schrieb Heiko Schocher:
> > it is possible to use the beagleboneblack with the 8250 serial
> > driver or with the deprecated omap serial driver.
> > 
> > Unfortunately serial console get different names (ttyS0 with
> > 8250 driver and ttyO0 with omap driver)
> > 
> > So set SERIAL_CONSOLES to
> > SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0"
> > 
> > (intentionally with "?=" so it is overwriteable)
> > and activate
> > 
> > SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
> > 
> > with that on the first boot the correct value is picked up
> > automatically.
> > 
> > Signed-off-by: Heiko Schocher 
> > ---
> > 
> >   meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 3 ++-
> >   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> gentle ping. Any issues with this patch?

No, it merged already:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=81e48b24dd9c97a3bdda3b4140f8e2bda29d24da

Cheers,

Richard

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

Re: [yocto] [PATCH] meta-yocto-bsp: beaglebone-yocto.conf: support 8250 serial driver

[Heiko Schocher]

Hello all,

Am 13.11.2018 um 08:06 schrieb Heiko Schocher:

it is possible to use the beagleboneblack with the 8250 serial
driver or with the deprecated omap serial driver.

Unfortunately serial console get different names (ttyS0 with
8250 driver and ttyO0 with omap driver)

So set SERIAL_CONSOLES to
SERIAL_CONSOLES ?= "115200;ttyS0 115200;ttyO0"

(intentionally with "?=" so it is overwriteable)
and activate

SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"

with that on the first boot the correct value is picked up
automatically.

Signed-off-by: Heiko Schocher 
---

  meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)


gentle ping. Any issues with this patch?

Thanks!

bye,
Heiko
--
DENX Software Engineering GmbH,  Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: h...@denx.de
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [OE-core] FILESYSTEM_PERMS_TABLE / fs-perms.txt

[madoga]

> On 12/5/18 11:12 AM, madoga wrote:
>
> > Hello List,
> > I am trying to configure my entire filesystem by using 
> > FILESYSTEM_PERMS_TABLES
> > variable pointing to my custom fs-perms.txt, but it does not work. While I
> > debugged package.bbclass looking for any error or failure, I found something
> > strange with os.chmod & os.lchown methods (at function fix_perms):
> > # Fix the permission, owner and group of path
> > def fix_perms(path, mode, uid, gid, dir):
> > if mode and not os.path.islink(path):
> > #bb.note("Fixup Perms: chmod 0%o %s" % (mode, dir))
> > os.chmod(path, mode)
> > # -1 is a special value that means don't change the uid/gid
> > # if they are BOTH -1, don't bother to lchown
> > if not (uid == -1 and gid == -1):
> > #bb.note("Fixup Perms: lchown %d:%d %s" % (uid, gid, dir))
> > os.lchown(path, uid, gid)
> > I have hardcoded mode variable to “0333”, just for testing: os.chmod(path,
> > 0o333)and I have seen that permissions were been configured into a “0711”. 
> > Also
> > I am going to ask about os.lchown, due to my filesystem is still been owned 
> > by
> > my user and my group.
> > Does anyone have an idea about what is going on? Has somebody have the same
> > problem?
>
> The commands run under the pseudo environment. Pseudo captures these commands
> and stores them in a database it can 'replay' at any time.
>
> It only make them in the actual filesystem if permitted by the host.
>
> You must look at the filesystem results in the live system (running pseudo) or
> in the results of the build -- otherwise what you are looking at is not valid.
>
> (BTW this is the reason that the commended code was left in that function. In
> case something is wrong, just remove the comments and you'll get notes on what
> it is doing to help debug. This shouldn't be necessary unless you are
> developing the function itself.. but that is why they are there.)
>

Thank you for your reply Mark!
Does the pseudo environment allow to set the entire rootfs by using fakeroot? 
Perhaps this is not the right way to make it, I am not pretty sure about that. 
I would like to obtain my rfs with a concrete permissions when bitbake 
finishes, folders, executables... Is there another/better way to accomplish?

About debbuging bb.notes, I have already removed the comments and everything 
seems working OK.

Best Regards,
Mario

> --Mark
>
> > Thank you
> > Best Regards,
> > Mario


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

[yocto] Some questions about mdns library (sumo branch, but also master)

[Stefano Cappa]

Hi!
I'm trying to use mdns library (
https://layers.openembedded.org/layerindex/recipe/72471/), however I have
some questions.

1) what is the purpose of "
files/0001-nss_mdns-Do-not-include-nss.h-when-libc-glibc.patch
"?
Is it really necessary?
2) Is it possibile to update it to the latest version in open embedded? I
updated to version 8xx.x.x and it seems to be ok, but I prefer to know if
there is a reason why it is still at 7xx.x.x.
3) Inside the mdns receipe there is a reference to "libnss_mdns" but it
seems fixed to version 0.2. On open embedded there is version 0.10. To use
mdns should I install libnss 0.10?
4) How does mdns library manage IPv4 Link local? Is there something to
configure or packages to add to receive a link local address after 60
seconds?

I'm asking about mdns and not avahi, because I want to use the official
Apple library instead of Avahi. Do you have other additional suggestions
about this topic?

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